2015-11-24 22:26 GMT+01:00 Paul W. Frields <stickster@gmail.com>:
On Tue, Nov 24, 2015 at 09:55:25PM +0100, Robert Mayr wrote:
> 2015-11-24 19:27 GMT+01:00 Remy DeCausemaker <decause@redhat.com>:
>
> > On Tue, Nov 24, 2015 at 12:09 PM, Paul W. Frields <stickster@gmail.com>
> > wrote:
> > > Recently I talked to robyduck in IRC about using a static site in the
> > > fedora-web repo for the next iteration of the main flocktofedora.org
> > > site.  This would make the standard public content (location, venue,
> > > dates, etc.) easier to manage and serve to users.
> >
>
> Is it really a static html website or are there any dynamic contents which
> require a framework? User login? Registration?
>
>
> > >
> > > How would we go about starting such a site?  Is it OK to simply do a
> > > commit with a new folder 'flocktofedora.org' and a simple Makefile to
> > > start?  Should we make a new topic branch, and keep work there until
> > > we're ready to merge?
> > >
> > > Thank you for any advice you can provide!
> >
>
> Well not only a folder, we need to setup a few things to make the website
> able to be built at least locally.
> When ready we will get in touch with infra to sync out the work in our
> fedora-web role on ansible.
> As it is a new website and you work in a separated folder it doesn't matter
> where we add it, also on master branch would be ok, because we don't build
> it for now.

This plus our IRC conversation was really helpful.  We'll start
pulling together some people to help (and Robert put up a hand too,
kind soul that he is) and start making plans.

--
Paul W. Frields                                http://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
    The open source story continues to grow: http://opensource.com

Ok so it's all set up now. flocktofedora.org has its folder in the master branch and can be built locally.
I've also added the changes to zanata and pushed a new POT file to make the website translatable. Actually the source is read only, nobody will be able to work on the strings.
The footer is the same as for our other websites, language selector also should work fine. The app.css file still contains some old classes, not sure if we need them in some way, but we can obviously make a new one.
Means, it's all ready to start working on it.
Cheers.

--
Robert Mayr
(robyduck)