Hi, Thanks for the feedback Bertrand. Our first choice is still to explore WordPress, the use-case is that non-technical persons who don't have Github accounts or git-know-how should still be able to contribute to CloudStack website and blogs (mostly marketing activities hence discussed on the marketing@c.a.o list). The current practice and requirements make it less inclusive for non-technical people involved.
+1 yes of course, we want the problem fixed and I think if we're not getting support on WordPress or similar CMSs then I would certainly try git-based/backed CMS + document this on our project cwiki for other projects to benefit. As an experiment, I just finished playing with netlify and looks like it may work as long as Ivet and others are happy with it. Netlify CMS requires certain access to Github repo and commit access as a Github account to allow for commits when pages are edited/saved. One thing I really liked so far is the netlify import/setup took me less than half-hour so far 🙂 The current CloudStack website is based on middleman which is slow, I tested it with github+netflify and found each commit/change took about 5mins to publish (which is in-line what we got here): Repo: https://github.com/cloudstack/netlify-cloudstack-www Test preview/publishing: https://happy-brattain-4bd9a5.netlify.app/ I also tested Hugo based on your suggestion which was super quick Repo: https://github.com/rhtyd/test-hugo-netlify Test: https://sleepy-wilson-181ad1.netlify.app/ Due to this limitation, I'll test and PoC and share results here if we can do something like this; * Fork www repo of a apache project * Integrate with netlify for non-technical person who uses UI-editor to work/with save/create stuff * Have a Github action that raises PR to the source repo when a commit is made * ACS bot or authorised committer/PMC merge/publish the website Regards. ________________________________ From: Bertrand Delacretaz <bdelacre...@apache.org> Sent: Wednesday, June 23, 2021 13:51 To: Rohit Yadav <rohit.ya...@shapeblue.com>; us...@infra.apache.org <us...@infra.apache.org> Cc: legal-disc...@apache.org <legal-disc...@apache.org>; priv...@cloudstack.apache.org <priv...@cloudstack.apache.org>; marketing@cloudstack.apache.org <marketing@cloudstack.apache.org> Subject: Re: Uploading Blog Post Hi, On Wed, Jun 23, 2021 at 9:07 AM Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > ...Alternatively, if indeed it is a policy of the ASF to require project > website and blog tracked by git/source code - > could we explore git-based CMS services such as https://forestry.io, > https://www.netlifycms.org/, > https://cloudcannon.com/, https://www.siteleaf.com... I'm not from infra, but if you find a solution that can update an ASF-hosted repository, using a client-side or a pass-through CMS service I suppose that would work. I see for example that Netlify CMS supports Hugo ( https://www.netlifycms.org/docs/hugo/ ) which several ASF projects use for their websites, at least those: https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories I haven't checked if that requires specific settings on the GitHub side, which is where our infra might need to get involved. If you pursue such an option I would suggest creating a place (wiki page or such) where people from other projects can collaborate, as I suppose others might be interested. Note also the poor man's variant of that which is to edit Markdown using the built-in GitHub editor - but I suppose you're looking for something less "technical" for content authors. And also https://blogs.apache.org/ which I think I already mentioned. -Bertrand
