[Governance] Article / paragraph content display - V2

[ChaimaaZaoui]

Feature: [Governance] Article / paragraph content display - V2

As a an end-user,
I want to explore the governance of a Data space
So that I read the terms and conditions of its section, subsections, articles and paragraphs

Acceptance criteria

Scenario 1: Paragraph order

Given that I am an end user navigating the governance page of a data space
When an article has more than one paragraph
Then the paragraphs are to be ordered following their order in the ontology
And the display order is horizontal

Normal desktop / Tablet

Large desktop

Mobile

Scenario 2: Scroll bar in a container

Given that I am an end user navigating the governance page of a data space
And I am using a desktop device,
When an article has more than 10 paragraphs
Then the height of the container remains fixed
And a scroll bar is available on the right of the container to scroll down and up the paragraphs
And it uses an infinite scroll, that mean the more i scroll down the more subsections are displayed (ideally with no delay)

When the article has 8 or less paragraphs
Then the height of the container is to be adapted

Scenario 3: Paragraph card

Given that I am an end user navigating the governance page of a data space
And I am using a desktop, mobile or tablet device,
When a paragraph is available in an article
Then the maximum lines displayed in its description are 3
And the height of the paragraph cards are all identical

When more than 3 lines are in the description
Then a see all button is on the top right of the paragraph card
And an ellipse ... at the end of the description is to be added to show that there is more to read

When the paragraph title is too long and there is no see all button
then its displayed maximum on two lines
And and ellipse at the end of the two lines

When the paragraph title is too long and there is a see all button
then its displayed on one line with an ellipse

Scenario 4: Internalisation

ENG
See all

FR
Afficher plus

DE
Mehr lesen

Resources

Mockups

Environment

• staging URL: https://app.staging.okp4.network/

Additional informations

None.

┆Issue is synchronized with this Wrike task by Unito

[ChaimaaZaoui]

• - title, description, and value statement
• - acceptance criteria (scenarios)
• - mockups (all devices and themes)
• - labels added
• - US presented to DEV team (refinement)
• - attached to an epic
• - estimation (planning poker)
• - external dependencies if applicable

[ChaimaaZaoui]

Hey team! Please add your planning poker estimate with Zenhub @0xLodz @AnjaMis @ErikssonJoakim @fredericvilcot @lolottetheclash

[loiclaudet]

the paragraphs are to be ordered following their order in the ontology

Is the order related to paragraph number from the ontology? e.g. Paragraph 1.1.1.1.1, 1.1.1.1.2, ... Or the list order fetched from the ontology? May be the list order is already guaranteed? Thanks

[ccamel]

@0xLodz The set of entities (section, subsection, paragraph, article, paragraph) is expected to be linearly ordered by the meta:hasNumber property, using the usual lexicographic ordering on strings ("less than or equal to" (≤), "greater than or equal to" (≥) operators), thereby establishing a totally ordered set. This point will be clarified in the ontology so that the expected use is well understood.

[loiclaudet]

Thanks for the clarifications!

[ChaimaaZaoui]

This ticket is on hold waiting for #96 to be implemented

[fredericvilcot]

@ChaimaaZaoui
If it's Ok for you,
This issue could be implemented after the governance's connection to handle fetches with an infinite scroll.
Because mocking this behavior with fake data in an asynchronous way could take some non negligent time that could be saved.