Merge lp:~nskaggs/autopilot/apdocs-restruct into lp:autopilot
| Status: | Merged |
|---|---|
| Approved by: | Leo Arias on 2015-01-22 |
| Approved revision: | 528 |
| Merged at revision: | 533 |
| Proposed branch: | lp:~nskaggs/autopilot/apdocs-restruct |
| Merge into: | lp:autopilot |
| Diff against target: |
185 lines (+86/-53) 4 files modified
docs/_templates/indexcontent.html (+74/-44) docs/contents.rst (+3/-0) docs/index.rst (+9/-6) docs/tutorial/tutorial.rst (+0/-3) |
| To merge this branch: | bzr merge lp:~nskaggs/autopilot/apdocs-restruct |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-01-22 | |
| Allan LeSage (community) | Approve on 2015-01-22 | ||
| Christopher Lee (community) | Approve on 2015-01-21 | ||
| Thomi Richards (community) | Needs Fixing on 2015-01-20 | ||
| Leo Arias | 2015-01-15 | Needs Information on 2015-01-16 | |
|
Review via email:
|
|||
Commit Message
Initial restructuring for the autopilot docs.
Description of the Change
Initial restructuring for the autopilot docs. I pulled out specific sections to shorten the tutorial and make them more prominent on the contents page instead.
| Leo Arias (elopio) wrote : | # |
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:521
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Leo Arias (elopio) wrote : | # |
I like how the index looks. But shouldn't you move these files:
79 + tutorial/
81 + tutorial/good_tests
82 + tutorial/running_ap
out of the tutorial directory?
| Nicholas Skaggs (nskaggs) wrote : | # |
Leo, I suppose so. Perhaps I'll create another directory to house them.
| Nicholas Skaggs (nskaggs) wrote : | # |
Reminder for that balloons guys; add installing_
| Christopher Lee (veebers) wrote : | # |
I get a warning when building the docs:
..snip.
The order that the resulting menu has me pondering what the order should be.
Personally I read the column: 1st column top-to-bottom then the 2nd column top-to-bottom.
This means I see the API reference and appendice before I see mention of the tutorial.
(This way of reading it seems correct with the original layout).
If I'm an oddball though, and the only one that doesn't read it that way then this is ok. I suspect that I'm not though (i.e. reading columns, newspapers for instance, is really top to bottom then next column.) (I might still be an oddball, but not when it comes to reading columns).
| Leo Arias (elopio) wrote : | # |
That warning is fixed in a branch by thomi. Seems to come from before.
| Nicholas Skaggs (nskaggs) wrote : | # |
> The order that the resulting menu has me pondering what the order should be.
>
> Personally I read the column: 1st column top-to-bottom then the 2nd column
> top-to-bottom.
>
I obviously read left to right, then top to bottom. So left, right, next row and so on. I will change it to read like a newspaper. I suspect I might be alone in reading it this way.
| Thomi Richards (thomir) wrote : | # |
I agree with veebers' comments, and added one of my own. Otherwise, looks good.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:524
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:525
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:526
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Allan LeSage (allanlesage) wrote : | # |
Following these changes, arrived late, no objection.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:527
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://

Makes sense to me. I haven't built the docs yet, I will do it after lunch.