Ability use Hextra in multiple sub-directories

[fmunteanu]

Hi @imfing,

I've struggling to find a proper solution for my problem, without much success. My goal is to use Hextra with the following design pattern:

• /docs - website frontpage
• /docs/projectA - website project A
• /docs /projectB - website project B

Each project will have different menus and must also a dedicated hextra-home page. To understand better what I mean, please visit the currently deployed website. The only way I managed to achieve the expected results, was by building Hextra for each directory, which introduces files duplication into /public directory, icons, sitemap, etc.

See my repository files structure, for more details:

.
├── docs -- WEBSITE FRONTPAGE
│   ├── content
│   ├── resources
│   │   └── _gen
│   └── static
│       └── images
├── global -- COMMON FILES, used on both frontpage and several to be added projects
│   ├── i18n
│   ├── layouts
│   │   ├── partials
│   │   └── shortcodes
│   └── static
│       └── images
├── k3s-cluster -- FIRST PROJECT
│   ├── content
│   │   ├── tutorials
│   │   └── wiki
│   ├── resources
│   │   └── _gen
│   └── static
│       └── images
└── public -- WEBSITE FRONTPAGE
    ├── categories
    ├── css
    │   └── compiled
    ├── images
    ├── js
    ├── k3s-cluster -- FIRST PROJECT
    │   ├── tutorials
    │   └── wiki
    ├── lib
    │   └── flexsearch
    └── tags

Related to hextra-home page into sub-directories, I could customize the single.html file, but that will block me to use it on sub-directories. So I need to be able to use the actual hextra-home template into each sub-directory.

Another issue I'm facing is the ability to have specific menus, per sub-directory. Check the deployed website, you can see specific menus defined. In real like, with Hugo, all you have to do is set the module mounts into /docs and everything works. This solution does not applies to me, unfortunately.

I'm wondering if you have any suggestions, I'm trying to find a proper solution for this, for over a week.

[imfing]

To be honest, I don't have much experience with multi-directory setup.
I would recommend ask this in Hugo forum which is a better place for general Hugo setup questions.

[fmunteanu]

No worries, I already did. I was hoping you might have some insight, since you know the theme well.

[fmunteanu]

@imfing I made some progress, see this PR with the related fixes. If I create the /layouts/docs/hextra-home.html, the page will render, but for some reason, I cannot disable the sidebar with exclude: true. If you could provide some guidance with this issue, it will be much appreciated.

Also, the menus show correctly into sidebar, but they don't load into top navbar. I would expect to have the top bar title and menus loaded from /k3s-cluster/hugo.yaml, but instead, they are loaded from /docs/hugo.yaml:

[fmunteanu]

@imfing looking at https://github.com/imfing/hextra/blob/main/layouts/hextra-home.html, I see you defined in there the following condition:

{{ partial "sidebar.html" (dict "context" . "disableSidebar" true) }}

I don't understand where the context dictionary is used/defined, so the above settings are taken into account.

[fmunteanu]

@imfing I would appreciate if you can take few minutes of your time to help me understand how I disable the sidebar. I don't understand how this is done for hextra-home.html.

[imfing]

you can just remove the line containing the sidebar

[fmunteanu]

@imfing I'm going to push a PR that fixes the issue the correct way, without removing anything from your templates. Also, you're hardcoding the .Site.Menus.main map, which takes away the ability to add other menus, as per Hugo documentation.

I'll add a condition from Hugo documentation into navbar.html, something like:

{{- $menu := .Site.Params.sectionPagesMenu | default "main" }}

Also, you use menu: instead of menus: in your deployment, see above documentation.

[fmunteanu]

@imfing I created #406.