Refresh Documentation Website
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reviewing the existing documentation website and comparing its new-user experience with Ratel's, as the issue suggests. The issue does not identify specific files, pages, or tests, and leaves the desired changes open-ended; first clarify the goals and scope with the maintainers. Done means the documentation website has an agreed, more new-user-friendly direction and the resulting changes are reviewed.
Written by the indexing model from the issue text.
Description
The documentation website isn't a new-user-friendly as Ratel's. We should revisit and think about how we want it to look.
- Dominant language
- C
- Stars
- 273
- Forks
- 84
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CEED/libCEED
-
release preparation spack
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CEED/libCEED#2094 · 2 comments ·
Maintainers usually reply within 1 day
-
GPU testing
Difficulty 4/5 3-5 days Newbie friendliness 48/100
CEED/libCEED#2086 · 5 comments ·
Maintainers usually reply within 1 day
-
examples Python
Difficulty 4/5 3-5 days Newbie friendliness 52/100
CEED/libCEED#2084 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Pin Action VersionsOpenCI
Difficulty 5/5 Over a week Newbie friendliness 35/100
CEED/libCEED#2075 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
area/docs
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Clodmony/starship-coop#72 ·
Maintainers usually reply within 1 day
-
ospf6d: heap-use-after-free in seqnumber_mismatch()/bad_lsreq() when a neighbor is deleted with events pendingPossibly taken @lichenlang89 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 2 days
-
5700模组网络优先级问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
luainkernel/lunatik#2372 ·
Maintainers usually reply within 1 day