<div dir="ltr">Hi Ryan,<div><br></div><div>Having seen your initial work on <a href="http://rclark.github.io/pycsw.org/">http://rclark.github.io/pycsw.org/</a> I am starting to get convinced about the Jekyll + Markdown combo.</div>
<div><br></div><div>As long as pycsw documentation stays in Python world (i.e. rst) I am +1 on moving the web site to Jekyll.</div><div><br></div><div>This does not mean I did not like the prototype made by Tom.</div><div>
<br></div><div>One more comment: the main <a href="http://pycsw.org">pycsw.org</a> web site must remain at OSGeo infrastructure in my opinion (we are under incubation), so GitHub can definitely hold your development version before deploying to OSGeo servers.</div>
<div><br></div><div>Thoughts?</div><div><br></div><div>Best,</div><div>Angelos</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 23, 2013 at 9:10 PM, Ryan Clark <span dir="ltr"><<a href="mailto:ryan.clark@azgs.az.gov" target="_blank">ryan.clark@azgs.az.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
I would say the big benefit to GitHub pages is that they provide your server hosting. Maybe that's not an issue. I think there's also a nice simplicity in keeping the website / documentation code literally in the same repository as the code itself -- just on
a separate branch. Again, that may or may not be an issue.
<div><br>
</div>
<div>Either way, I'd like to try and help with the website / templating / design. Have you already started some of this work in a separate repository?</div>
<div><br>
</div>
<div>Thanks!<br>
<div>
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div>____________________</div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Ryan Clark</div>
<div>Arizona Geological Survey</div>
<div><a href="mailto:ryan.clark@azgs.az.gov" target="_blank">ryan.clark@azgs.az.gov</a></div>
<div><a href="tel:%28520%29%20302-4871" value="+15203024871" target="_blank">(520) 302-4871</a></div>
<div><a href="https://www.facebook.com/ModernGeologist" target="_blank">facebook.com/ModernGeologist</a></div>
<div><a href="https://twitter.com/worbly" target="_blank">@worbly</a></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</font></span></div>
</div>
</div>
<br>
</div>
<br>
</div>
<br>
<br>
</div><div><div class="h5">
<br>
<div>
<div>On Aug 23, 2013, at 7:03 AM, Tom Kralidis <<a href="mailto:tomkralidis@hotmail.com" target="_blank">tomkralidis@hotmail.com</a>> wrote:</div>
<br>
<blockquote type="cite">Looks like it. Since the existing content is rST, I thought that would be easier. Are there advantages to using Jekyll + GitHub pages? I'm still in the template/design stage, so there's time to change engines.<br>
<br>
________________________________<br>
<blockquote type="cite">From: <a href="mailto:ryan.clark@azgs.az.gov" target="_blank">ryan.clark@azgs.az.gov</a>
<br>
To: <a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a> <br>
CC: <a href="mailto:tomkralidis@hotmail.com" target="_blank">tomkralidis@hotmail.com</a>; <a href="mailto:pycsw-devel@lists.osgeo.org" target="_blank">
pycsw-devel@lists.osgeo.org</a> <br>
Subject: Re: [pycsw-devel] new website development <br>
Date: Fri, 23 Aug 2013 12:53:05 +0000 <br>
<br>
This kind of documentation would be a great target for Jekyll + GitHub <br>
pages. I guess you would have to use markdown though? <br>
<br>
<br>
On Aug 23, 2013, at 2:38 AM, "Angelos Tzotsos" <br>
<<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a><<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">mailto:gcpp.kalxas@gmail.com</a>>> wrote:
<br>
<br>
Hi Tom, <br>
<br>
This is a very good idea for all the reasons you mentioned. <br>
+1 <br>
<br>
BTW, I am preparing an HTML5 presentation for FOSS4G 2013 and I am <br>
wondering where this would live and be maintained. <br>
<br>
If the web-site code lives in a new git repository, then I guess it <br>
would be natural to add resources there, right? <br>
<br>
Best, <br>
Angelos <br>
<br>
<br>
On Thu, Aug 22, 2013 at 2:48 AM, Tom Kralidis <br>
<<a href="mailto:tomkralidis@hotmail.com" target="_blank">tomkralidis@hotmail.com</a><<a href="mailto:tomkralidis@hotmail.com" target="_blank">mailto:tomkralidis@hotmail.com</a>>> wrote:
<br>
Hi all, <br>
<br>
The Sphinx documentation in [1] powers the <a href="http://pycsw.org" target="_blank">pycsw.org</a><<a href="http://pycsw.org" target="_blank">http://pycsw.org</a>> <br>
website and associated documentation. <br>
<br>
Sphinx docs were initially setup to manage both to make things easy, <br>
however given project maturation, our OSGeo incubation process, I think <br>
it's a good time to decouple the website content from pure software <br>
documentation and manage them separately. Rationale/benefits: <br>
<br>
- web content is growing (OSGeo incubation will soon lead us to <br>
PSC/RFC's and so on, community, FAQ) <br>
- website is due for a nice redesign (the docs don't need as much flare) <br>
- website announcements are natural for a blog setup <br>
- the website's lifecycle shouldn't/won't have to move along with <br>
software release <br>
<br>
I've opened a ticket for this [2]. <br>
<br>
Comments? Ideas? Objections? <br>
<br>
It would be great to have some help especially in the website/template <br>
design, so if anyone has a flare for web design/UI, any contributions <br>
are more than welcome. <br>
<br>
I'm initially thinking for the design to be implemented using Bootstrap <br>
[3], and setup using Pelican [4] (n.b. we don't have to redo the web <br>
content which is already in rST). <br>
<br>
..Tom <br>
<br>
[1] <a href="https://github.com/geopython/pycsw/tree/master/docs" target="_blank">https://github.com/geopython/pycsw/tree/master/docs</a>
<br>
[2] <a href="https://github.com/geopython/pycsw/issues/180" target="_blank">https://github.com/geopython/pycsw/issues/180</a>
<br>
[3] <a href="http://getbootstrap.com" target="_blank">http://getbootstrap.com</a> <br>
[4] <a href="http://docs.getpelican.com" target="_blank">http://docs.getpelican.com</a> <br>
_______________________________________________ <br>
pycsw-devel mailing list <br>
<a href="mailto:pycsw-devel@lists.osgeo.org" target="_blank">pycsw-devel@lists.osgeo.org</a><<a href="mailto:pycsw-devel@lists.osgeo.org" target="_blank">mailto:pycsw-devel@lists.osgeo.org</a>>
<br>
<a href="http://lists.osgeo.org/mailman/listinfo/pycsw-devel" target="_blank">http://lists.osgeo.org/mailman/listinfo/pycsw-devel</a>
<br>
<br>
<br>
<br>
-- <br>
Angelos Tzotsos <br>
Remote Sensing Laboratory <br>
National Technical University of Athens <br>
<a href="http://users.ntua.gr/tzotsos" target="_blank">http://users.ntua.gr/tzotsos</a> <br>
_______________________________________________ <br>
pycsw-devel mailing list <br>
<a href="mailto:pycsw-devel@lists.osgeo.org" target="_blank">pycsw-devel@lists.osgeo.org</a><<a href="mailto:pycsw-devel@lists.osgeo.org" target="_blank">mailto:pycsw-devel@lists.osgeo.org</a>>
<br>
<a href="http://lists.osgeo.org/mailman/listinfo/pycsw-devel" target="_blank">http://lists.osgeo.org/mailman/listinfo/pycsw-devel</a>
<span style="white-space:pre-wrap"></span><span style="white-space:pre-wrap"></span><span style="white-space:pre-wrap"></span> <span style="white-space:pre-wrap">
</span><span style="white-space:pre-wrap"></span> </blockquote>
</blockquote>
</div>
<br>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times New Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:arial;font-size:small"><div>
Angelos Tzotsos</div><div>Remote Sensing Laboratory</div><div>National Technical University of Athens</div><div><a href="http://users.ntua.gr/tzotsos" target="_blank">http://users.ntua.gr/tzotsos</a></div></span></span>
</div>