Error: command error: failed to load modules: failed to apply mounts for project: invalid module config for "project": mount target must be one of: [archetypes assets content data i18n layouts static]
I’m holding out hope that I’ve overlooked something, and there’s still a way to share themes with child projects without having to duplicate them?
Those are valid points! However, it seems those reasons force users into dealing with higher complexity and/or making significant changes to existing projects. This isn’t always desirable. Even though the developers’ intentions are noble, it will create a lot of mess and extra work for projects that currently rely on using symlinks. I believe it wouldn’t cost the Hugo developers anything to just add a --allow-symlinks flag?
Though, I believe many people would appreciate it if you reconsidered. While modules are indeed better, reconfiguring many large projects could be very time-consuming.