32
41
Fork
You've already forked website
54

Add rel-me link to fedi account from homepage #35

Closed
opened 2022年12月05日 10:56:00 +01:00 by caesar · 4 comments
Member
Copy link

The home page of the website should have a link to our Fediverse account @forgejo@floss.social, with rel="me". This will allow us to add a "verified" link to the wbsite from our Mastodon profile.

I'm not sure where we want this link, it will depend on the site design. Maybe in the footer, or maybe we want a section on the homepage with a CTA to follow us there, and also a link to our Matrix space and probably the Keyoxide profile.

I'm adding this to the Launch milestone because I think it's imporant that when we link to the website from Mastrodon it should show as verified.

The home page of the website should have a link to our Fediverse account [@forgejo@floss.social](https://floss.social/@forgejo), with `rel="me"`. This will allow us to add a "verified" link to the wbsite from our Mastodon profile. I'm not sure where we want this link, it will depend on the site design. Maybe in the footer, or maybe we want a section on the homepage with a CTA to follow us there, and also a link to our Matrix space and probably the Keyoxide profile. I'm adding this to the Launch milestone because I think it's imporant that when we link to the website from Mastrodon it should show as verified.
caesar added this to the Launch milestone 2022年12月05日 10:56:00 +01:00

FWIW, Mastodon also allows <link> for verification, which can be "hidden" away in the <head> section. No need to give it a place on the website for now.

FWIW, Mastodon [also allows](https://github.com/mastodon/mastodon/blob/daf6f3453e2a37db3d9a8362d64106b6c7cf0763/app/services/verify_link_service.rb#L29) `<link>` for verification, which can be "hidden" away in the `<head>` section. No need to give it a place on the website for now.
Author
Member
Copy link

Ah, true, I'd forgotten that. Though I think it would be good to include it visibly anyway.

Ah, true, I'd forgotten that. Though I think it would be good to include it visibly anyway.

Cross-ref'ing to MoSCoW checklist forgejo/meta#30

Cross-ref'ing to MoSCoW checklist https://codeberg.org/forgejo/meta/issues/30
Author
Member
Copy link

Completed in #37.

Completed in #37.
Sign in to join this conversation.
No Branch/Tag specified
main
monthly-2026-05
mahlzahn-eslint-js
preview-link-status
nightfire
2022年12月14日-main
No results found.
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
forgejo/website#35
Reference in a new issue
forgejo/website
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?