Skip to content

Add table of contents to about page#11885

Merged
Gargron merged 1 commit intomasterfrom
feature-about-toc
Sep 19, 2019
Merged

Add table of contents to about page#11885
Gargron merged 1 commit intomasterfrom
feature-about-toc

Conversation

@Gargron
Copy link
Member

@Gargron Gargron commented Sep 18, 2019

Generate a table of contents out of the extended site description HTML.

Move the public listing of domain blocks (when enabled) to the about page. Instead of displaying them in a table with jargon words such as "suspend" or "silence", everything is presented in a format readable by the average person, with focus on what impact it has on that person.

image

Also, improve vertical flow of .rich-formatting elements, i.e. improve CSS for headers, lists, inline elements and more.

@Gargron Gargron added the ui Front-end, design label Sep 18, 2019
@Gargron Gargron force-pushed the feature-about-toc branch 4 times, most recently from 4f78584 to 6b1529f Compare September 19, 2019 00:25
Move public domain blocks information to about page
@Gargron Gargron merged commit d930eb8 into master Sep 19, 2019
@ykzts ykzts deleted the feature-about-toc branch September 19, 2019 09:28
@ClearlyClaire
Copy link
Contributor

I think we can keep the ToC thing and have the block information directly on /about/more, but can we please move back to the older design (maybe with the reworded severity explanations, and maybe with a link to the explanation in the severity level)?

We went from this:
image

To this:
image

Pardon my words, but this looks untidy and unprofessional

@0xa
Copy link
Contributor

0xa commented Sep 25, 2019

yeah i have to agree, i like the helpful text but i'm very worried about how it would look with longer reasons and eighty entries.

the domain/severity table is clearly more readable and browsable. i think it would be better to take the good parts of both solutions and keep the table with the domain and a very short severity summary, with entries that unfold to show the full severity description and the full reason, however long both might be.

having a dedicated page also might be a better option, since about pages tend to already have a lot of content, and blocklists tend to be long and grow with time. maybe it could be linked in the table of content anyway, i'm sure there is a way to cleanly indicate that it's a separate page

hiyuki2578 pushed a commit to ProjectMyosotis/mastodon that referenced this pull request Oct 2, 2019
Move public domain blocks information to about page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ui Front-end, design

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants