Skip to content

Format off for Community Page #126

Open
@swzCuroverse

Description

@swzCuroverse

The meeting details on the new community page are not formatted by like the rest of the page.

In general: Perhaps we don't need this on the community page but a link to a new page since it swallows up the rest of the resources of which the page was intended. We already have a mention of the weekly chat in the bullet points, so it is extra confusing. Perhaps that should link to a nicely formatted page about the meetings if people are interested.

To look like the rest of the page/general guidelines:
(1) Follow look and feel of rest of site

  • Titles should be in all caps --> Agenda and Notes not Agenda and notes (and/if/but not caps)
  • If you have a list of items --> Use the bullets
  • We use numbers no where else on the site
  • Periods only needed at end of sentences (https://w3id.org/cwl/meeting_minutes.)
  • Hyperlinks should be given context (https://w3id.org/cwl/meeting_minutes.) and alt text instead of the direct link.
  • Avoid long hyperlinks if possible: EMEA-Americas: weekly every Wednesday at 16:00 UTC from March-November and 17:00 UTC from November-March
  • You should try to not have have section headers just start mid-page, for a good example to do this correctly see here: https://www.commonwl.org/features
  • Balance new sections with existing format and content: Code of conduct already lives here: https://www.commonwl.org/code-of-conduct/ -- link to it perhaps in the list of bullet points above instead of having a new section for it.
  • Consider making a new page when a topic seems to overwhelm the content of the page and/or is not of interest to all participants or very detailed on one topic
  • Avoid hyperlinks when you can just put the detail easily on the page -- aka EMEA (Europe, the Middle East and Africa) is way more informative than linking to a wikipedia article. Same with APAC.

(2) Make things are new person/user friendly as possible: No explanation made about what the Weekly Meeting is, why one would attend or any context. Again, lots of work to make things as user-friendly in mind so we should keep doing this.

In general, we should have a review process since a bunch of work was made to make the website look good , organized, be approachable and consistent. Otherwise, I fear we will lose the headway we made quickly with the reformat.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions