Skip to content

[EPIC] Bring developer documentation up-to-date with new systems #5832

@neilmb

Description

@neilmb

Feature/what we're after

Our team's internal documentation that we use for O+M tasks needs to be reviewed and updated so that it accurately represents the systems and tasks that we need to do in the CKAN-free, H2.0 era.

Anticipated/hypothesized benefits

  • Everyone on the team can contribute to what needs to be done on O+M
  • Quicker to find what you need because outdated docs are not present

Measurements/metrics

  • Count of Wiki pages that are no longer accurate or relevant

References/background

Audit checklist

Working through the 67 wiki pages to tag each one. Legend:

  • ✅ Keep as-is
  • 🔧 Needs update
  • 🗑️ Archive or delete (CKAN-era / no longer relevant)
  • ❓ Needs review before deciding

Note: ✅ items have not all been individually verified -- a quick scan of each is recommended before confirming.


Priority pages (update these first)


Marked with "no longer relevant except maybe inventory.data.gov note" (CKAN-era / no longer relevant)


Needs review before deciding


Likely keep as-is (verify before confirming)

Metadata

Metadata

Labels

No fields configured for Feature.

Projects

Status
🗄 Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions