Announcing Libretro Overview
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Review the linked Libretro Overview repository and its docs/all.md report to understand the generated content and update process. Then check how this repository builds and publishes docs.libretro.com. Done means deciding whether to host the report and link it from the official documentation; the issue does not specify the integration or hosting changes.
Written by the indexing model from the issue text.
Description
Hi,
I wanted to share a new repository I recently created called Libretro Overview that might be of interest to you.
In particular, I’d like to highlight the master report: docs/all.md. It provides a convenient overview of OS and architecture support for users, while also helping developers quickly identify missing or obsolete .info files and documentation across Libretro projects.
Since it auto-refreshes daily, I think community members would really appreciate having this data integrated into the official documentation. Would it be possible to host and run the generation script on the docs.libretro.com server so it stays updated there directly along with a 'Libretro Overview' link (e.g, https://docs.libretro.com/overview)?
What do you think about this idea?
- Dominant language
- TeX
- Stars
- 354
- Forks
- 866
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No 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 libretro/docs
-
Update bounties page with new preferred bounty payment serviceMay be free again A pull request for this issue was closed without being merged. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
libretro/docs#960 · 3 comments ·
Maintainers usually reply within 2 days
-
Pull Requests fail with errorMay be free again A pull request for this issue was closed without being merged. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libretro/docs#1145 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
libretro/docs#1057 · 2 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
libretro/docs#958 · 3 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 5/5 Over a week Newbie friendliness 25/100
libretro/docs#946 · 9 comments ·
Maintainers usually reply within 2 days
Similar issues
-
content triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
QuantEcon/lecture-python.myst#1130 ·
Maintainers usually reply within 1 day
-
Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JSPrismarine/JSPrismarine#3214 ·
Maintainers usually reply within 1 day
-
feature request status/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
karakeep-app/karakeep#3383 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/aspire.dev#2184 ·
Maintainers usually reply within 2 days