nextlyhq.com valid

Nextly

Open-source CMS and Visual Page Builder for Next.js.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T22:43:39.235Z. Cached copy · Source on nextlyhq.com

# Nextly

> Open-source CMS and Visual Page Builder for Next.js.

Nextly is an open-source CMS and Visual Page Builder for Next.js. Model content, build pages, localize, version and release from your own stack. Model content in TypeScript or in the Visual Schema Builder. Both feed the same Nextly runtime, admin and APIs. Runs on PostgreSQL or MySQL, or SQLite for local work. MIT licensed.

Current release: `0.0.2-alpha.70`, published 25 Oct 2026. Nextly is in alpha. APIs may change before 1.0. Pin exact versions in production. The documentation describes the current release and is not version-stamped. A project may run an older one, so check it first with `npx nextly --version`.

For the complete documentation in a single file, see https://nextlyhq.com/llms-full.txt

## Docs

- [Nextly documentation](https://nextlyhq.com/docs): Nextly is an open-source CMS and Visual Page Builder for Next.js. Model content, build pages, localize, version and release from your own stack.
  - [Quick start](https://nextlyhq.com/docs/getting-started/quick-start): Create a Nextly project, start it, and create the first admin. Then build something with it.
- [Getting Started](https://nextlyhq.com/docs/getting-started): Learn what Nextly is and understand its core concepts.
  - [Installation](https://nextlyhq.com/docs/getting-started/installation): Install Nextly in a new or existing Next.js project with step-by-step instructions.
  - [Tutorial: build a blog](https://nextlyhq.com/docs/getting-started/build-a-blog): Create a blog with posts and categories using Nextly. Define content with code or build it visually.
  - [Project Structure](https://nextlyhq.com/docs/getting-started/project-structure): Understand how a Nextly project is organized, where key files live, and what each directory does.
- [Configuration](https://nextlyhq.com/docs/configuration): Configure your Nextly application with collections, singles, field groups, fields, storage, security, and more.
  - [Nextly Config Reference](https://nextlyhq.com/docs/configuration/nextly-config): Complete reference for every option accepted by defineConfig() in nextly.config.ts.
  - [Collections](https://nextlyhq.com/docs/configuration/collections): Define content types with multiple entries using collections.
  - [Singles](https://nextlyhq.com/docs/configuration/singles): Define single-document content like site settings, headers, and footers.
  - [Field Groups](https://nextlyhq.com/docs/configuration/field-groups): Define reusable field groups that can be shared across collections and singles.
  - [Fields](https://nextlyhq.com/docs/configuration/fields): Complete reference for every field type, their options, and usage patterns.
  - [Environment Variables](https://nextlyhq.com/docs/configuration/environment): Every environment variable Nextly reads, organized by category with required vs. optional indicators.
  - [Limit store](https://nextlyhq.com/docs/configuration/limit-store): Where limits keep their counts, how t
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Open source projects. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=nextlyhq.com · GET /v1/domain/nextlyhq.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for nextlyhq.com:
1. POST https://agentwebmap.com/v1/sites/nextlyhq.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://nextlyhq.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/nextlyhq.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nextlyhq.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.