My current thoughts are this.
We tweak the module formatter code so it makes new pages like:
modules/modules_cloud.rst
modules/modules_networking.rst
etc
And in page that we auto-generate, it links to pages that are also
auto-generated like:
modules/module_foo.rst
As a result, each module will appear on it's own seperate page.
You will first go to the "Cloud" page to see all the cloud modules, and
then click on the module you want from the list.
In the left hand index, when you click to expand modules, you'll see all
the categories below and can quickly hop to a per-category index.
If someone wishes to have at, please do, otherwise I may take a look at
this starting around the 26th or 27th.
While we might not want to split all the modules into different pages just
yet for easy browseability, I think we'll still be able to show a full list
(TOC tree) on the "modules" page that will satisify most folks.
This should mean we can have the new docs theme pushed before the first of
the year.
So far I think this is a big improvement, we just need to make it work for
the modules list, which is obviously the docs that people come back to the
most.
On Tue, Dec 24, 2013 at 6:12 PM, Michael DeHaan <[email protected]>wrote:
> Ok, I have everything in the tree looking pretty awesome if people want to
> try "make docs" and look around.
>
> I could still use some help making module navigation good -- right now it
> needs some work. This might mean splitting modules up into seperate
> category pages -- and that's easy -- but I'd like other ideas or approaches
> if we can do something better.
>
> To make it easy to tweak the theme I have a copy now in docsite/_themes
>
> Thanks!!!
>
>
> On Tue, Dec 24, 2013 at 5:22 PM, Michael DeHaan
> <[email protected]>wrote:
>
>> Thanks for this -- This looks QUITE excellent and I'm going to push
>> changes to make this what we are using in the source control tree shortly.
>>
>> It looks like we may need to restructure things in a few places to make
>> sure everything starts with the right level of depth, and so that the
>> modules are still easily skimmable.
>>
>> It might be that we need to generate a different module index page for
>> each category, but I'm hoping we can do something more clever.
>>
>>
>>
>>
>> On Tue, Dec 24, 2013 at 5:01 PM, Michael DeHaan <[email protected]
>> > wrote:
>>
>>> I haven't and that looks really good for the index, I'll have to see
>>> what it docs to our templates.
>>>
>>> (We might still need to do something custom-ish for the modules index at
>>> least?)
>>>
>>> Seems a bit dependency heavy in the GitHub info but maybe not too bad.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Dec 24, 2013 at 4:52 PM, Mikhail Sobolev <
>>> [email protected]> wrote:
>>>
>>>> Just out of curiousity (I'm not a web designer :)), did you consider
>>>> using readthedocs.org's theme (
>>>> https://github.com/snide/sphinx_rtd_theme) ?
>>>>
>>>> --
>>>> Misha
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Ansible Project" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>
>>>
>>> --
>>> Michael DeHaan <[email protected]>
>>> CTO, AnsibleWorks, Inc.
>>> http://www.ansibleworks.com/
>>>
>>>
>>
>>
>> --
>> Michael DeHaan <[email protected]>
>> CTO, AnsibleWorks, Inc.
>> http://www.ansibleworks.com/
>>
>>
>
>
> --
> Michael DeHaan <[email protected]>
> CTO, AnsibleWorks, Inc.
> http://www.ansibleworks.com/
>
>
--
Michael DeHaan <[email protected]>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
