In PageSeeder terminology, ‘list’ is interpreted as the generic description for ordered
(<nlist>) or unordered (
<list>) items (
<item>) in a document, not as the programming term for a type of data structure.
Because the PageSeeder information architecture is deliberately oriented to documents/publications being composed of multiple files, the editing and storage view of a list is typically incomplete. Additional values such as prefixing items with a heading number aren’t supported for
<item> but require a numbered <para>. When order of the documents is final and the collection is published, these values are added programmatically by the process task when the files are sent to a website or docx file.