You can see I already created two tasks: * Create skeleton of Apache CMS for website * Create content page: index
Just keep going and add the other pages as one task each. So the next would be "Create content page: what is openaz" or something close to that. And you just keep going. Skip descriptions for now. It would be ideal if you could create a Website Epic, and assign them to it. But we can do that later, too. Once we have tasks in there, we can prioritize and assign them out. My priorities are first most on the skeleton, and next on the index and any pages for contributors. On Wed, Apr 20, 2016 at 2:22 PM, David Ash <[email protected]> wrote: > Nevermind, I see that you are. :-) > > Previously, I came up with a top-level map that detailed the pages. > > > I. Homepage >> - What is Apache OpenAZ? (very briefly, marketing material) >> - Release information >> - Links > > > >> >> II. General information >> - About (maybe more detailed) >> - License >> - FAQ > > > >> >> III. Download > > > >> >> IV. Documentation >> - Quick start guide >> - Detailed documentation >> - Wiki > > > >> >> V. Support > > > >> >> VI. Community >> - Mailing lists >> - Bug reports >> - Developer information >> - Contributors >> - Sponsors / Sponsorships > > > > Does anyone have any objections to using this as the sitemap for now? > > If not, Farasath, could you create new tasks in Jira for each page? We > need to break it up so different people can do different things. > > Also, we're going to need the repo you found mirrored on github. Do you > know/have the ability to make that happen, so the github URL would be: > > https://github.com/apache/incubator-openaz-site > > > > On Wed, Apr 20, 2016 at 2:14 PM, David Ash <[email protected]> wrote: > >> Awesome! Are you signed up on the Jira? >> >> On Wed, Apr 20, 2016 at 2:07 PM, Farasath Ahamed <[email protected]> >> wrote: >> >>> When creating content I would like to give a hand. Let's get started :) >>> >> >> >
