[Pywps-dev] GitHub pages

[Tom Kralidis]

Luis: thanks for the info -- great work!  Comments/suggestions based
on our pycsw-workshop [1] experiences:

- it might be cleaner to have a single repository called, say,
pywps.org in which the master branch is the source and the output is
in branch gh-pages.  A build step would build the docs in master and
commit the output to gh-pages [2]
- consider adding a CNAME file which contains pywps.org (I think
someone in PyWPS has this domain already?)
- given PyWPS is itself within the geopython GitHub organization [2],
you're more than welcome to setup shop there for pywps.org repo

Cheers

..Tom

[1] https://github.com/geopython/pycsw-workshop
[2] https://github.com/geopython/pycsw-workshop/blob/master/Makefile#L163
[3] https://github.com/geopython/PyWPS

On Thu, Jul 16, 2015 at 11:55 AM, Luís de Sousa
<luis.a.de.sousa at gmail.com> wrote:
> So we have a web page working on GitHub (sort of):
>
> https://pywps.github.io/
>
> There is no styling, and at this stage I am not sure why. Should
> sphinx also generate some css?
>
> This is what I did:
>
> 1. Created a new project to contain the source (on which sphinx runs)
> called pywps.github.io.source
>
> 2. The project pywps.github.io now only contains the output from sphinx (html)
>
> 3. pywps.github.io is now a submodule of pywps.github.io.source, under
> the build folder
>
> 4. Updated the README with new compile instructions.
>
> Cheers,
>
> Luís
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev