[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fCUsEz7t3z97-fwSE9b7YgZ2Xw9IrhTF1GA0J8qIQbjI":3},{"statusCode":4,"data":5},200,{"_id":6,"url_key":7,"content":8,"createdAt":9,"date":10,"meta":11,"name":12,"published_at":9,"short_description":15,"status":16,"updatedAt":9},"6a3ee5f08db97e9a59c00641","mongodb-data-layer","\u003Cp>\u003Cstrong>MongoDB\u003C/strong> is Tempest CMS's single source of truth. Pages, news, references and team members are stored as flexible documents, which suits a CMS where every site has a slightly different content shape.\u003C/p>\u003Cp>Tempest reads it through a built-in, server-side API and caches responses at the edge — so the database stays fast under load and editors see changes immediately.\u003C/p>\u003Cp>It's the data layer behind every Tempest site, including \u003Ca href=\"/projects/teknodan\">Stråtækker Teknodan\u003C/a> and \u003Ca href=\"/projects/rcs-vvs\">Regner & Claus Sørensen VVS\u003C/a>.\u003C/p>","2026-06-26T20:49:52.586Z","2026-06-06",{"title":12,"description":13,"og_image":14},"MongoDB: the data layer behind Tempest","Why Tempest CMS stores content as flexible MongoDB documents, served through a built-in edge-cached API.","","Flexible documents for content that never has exactly the same shape twice — and why that fits a CMS.",true]