- π©πͺGermany woldtwerk Stralibu
I would still be interested in the results of your investigation.
Did it work well with nuxt content?
It would be great if there was an option with the tome:export
feature to export the json files into a directory and filename structure that match's the site's paths/directories for content.
Using the Umami demo site as an example, some of the exported recipe files would be:
/content/recipes/deep-mediterranean-quiche.json
/content/recipes/thai-green-curry.json
/content/recipes/vegan-chocolate-and-nut-brownies.json
For entities without path aliases, I would imagine the fallback would be the /node/###, /taxonomy/term/###, etc. internal paths.
I'm investigating using the tome:export
feature with the Nuxt Content module to allow the exported json files to be the source content for a Nuxt.js SPA.
Maintaining the site structure for the files would greatly help this, and I think would generally make working with the export files easier.
Closed: won't fix
1.4
Tome Sync
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I would still be interested in the results of your investigation.
Did it work well with nuxt content?