# Smoodly > Smoodly is a code-first CMS for Astro and Next.js. A developer registers sections, collections and page types in code, editors build pages in a visual admin mounted in the site at /admin, and the content lives in Smoodly Cloud, read by the site over the API. Start a site with the installer. It creates a fresh app; it does not add Smoodly to an existing one. With these flags it asks nothing: npx create-smoodly-app --yes --framework astro|next --starter blank|lorem [--locales en,fi] --space --secret-key --publishable-key The three space values are on the project's production space page at smoodly.io. In an installed site, the guides for that version are in node_modules/smoodly/docs/ and the project's AGENTS.md holds the working rules. ## Getting started - [Install with create-smoodly-app](https://smoodly.io/docs/getting-started/install.md): One command creates a website with the Smoodly admin mounted, connected to a space that holds its content. At the end you have the Lorem Co. starter running on your machine. - [Project structure](https://smoodly.io/docs/getting-started/project-structure.md): What create-smoodly-app puts in your project, and which files you change as you build the site. Everything is ordinary code in your repository; Smoodly adds a folder of setup and mounts the admin. - [Your first page](https://smoodly.io/docs/getting-started/first-page.md): Create a page in the admin, fill it with sections and publish it, as an editor would. Then look at the code that decided what the editor was allowed to do. - [Content from code](https://smoodly.io/docs/getting-started/content-from-code.md): Write pages, entries, globals and images from a script instead of the admin: to seed a new site, or to move a client's old content in. At the end you have a script you can run again after it stops halfway. - [Working together](https://smoodly.io/docs/getting-started/working-together.md): Who can open the admin, and what happens when two people open the same page: the admin shows who is where, and never lets one person's save silently overwrite another's. - [Keys](https://smoodly.io/docs/getting-started/keys.md): The space id and the two keys a Smoodly site uses, where each one may live, what the public one can reach, and how to rotate or revoke a key. - [Deploying](https://smoodly.io/docs/getting-started/deploying.md): Put your Smoodly site on the internet: give it the production space's values and let its build push the schema; then, once it is live, add a preview space to develop against. - [Export and import](https://smoodly.io/docs/getting-started/export-and-import.md): Copy a space's content into a folder, and from the folder into a new space: every page, entry, version and media file. It is how you move a site or keep a copy. ## Content modeling - [Modeling content](https://smoodly.io/docs/content-modeling/overview.md): The five things you register, what each one holds, and where it lives in your project. Read this once; the rest of the group takes them one at a time. - [Defining a section](https://smoodly.io/docs/content-modeling/sections.md): A section is a full-width component editors place in a zone. You describe its fields once, in a schema file, and Smoodly derives the editor form, the Add section entry and the TypeScript props from that one definition. This page walks through the Lorem Co. starter's Hero. - [Defining a page type](https://smoodly.io/docs/content-modeling/page-types.md): A page type is a page component with zones: the places where editors add sections. This page walks through the Lorem Co. starter's Home and Page types, and what a page type learns about its place in the site. - [Zones and freedom](https://smoodly.io/docs/content-modeling/zones.md): A zone is a place in a page type where editors add sections. Its policy sets how much they may change there, from filling one section's fields to placing any section in any order. - [Settings, styles and CSS](https://smoodly.io/docs/content-modeling/styles-and-settings.md): Beyond its fields, a placed section carries three more things editors can change: the settings you declare, Smoodly's own spacing and width steps, and a custom CSS box you can turn on. All three sit on the Settings tab. - [The custom section](https://smoodly.io/docs/content-modeling/custom-section.md): The one section editors lay out themselves: rows of richtext columns on a 12-column grid, offered where a zone allows it. You turn it on, pick what its columns may hold, and style the result; Smoodly owns the grid. - [Marks and inline editing](https://smoodly.io/docs/content-modeling/marks.md): Marks are the attributes a section spreads on the elements that render its fields. They tell the canvas which field an editor clicked, so text edits in place and everything else opens in the inspector. - [When the schema changes](https://smoodly.io/docs/content-modeling/changing-schemas.md): Sites change after launch: a section goes, a field is renamed, a zone gets stricter. This page covers what stored content keeps when the code moves on, how the admin shows it, and what Publish refuses until an editor fixes it. ## Fields - [All fields](https://smoodly.io/docs/fields/overview.md): Every field builder on f, what editors see for each, and the chain of modifiers they share. The pages that follow take them a few at a time. - [Text, number, date and time](https://smoodly.io/docs/fields/text.md): The plain values: a line of text, a number, a date, a date with a time, and the slug that becomes part of an entry's URL. - [Richtext and elements](https://smoodly.io/docs/fields/richtext.md): Formatted text stored as structured data, the toolset that decides what editors may put in it, and the elements they can insert between the paragraphs. - [Link](https://smoodly.io/docs/fields/link.md): A link is a text box that takes a full URL or a path on your site. Pair it with a label in an object to make a button. - [Choices](https://smoodly.io/docs/fields/choices.md): A switch, a dropdown, a row of pills or a checkbox list: the fields that pick from a closed set you declare. - [Image, video and file](https://smoodly.io/docs/fields/media.md): The three media fields, the resolved values your view receives, and the components that render them. - [List and object](https://smoodly.io/docs/fields/list-and-object.md): Group fields into one value with an object, or let editors repeat a value with a list. The two nest one level, which is as far as a sidebar form stays readable. - [Reference and tags](https://smoodly.io/docs/fields/reference-and-tags.md): A reference points at an entry in a collection and arrives in the view already loaded. Tags are short labels editors reuse across entries. - [Conditional fields](https://smoodly.io/docs/fields/conditional.md): Hide a field while another field has a certain value, so editors see only the fields that apply. ## Pages - [The page tree](https://smoodly.io/docs/pages/page-tree.md): How editors create, arrange and remove pages in the admin, and what your configuration allows them to do. - [Paths and slugs](https://smoodly.io/docs/pages/paths-and-slugs.md): A page's URL is derived from its place in the page tree: each item contributes one slug. This page covers what a slug may be, which URLs your code reserves, how a URL changes and how old addresses redirect. - [Drafts and publishing](https://smoodly.io/docs/pages/drafts-and-publishing.md): Every change saves as a draft on its own. Publish makes the draft live, after Smoodly checks it. This page covers the three states, what publish checks, and the two ways back. - [Version history](https://smoodly.io/docs/pages/version-history.md): Every publish keeps a version. Editors look back at any of them and restore one as the new draft, without touching what is live. - [SEO and social](https://smoodly.io/docs/pages/seo.md): A page type can give its pages an SEO & Social tab: a title, a description, a social image and a switch to hide the page from search engines. Smoodly turns them into the page's metadata. ## Collections - [Defining a collection](https://smoodly.io/docs/collections/defining.md): A collection is a content type with a fixed shape and many entries: posts, people, products. You declare its fields once; editors get a list, a form and publishing for it. - [Entry pages](https://smoodly.io/docs/collections/entry-pages.md): Give a collection a path and each entry gets its own URL. The entry page is the component that renders one entry there. - [Queries](https://smoodly.io/docs/collections/queries.md): Read entries, globals and the page tree from your own views, typed by your registry, cached, and aware of drafts. - [Ordering](https://smoodly.io/docs/collections/ordering.md): A collection has one order, set in its schema, that the admin's list and your queries share. ## Globals - [Defining a global](https://smoodly.io/docs/globals/defining.md): A global is content that exists once and appears on many pages: the header, the footer, the company's contact details. You declare it in code; editors edit it in one place under Globals. - [Header and footer](https://smoodly.io/docs/globals/header-and-footer.md): The starter's header and footer are visual globals rendered by your layout, not sections placed on pages. This page walks through how they are defined, rendered and edited. ## Media - [The media library](https://smoodly.io/docs/media/library.md): Every image, video and file editors upload lives in one library. A field stores a reference to an asset, so one photo can appear in many places and be found from each of them. - [Images and crops](https://smoodly.io/docs/media/images-and-crops.md): An image field stores which asset to show and how to frame it. Smoodly's media host cuts the framed area at the width the layout needs, in a modern format, and the image component renders it without layout shift. ## Languages - [Locales and routing](https://smoodly.io/docs/languages/locales.md): A site publishes in one language or several. This page covers declaring the languages, how each gets its own URLs, and what editors see when a page exists in some languages and not others. - [Localized fields](https://smoodly.io/docs/languages/localized-fields.md): On an entry or a global, a field is shared across languages unless it chains .localized(). This page covers the rule, where it applies and what it means for queries. - [Language switcher and hreflang](https://smoodly.io/docs/languages/language-switcher.md): Every page and entry knows its own address in every language. A language switcher links from that map, and the site's hreflang tags come from the same one. ## Frameworks - [Astro](https://smoodly.io/docs/frameworks/astro.md): How Smoodly plugs into an Astro project: one integration in astro.config, views by file name, reads as live collections, pages cached whole and expired by tag, and what happens on a request. The installer writes all of it; this page is for reading it. - [Next.js](https://smoodly.io/docs/frameworks/nextjs.md): How Smoodly plugs into a Next.js app: the one route file, the server seam, the admin route group, and what happens on a request. The installer writes all of it; this page is for reading it. ## Reference - [Upgrading](https://smoodly.io/docs/reference/upgrading.md): Update the package and deploy. Your content model lives in your code and every build pushes it to your space: there is no migration to run. Every guide in one file: https://smoodly.io/llms-full.txt