Feature Request: Export Collective to Obsidian Publish-like Interactive Website (with digital garden references)

[jab-AStA]

The Problem

For some time, I am thinking of migrating documentation I maintain from e.g. Dokuwiki to Collectives, because of the prettier an easier UX for non-tech people :)

The point that prevents me from doing this is, that I can't manage to get a publicly shared Collective to a non-laggy performance, which of course also depends on the limited resources of my NC instances.

Nevertheless I can't get away from the idea, that using Collectives in Nextcloud, with it's deeply integrated feature with tagging users, other apps ( e.g. Deck) and the general UX of editing a Collective is very much more userfriendly than many other options I have tried.

The Idea

I would love to export a collective to an interactive website, similar to Obsidian Publish, with features such as link previews, backlink navigation, and a graph view, enabling richer sharing and browsing of collective knowledge.

The huge pro on this is that users can just edit the website from inside the Collective, which would be awesome!

How this could be achieved:

• There are open-source digital garden/static site generators, such as Quartz (based on Hugo), or Dendron, which can convert Markdown content into an interactive website with backlink support, graph view, and link previews.
• The export could convert collective files (Markdown and metadata) into a format consumable by these tools, or use their codebases directly to generate the site.

Integration options:

• As a feature in the Collectives app
• As a separate Nextcloud app that would have to be installed next to collectives

Request:

• Would the Collectives team be open to integrating such an export feature?
• Or, do you recommend this as a separate app in the Nextcloud ecosystem?
• Any guidance on architecture or best practices for maximum compatibility and maintainability?

What do you think of this? :)

[max-nextcloud]

We've been discussing this before. It's definitely an interesting option. One possibility would also be to revive the pico cms app and integrate it with collectives.

This seems like a dev project fitting well to apply for funding by the prototype fund if people want to get paid to work on it for halve a year to get it off the ground.