Archived
15
23
Fork
You've already forked meta
6

Website MoSCoW quality checklist #30

Closed
opened 2022年11月09日 04:54:07 +01:00 by circlebuilder · 11 comments
Contributor
Copy link

Well.. this should be in a place where it can be collectively updated. But here goes.

Let's define MoSCoW quality criteria we find desirable at launch date and prioritize..

Must have

  • Responsive design (tested to multiple common device fallbacks)
  • Privacy policy (peek at:fedi.foundation policy)
  • Zero trackers
  • Good enough accessibility (define: good enough)
  • SEO: Opengraph, twitter, schema.org metadata (peek at: fediverse/fedi-foundation#4)

Should have

  • No remote fonts and CDN assets (mostly trackers anyway)
  • Blog facility
  • CSS for blog

Could have

  • Zero JS (tradeoff: theme switch then only possible via CSS)
  • Translations (which languages?)
  • A Blog pre-filled with some articles already (invite blog writers to guest-author)
  • CSS for release notes (maybe others: issues/PR's?)

Won't have

(Add here what will NOT be part of the site at launch date)

Well.. this should be in a place where it can be collectively updated. But here goes. Let's define [MoSCoW](https://en.wikipedia.org/wiki/MoSCoW_method) quality criteria we find desirable at launch date and prioritize.. ### Must have - Responsive design (tested to multiple common device fallbacks) - Privacy policy (peek at:[fedi.foundation policy](https://fedi.foundation/privacy.html)) - Zero trackers - Good enough accessibility (define: good enough) - SEO: Opengraph, twitter, schema.org metadata (peek at: https://codeberg.org/fediverse/fedi-foundation/issues/4) ### Should have - No remote fonts and CDN assets (mostly trackers anyway) - Blog facility - CSS for blog ### Could have - Zero JS (tradeoff: theme switch then only possible via CSS) - Translations (which languages?) - A Blog pre-filled with some articles already (invite blog writers to guest-author) - CSS for release notes (maybe others: issues/PR's?) ### Won't have _(Add here what will NOT be part of the site at launch date)_

Excellent checklist 👍

Do you mind moving it to the website issue tracker at https://codeberg.org/codename/website/issues?

Excellent checklist 👍 Do you mind moving it to the website issue tracker at https://codeberg.org/codename/website/issues?

I added the privacy policy to the content hedgedoc (I think it can be removed from this technical list).

The rest of you list looks very good 👍

I only disagree with Zero JS:

  • gitea is already heavily using JS
  • some features are only possible with JS (search on static site, auto-anchoring on scroll, theme switch...)

Maybe this could be changed to Perfectly usable without JS? (so that JS are only progressive enhancements)

I would move No remote fonts and CDN assets to Must have, since we know that they are problematic regarding privacy.

I added the privacy policy to the content hedgedoc (I think it can be removed from this technical list). The rest of you list looks very good 👍 I only disagree with `Zero JS`: - gitea is already heavily using JS - some features are only possible with JS (search on static site, auto-anchoring on scroll, theme switch...) Maybe this could be changed to `Perfectly usable without JS`? (so that JS are only progressive enhancements) I would move `No remote fonts and CDN assets` to `Must have`, since we know that they are problematic regarding privacy.

Instead of CSS for blog, didn't you mean RSS for blog ? (syndication feed)

For the releases as well.

Instead of `CSS for blog`, didn't you mean `RSS for blog` ? (syndication feed) For the releases as well.

Another Could have: light/dark theme ;)

Another `Could have`: light/dark theme ;)
Contributor
Copy link

this should be in a place where it can be collectively updated.

Owners have the permission to update other people's posts. Just sayin'.

define: good enough

Passes aXe Core. That's a good base level.

SEO: Opengraph, twitter, schema.org metadata

Also canonical links, sitemap and robots.txt at the very least.

> this should be in a place where it can be collectively updated. Owners have the permission to update other people's posts. Just sayin'. > define: good enough Passes aXe Core. That's a good base level. > SEO: Opengraph, twitter, schema.org metadata Also canonical links, sitemap and robots.txt at the very least.
Member
Copy link

Another Could have: light/dark theme ;)

I'd say Must have 😜 or more realistically Should have

> Another `Could have`: light/dark theme ;) I'd say `Must have` 😜 or more realistically `Should have`
Owner
Copy link

I think Zero JS is great, especially to not rely on it. Many things (dark/light theme switch, even modals and navbars) are possible without a single line of JS.

Implementing additional convenience features like search with JS is ok, but I hate broken websites without.

I think Zero JS is great, especially to not rely on it. Many things (dark/light theme switch, even modals and navbars) are possible without a single line of JS. Implementing additional convenience features like search with JS is ok, but I hate broken websites without.

Excellent checklist 👍

Do you mind moving it to the website issue tracker at https://codeberg.org/codename/website/issues?

I created codename/website#9 to link to this issue for discussions so that it can also be found in the context of working on the website. Removing the "Launch" milestone as it is included in the existing issue regarding the website.

The idea is to keep the list of tasks in the Launch milestone small (13 of them) and the details can be explored in other repositories. That's also what the daily updates link to and should help people who want to get involved to get oriented.

> Excellent checklist 👍 > > Do you mind moving it to the website issue tracker at https://codeberg.org/codename/website/issues? I created https://codeberg.org/codename/website/issues/9 to link to this issue for discussions so that it can also be found in the context of working on the website. Removing the "Launch" milestone as it is included in the [existing issue regarding the website](https://codeberg.org/codename/meta/issues/2). The idea is to keep the [list of tasks in the Launch milestone small](https://codeberg.org/codename/meta/milestone/2788) (13 of them) and the details can be explored in other repositories. That's also what the [daily updates](https://gitea-open-letter.coding.social/updates/) link to and should help people who want to get involved to get oriented.
Ghost removed this from the Launch milestone 2022年11月09日 14:48:38 +01:00
Author
Contributor
Copy link

Instead of CSS for blog, didn't you mean RSS for blog

Yes, RSS :)

I created codename/website to link to this issue

Thanks, Loic 👍

> Instead of CSS for blog, didn't you mean RSS for blog Yes, RSS :) > I created codename/website to link to this issue Thanks, Loic 👍

Now that https://forgejo.org is online, is it still relevant here? Or does it belong to https://codeberg.org/Forgejo/website?

Now that https://forgejo.org is online, is it still relevant here? Or does it belong to https://codeberg.org/Forgejo/website?

Oh, I forgot that it already exists here forgejo/website#9 so let's close this one to avoid duplicating.

Oh, I forgot that it already exists here https://codeberg.org/forgejo/website/issues/9 so let's close this one to avoid duplicating.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
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
6 participants 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/meta#30
Reference in a new issue
forgejo/meta
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?