# Documentation: what else should we provide?

**URL:** <https://forum.openreferral.org/t/documentation-what-else-should-we-provide/789>\
**Category:** General\
**Tags:** documentation\
**Created:** [February 23, 2026, 8:53pm UTC](https://forum.openreferral.org/t/documentation-what-else-should-we-provide/789 "2026-02-23T20:53:54Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![bloom](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/bloom/32/103_2.png) [@bloom](https://forum.openreferral.org/u/bloom)\
**Post date:** [February 23, 2026, 8:53pm UTC](https://forum.openreferral.org/t/documentation-what-else-should-we-provide/789/1 "2026-02-23T20:53:54Z")

</div>

We have been pulling together a backlog of practical knowledge for which we can provide documentation.

See [this spreadsheet](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=1976665603#gid=1976665603), and the table below for a set of examples.

We’d like to hear from members of the community – what’s missing? What’s a high priority?

Do you have any documentation that you’ve produced through your own projects, which might be valuable to others in this community? Let us know!

#

| **Name** | **Purpose** | **Type** |
| --- | --- | --- |
| Generating profiles | Instruct users on how to generate profiles (to accompany “HSDS Profile Wizard”?) | How-to |
| Mapping schemas to HSDS | Instruct users on how to map their schemas to HSDS, using the mapping template as example (to accompany transformer) | How-to |
| Validating compliance with HSDS | Instruct users on how to validate compliance with HSDS (to accompany the HSDS validator?) | How-to |
| Bootstrapping a database with HSDS | Instruct users on how to bootstrap a database from the HSDS schema (to replace the SQL dump?) | How-to |
| Serializing contact information | How to delineate different types of contact information using the Attributes table. | How-to |
| Schemas and API spec | Explanation for relationship between schemas and API spec | Explanation |
| Using the Attributes table | | Explanation |
| Program \> Services \> Secondary services | Educate users on the nuances of these concepts and how they can be applied to structure complex service information | Explanation |
| Working with spreadsheets | Guidance for working relational data into and out of ‘flat’ structures. | Tutorial |
| Concept model \> logical model | Clarifying the relationship between the concept model and logical model | Explanation |
| Authoring a “data guide” | Guiding users for producing a “data guide” to accompany their API / open data | How-to |
| Designing data partnerships (non-technical) | Guiding users through the process of designing equitable and sustainable data partnerships | Tutorial |

---

_[View the full topic](https://forum.openreferral.org/t/documentation-what-else-should-we-provide/789)._