Minor Manual Overhaul. Add appendixes and Rename "Current status" to 'Release Notes"

[porres]

We now have a current PR with a better organization and chapter names of the manual, see #296

I have big plans for a big overhaul of the manual, see #225

The idea is to reorganize all chapters but now that we have these descriptive names, I thought it's a good time to make a minor change that was already planned.

So, instead of

4.externals.htm
5.current.status.htm
6.building.from.source.htm

we could have

4.Appendix.I.externals
5.Appendix.II.building.from.source.htm
6.Appendix.III.release.notes

[ben-wes]

my 2 cents: the rearrangement makes sense to me. also renaming to release.notes. but i would omit the additional Appendix.I+. since the descriptive names allow users to decide themselves what to consider an appendix. so it would be just:

4.externals.htm
5.building.from.source.htm
6.release.notes.htm

... maybe 4 could even be slightly more descriptive for people that are not yet familiar with "externals"?:

4.externals.and.libraries.htm

[porres]

maybe 4 could even be slightly more descriptive f

4.installing.externals

but i would omit the additional Appendix.I+. since the descriptive names allow users to decide themselves what to consider an appendix.

I think we should organize the manual with appendixes as "extra" and focus on the operation of Pd. But I agree this may not be exposed in the file name

[porres]

So, I guess, for now, just to make things simple, we can just rename these files and chapters, and reorder them

[porres]

working on it on this branch

[umlaeute]

it would be great however, if we could find a stable naming scheme, so that links to the homepage will keep working.

obviously renaming the resources/chapter1.htm to 1.introduction.htm will always break it (and it cannot be helped, except with some symlinks).

however, i would like to stress that we should find a naming scheme, where simply adding a new chapter will not break any links.

(my personal motivation for this is, that i use some scripts that parse the content of the release-notes HTML, without my interaction. I would hate if this kept breaking just because new chapters pop up and down.)

[ben-wes]

we should find a naming scheme, where simply adding a new chapter will not break any links.

while i obviously agree with this, i'm not sure about the consequences. if @porres finds a more appropriate scheme that makes it into the same Pd version as the pending PR, it would be fine, i guess?

or should we generally try to find a way to make this more flexible concerning chapter addition? that would probably mean that we omit the numbers, which doesn't seem like an option (or does it?)?

[umlaeute]

i guess i'm mostly saying that we should properly think about the names now rather than treat it as "don't care".

i tend to agree with porres idea of separating the actual Pd manual from more general/specialist things, like building-externals or release-notes. (i'm not entirely sure about the "externals", but nevermind).
so we probably want to keep these two sections apart.
maybe something like

A.01_introduction.htm
A.02_theory_of_operation.htm
A.03_installing_configuring.htm
A.04_externals.htm
B.01_current_status.htm
B.02_building_from_source.htm

or somesuch; i don't care much about the actual numbers or titles; but a short prefix (e.g. A.) gives us nice sortable grouping