Hi All, @Bjoern thanks for input. I requested the student to have a look at Hugo.
I also requested a new Apache git repo (celix-site) and this repo is now available [1]. The approach I want to take now is to start getting something up and running with either jykell or hugo on the celix-site. Meaning having a src dir with some markdown files, a generated content dir with html and some instructions/scripts on root level which should be used to generate the site. >From there build up the new site (hopefully with some pull request from our student) and finally request infra to use the celix-site git repo instead of the svn one. Any thought or remarks are welcome. Greetings, Pepijn [1] https://git-wip-us.apache.org/repos/asf/celix-site.git On Sun, Oct 8, 2017 at 1:26 PM Bjoern Petri <[email protected]> wrote: > > Hi Pepijn, > > > Good Idea - separating documentation into a dedicated > git repo could give us more flexibility e.g of the organization > of the docs which in turn will help users to pick it up more easily. > So definitely no objections from my side. > > Anyway, I wanted to point you to hugo[1] as an alternative > to jekyll. Saying this, I should mention that I do not have any > experience with jekyll, but I really like hugo for it's simplicity. > > So maybe your student wants to give it a try as well. > > Regards, > Bjoern > > [1] https://gohugo.io/ > > > On 02.10.2017 21:06, Pepijn Noltes wrote: > > Hi All, > > > > I currently mentoring a student with the assignment to update/redesign > the > > Celix website. > > There are a few reasons why I think a update for the website is needed. > > First of IMO we could do a better job in explaining the ideas behind and > > benefits of Celix, how Celix works and the plain look & feel of the > website > > can be improved. > > But also for a technical point of view I would like to move away from the > > svnpubsub mechanisme to a more git friendly approach. > > The latter I like to discuss in this mail. > > > > Personally I like the way Apache Beam has organised it's website. > > They have a separate git repository for their website [1] and use jekyll > > [2] to generate most html files from markdown files. > > If I am correct this means that we can still mainly use markdown files to > > write and maintain the Celix website and use a (IMO) more friendly > > environment to generate and commit the website. > > > > [1] https://github.com/apache/beam-site > > [2] http://jekyllrb.com > > > > Let me know what you think if this approach. If nobody disagrees I will > go > > ahead and see what step we can take to arrange this. > > > > Greetings, > > Pepijn > > > > >
