Hi,

well I could help with this.
I guess the PLC4X podling is the cleanest of my examples for a setup in which 
the website is generated from asciidoc as part of the maven build
And it is also automatically staged and published by git-pub-sub.
IANAWD (I am not a web designer), and the content definitely needs an update, 
but I'm quite happy with the results.

https://plc4x.apache.org

Chris

Am 23.02.19, 01:06 schrieb "Kenneth Knowles" <[email protected]>:

    It can all be in one repo. Beam recently moved the site from the
    apache/beam-site repo to a directory in the main apache/beam repo. It is
    nice to not have multiple places you have to go looking for bits. And it is
    published on every commit using gitpubsub. I didn't set that up, but I can
    ask around. We've had a pretty good time with Jekyll though I think mostly
    we don't change it since it is working. I think various flavors of markdown
    have the most widespread support.
    
    Kenn
    
    On Fri, Feb 22, 2019 at 2:49 PM Lars Francke <[email protected]> wrote:
    
    > We need a website :)
    >
    > I have almost no skills in any kind of frontend work. CSS/HTML etc. That
    > means I also don't have any strong opinions on this but I know that some 
of
    > you (Christofer etc.) have already dealt with this in other projects.
    >
    > I'm happy to help with content when the basics are set-up.
    >
    > The only opinion I do have is that it'd be good to have the content in a
    > format like Asciidoc - ideally in the same format as some/all of our 
actual
    > content.
    >
    > It'd be fabulous if anyone is willing to take this up?
    >
    > I know that Infra has a "gitpubsub" thing which allows us to automatically
    > build and deploy a site from git somehow. I've never used it and there are
    > lots of things I don't know. One of them being whether it can all be one
    > repository or whether we need a training-site repo.
    >
    > <https://www.apache.org/dev/project-site.html>
    > <https://www.apache.org/dev/gitpubsub.html>
    >
    

Reply via email to