You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frontmatter-pipeline as documented in https://www.bridgetownrb.com/docs/content/front-matter-defaults is a promising bridgtown-property.
However, during experiments with the tailwindcss-based cookie template its behavior was inconsistent.
Its Navbar-design is controlled by some frontmatter-variables.
If I move them from the article-frontmatter-section to _defaults.yml some are recognized, some not.
That leaves me with the choice, not to use this feature at all or to live with the uncertainty, then for unknown reasons, some frontmatter-variables are not suitable as defaults. Sadly, the documentation of this feature does not reflect reality.
My problem: I don't know how to investigate the origin of this inconsistency.
To reproduce:
clone the cookie template
create a _defaults.yml in _src/pages and copy the navbar_*properties from any article file to the yml (adjust for yml-format )
Its not possible to change the label, icon or logo-color using _defaults.yml. That works perfectly in the article-files.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi alltogether
The frontmatter-pipeline as documented in https://www.bridgetownrb.com/docs/content/front-matter-defaults is a promising bridgtown-property.
However, during experiments with the tailwindcss-based cookie template its behavior was inconsistent.
Its Navbar-design is controlled by some frontmatter-variables.
If I move them from the article-frontmatter-section to
_defaults.yml
some are recognized, some not.That leaves me with the choice, not to use this feature at all or to live with the uncertainty, then for unknown reasons, some frontmatter-variables are not suitable as defaults. Sadly, the documentation of this feature does not reflect reality.
My problem: I don't know how to investigate the origin of this inconsistency.
To reproduce:
clone the cookie template
create a _defaults.yml in _src/pages and copy the
navbar_*
properties from any article file to the yml (adjust for yml-format )Its not possible to change the label, icon or logo-color using _defaults.yml. That works perfectly in the article-files.
Beta Was this translation helpful? Give feedback.
All reactions