Extract/expand Journal content into separated file

[Cussa]

Following a similar idea about the expand folders, this could give a better control to track changes in journals.
My current idea would be to get the content, create a html/markdown file with the same file name and save a prettified version of the content.
During the pack, we would check that the flag is used and include back the content before doing the real pack.

Pros

• Improve change track, as today the Journal content is a single line which can be complicated to review

Cons

• We would need a special handler for the object if they are a Page

Considerations

• We would need to check a library to prettify and minify the files during unpack/pack
• We would need a special handler for the object if they are a Page

Possible solutions with the current model

• Use the transformEntry to do that

[xyzzy42]

PR #54 has something that can address the pack side of that. By allowing the library to directly get objects to pack into the database, you can write your module build process so it finds all your markdown files, converts it into valid foundry document objects, and then hands those objects to the foundrycli library to turn into a database.

[Cussa]

It's a shame that is not merged... :(