Reviewed geoext QuickStart

[flicstar]

Reviewed as part of the QuickStart project during Google Season of Docs 2019. The aim is consistency across all OSGeoLive QuickStarts. Also see PR 498 #498

The document is structured well and only requires minor changes.

@geographika Please action comments and suggestions you agree with, and ignore those you don't.

Partner trac ticket link: https://trac.osgeo.org/osgeolive/ticket/2195

See this page for reference: https://trac.osgeo.org/osgeolive/wiki/How%20to%20document%20the%20quickstart%20file

[geographika]

@flicstar - changes look good. A few comments:

• The underlining for subtitles / headings needs to be the same length or Sphinx gives warnings. E.g.

Create an HTML Page
---------

doc\quickstart\geoext_quickstart.rst:24: WARNING: Title underline too short.

• In terms of styling, should all subheadings be in title case? E.g. "Configure OpenLayers objects" should be "Configure OpenLayers Objects". This is currently inconsistent.

• Sphinx allows autoenumerated lists/steps of paragraphs using # - see here. Should these be recommended or avoided? It helps keeps the numbering correctly ordered, but writers need to know the syntax.

[flicstar]

Thanks @geographika I update the heading markup and also made them title case. I think my preference is for sentence case but sometimes it's hard for me to know which things are proper nouns and so require capitalization. Also the 'What Next' at the end does look better as title case and consistency is important.
In terms of the numbering, I tried to always use the hash symbol except for when I found that if a procedure had anything nested like code blocks or images, it tended to restart at 1 in the middle of a procedure.

[geographika]

@flicstar - see flicstar#1
With regards to the numbering - any code or image blocks have to be indented in line with the start of the text after the numbering - so typically 3 spaces to match #.

[flicstar]

@geographika Any idea why these "numbers" are displaying as hash symbols rather than numbers? Argh! I can see your tip about indenting the codeblocks has worked in the later sections, thanks!

[geographika]

@flicstar - see flicstar#2 - the text also has to be aligned with the block.

[flicstar]

http://irclogs.geoapt.com/osgeolive/%23osgeolive.2019-11-26.log

20:14:30 sethg: "mapserver, mapcache, geoext can all be considered approved"