Assets File Structure

[glassjaw]

I have a pretty big site I'm migrating to docmd, and as part of the migration I wanted to organize all assets and images to match the file tree of the site itself. However, all links viewed directly from disk now append /index.html to the end, breaking images and asset downloads.

Does docmd only support files in /assets/ and images in /assets/images/ without any subdirectories?

[mgks]

No, docmd doesn't restrict assets to /assets/ or /assets/images/. You can place assets anywhere in your documentation. The issue was a bug in offline builds that incorrectly treated some asset files as pages and appended /index.html to their paths.

This is fixed in 0.8.16. Non-HTML assets (images, PDFs, JSON, etc.) are now left untouched regardless of where they're located.

More generally, I've realised offline builds deserve the same level of attention as regular builds, so you'll see continued improvements in that area over the coming releases.

Give 0.8.16 a try, I hope it resolves the issues you were seeing with --offline as well. If anything still isn't working as expected, let me know and I'll take a look.

[mgks]

@glassjaw if this issue was still persistent in 0.8.16, update your current setup to use the latest docmd update 0.8.17.

[mgks]

@glassjaw have you tried it? You can upgrade directly to 0.9.0 if you haven't yet.