Components: use a project table for a11y and status census, automate status tables
Closed this issue · 1 comments
Fupete commented
Does a discussion already exist on the topic you are interested in, or on a similar topic?
- I verified and it doesn't exist
What
Related to this ongoing a11y human check: #879
And the need for a complete human census of the status of our various repos/resources.
I am testing the use of a project table (https://github.com/orgs/italia/projects/32/ - currently private) as a "Census-sheet", exportable as csv/tsv or via api rest, to be read from our website docs to render all the different status tables on component pages. We need to automate these tables.
cc @astagi
Why
Scalability and maintainability. Open source and transparency. Time.
Context
Drafts:
More
No response
Fupete commented
Valutare di aggiungere colonne dove 'segnare' le issue di eventuali stati "DA RIVEDERE" cc @zetareticoli @astagi