feature: easy adoption of Bridgetown for Obsidian vaults and similar Markdown folders

[brandondrew]

Summary

For many people, a directory full of markdown comes before any thought of Bridgetown. There are undoubtedly many thousands of users of Obsidian, to give just one example. I know less about other apps, but if memory serves me well Notable also stores its files as a directory full of Markdown files.

Rather than asking them to retroactively adopt Bridgetown's directory structure, I think it makes sense to allow Bridgetown to adapt to whatever structure a user already has. Rather than conceive of the main directory as "belonging" to Bridgetown, and the markdown being pushed into a subdirectory like src, I think it makes more sense if we could alternately think of the main directory as "belonging" the the Markdown (and the app that creates it), and for Bridgetown to behave as a guest that is willing to cooperate with whatever structure is needed.

Motivation

It will

• make it much easier to use Bridgetown to publish Obsidian vaults and similar content
• make it easier for non-technical users to adopt Bridgetown
• make the potential pool of users of Bridgetown much larger

Drawbacks

I really can't see any drawbacks.

Unresolved Questions

I don't see any unresolved questions, but ask me any questions you have.

[jaredcwhite]

Related issues: #515 #819