[SeasonOfDocs] Information Architecture

[Clarence Cromwell]

I agree with the idea of creating units of content first and deciding on the architecture later. 

We can know what templates and best practices we need without resolving architecture, and taking time to think about it will probably make architecture better.

I’m in favor of creating repos, and making space to talk about architecture, whether in a repo, a Google doc, or wherever.

Sent from my iPhone

> On Jul 11, 2019, at 3:00 AM, Jo Cook <jo.k.cook at gmail.com> wrote:
> 
> Hi Cameron,
> 
> To clarify, I'm not specifically referring to the action I had to start collating ideas about the structure of tGDP- sure I'll create that in google docs. I was thinking more generally about starting to use tGDP organisation/family of repositories on github to start collecting things, and to be a public-ish location for those people (Google/Uber/Atlassian employees for instance) that need something that they can point their respective organisations to. It's not a big deal though :-)
> 
> Jo
> 
>> On Thu, Jul 11, 2019 at 10:53 AM Cameron Shorter <cameron.shorter at gmail.com> wrote:
>> Jo, I suspect it might be easiest to bootstrap your ideas in a Google doc that you share and get comments. It is quick and dirty and can be thrown away after a few weeks.
>> 
>> 
>> 
>>> On 11/7/19 6:17 pm, Jo Cook wrote:
>>> Hi Cameron,
>>> 
>>> I really meant temporary repositories for information while we get things up and running. If we start with the website structure, IMHO we have to decide on how that's going to work before we can think about getting any content in. My thought was just to get *something* in place that's publicly accessible (for, say, licensing discussions) and then move to sorting out the website and the official structure of the project when we've had time to think things through properly.
>>> 
>>> Regards
>>> 
>>> Jo
>>> 
>>>> On Wed, Jul 10, 2019 at 9:15 PM Cameron Shorter <cameron.shorter at gmail.com> wrote:
>>>> Jo, I think this doc structure idea is important enough to break into a new email thread and get it's own title. I'm hoping to see ideas debated here.
>>>> 
>>>> I'm erring toward thinking that all our material should fit within a website folder. Also, I'm not sure planning deserves it's own folder. Instead I'm thinking it should just be thought of as a development branch of all the content.
>>>> 
>>>> If we continue to align ourselves with WriteTheDocs, as we are considering, we should also consider how we fit within https://www.writethedocs.org/
>>>> 
>>>> So I'm thinking our structure could be:
>>>> 
>>>> WriteTheDocs Website
>>>> 
>>>> + <other WriteTheDocs pages>
>>>> 
>>>> + WriteTheDocsGuide / TheGoodDocsProject -> external link to our guide.writethedocs.org or similar
>>>> 
>>>> ++ Index.html (introduction and jump page)
>>>> 
>>>> ++ Community/
>>>> 
>>>> +++ CodeOfConduct.html
>>>> 
>>>> +++ Governance.html (our decision making processes)
>>>> 
>>>> +++ DevelopmentProcess.html (This is likely big enough to be split out from Governance)
>>>> 
>>>> +++ CommunicatonChannels.html (how we talk with each other and how to get involved)
>>>> 
>>>> ...
>>>> 
>>>> ++ Templates/
>>>> 
>>>> +++ Quickstart/
>>>> 
>>>> +++ Template.html
>>>> 
>>>> +++ Guide.html (how to use the guide)
>>>> 
>>>> +++ Background.html (Where we discuss metadata concepts and research about the Quickstart)
>>>> 
>>>> ...
>>>> 
>>>> ++ Information Architecture
>>>> 
>>>> +++ <site wide information architecture theory>
>>>> 
>>>> +++ StarRatingSystem.html (Not sure if this deserves it's own directory)
>>>> 
>>>> 
>>>> 
>>>>> On 11/7/19 2:28 am, Jo Cook wrote:
>>>>> Hi Felicity,
>>>>> 
>>>>> Thanks for taking notes- it looks good to me. I was also thinking about getting some proto-repositories going on github- with suggested headings of:
>>>>> 
>>>>> * governance- for holding (for now) the Code of Conduct, details of PSC, licensing discussions etc
>>>>> * planning- for my nascent document on project structure
>>>>> * website
>>>>> 
>>>>> That way we can use the wikis in the various repositories for some of our discussion documents rather than google docs. I still like the idea of google docs for the first-pass collaborative commenting on quick starts though.
>>>>> 
>>>>> Thoughts?
>>>>> 
>>>>> Jo
>>>>> 
>>>> -- 
>>>> Cameron Shorter
>>>> Technology Demystifier
>>>> Open Technologies and Geospatial Consultant
>>>> 
>>>> M +61 (0) 419 142 254
>>>> _______________________________________________
>>>> SeasonOfDocs mailing list
>>>> SeasonOfDocs at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>>> 
>>> 
>>> -- 
>>> ------------------------
>>> http://about.me/jocook
>> -- 
>> Cameron Shorter
>> Technology Demystifier
>> Open Technologies and Geospatial Consultant
>> 
>> M +61 (0) 419 142 254
> 
> 
> -- 
> ------------------------
> http://about.me/jocook
> _______________________________________________
> SeasonOfDocs mailing list
> SeasonOfDocs at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/seasonofdocs/attachments/20190711/ba7d707d/attachment.html>