Content storage
Where the content lives decides much of the hosting.
Content storage records where the pages, entries and settings a site publishes are kept. It shapes what a server must provide, how content moves between a laptop and production, and how backups work. A record carries every storage model its documentation describes as built in, so a tool that reads Markdown files and can also query a database holds both flat files and database. Libraries and tools that hold no content of their own carry no value here, and neither does software that only reads content from another service.
2 values in use. 170 records do not record this field. For a further 374 the question does not apply, so there is nothing to record.
- DatabaseContent in tables, edited through an admin or an API.25 records
- Flat filesContent as files, versioned with the code.29 records