Our in-house foundation for Next.js websites on Contentstack takes routine setup out of your build. Running inside the live site, it reduces repeat requests, refreshes only the content that changes and helps catch content errors before release, so more of your build goes into the experience your customers see.
1 of 4
Elite Contentstack partners
1
Connected foundation
4
Built-in capabilities
Repeat requests and rebuilt integrations cost every Contentstack project time.
Marketing teams need sites that feel fast and reflect their latest content. Fetching the same content again and again adds work and API usage, and rebuilding common integrations takes time away from customer-facing features.
How Basecamp works _
Three connected steps replace rebuilt integrations and repeat requests.
Step 1: Fetch Once
Next.js caching and duplicate-request handling work with Contentstack, and GraphQL retrieves related content together. Content already fetched gets reused.
Step 2: Refresh what changed
Contentstack publishing webhooks connect to Next.js caching for pages and components. When shared content changes, cached content clears for every page that uses it and not for unrelated pages.
Step 3: Check before release
TypeScript types are generated from the queries that retrieve your content. Generation runs during builds and in the delivery pipeline, so query and type mismatches surface before release.
What Basecamp Delivers _
One foundation gives marketers efficiency and developers confidence.
For marketing and digital leaders
| For developers and architects
|
Basecamp Capabilities _
One foundation covers delivery, caching and checks for every build.
Fewer repeat requestsIntegrates Next.js caching and duplicate-request handling with Contentstack, and uses GraphQL to retrieve related content together. Targeted content refreshConnects Contentstack publishing webhooks to Next.js caching for pages and individual components. Typed queriesGenerates TypeScript types from the queries that retrieve your content. Checks in the pipelineType generation runs in builds and in the automated delivery pipeline. Query and type mismatches caught before release. |
COMPANION PRODUCT _
Basecamp pairs with Beacon.
Beacon manages your content model during development and deployment. Basecamp runs inside the live site. Together, they cover how your content is structured and how it reaches your audience.
EXPLORE BEACONBasecamp Frequently Asked Questions
What is Basecamp?
Basecamp is the foundation MSQ DX teams build Next.js websites on Contentstack from. It gives our delivery teams a connected starting point that uses content efficiently, keeps sites current as content changes and builds checks into delivery.
Is Basecamp sold or licensed separately?
No. Basecamp is part of MSQ DX’s Contentstack engagements, with no separate license or added charge.
How do I get Basecamp?
Organizations get Basecamp by working with MSQ DX. Our delivery teams use it when building or modernizing Next.js sites on Contentstack.
Will Basecamp reduce my Contentstack API usage?
Reusing content that has already been fetched can reduce calls to Contentstack and help manage usage against your plan’s allowance. Actual usage depends on your site, traffic and content.
How is Basecamp different from Contentstack’s starter kits?
Starter kits, the Delivery SDK and type generators each cover part of the job. Basecamp bundles caching and call reduction, selective content refresh and typed queries into a single layer, and it is included in our Contentstack engagements.
How is Basecamp different from Beacon?
Beacon is an open-source command-line tool that manages your Contentstack content model across stacks during development and deployment. Basecamp runs inside the live site, handling how content is fetched, cached and checked. They are separate products that work well together.
Which sites benefit most?
Content-rich sites, sites that reuse shared content across many pages, and sites with high traffic.