theupdateframework / theupdateframework/theupdateframework.io

Spec page rework suggestions

Open
#107 0 comments 0 reactions 1 assignee View on GitHub

@chalin is already working on this.

Since Oct 12, 2024.

Dominant language
HTML
Stars
25
Forks
46
PR merge metrics
No merged PRs in 30d

Description

Originally posted by @jku in https://github.com/theupdateframework/theupdateframework.io/issues/105#issuecomment-2401663449 and https://github.com/theupdateframework/theupdateframework.io/pull/105#issuecomment-2401680928


Looks nice.

On content/en/spec.md:

  • is the idea that spec maintainers should update this page too when they make a specification release? This feels like unnecessary process. I would suggest replacing the list with:
  • Currently the link for list of releases /specification/list/ is broken: should be /specification/

Also header for the "spec" tab seems wrong -- it's got a large image that looks a bit placeholdery. Or is this intended?

Compare partial screenshot from docs and spec tab: ...


Tasks
  • Fix redirect to spec list - #108
  • Propose a rework / reorg of the spec page (?)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.