On Tue, Nov 24, 2015 at 12:09 PM, Paul W. Frields <stickster@xxxxxxxxx> 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. > > 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! I'm very new to websites list, so I may be unaware of any SOP that predates my joining. That being said, I have been hanging out with Fedora-infra for a while, and whenever they do new sites, there are some tools/practices they use: 0) We should use revision control (git) 1) We should host the repository on Pagure.io (and mirror on Github?) 2) We should serve the content on OpenShift (like past FLOCK websites) or on maybe hosted infra? Them's my thoughts: --RemyD. P.S. - I've used Nikola as my static site generator of choice for my personal blog, and it has been *lovely* http://getnikola.com > > -- > 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 > -- > websites mailing list > websites@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/websites@xxxxxxxxxxxxxxxxxxxxxxx -- Remy DeCausemaker Fedora Community Lead & Council <decause@xxxxxxxxxx> https://whatcanidoforfedora.org -- websites mailing list websites@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/websites@xxxxxxxxxxxxxxxxxxxxxxx
