Feedback: Hugo with partial content in modules vs. Dashboard

[davidsneighbour]

Hi. I have a Hugo website and recently moved out a certain content folder (not ALL content) into a module where it is mounted via the following (config/_default/module.toml):

[[mounts]]
source = "documentation/"
target = "content/components"

The folder documentation in that module is mapped into my website's content/components folder, and Hugo does its thing with that.

What is working:

• Hugo - the folder's contents appear on the website
• single content file editing with Frontmatter - the frontmatter sidebar is there and working

What is not working:

• the posts/pages from the mounted folder do not appear on the dashboard.

My configuration is scattered into folders, and the content folder config is this:

{
  "$schema": "https://frontmatter.codes/config/content.pagefolders.schema.json",
  "title": "Components",
  "path": "[[workspace]]/../hugo-modules/documentation",
  "contentTypes": ["component"]
}

I tried various path values ([[workspace]]/documentation, [[workspace]]/content/components, etc) with no luck.

My workspace looks like this:

|
|-kollitsch.dev (the website folder, also containing the workspace configuration)
|-hugo-modules (folder with the module(s)
|-hugo-theme (another module with the theme)

To test this you can clone the three repos into a folder next to each other, then open the workspace inside of kollitsch.dev.

It appears that [[workspace]] is relative to the location where the configuration is saved, not the "actual" workspace (one level above).

Is there any way to configure the content module into the dashboard using a relative path?

[estruyf]

Hi @davidsneighbour, FM did not support this yet as it uses the workspace folder in which you added the frontmatter.json file.

A change is coming up to locate files outside the workspace folder. So if you use "[[workspace]]/../hugo-modules/documentation", it should correctly concat the file path to the absolute folder path.

[estruyf]

I pushed out an update, let me know if it works in the latest beta.

[davidsneighbour]

I will need to verify if I messed up my configuration, but it now shows a "no markdown to
show" error.

[estruyf]

This is how it shows up on my end (filter on components).

I didn't make any configuration change. I have cloned the main and modules project. Created a workspace with both projects and loaded the dashboard.

[estruyf]

It seems to be an issue on Windows. 🫣

[davidsneighbour]

No, on Linux then ;) I am on Ubuntu.

[estruyf]

Could you test out the latest beta to check if that would also fix it on your end? Version v8.5.5519848.

[davidsneighbour]

Perfect, all working :)