Preserve directory organization in exploded markdown content #147
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coulomb/markitect-main#147
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When exploding markdown into a directory tree. I want to preserve the directory organization.
How do I do that? There is no canonical way to do it but several variations will provide specific benefits and drawbacks.
Instead of solving for one special case, the explode implode functions should provide switches to select specific variants.
And they should provide auto detection of how the exploded markdown is orgenized when imploding it using the correct set of switches and the other way around.
As a boundary condition all variations need to preserve all information to enable reversable operations. Even if some feature might not be expressed prominently by an explosion there needs to be a mechanism to keep the original information content.
For the current mode of explosion, the order of chapters is not preserved. Therefor a manifest.md file documenting the order needs to be generated allowing the implosion function to generate the correct ordering of chapters.
I think we need some terminology:
SomeContent.md - A markdown file
SomeContent.mdd - A markdown directory generated from exploding a markdown file
SomeContent.mdz - A zip archive of a markdown mdz directory
SomeContent.mdt - A zip archive of a markdown mdz directory containing all transcluded resources