Allowing categorisation of files under pages into sub-directories

[ziadbkh]

Maybe it is useful to have subdirectories under pages directories and then the user can redirect to these pages as base_url/subdirectory/page_name. It does not work like this now, but it works with the full link base_url/pages/subdirectory/page_name

[supernord]

hi @ziadbkh I think this is already possible. @bedroesb, please let me know if the below isn't correct 😄 The config file and pages directory for the [ELIXIR toolkit theme example)(https://elixir-belgium.github.io/elixir-toolkit-theme/):

• uses sub-directories within the pages directory
• refers to its pages directory within the config.yml file
• includes this in the main.yml sidebar file without referring to the directory structure, and
• "pages" does not appear in the urls, for example see https://elixir-belgium.github.io/elixir-toolkit-theme/getting_started

as long as this matches to our implementation of the theme, then it should work?

what about if we remove the pages/directory bit for each of the pages in the main.yml? here: https://github.com/AustralianBioCommons/tower/blob/main/_data/sidebars/main.yml

[bedroesb]

@supernord Correct, this is possible. The most robust way is to serve the subfolders in the root of the project instead of the pages directory. This will also create the most robust urls (who work with and without trailing backslash).

An example website where this is in use is https://www.infectious-diseases-toolkit.org/ with in its config file:

permalink: /:categories/:year/:month/:day/:title

with having index files in the main sections of the website: https://github.com/elixir-europe/infectious-diseases-toolkit/tree/main/socioeconomic-data.

The only thing I want to make aware of is the following:

• The theme itself makes for every link/image use of the relative_url function so having these more verbose urls are not a problem.
• in RDMkit we make use of folder hierarchy for the markdown files, but not for the url structure because it adds complexity in linking towards the pages, now they use the filename of the markdown without worrying about absolute urls not working on their fork. Disadvantage: all md files need to be unique
• Be aware that images/links used in the md files will need to have a relative path in order to work on forks (githubdomainfork.io/repo/page has the problem that /page root does not work, and page will as link will not work from a subdirectory because it will try to access subdirectory/page ). This means you need to add relative_url all the paths. With images it can be prevented by using the {% include image.html %} snippet, but with links it will be sucky...