-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate front-matter to nesting #69
Comments
A few examples:
As we are using nesting already for buttons and more complicated variables, we should default to nesting. |
Still needs input from @lauragift21 and @mpourismaiel |
Would be good, if we can pin down the user facing format aka content files, static file usage etc. Then we can already document and users don't have to migrate between changes. Also gives us the ability to refactor internally without affecting the user. |
I like nested format a lot more. It's more readable and much more manageable. |
Yeah I think I agree. Looks cleaner and we make everything more consistent. So if @lauragift21 agrees, that means: |
Sure i agree with the nested convention it looks better. |
Is this a BUG REPORT or FEATURE REQUEST?:
feature
What happened:
Currently we haven't defined the front-matter convention to use.
What you expected to happen:
Either use nested or use flat variables in front-matter.
Anything else we need to know?:
For almost all fragments we use nesting. So that seems to be the one we should go with.
Examples
Flat:
Nested:
The text was updated successfully, but these errors were encountered: