300
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
informations about css
Tag: 2017 source edit |
Eric.seigne (talk | contribs) (informations about css) Tag: 2017 source edit |
||
| Line 420: | Line 420: | ||
There is a ton of other reasons to not use an external template system and all arguments to use them are also the best argument to use HTML/PHP as our template system. We just ask to keep separation between '''Controllers''' (the first section of PHP pages juste after the /* Action */ line), and the '''Views''', the second section after the /* View */ comment). | There is a ton of other reasons to not use an external template system and all arguments to use them are also the best argument to use HTML/PHP as our template system. We just ask to keep separation between '''Controllers''' (the first section of PHP pages juste after the /* Action */ line), and the '''Views''', the second section after the /* View */ comment). | ||
=CSS norms= | |||
==Syntax rules== | |||
There is NO syntax rules or norms for CSS. During Dolibarr Devcamp 2024/06 (Montpellier) a collective proposition was made to respect classes name from tailwindcss. | |||
The objective is not to include tailwindcss into Dolibarr but to use syntax and classes norms issued from tailwindcss. | |||
PR: (link to PR to become) | |||
=Dolibarr norms and code skeleton= | =Dolibarr norms and code skeleton= | ||