-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Move the Textual FAQ into the main docs #3129
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
Conversation
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.
Don't we need to add faqtory to the (dev) dependencies of Textual, then?
|
Good call; I had thought it was. |
For this to work faqtory needs to be a development dependency of Textual. Textual still maintains support for Python 3.7; faqtory is Python 3.8 or greater. So, for the moment, we're going to cheat a little and make it so that you have to remember to run faqtory to rebuild FAQ.md. All hail the walrus!
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.
Nice
|
I just realised something: rather than have the two different link IDs floating around, I dropped faqtory's slugs from the generated FAQ and leaned into mkdocs-materials' IDs generated from the headers; but now I think about it faqtory and mkdocs-material might not slug the same. I'll make an issue to double-check this tomorrow and I might have to add the faqtory slugs back and we'll just accept the duplication of effort in the page. |
|
Good point! |
|
I'm open to modifying the slug generation in FAQtory to match. |
Implements #3068.