<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span class="Apple-style-span" style="color: rgb(69, 69, 69); font-family: Arial, Helvetica, sans-serif; font-size: 12px; "><table cellspacing="0" cellpadding="0" border="0" style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: table; border-collapse: separate; "><tbody style="width: 1043px; "><tr style="display: table-row; vertical-align: inherit; "><td valign="top" style="display: table-cell; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; font: inherit; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">I agree with James about the basic functions of the <span class="yshortcuts cs4-visible"
id="lw_1334166062_0" style="cursor: pointer; color: rgb(54, 99, 136); border-bottom-width: 2px; border-bottom-style: dotted; border-bottom-color: rgb(54, 99, 136); ">club website</span>. It frustrated me as a newcomer to the LUG that I couldn't tell from the website if it was active or when the next meeting was. I've become accustomed to getting all my news from the mailing list, but Jesse's email reminded me again why the club website is important.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left:
0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">This club is a functioning anarchy. There is no one person who is designated to do something. We do it because we want to, because we see a need, and because it is convenient (or not too inconvenient).</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">Though I long saw a need to update the club website, it had been way too inconvenient to do so.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right:
0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">The current club website is hard to edit. Joomla is completely unintuitive to me. It took me a while to find an old meeting notice so I could see the template, and then I could only post one item, because when I tried posting more, I couldn't get it to show up in the right place. This took way more time than I really wanted to devote to it, and I really didn't want to touch it again.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">James' suggestion sounds like the right approach to me and if it's as easy
as he says, I plan on adding a lot more content to it.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; ">Lan</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; display: block; line-height: normal; "><br></div></td></tr></tbody></table></span></div> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr
size="1"> <b><span style="font-weight:bold;">From:</span></b> James McDuffie <mcduffie@pitfall.org><br> <b><span style="font-weight: bold;">To:</span></b> sgvlug@sgvlug.net <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, April 11, 2012 9:41 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> [SGVLUG] A modest proposal (for the SGVLUG website)<br> </font> </div> <br>
I have a modest proposal for what should be done with the SGVLUG website. I know that Matt and Miguel put effort into putting together a Drupal website, but I think I have a idea that is more maintainable given the structure of the club.<br><br>Firstly, I do not believe that our club needs a dynamic website for its own sake. I believe the purpose of our club website is:<br>1. To let people know when and where we meet<br>2. Post description of upcoming topics<br>3. Archive presentations from past meetings<br>4. Link to the mailing list<br><br>All of this can be done with static pages given the frequency of updates needed.<br><br>Now that being said, these do not have to be hand edited pages or pure HTML. There is a growing trend of using static website generators.<br>http://inessential.com/2011/03/16/a_plea_for_baked_weblogs<br>http://news.ycombinator.com/item?id=2378237<br><br>So with this in mind I investigated and found that using one such combination
of generator and open source friendly website: Jekyll + Github we can get a pretty nice website for free. Here is why I like this combination:<br><br>1. Its free, no one has to shell out for hosting<br>2. Can utilize Github for user management<br>3. Can use Git for version control and essential mirror the website to whoever clones the repository (free backups!)<br>4. The entire website can be deployed pretty much anywhere should Github drop into the ocean<br>5. As long as enough people are admins there is no single point failure<br>6. Even if all the admins for the Github page suddenly disappear, anyone could clone the website and redeploy elsewhere<br>7. Anyone can fork the website and contribute (sending a pull request) without waiting for or needing direct repository access<br>8. Its pretty easy to use (IMHO)<br>9. Non-programmers and more web design centric people can contribute more easily<br>10. Our website is also open sourced!<br><br>Stated
another way I think this works best with the semi-functioning anarchy of the club.<br><br>It requires a minimal amount of effort to be able to contribute:<br>1. Install git<br>2. Fork<br>3. Edit<br>4. Push changes<br>5. Issue pull request<br><br>Even less effort for people who don't want to use Github<br>1. Install git<br>2. Clone repository<br>3. Edit<br>4. Email a patch to someone<br><br>So if your still reading, I have already set up an example club website here:<br>http://sgvlug.github.com/<br><br>I think its ready to use and just needs additional stuff pulled from the old Joomla website.<br><br>Need more information? Well here is a more detailed guide to getting started using a Jekyll website:<br>http://jekyllbootstrap.com/lessons/jekyll-introduction.html<br>http://jekyllbootstrap.com/usage/jekyll-quick-start.html<br><br>And for people who want to skip straight to the reference material, I found these pages more useful for knowing how to change the
bootstrapped website:<br><a href="https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter" target="_blank">https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter</a><br><a href="https://github.com/mojombo/jekyll/wiki/Template-Data" target="_blank">https://github.com/mojombo/jekyll/wiki/Template-Data</a><br><a href="https://github.com/mojombo/jekyll/wiki/Liquid-Extensions" target="_blank">https://github.com/mojombo/jekyll/wiki/Liquid-Extensions</a><br>http://daringfireball.net/projects/markdown/syntax<br>http://github.github.com/github-flavored-markdown/<br><br>Did I mention I already have a working example, that just needs a CNAME pointed towards it :) ?<br><a href="http://sgvlug.github.com/" target="_blank">http://sgvlug.github.com/</a><br><br>Now please discuss.<br><br><br> </div> </div> </div></body></html>