Fix few markup inconsistencies #3275

Closed
pleromian wants to merge 5 commits from gitlab-mr-iid-2008 into develop
Member

Fix some more markup inconsistencies and make ToS a first-class citizen; see screenshots (kazv.moe proxied)

/about
Screenshot_2025-01-25_at_16.55.13

/registration
Screenshot_2025-01-25_at_16.55.47

adding sticky allows to have active panel be always focused after scrolling down (about page):
Screenshot_2025-01-28_at_17.57.27

padding for Staff panel:

Screenshot_2025-02-04_at_19.52.42

Drafts:

Screenshot_2025-02-04_at_19.54.09

Fix some more markup inconsistencies and make ToS a first-class citizen; see screenshots (kazv.moe proxied) `/about` ![Screenshot_2025-01-25_at_16.55.13](/attachments/4a28355d-3c46-4e62-bc48-898000d25ed4) `/registration` ![Screenshot_2025-01-25_at_16.55.47](/attachments/bc09f844-482b-4afc-a201-fc57997e9806) adding `sticky` allows to have active panel be always focused after scrolling down (about page): ![Screenshot_2025-01-28_at_17.57.27](/attachments/d8dffc2a-e23a-4a75-922e-b7da8c80182a) padding for Staff panel: ![Screenshot_2025-02-04_at_19.52.42](/attachments/31e3c39d-8bf6-4081-846a-7f9ec50824f1) Drafts: ![Screenshot_2025-02-04_at_19.54.09](/attachments/bcd5e0e0-0982-4077-b247-4c322e2c47bb)
Author
Member

Optionally registration page can feature "By registering, you're agreeing with Terms of Service" somewhere, but I think it's already assumed if they go first.

Optionally registration page can feature "By registering, you're agreeing with Terms of Service" somewhere, but I think it's already assumed if they go first.
Author
Member

Also GitLab's diff viewer doesn't like registration page, but essentially ToS were moved to a separated if-guarded component and page class was added, no changes to the form at all.

Also GitLab's diff viewer doesn't like registration page, but essentially ToS were moved to a separated if-guarded component and page class was added, no changes to the form at all.
Owner

i think this has been discussed in #2511

i think this has been discussed in https://git.pleroma.social/pleroma/pleroma-fe/pulls/2511
Author
Member

@tusooa fair point, but I believe for the ToS panel feature mentioned there one would be better off with instance-specific panel? Otherwise, separation/embedding of ToS panel can be a configuration setting

@tusooa fair point, but I believe for the ToS panel feature mentioned there one would be better off with instance-specific panel? Otherwise, separation/embedding of ToS panel can be a configuration setting
Author
Member

also I'd swap Staff and ToS places on the About page, it would look more consistent in my opinion (terms first, then everything else)

also I'd swap Staff and ToS places on the About page, it would look more consistent in my opinion (terms first, then everything else)
Owner

I think ToS panel should be left as-is. People might not use "terms of service" uh, term, and replace it with "Instance rules" for instance.

I think ToS panel should be left as-is. People might not use "terms of service" uh, term, and replace it with "Instance rules" for instance.
Author
Member

@hj what's about making it configurable? i.e. by default it's embedded, but users can make it separate if they feel like.

@hj what's about making it configurable? i.e. by default it's embedded, but users can make it separate if they feel like.
Owner

Yes, it can be instance option

Yes, it can be instance option
Author
Member

@hj should be ready now

@hj should be ready now
Author
Member

@tusooa what do you think?

@tusooa what do you think?

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe!3275
No description provided.