Publishing a collective as a (public) static website

[xplosionmind]

Is your feature request related to a problem? Please describe.
One of the most frequent use cases for my association’s wiki is to send it to newcomers (who don’t have an account in Nextcloud yet) so that they can learn about how we work. This is not possible with the current Collectives. It is the only thing that blocked me in moving the whole documentation to Collectives.

Describe the solution you'd like It would be great to publish the whole wiki as a static website. Ideally, at a specific domain designed for it. Some pages could be kept private (hence visible only to Nextcloud users) but all of the rest gets published by default.

Describe alternatives you've considered Publish the documentation with a static website (Eleventy), building it locally after syncing the Markdown pages with Nextcloud Desktop.

Additional context
Related requests:

515 #511 #505

[juliushaertl]

https://apps.nextcloud.com/apps/cms_pico might be an option for that already.

[xplosionmind]

Thanks a lot @juliushaertl! I knew Pico CMS already, even though I actually never tested it.

It would be awesome if Collectives could integrate with it, without needing to code new stuff, but just make them interoperate!

[TheNomad11]

https://apps.nextcloud.com/apps/cms_pico might be an option for that already.

PicoCMS is not compatible with Nextcloud 26, while Nextcloud 27 is already around the corner....

[42ske]

Maybe https://github.com/nextcloud/collectives/issues/511 and https://github.com/nextcloud/collectives/issues/515 could be a solution?

[gbertolottiKS]

+1 on this. It would be very useful.

Thanks

[juliushaertl]

@gbertolottiKS Please use github reactions instead of +1 comments if you just add your interest in a feature

[jancborchardt]

It is already possible to share a whole Collective quite easily as a link to people without an account. And in the next release sharing of pages (including their subpages) will also be possible: https://github.com/nextcloud/collectives/issues/515

This seems to cover most of the usecase you described @xplosionmind. So I would be curious what the things are which are missing and how important they are. Probably it is best to open separate issues for each of them? cc @TheNomad11 @42ske @gbertolottiKS

• At a specific domain designed for it: You would have to do this at your domain registrar anyway, no @xplosionmind ?
• Some pages could be kept private (hence visible only to Nextcloud users) but all of the rest gets published by default. → I would say this should be a specific separate issue @xplosionmind ?

Action menu	When shared

What people see

[xplosionmind]

Hi @jancborchardt!

Thanks a lot for your work!

At a specific domain designed for it: You would have to do this at your domain registrar anyway

I don’t really understand what you mean… for example, my org has its Nextcloud instance at https://nuvola.scambi.org, but we’d like to host the docs on https://manuale.scambi.org.

Some pages could be kept private (hence visible only to Nextcloud users) but all of the rest gets published by default. → I would say this should be a specific separate issue

Indeed. To be honest, though, I have not been using the Collectives app much recently, so I would prefer not creating the issue myself, since I am not 100% confident about how it is working.

[jancborchardt]

Since this was completed as per https://github.com/nextcloud/collectives/issues/515 (pull request at https://github.com/nextcloud/collectives/pull/1041 ) I would close this as done.

If any related things are still relevant, it would be best to open follow-ups as mentioned above. :)