Repository navigation
docs: fix the template override path and the fallback order - #68
Merged
Merged
Conversation
The README told users to uncomment `meta: _metatags.html.twig`, but the
lines shipped in config.yaml read `meta: _partials/_metatags.html.twig`.
Users who followed both got a "template not found" error. Both now use
`_metatags.html.twig`, so the copy can sit in the root of the theme. The
path is resolved relative to the theme folder, and the README and a new
comment in config.yaml give a subfolder example.
The fallback order ("override, SEO field, record fields, defaults") was
only true for title and description. Each step now says which values it
applies to, and the README lists the final fallbacks after the `default`
values and the special titles on listing and taxonomy pages.
Vondry
force-pushed
the
docs/readme-accuracy
branch
from
October 24, 2026 07:47
7df4680 to
e28565d
Compare
This was referenced Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two fixes where the README didn't match the code. This PR changes the README and a comment in
config/config.yaml. There are no code changes.Changes
meta: _metatags.html.twig, but the lines thatconfig/config.yamlships readmeta: _partials/_metatags.html.twig. Users who followed both got a "template not found" error. Both now use_metatags.html.twig, so the copy can sit in the root of the theme and nobody has to create a_partialsfolder. A new comment inconfig.yamland a sentence in the README explain that the path is relative to the theme folder, with a subfolder example (partials/seo/_metatags.html.twig).title()anddescription(). The README now says which values each step applies to:image;title,descriptionandimagefall back to the record's own fields (fields.keywordsisn't used for output);defaultvalues, the title falls back tositename, the description topayoff,canonicalto Bolt's canonical URL,ogtypetowebsite,robotstoindex, follow, andimageto the record's image as Bolt finds it;Existing sites keep their copy of
appolo-boltseo.yaml, because Bolt never updates it. The changed comment only affects new installs.Verified
Seo::title(),description(),keywords(),image(),robots(),ogtype()andcanonical().theme/template_directory, if set) to Twig's template paths inTwigAwareController::setTwigLoader(). Sotemplates.metais resolved relative to the theme, and a bare filename is found in the theme root.meta: partials/seo/_metatags.html.twig, with the file atpublic/theme/<theme>/partials/seo/_metatags.html.twig. This confirms that a subfolder works.config/config.yamlstill parses, andtemplatesstays commented out by default.