Website restructuring

Jiří Stránský jstransk at redhat.com
Thu Nov 15 16:36:23 UTC 2012


On 13.11.2012 17:00, Matt Wagner wrote:

<snip>

>
>> * Projects - the thing that Mo has done. We have so many components now that people deserve a special page just to get the 3048 meter (ten thousand foot) view of Aeolus.
>
> https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Aeolus_Components
> has some overlap too, I think, though it's more about what currently
> exists.
>
>> * Install - describe how to download and install Aeolus. "Get It" is fine too, but I just think "Install" is clearer and more common. Regarding content of the page, we should decouple it from Fedora, as discussed on the Conference.
>
> +1
>
> Does this entail squashing 'Get It' and 'Use It' into one section?

It's more like renaming 'Get It' to 'Install' and putting there instructions for also other systems than Fedora. And 'Use It' in my opinion should get away in favor of Docs page, and on the Docs page the first link can be 'Tutorial', which would be what we now call 'Use It'. Docs page would also contain other links. See below.

>
>> * Docs - point of origin when you search for tutorials, reference guides etc., regardless of who you are. Link to our usage guide with screenshots, links to GitHub wikis (when we have them) of various subprojects, links to API docs. We should make clear what links are for what "persona". I'd differentiate here between three groups: Admins (Sam, the sys admin - installation and setup), Users (Dennis, the app designer + Carl/Bert, the infrastructure consumer - clicking and CLIing), Developers. -- Yeah, Mike, the develper persona might be useful :)
>
> This makes a lot of sense to me. Though I'm not sure how to present the
> personae information in a way that will be clear to new users, who
> probably won't think of themselves as "Connor the Infrastructure
> Consumer" or whatnot.

I could see 3 subheadings on the Docs page.

* For Admins (related to aeolus-configure and similar)
* For Users (related to Conductor WUI and CLI mostly)
* For Developers (related to API mostly)

I wouldn't squeeze much info here, the Docs page should not be much more than a set of links to proper documentation (documentation itself can be on the website or GH wikis or both).

>> * Contribute - information for everyone who wants to help. What stuff we need - helping newbies, updating tutorials, writing code etc. and how should people get involved (installation for development, finding easy "onboarding" stuff to work on, etc.).
>
> We have really bad docs here right now, I think. So this could be good.
> That said -- how many people are actually trying to contribute right
> now?

IMO that's a chicken and egg problem. There can't be many people trying to contribute if we don't give them any info. Currently, the aeolusproject.org site doesn't look like we want/appreciate contributions. I'd like to change that.

A thing worth noting - I don't consider just pull requests as contributions, it could be also helping newbies on #aeolus so that we don't have to do it, it could be packaging for Debian or whatever. But again, I think we can't expect people to do that unless we actually tell them that we'd like them to do that. I'd like to bring this up on the next Website Cabal and take creating the "Contribute" page as my responsibility, if we agree that we want to have it.

>> * Blog - feed from our external blog. (Or, we could move the blog to be part of the website. Not sure if there would be issues with this though.) We could get rid of News section, as Mo did in his pull request. I think Blog/News are largely overlapping and we might struggle to find enough items for News section alone. Or, should News stay, I'd let them be only on the Home page with some link to show older news, but I wouldn't put that into main menu. I believe this main menu item wouldn't be used much.
>
> Can we just make this a link to blog.aeolusproject.org? That would, by
> far, be the easiest choice.
>
>> * Contact / Need help? / something else? - not sure of the name here, but the purpose of the page is the same as we have it now - document our communication channels, allow people to reach out for help or give feedback.
>
> Agreed, though I'd like to give the Contact page some TLC since right
> now I think it's kind of overwhelming. (IMHO).
>
> What about the News tab? Does that just fall under the Blog and/or get
> duped on the homepage?

The blog/news issue has been solved on the Cabal, others please see:
https://lists.fedorahosted.org/pipermail/aeolus-comm-mgmt/2012-November/000012.html

J.



More information about the aeolus-comm-mgmt mailing list