Skip to content
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

Use awesome-pages plugin for easier directory pages configuration #243

Open
alyssadai opened this issue Nov 19, 2024 · 0 comments
Open

Use awesome-pages plugin for easier directory pages configuration #243

alyssadai opened this issue Nov 19, 2024 · 0 comments

Comments

@alyssadai
Copy link
Contributor

Description

When we want to organize docs pages in subdirectories (paths), mkdocs doesn't have a built-in way of defining directories that a set of pages should live under, and instead you have to specify the entire path to each .md file in mkdocs.yml, e.g.:

    - Running cohort queries:
        - Search the public nodes: "user_guide/public_nodes.md"
        - How to use the query tool: "user_guide/query_tool.md"
        - Querying the API directly: "user_guide/api.md"

This quickly gets tedious if you have a lot of docs pages or want a slightly more nested docs structure.

The awesome-pages plugin (the top navigation plugin for mkdocs, see https://github.com/mkdocs/catalog?tab=readme-ov-file#-navigation--page-building) helps solve this problem by allowing you to define the docs structure in a .pages file in your docs directory instead of mkdocs.yml. Here you can specify the name / order / etc. of both files and directories, using the same nav attribute (by default, it should include all files in a directory you specify).

If desired, you can then use .pages in a subdirectory to control the order/names of files in just those subdirectory.

This could make it more intuitive to organize the docs, as each directory could have its own .pages, and also minimizes repetition.

Relevant documentation pages

No response

Additional details

No response

@alyssadai alyssadai self-assigned this Nov 19, 2024
@alyssadai alyssadai added the flag:schedule Flag issue that should go on the roadmap or backlog. label Nov 19, 2024
@alyssadai alyssadai removed their assignment Nov 19, 2024
@surchs surchs moved this to Backlog in Neurobagel Nov 19, 2024
@surchs surchs removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Nov 19, 2024
@surchs surchs added the flag:schedule Flag issue that should go on the roadmap or backlog. label Dec 12, 2024
@surchs surchs removed the status in Neurobagel Dec 12, 2024
@rmanaem rmanaem moved this to Backlog in Neurobagel Jan 6, 2025
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 6, 2025
@alyssadai alyssadai moved this from Backlog to Specify - Done in Neurobagel Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Specify - Done
Development

No branches or pull requests

3 participants