Okay, some user feedback... Would prefer not to land on the cwiki 'Index' page.
E.g. Wikipedia tells people the project page is http://cloudstack.org/ , which redirects to http://incubator.apache.org/cloudstack/ From here, you clikc 'Apache CloudStack Wiki and get to http://cwiki.apache.org/confluence/display/CLOUDSTACK/Index , which is the index. Would prefer faster page. It takes 30s (I timed it) for the link about to load. I think this is specific to the 'index' page, but I could be wrong. Finally, and apologies if this is covered under a thread earlier this week, where do all things related to a feature go? E.g. I'd like to note the setup instructions for Hyper-V dev environment. This isn't quite design, but it is a developer thing. Should I put a child under the design, or should there be a feature specific page? DL -----Original Message----- From: Alex Huang [mailto:alex.hu...@citrix.com] Sent: 19 December 2012 9:54 PM To: cloudstack-dev@incubator.apache.org Subject: RE: Changes to the wiki > > The top level structure is clean now, but we still have a bit of a > mess within the top sections. It might make sense to have people sign > up to clean/up and structure each top level section. I'll start by > doing the "Releases" section (which, yes, I know is easy). Yes. Each top level section requires someone to go through and think about what that type of user wants to see and add pages for them. For example, under operators(which I welcome a better name, maybe Administrators?), I can see at least Deploying tips, Debugging tips, Dealing with bugs, FAQ, Deployment Stories, Use cases, etc as top level page. Like I said in a previous email, I had wanted the current top level pages to be tabs with table of content inside each tab but I just couldn't find a way to do it that way, at least not with my privileges on confluence. --Alex
