Make a complete indieweb h-card for Agaric (and for each of our profiles) #146
Labels
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: agaric/agaric-coop#146
Loading…
Reference in a new issue
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?
Unfortunately there's not an accepted indieweb standard for putting h-card information on a contact page instead of the homepage. On the plus side we might be able to propose such a standard.
Jeena's about page is an example of an internal page that has more h-card information than the homepage, but unless i'm missing something in the markup there's no way that it has of indicating from the home page for bots to go gather more information on the about page.
Another approach would be to consider anything we'd want to mark up as our organization-representing h-card as important enough to get on our homepage in a paragraph introducing ourselves or in an informational box:
p-locality
) and country (p-country-name
) parts of our addresses.u-logo
) — which we don't have any place that makes it obvious its our logo, and maybe we'd want our canonical logo to be the logo + wordmark (stacked), which we don't have on our site anywhere yet!u-email
) — which yeah, should really be on the front page.p-tel
) — which also should go on the front page.u-url
s, which is still being discussed but seems very common) — here's where i'd want only the ones we really encourage people to visit to be on our front page, but maybe anything we don't want people to visit shouldn't be linked at all or at least not marked up (in either case, that is, not listed as part of our identity).p-note
).u-sound
property).This could go in a paragraph or in a sort of super-footer, but we can't have an h-card that stretches from our name in the header to our mastodon account in the footer, because we'll (want to) have other microformatted content (like our blog post teaser entries) in between.
CC @cedewey @wolcen
marked this issue as related to #132
We can also do:
u-photo
); this is separate and in addition to a logo.bday
).category
).And a little addendum to the discussion about putting about information on a separate page:
u-url
, let alone au-uid
) on his home page, with no relation between the h-card about h-card back to the home h-card, but with a u-url relation from the home h-card to the about h-card.marked this issue as related to #161