A couple of years ago, I prototyped something between a static site generator and a decoupled/headless CMS, called Brea[1] and we did a lot of extensive workshops to teach how to use it. The site (in Spanish) for the workshops and documentation of Brea is made using Brea and you can see it at [2]. It tries to address the documentation needs of the local communities which use diverse places to write documentation (HegdeDoc, Internet Archive) and want to consolidate them in a unified place. We're now discussing to integrate Brea with TiddlyWikiPharo[3] as TiddlyWiki has become an integral part of our documentation practices and maybe we could try another take on it if we get enough resources for that.

[1] https://code.tupale.co/Offray/Brea
[2] https://mutabit.com/repos.fossil/indieweb/
[3] https://code.tupale.co/Offray/TiddlyWikiPharo/

Cheers,

Offray

On 1/09/22 7:36, Marcus Denker wrote:
The pharo.org <http://pharo.org> website is generated statically, see

https://github.com/pharo-project/pharo-site

(you can do PRs to edit / improve it).

This uses https://github.com/estebanlm/Foliage

Marcus

On 28 Aug 2022, at 00:41, Tim Mackinnon <tim@testit.works> wrote:

I recall that that Norbert was doing some interesting cms stuff (check old messages, or maybe he will chip in).

To be honest though, I’d consider using StoryBlok (https://www.storyblok.com/) or Prismic and interface with that with zinc

Tim

On 26 Aug 2022, at 10:20, Siemen Baader <siemenbaa...@gmail.com> wrote:


Hi everyone,

I was looking for a Pharo CMS. I got the Pier one-click image from www.piercms.com <http://www.piercms.com/>, but it seems there is a hardcoded path in the image. I get the error message:

Pharo cannot write to the changes file named /private/var/folders/ImndBm_rpdOz3Bpyfiqvv0d4dc000Ogn/T/AppTranslocation/24424,42 BEB3 4E. BBC5 CMFBIElgi12/3/35/d/Pier app/Contents/Resources/Pier.changes

(the image is not there but in my ~/Downloads folder).

Any ideas how I can fix this?

And what does Pharo.org <http://Pharo.org> use for its CMS?

thanks,
Siemen

Reply via email to