-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create Jekyll project and render FAQs #24
Conversation
The HTML ist just copied from index.html for now. FAQ contents are in faq_contents.md.
To be consistent with /privacy-policy/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow this is pretty much as I imagined, thank you very much!
Also it was super easy to set up locally.
Some new faqs have been merged recently in the other repo, can you add them here as well please?
Also, we have a french translation of the faqs, can we have them here as well? Maybe /faq/fr or something like that?
Without this comment or a leading empty line, the first line is not rendered as headline, dunno why.
Happy to hear that! The english FAQ contents are now updated to the latest version. I've added the french version under |
Thanks! ❤️ |
As started here https://chaos.social/@ConnyDuck/112304265215565337: convert the static website to a Jekyll project so that there is a build step that can render the FAQ to HTML while still being able to author it in Markdown.
I tried to change as little as possible on the rest of the site for now, only what is necessary to add the automatically rendered FAQ page. The new FAQ page at
/faq/
is styled similar to the privacy policy page. On hover, anchor links to individual headlines are shown and point to e.g./faq/#why-is-the-tusky-release-on-f-droid-out-of-date
.The new FAQ page is not linked from the root page yet so that this PR could be merged first to see if the build is working, and publish the new FAQs later.
Let me know where you want to go from here, I'm happy to make more changes but beware I'm not a great designer 😄.