Reference
FAQ
Common questions about DocSteer.
Short answers to what people ask most. Can’t find yours? Press / to search the whole site, or open an issue.
Licence and cost
Is it really free?
Setup and hosting
Does it work on GitHub Pages?
Yes. Use the GitHub Actions workflow in Deploying so you get Jekyll 4 and all three plugins. The classic “legacy” Pages build also works if you stick to its allowed plugin list.
Customising
How do I change the font?
How do I add a 7th colour skin?
How do I build a FAQ page like this one?
Set layout: faq on any page and list the questions under a faq: key
in its front matter, each with a q, an a and an optional section.
Answers are Markdown, so code blocks and links work as usual.
For a long list shared across pages, put the same structure in
_data/faq.yml and point at it with faq_data: faq instead.
Troubleshooting
The colours don’t change when I edit _config.yml
Dark mode flashes white on load
Search returns nothing
Something is broken — where do I report it?
Open an issue on the GitHub repository.
About the name
Why “DocSteer”, and how do I pronounce it?
/dɒkˈstɪə/ — dok-STEER, stress on the second syllable, rhyming with beer. Two syllables, not three.
The name is the job description: the sidebar, the search box and the table of contents are all there to steer a reader to the page they actually came for.
A steer is also a young ox. That was not the plan, but as a description of something that hauls a large pile of documentation around without complaining, it is hard to argue with. The full confession is on the home page.