CERIGO naming conventions

Jul 18, 2017

Naming conventions for global variables in the CERIGO namespace :
~CSS~
.cerigo-element-class
.cerigo-element-class__property
.cerigo-element-class–state
.cerigo-element-class__property–state
~PHP~
$cerigo_element
$cerigo_element__property
$cerigo_element_state
$cerigo_element__property__state
~JS~
cerigoElementVariable
cerigoElementState
Cerigo file headers:
/*¸.·’´¯),ø¤°„°¤ø,¸¸,ø¤°`°¤ø,¸(¯`’·.¸
Cerigo component:
specific component name
`’·.¸_)’°¤ø,¸,ø¤°„°¤ø,¸,ø¤°`(_¸.·’´
*
* == prerequisites/ requirements ==
*
*
* == known issues ==
*
*/
//«»«»«[ major block ] »«»«»//
// sub block
/*¸.·’´¯)¸,ø¤°` CERIGO `°¤ø,¸(¯`’·.¸
vanilla settings for …
`’·.¸_)`°¤ø,¸ v.0.0.1 ¸,ø¤°`(_¸.·’´*/
*
*
* == known issues ==
*
*/
//«»«»«[ major block v0.0.1module version number, etc.
] »«»«»//
// sub block
/*¸.·’´¯)¸,ø¤°` CERIGO `°¤ø,¸(¯`’·.¸
CERIGO import hub …
`’·.¸_)’°¤ø,¸,ø¤°„°¤ø,¸,ø¤°`(_¸.·’´
*
*
* == known issues ==
*
*/
// sub block
@import ‚_filename‘;
/* NO CSS allowed! ONLY imports! */