Re: [discussion] CMS migration (was: svn migration plan)
Welcome back George, yes I have not forgotten your work. I do hope you continue. I am really happy on your post. I liked your proposal for the new design. I would really like to see that they move into our "production". The only thing is that in my opinion the static side generator does not fit to the 2 wikis, to bugzilla and to our maybe hopefully soon returning OpenGrok instance. What I would opt for that we are able to move all written content into one single cms that also works like a wiki. However it is more important that we move away from the old cms. So if you guys think we should go for a page gen then lets go on this journey. I am in full support for a redesign. I usually get lost in our materials. I would so much like to see a improvement on our material. I also tried to motivate new people but I did not manage to accompany them enough. So I am really sad it did not work. All the best Peter On 29.07.19 10:17, George Karalis wrote: > Hello Peter, > > I have proposed some time ago the move to a static site generator — like > Jekyll, Hugo etc. — > as I was redesigning OpenOffice’s front-page. That would greatly help reduce > tech diversity > and maintenance as only static html files will be served. > > Most static site generators work with markdown and I believe that content > writers won't have > a problem working with markdown. We could also setup an automated build > pipeline that > serves the generated site with every commit, i.e. every markdown or template > change. > > By the way there's a fully functional redesigned front-page for anyone > interested, that time > there was a server migration and it hadn't got much attention. The CMS > migration provides an > opportunity to move to a whole website redesign. > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] CMS migration (was: svn migration plan)
BTW - A good portion of the site is html as donated in 2011. It is extracted using additional functions in the CMS and then wrapped in the templates. There is about 9GB content and as the template was developed we hammered the CMS system. We will need to revisit how we handle NL for the headers. I did the bulk of the work in Dec 2011. No real plans to help until after Apachecon. Please keep the OpenOffice website in SVN until a Git based framework using new tools is built. Once it is we can do a bulk move which could include html conversions. Personally, I kind of like the JBake approach used in the Incubator ... Regards, Dave Sent from my iPhone > On Jul 29, 2019, at 7:33 AM, Raphael Bircher wrote: > > Hi Gavin > > Sounds like a load of work, Especially for the Templates. Does Pelican > serve HTML and markdown mixed? > > Regards Raphael. > >> On Mon, Jul 29, 2019 at 10:48 AM Gavin McDonald wrote: >> >> Hi all, >> >>> On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: >>> >>> Hello Peter, >>> >>> I have proposed some time ago the move to a static site generator — like >> Jekyll, Hugo etc. — >>> as I was redesigning OpenOffice’s front-page. That would greatly help >> reduce tech diversity >>> and maintenance as only static html files will be served. >>> >>> Most static site generators work with markdown and I believe that content >> writers won't have >>> a problem working with markdown. We could also setup an automated build >> pipeline that >>> serves the generated site with every commit, i.e. every markdown or >> template change. >> >> >> Hi George, you have just described almost perfectly Infras replacement for >> the CMS! >> Using Pelican and GHFM and Buildbot, you only need to 'edit' a page in >> Github and that >> commit will trigger a site rebuild and automatic publish of the site. It is >> still in testing but >> almost ready for use. I'll post more details and a docs link when its ready >> for wider testing. >> >> Gav... >> >> >>> >>> >>> By the way there's a fully functional redesigned front-page for anyone >> interested, that time >>> there was a server migration and it hadn't got much attention. The CMS >> migration provides an >>> opportunity to move to a whole website redesign. >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> >> -- >> Gav... > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] CMS migration (was: svn migration plan)
Hi Gavin Sounds like a load of work, Especially for the Templates. Does Pelican serve HTML and markdown mixed? Regards Raphael. On Mon, Jul 29, 2019 at 10:48 AM Gavin McDonald wrote: > > Hi all, > > On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: > > > > Hello Peter, > > > > I have proposed some time ago the move to a static site generator — like > Jekyll, Hugo etc. — > > as I was redesigning OpenOffice’s front-page. That would greatly help > reduce tech diversity > > and maintenance as only static html files will be served. > > > > Most static site generators work with markdown and I believe that content > writers won't have > > a problem working with markdown. We could also setup an automated build > pipeline that > > serves the generated site with every commit, i.e. every markdown or > template change. > > > Hi George, you have just described almost perfectly Infras replacement for > the CMS! > Using Pelican and GHFM and Buildbot, you only need to 'edit' a page in > Github and that > commit will trigger a site rebuild and automatic publish of the site. It is > still in testing but > almost ready for use. I'll post more details and a docs link when its ready > for wider testing. > > Gav... > > > > > > > > By the way there's a fully functional redesigned front-page for anyone > interested, that time > > there was a server migration and it hadn't got much attention. The CMS > migration provides an > > opportunity to move to a whole website redesign. > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > -- > Gav... - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] CMS migration (was: svn migration plan)
Hi all, On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: > > Hello Peter, > > I have proposed some time ago the move to a static site generator — like Jekyll, Hugo etc. — > as I was redesigning OpenOffice’s front-page. That would greatly help reduce tech diversity > and maintenance as only static html files will be served. > > Most static site generators work with markdown and I believe that content writers won't have > a problem working with markdown. We could also setup an automated build pipeline that > serves the generated site with every commit, i.e. every markdown or template change. Hi George, you have just described almost perfectly Infras replacement for the CMS! Using Pelican and GHFM and Buildbot, you only need to 'edit' a page in Github and that commit will trigger a site rebuild and automatic publish of the site. It is still in testing but almost ready for use. I'll post more details and a docs link when its ready for wider testing. Gav... > > > By the way there's a fully functional redesigned front-page for anyone interested, that time > there was a server migration and it hadn't got much attention. The CMS migration provides an > opportunity to move to a whole website redesign. > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Gav...
Re: [discussion] CMS migration (was: svn migration plan)
Hello Peter, I have proposed some time ago the move to a static site generator — like Jekyll, Hugo etc. — as I was redesigning OpenOffice’s front-page. That would greatly help reduce tech diversity and maintenance as only static html files will be served. Most static site generators work with markdown and I believe that content writers won't have a problem working with markdown. We could also setup an automated build pipeline that serves the generated site with every commit, i.e. every markdown or template change. By the way there's a fully functional redesigned front-page for anyone interested, that time there was a server migration and it hadn't got much attention. The CMS migration provides an opportunity to move to a whole website redesign. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] CMS migration (was: svn migration plan)
On 28.07.19 23:10, Marcus wrote: > Am 28.07.19 um 21:31 schrieb Peter Kovacs: >> Cms will be shut down soon. The question is how we deal with this. >> Info is in the chat protocol in my original post. > > OK, then we will have a big problem in order to serve our website pages. > > Marcus > > There are no deadlines yet. Just whishes on time frame. There is current a loose target at Infra in 3 month. Lets say november. If we manage to switch at december we will still be fine. Infra offers an incompatible replacement suite. Maybe there will be migration scripts helping us with the migration. I would like more to move to a easy to use cms system that might help us to reduce tech diversity and maintenance. I am quite fond of neo (1) Neo looks interesting since it promises a easy to use front end, multi language setup of content and the ability to integrate other sites and resources, while technical relative "easy" maintenance. Both Ideas sound like promising ways. with pro and cons. I am open for more ways. (1)https://www.neos.io/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
