----- Original Message -----
> From: "Brian Exelbierd" <bex@pobox.com>
> To: developer-portal@lists.fedoraproject.org
> Sent: Friday, October 20, 2017 10:54:44 AM
> Subject: [Developer-portal] Re: vNext
>
>
>
>
> On Fri, Oct 20, 2017, at 02:28 AM, Radka Janekova wrote:
>
>
>
> Hi there,
> please let me know before you plan to deploy next one, I have some changes.

Hello,
please submit the changes before Thu 26/10 EOD.
(Thought: would it be possible to include mostly 'stable' content? E.g. that spans at least two releases. I do not consider this news-website. Fixes are however to be made:).)

> On a related note, do we want to consider moving this to the new docs
> publishing engine so it is less of a hassle to get built/maintained? That
> would reduce the commiter needs to accepting patches (mostly). It may
> require a bit of a rethink on the design though.

Bex, can you please point me to the 'engine' info, sources, example code?

Who would do the porting/maintenance? I think most of the time I spend on this is reviewing the commits/actual content, not building/releasing. Having automated OpenShift builds for PRs(or local), which is what I've planned, would put a bit ease the contributions IMHO. Apart from that, it's just a Markdown with simple YAML headers.

Pavel

PS: I find it a bit funny, to use docs engine, as we specifically avoid accepting(or forbid) any documentation-type content.
http://developer-portal.github.io/contributing/write-introduction.html

>
> regards,
>
> bex
>