Change order of codelists in Reference

[JachymHercher]

When going through OCDS, I often go directly to one of the codelists in https://standard.open-contracting.org/latest/en/schema/codelists/, but then I am unsure whether it is open or closed, so I scroll up or down to find which section it is in. This seems a bit clumsy.

1. Wouldn't it be better if each codelist has an [open] or [closed] attribute below/after it's title?
2. If we added such an attribute, we could also remove the open / closed subsections. I'm not sure how useful they are (do people want to read about "all closed codelists" in one go? Seareching for codelists probably happens via ctrl-f.) and we could then have the same sorting across the whole page (see below).
3. I'm not sure how the codelists are sorted. Doesn't seem to be alphabetical, by importance, nor chronological? I would go by importance/chronology.

(This issue is about ordering codelists as whole, #1198 is about ordering codes within codelists.)

[jpmckinney]

To avoid merge conflicts, and since the reference section for 1.1 is frozen, I've moved this to 1.2.

In #1075 I suggest one page per codelist, because some codelists are extremely long (like currency).

In that case, we will definitely need a way to indicate open/closed in an easily recognizable way.

To make it easier to find a known codelist, we can sort the codelists alphabetically in the navigation.

On the landing page for all the codelists (e.g. /schema/codelists/), we can instead logically group and order the links to the individual codelist pages (e.g. a Status section with Tender status, Award status, Contract status, Milestone status, in that order). This grouping would be easier for people who are discovering or learning about the standard.

[duncandewhurst]

@jpmckinney your suggestions sound good to me. I think that @odscjen or I can progress with this issue as follows:

1. Move codelists to individual pages
2. Add a badge below each codelist page title to indicate whether the codelist is open or closed. The badges can link to the sections of the codelist landing page that explain open and closed codelists.
3. Order the codelist pages alphabetically in the navigation
4. Propose a grouping and ordering for the links from the codelist landing page to the individual codelist pages

Are you happy for one of us to do that?

[jpmckinney]

Yes, but please check all open PRs to review whether any touch the same pages. If there are any, you can report your findings here and we can decide how to proceed.

[duncandewhurst]

The only PR that touches codelists.md is #1660. It makes one non-whitespace change.

However, links to codelist documentation will need to be updated, e.g. ../../schema/codelists.md#party-scale will change to ../../schema/codelists/party_scale. I think that will cause conflicts with the following changes:

#1660:

• https://github.com/open-contracting/standard/pull/1660/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L14
• https://github.com/open-contracting/standard/pull/1660/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L46

#1680:

• https://github.com/open-contracting/standard/pull/1680/files#diff-ad7a21639d13433e0d0f06126a4ce0f979ab8e86ed7f6a28a439df33458419c9L27
• https://github.com/open-contracting/standard/pull/1680/files#diff-af676d9a2255c8a21a90169ef19b49248b12212bb6e4663a92102f2bde4c7114L34
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L13
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L14
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L26
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L46
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L46
• https://github.com/open-contracting/standard/pull/1680/files#diff-0a32de0359d87c42644de479f85c247d27d5f0dbb0959f162fb4b8b9389b1bb6L46

Shall we prepare the PR without updating links and leave it as a draft until at least #1680 is merged?

[jpmckinney]

You can start on the PR, without updating links :)