Skip to content

lists are not nested properly #348

@TallTed

Description

@TallTed

It is clear that some of these unordered lists are meant to be nested within some of these ordered lists. There might be some ordered lists that are meant to be nested within some of the unordered lists. It is not clear to me exactly what nesting is intended, especially where there might be more than 2 levels, partly because the numbering is all 1..

1. The FO Assignee produces a Team Report:
* The Team Report is circulated to the Team for review (one week review time)
* The Team Report is circulated (at the same time or after Team review) to both parties.
1. The FO Assignee updates the [Formal Objection dashboard](https://www.w3.org/Member/wiki/DirectorFOdashboard).
1. The Council Team Contact drafts an announcement and call for dismissal reasons with a minimum deadline of two weeks (See this [example](https://lists.w3.org/Archives/Member/w3c-ac-members/2024JanMar/0021.html), and the [Council composition](https://www.w3.org/policies/process/#council-composition)).
* Announcement is sent to the AC members list
1. The Council Team Contact creates a new [Group](https://www.w3.org/admin/othergroups/list) (name should be _Council-YYYY-MM-\<readable shortname>_) in the db, filled with all the potential members of this Potential Council

This (with 2 spaces preceding the *) —

1. text
1. text
  * text
  * text
1. text

— renders as (modulo blockquote), putting the unordered list on the same level as the ordered lists, and restarting the numbering of the ordered lists, i.e., starting a new ordered list at 1

  1. text
  2. text
  • text
  • text
  1. text

While this (with one additional space before the *, aligning it with the text of the superior numbered item) —

1. text
1. text
   * text
   * text
1. text

— renders as (modulo blockquote), putting the unordered list on the next level down from the ordered list, and continuing the numbering of the ordered list, i.e., not starting a new ordered list at 1

  1. text
  2. text
    • text
    • text
  3. text

Nitpicky? Yes.
Clarity over all? Please.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions