Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.the http://aegirproject.org/ site is pretty, but not very helpful. it redirects to the community site, which in itself directs users (vaguely) to the obscure install instructions which are basically a wall of text explaining in excrutiating details all the possible ways to install aegir.
we should, instead, have something like what http://getdevshop.com/ is doing: simple bullet point explanation of what aegir does, and two liner to install it:
echo "deb http://debian.aegirproject.org stable main" | sudo tee -a /etc/apt/sources.list.d/aegir-stable.list
curl http://debian.aegirproject.org/key.asc | sudo apt-key add -
sudo apt-get update
sudo apt-get install aegir
okay, it's not a two-liner.... but it's pretty much the shortest we can get.
as for the bullet points of aegir, what should it be?
1. aegir is the place where we put in common our Drupal deployment tools and strategies instead of writing our own little shell scripts over and over again on our own
2. aegir allows you to manage and deploy large numbers of drupal installs on multiple server clusters
3. aegir is extendable through drush and of course drupal and supports a wide array of functionality through contrib modules
So those could be rephrased, but that's the rough general idea.
Now the concern with the static website is that not everyone can contribute to it. Now one thing we could do about that is setup something like the github pages where the content is on a git repository (hosted on d.o of course) but that gets pulled into a system like Ikiwiki (hard to theme?) or jekyll (ruby, github-specific)










Comments
Comment #1
ergonlogicI agree that our install instructions need fixing. I think for Aegir2 we should start from scratch; archive the Aegir1 docs, then have one page per OS. I know this means duplication, but right now everyone has to wade through lots of stuff that's irrelevant to them, and it's all terribly confusing.
As for allowing others to participate, I don't know why we'd need Jekyll, or whatever. Couldn't we just drop the HTML/CSS into a d.o project, and occasionally 'git pull' wherever we're hosting the static site? We could set up a regular 'git pull' in a cron job, if we want to make the deployment fancier, and we could always switch to Jekyll or whatnot, if anyone wants to invest the time.
I've gone ahead and done the first step (see: https://drupal.org/project/aegirproject_org) and added all the Aegir maintainers. Also, I went ahead and updated the site (still basic html/css), as per the suggestions above, with my take on the suggested bullet points. Obviously, feel free to modify it as you like. I've also deployed the site on our ci/archive server: http://new.aegirproject.org, so all we need is to switch the DNS, and we're ready to go live.
Comment #2
ergonlogicActually, I'll be bold here, and redirect the DNS to the new site. All the maintainers have access, so just go ahead and fix anything you find lacking. Any way you look at it though, the new one is better than the old (which is still available at http://old.aegirproject.org, btw.)
Comment #3
anarcat CreditAttribution: anarcat commentedthis looks awesome.