@StefanoCecere I could accept a compromise like that too. I’ve thought about the viability of storing application data in commented HTML, that Obsidian would automatically hide. This seems like it would have side effects though. A plugin for numbering files with a suffix would be alright too.
@Dor I hadn’t thought about setting up a specific outline file. That might work for smaller pieces that you need to compose and compile, but I feel it could get pretty messy with the kind of worldbuilding and tracking that I tend to do. A writer’s plugin would be pretty sweet though.
@Pda0 Yep, WYSIWYG is on the roadmap. I still can’t wait though! As for the subpages, the problem is mostly an organizational one. Say I have a “locations” directory for some sort of fictional project. Within that, I have a page for each town. But then I would also wish to have pages “underneath” the towns’, for characters, specific buildings, and other granular details. The two options would be to create a separate folder elsewhere, with all relevant pages linked, and trust that nothing is forgotten or lost. Or each town page could have its own corresponding folder, and Obsidian would display the two as a single object. This would really be just a small change to the UI, but it would emulate the functionality of a node-based app.