Pre-preview nitpicks #59

New Issue

2026-05-25T04:12:21Z

ntnsndr commented

2026-05-25 04:12:21 +00:00

It is super thrilling to see the pre-preview of the new CommunityRule live! As requested, here are some things I'm noticing, mostly quite tiny. I'm just tossing them in here in the order that I'm noticing them.

Homepage menu hover colors

Hover hinders visibility on mainpage, but not everywhere else:

"Trusted by leading collaborators"

First, this header feels off-center—not because it is, but because the logos below are spread out in a way that messes up the centering. I can imagine a few potential remedies, but I found it immediately distracting.

Second, I don't think we can yet claim that this is "trusted" by these organizations yet. I'd recommend removing this until we can get some clearer agreements.

Social links

Remove the GitLab link; we now only use GitLab for CI tasks. Instead, the git link should go to this repo once it is live.
Bluesky should be: https://bsky.app/profile/medlabboulder.bsky.social
Could also add Mastodon? https://bsky.app/profile/medlabboulder.bsky.social

Blog bylines

Blog posts have "Author name" as the bylines. Maybe use a generic one like "CommunityRule"? Or maybe we don't need bylines since I assume all our posts will just come from the same organizational voice?

"Worker's coop"

This is the first organization type listed in the authoring flow.

I know this has been a longstanding usage on the redesign, but it's not really normal (or even grammatical, since there is no such thing as a co-op with only one worker, as the placement of the apostrophe suggests). The more common way to render this (following the US Federation of Worker Cooperatives) would be "worker cooperative" or "worker co-op."

Organization type entry

I can't include spaces when adding a custom organization type, even though the default options include spaces.

Magic link UX

I think avoid exclamation marks. Something like moving from:

Check your email to log in!
Your account is created, now just check your email for a magic link

to:

Check your email to log in
Your account has been created. A login link has been emailed to you.

Oh, and I didn't get an email:)

It is super thrilling to see the pre-preview of the new CommunityRule live! As requested, here are some things I'm noticing, mostly quite tiny. I'm just tossing them in here in the order that I'm noticing them. ## Homepage menu hover colors Hover hinders visibility on mainpage, but not everywhere else: ![image.png](/attachments/cc105d36-e792-4719-8473-7ca44e0c7d44) ## "Trusted by leading collaborators" First, this header feels off-center—not because it is, but because the logos below are spread out in a way that messes up the centering. I can imagine a few potential remedies, but I found it immediately distracting. Second, I don't think we can yet claim that this is "trusted" by these organizations yet. I'd recommend removing this until we can get some clearer agreements. ## Social links * Remove the GitLab link; we now only use GitLab for CI tasks. Instead, the git link should go to this repo once it is live. * Bluesky should be: https://bsky.app/profile/medlabboulder.bsky.social * Could also add Mastodon? https://bsky.app/profile/medlabboulder.bsky.social ## Blog bylines Blog posts have "Author name" as the bylines. Maybe use a generic one like "CommunityRule"? Or maybe we don't need bylines since I assume all our posts will just come from the same organizational voice? ## "Worker's coop" This is the first organization type listed in the authoring flow. I know this has been a longstanding usage on the redesign, but it's not really normal (or even grammatical, since there is no such thing as a co-op with only one worker, as the placement of the apostrophe suggests). The more common way to render this (following the US Federation of Worker Cooperatives) would be "worker cooperative" or "worker co-op." ## Organization type entry I can't include spaces when adding a custom organization type, even though the default options include spaces. ## Magic link UX I think avoid exclamation marks. Something like moving from: > **Check your email to log in!** > Your account is created, now just check your email for a magic link to: > **Check your email to log in** > Your account has been created. A login link has been emailed to you. Oh, and I didn't get an email:)

image.png

5.7 KiB

an.di referenced this issue from a commit

2026-05-26 15:04:29 +00:00

Issue #59 fixes

an.di closed this issue

2026-05-26 15:13:25 +00:00

Sign in to join this conversation.