D2.2 Documentation Plan for OSPO‑RADAR

The OSPO-RADAR project develops the technical tooling that enables Academic Open-Source Programme Offices (OSPOs) to archive, manage and showcase their institutions’ software, built on integration with Software Heritage. OSPO-RADAR will be offered both as a hosted service operated by Software Heritage and as free software that institutions can host themselves. D2.2 sets out how the product’s user documentation will be implemented for both settings. It compares two options: adding the documentation to the existing Software Heritage documentation website, or keeping it independent on the product’s own website. It recommends independent documentation built with Zensical, a Markdown-based static site generator, which also serves as a test case for a possible future migration of the Software Heritage documentation. The plan defines three content phases (API and system administration, institution setup, and curation and maintenance), a task-oriented help-centre content structure, and the scope of the API reference. Content development can begin now, while the software is still being developed.

Authors

Institutions

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-11-10
DOI
https://doi.org/10.5281/zenodo.24094282
Primary Topic
Software Engineering Techniques and Practices
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
article

D2.2 Documentation Plan for OSPO‑RADAR

Melissa Draper
Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Techniques and Practices
article

D2.2 Documentation Plan for OSPO‑RADAR

Melissa Draper
article en

Abstract

The OSPO-RADAR project develops the technical tooling that enables Academic Open-Source Programme Offices (OSPOs) to archive, manage and showcase their institutions’ software, built on integration with Software Heritage. OSPO-RADAR will be offered both as a hosted service operated by Software Heritage and as free software that institutions can host themselves. D2.2 sets out how the product’s user documentation will be implemented for both settings. It compares two options: adding the documentation to the existing Software Heritage documentation website, or keeping it independent on the product’s own website. It recommends independent documentation built with Zensical, a Markdown-based static site generator, which also serves as a test case for a possible future migration of the Software Heritage documentation. The plan defines three content phases (API and system administration, institution setup, and curation and maintenance), a task-oriented help-centre content structure, and the scope of the API reference. Content development can begin now, while the software is still being developed.

Zenodo (CERN European Organization for Nuclear Research)
Software Heritage (FR)
Software Engineering Techniques and Practices
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon