Hello list,
I am documentating and research about the opportunity in $subj to migrate our static website from nanoc + few accounts able to access our www machine to the opportunity to have it hosted on github pages. Mainly the idea to suggest this method is because the current solution is:
* Complex (deal with haml and nanoc) * Not everyone in the team can update the page (lack of permissions) * Usually is time wasting to update it (nanoc time + fix time + ɛ * rand() ) ( ɛ = epsilon)
I did a small list of pro and cons about this migration:
Pros: * Far more easy deploy phase * Reducing delays for website updates. * _Everyone_ within the team in github can update those pages. * Easy and _straightforward_ MarkDown syntax without tab/spaces weirdness
Cons: * Migrate haml to md+liquid (isn't really complex) * Change a bit the layout + styling (e.g. [1,2])
Please let me know your thoughts about it,
Cheers, Francesco Vollero
On 28/06/2012, at 11:51 PM, Francesco Vollero wrote: <snip>
Pros:
- Far more easy deploy phase
- Reducing delays for website updates.
- _Everyone_ within the team in github can update those pages.
- Easy and _straightforward_ MarkDown syntax without tab/spaces weirdness
Cons:
- Migrate haml to md+liquid (isn't really complex)
- Change a bit the layout + styling (e.g. [1,2])
Please let me know your thoughts about it,
As a thought, are we able to test/trial this somehow?
test.aeolusproject.org or something?
+ Justin
-- Aeolus Community Manager http://www.aeolusproject.org
I just realized i /missed/ the [1,2]
[1] https://github.com/jrom/jrom.github.com && http://jrom.net [2] https://help.github.com/articles/using-jekyll-with-pages
Forgive me plz :)
Cheers, Francesco
On Thu, Jun 28, 2012 at 03:51:28PM +0200, Francesco Vollero wrote:
Hello list,
I am documentating and research about the opportunity in $subj to migrate our static website from nanoc + few accounts able to access our www machine to the opportunity to have it hosted on github pages. Mainly the idea to suggest this method is because the current solution is:
- Complex (deal with haml and nanoc)
- Not everyone in the team can update the page (lack of permissions)
- Usually is time wasting to update it (nanoc time + fix time + ɛ * rand() ) ( ɛ = epsilon)
I did a small list of pro and cons about this migration:
Pros:
- Far more easy deploy phase
- Reducing delays for website updates.
- _Everyone_ within the team in github can update those pages.
- Easy and _straightforward_ MarkDown syntax without tab/spaces weirdness
Cons:
- Migrate haml to md+liquid (isn't really complex)
- Change a bit the layout + styling (e.g. [1,2])
Please let me know your thoughts about it,
Cheers, Francesco Vollero
On Fri, Jun 29, 2012 at 12:04:19AM +1000, Justin Clift wrote:
On 28/06/2012, at 11:51 PM, Francesco Vollero wrote:
<snip> > Pros: > * Far more easy deploy phase > * Reducing delays for website updates. > * _Everyone_ within the team in github can update those pages. > * Easy and _straightforward_ MarkDown syntax without tab/spaces weirdness > > Cons: > * Migrate haml to md+liquid (isn't really complex) > * Change a bit the layout + styling (e.g. [1,2]) > > Please let me know your thoughts about it,
As a thought, are we able to test/trial this somehow?
test.aeolusproject.org or something?
Well, surely we can be able do to so, I was tempted to do a staging solution first, to see that everything was working in the right way.
Cheers, Francesco
- Justin
-- Aeolus Community Manager http://www.aeolusproject.org
On 29/06/2012, at 12:09 AM, Francesco Vollero wrote:
On Fri, Jun 29, 2012 at 12:04:19AM +1000, Justin Clift wrote:
On 28/06/2012, at 11:51 PM, Francesco Vollero wrote:
<snip> > Pros: > * Far more easy deploy phase > * Reducing delays for website updates. > * _Everyone_ within the team in github can update those pages. > * Easy and _straightforward_ MarkDown syntax without tab/spaces weirdness > > Cons: > * Migrate haml to md+liquid (isn't really complex) > * Change a bit the layout + styling (e.g. [1,2]) > > Please let me know your thoughts about it,
As a thought, are we able to test/trial this somehow?
test.aeolusproject.org or something?
Well, surely we can be able do to so, I was tempted to do a staging solution first, to see that everything was working in the right way.
That sounds like a good idea then. We can make sure it doesn't suck first :), then switch to the new home page if/when people are happy with it.
+ Justin
-- Aeolus Community Manager http://www.aeolusproject.org
----- Original Message -----
On 29/06/2012, at 12:09 AM, Francesco Vollero wrote:
On Fri, Jun 29, 2012 at 12:04:19AM +1000, Justin Clift wrote:
On 28/06/2012, at 11:51 PM, Francesco Vollero wrote:
<snip> > Pros: > * Far more easy deploy phase > * Reducing delays for website updates. > * _Everyone_ within the team in github can update those pages. > * Easy and _straightforward_ MarkDown syntax without tab/spaces > weirdness > > Cons: > * Migrate haml to md+liquid (isn't really complex) > * Change a bit the layout + styling (e.g. [1,2]) > > Please let me know your thoughts about it,
As a thought, are we able to test/trial this somehow?
test.aeolusproject.org or something?
Well, surely we can be able do to so, I was tempted to do a staging solution first, to see that everything was working in the right way.
That sounds like a good idea then. We can make sure it doesn't suck first :), then switch to the new home page if/when people are happy with it.
- Justin
-- Aeolus Community Manager http://www.aeolusproject.org
Yea, I'd love to see a staging run of this to make sure we can keep it looking pretty and that the auto-updating of pages is auto as github claims.
I think the pro's that you listed are HUGE wins really and make this a much easier job to distribute across the team.
Thanks for getting the ball rolling!
Mike
On Thu, Jun 28, 2012 at 03:51:28PM +0200, Francesco Vollero wrote:
Hello list,
I am documentating and research about the opportunity in $subj to migrate our static website from nanoc + few accounts able to access our www machine to the opportunity to have it hosted on github pages.
Yes! I'm one of a few people who has his key on the webserver so that I can push updates, but I'm never sure _how_ to do it, and when I finally find my notes on it, I'm still terrified of breaking something. It's a needlessly complex process. The ability for anyone with commit rights to be able to update the site -- by just doing a push -- is a huge win IMHO.
A small added bonus, I think, is that it makes us that much more of an independent project, versus something hosted on Red Hat infrastructure.
However, one thing I think we need to sort out -- right now we have Redmine running at aeolusproject.org/redmine. If we just moved the static site, that would start to 404, and I'm willing to bet you can't do rewrite rules on GitHub Pages.
It seems like the ideal solution would be to move Redmine to redmine.aeolusproject.org, though that does make the change a bit more disruptive.
-- Matt
On 06/28/2012 04:42 PM, Matt Wagner wrote:
The ability for anyone with commit rights to be able to update the site -- by just doing a push -- is a huge win IMHO.
I don't think I've seen this before, from my experience the static site is usually maintained by a few individuals w/ most of the editable content being on a wiki or similar.
That being said, I'm not against this, and would be down to try it out to see if it works.
-Mo
aeolus-devel@lists.fedorahosted.org