<div dir="ltr">Hi Deb,<div><br></div><div>Thanks for the thought & effort you're putting into the gluster web site!</div><div><br></div><div>I have a few comments, for whatever they're worth. Some general thoughts here, then individual comments on your points inline below.</div><div><br></div><div>In general, even if you post details of what you're planning or doing on your blog, please also drop a note with link on this mailing list so we know to go check your blog. I'd appreciate reading your blog but I wouldn't know when or where to look unless you posted something about it here.</div><div><br></div><div>Also, since I'm the de facto Varnish admin (as far as I know), I want to offer any help you may need, and answer any questions you have, about Varnish and its role on <a href="http://gluster.org">gluster.org</a>.</div><div><br></div><div>The rest, see below.</div><div><br></div><div>Thanks again!</div><div><br></div><div>-louis</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 15, 2014 at 7:12 AM, Soumya Deb <span dir="ltr"><<a href="mailto:deb@redhat.com" target="_blank">deb@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi all,<br>
<br>
I was looking at the Gluster website for a while.<br>
Liked the last overhaul, much responsive now, but found that we could do even better.<br>
<br>
I'm planning on writing a 3-part blog post (public; so, raise a flag if anyone has concern against that) explaining by thoughts in details. But that's taking a while now & so I'll put the main topics here only. Correct me if I'm wrong/short-sighted anywhere - I know there have been a lot of discussion that I haven't been a part of, so unaware of the limitations you had to deal with (that I might accuse you of :P). I intentionally didn't check commit sign-offs - just so that I can give my opinions fair & square.<br>
<br>
1. Using static site generator using Ruby: is it really required? (Alternative, pure static site, with client side templating)<br></blockquote><div><br></div><div>As far as I know, it is ultimately up to the person who manages the site to pick the tools they use. However, I know whenever anyone takes over (or gets involved with) a project they will have a tendency to redevelop/migrate things to tools they are comfortable with. This is not necessarily a problem, but I would be careful to not spend time migrating the project to new tools unless it's really necessary. Is it really required? I think the question should be, "Is it getting in the way?" If not, then lets just keep it the way it is (IMHO).</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
2. Using the right tools/frameworks for the purpose, and not trying to emulate the purpose of one framework/CMS with another.<br></blockquote><div><br></div><div>Could you be more specific? Are we facing serious problems due to the tools/frameworks currently used? (I agree with your statement in general, it just doesn't seem like a top priority right now.)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
3. Each of the facets of the site as short typable subdomains: docs, wiki, bugs, code etc. (with proper HTTP/301, as needed)<br></blockquote><div><br></div><div>If it's just an aesthetic preference for subdomains over path directories then I would say it's not very important in the grand scheme of things. On the other hand, if we do switch to subdomains, then Varnish might prove useful for routing requests and I'd be happy to help.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
4. One go-to place for each facet/purpose (especially docs). <a href="http://gluster.org/documentation/" target="_blank">http://gluster.org/documentation/</a> & <a href="http://www.gluster.org/community/documentation/index.php/Main_Page" target="_blank">http://www.gluster.org/community/documentation/index.php/Main_Page</a> are highly confusing to get right information from & also creates fragmentation. A single <a href="http://docs.gluster.org/" target="_blank">http://docs.gluster.org/</a> (wiki with pretty URL, thus no /index.php/Main_Page etc.)<br></blockquote><div><br></div><div>Agree. We would benefit from having "landing pages" with pretty URLs and clear content aimed at common site visitor needs. Once we have landing pages like this we can work on focusing search engines on them, so people are less likely to find outdated or irrelevant information when starting out.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
5. URLs like <a href="http://www.gluster.org/about" target="_blank">http://www.gluster.org/about</a>, <a href="http://blog.gluster.org/blog/" target="_blank">http://blog.gluster.org/blog/</a> etc. are to be sanitized, decommissioned and/or properly redirected<br></blockquote><div><br></div><div>Agree. Even more broadly, there's a lot of old content around that confuses new users. There's plenty of old stuff on <a href="http://gluster.org">gluster.org</a> sites, and unfortunately also on other sites around the net. We should at least take inventory of our own sites & do a better job of hiding the outdated information from new users. I think this is a big, important issue, that may need to be addressed on its own, independent of a <a href="http://gluster.org">gluster.org</a> web site refresh.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
6. Properly responsive website (like <a href="http://blog.gluster.org" target="_blank">blog.gluster.org</a> isn't) with seamless themes & url-integration for all sub-sites with better typography, legibility, color scheme etc.<br>
7. More performing website, by removing code bloats, ghosts of copy-pastes etc. Also, needs some help with JS & CSS performance tuning.<br>
<br>
I'll details them in my blog & you'll get to comment there & continue the discussion. But please do correct me if I'm starting with the wrong foot somewhere.<br></blockquote><div><br></div><div>In my opinion, your issues #4 & #5 are the most important.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Cheers,<br>
Deb<br>
<br>
P.S: will have to miss today's meeting as well. On the move & flaky connectivity. Apologies!<br>
_______________________________________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-infra" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-infra</a><br>
</blockquote></div><br></div></div>