CSSGrid
(Updated Edited template to July 12, 2025.)
No edit summary
 
Line 8: Line 8:
Using CSSGrid has advantages since we know exactly where we place content and it is not dependent on the environment as Bootstrap is.
Using CSSGrid has advantages since we know exactly where we place content and it is not dependent on the environment as Bootstrap is.


If you do generic [[EXT Components|components]], you do not need to know the surroundings of your HTML snippet - placement will be managed by the CSSGrid values read from the ViewModel.
If you do generic [[Documentation:EXT Components|components]], you do not need to know the surroundings of your HTML snippet - placement will be managed by the CSSGrid values read from the ViewModel.
[[Category:CSS]]
[[Category:CSS]]
{{Edited|July|12|2025}}
{{Edited|July|12|2025}}

Latest revision as of 05:07, 23 January 2025

This page was created by Hans.karlsen@mdriven.net on 2018-10-10. Last edited by Stephanie@mdriven.net on 2025-01-23.

If you place a tagged value on the ViewModel level CSSGrid=true, we will render HTML with CSSGrid instead of Bootstrap.

If the TurnkeySettings file sees:

<UseCSSGridByDefault>True</UseCSSGridByDefault>

We will always render with CSSGrid unless you explicitly say CSSGrid=false.

Using CSSGrid has advantages since we know exactly where we place content and it is not dependent on the environment as Bootstrap is.

If you do generic components, you do not need to know the surroundings of your HTML snippet - placement will be managed by the CSSGrid values read from the ViewModel.