WWW: Republish selected blog posts
@johnmhoran is already working on this.
Since Jan 24, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, markdown
- Domain
- content, documentation
Research direction
Start by locating the blog entries in the Docusaurus/markdown-based repository that correspond to the listed aboutcode.org URLs. Review the selected posts for needed updates, decide whether unchanged posts retain their original publication dates, and confirm which candidates are republished; the issue notes that one historical post may remain as-is.
Written by the indexing model from the issue text.
Description
We should republish selected blog posts from the current aboutcode.org website. For each post we will want to review the content and update it since most are from 2023 or earlier.
Some candidates are:
- P1 https://aboutcode.org/2023/purl-universal-software-package-identification/
- P1https://aboutcode.org/2023/non-vulnerable-dependency-resolution/
- P1 https://aboutcode.org/2023/curated-licenses-public-database-scancode-licensedb/
- https://aboutcode.org/2023/what-is-a-dual-license-anyway/
- https://aboutcode.org/2022/software-versioning/
- https://aboutcode.org/2022/scancode-license-clarity-scoring/
- https://aboutcode.org/2023/update-copyright-each-new-year/
- PI https://aboutcode.org/2021/copyleft_licensed_software_java_app/
- https://aboutcode.org/2020/snippet-matching-for-software-provenance-analysis/
- https://aboutcode.org/2016/software-dependencies-guide/
- https://aboutcode.org/2013/datatables-and-healthcare-gov-oss-attribution-case-study/ - keep as-is for historical context as our first blog post?
This list represents about half of the historical posts. If we do not modify the content I suppose that we can/should (?) keep the original publication date.
I did not include any posts related to Open Source Stack Exchange.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 aboutcode-org/www.aboutcode.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Add hover effects to adopter logos in the Community and Adopters sectionPossibly taken @riddheshkadu3637-ui claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Making all post button.Possibly taken @sarthaklole claimed this 90 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aboutcode-org/www.aboutcode.org#117 · 3 comments ·
-
WWW: Reduce frequency of update-releasesMay be free again @johnmhoran claimed this 71 days ago, and no pull request is open. Openci-workflow
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
aboutcode-org/www.aboutcode.org#180 · 1 assignee ·
-
DOCS: Create new AboutCode stack diagram(s)May be free again @hixvikas claimed this 72 days ago, and no pull request is open. Opendocumentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
aboutcode-org/www.aboutcode.org#166 · 1 comment ·
All issues in aboutcode-org/www.aboutcode.org
Similar issues
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JSPrismarine/JSPrismarine#3271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day