Skip to content

Free early access: build and publish your site by hand today. AI features (drafting, editing, images) are not open yet.

Developers & content teams

Start with the shape of your content. Build the pages on your canvas.

Define fields for reading time, difficulty, team, publication date, or anything else your content needs. Build pages on the canvas, connect them to your fields, and publish.

Collections & fields

Your content has attributes no template ever offered you

Every kind of content needs different attributes. They have to exist as data before you can list by them, filter on them, or reuse them somewhere else.

Swipe or use the arrow keys to explore the content types.

  • Blog

    • excerptExcerpt
    • read_timeReading time
    • topicTopic
    • authorAuthor
  • Case studies

    • industryIndustry
    • outcomeOutcome
    • durationEngagement length
    • stackStack used
  • Job posts

    • teamTeam
    • locationLocation
    • employment_typeEmployment type
    • senioritySeniority
  • Events

    • starts_atStarts at
    • venueVenue
    • capacityCapacity
    • rsvp_urlRSVP link
  • Help docs

    • categoryCategory
    • difficultyDifficulty
    • updated_atLast updated
    • relatedRelated docs
  • Team

    • roleRole
    • photoPhoto
    • bioBio
    • linksLinks

Until now

Two common approaches, each with a tradeoff

Template builders

You trimmed the content to fit the template

When a template does not let you add a field, information often goes into the body instead. Without a separate field, that information is harder to filter, sort, or reuse on another page.

Your data becomes a paragraph

Headless, built in-house

You built exactly what you wanted, then waited

You can define the content structure freely, but building and changing the interface takes development work. Content updates can depend on the engineering schedule.

Interface changes need development work

With Asella, you can keep both structured content and design freedom.

How it works

Define your content, then build the pages

Define collections and fields, build pages on the canvas, and publish your site.

  1. 01Admin → Collections

    You define the fields

    Create the fields each collection needs and choose a type: text, number, date, option, toggle, or image. The ai_hint metadata can describe what a field means.

  2. 02GET /meta/schema/collection:guide

    Use one field definition

    View field definitions as JSON Schema 2020-12, including x-ai-hint and x-ui metadata. Use that structure to connect your content API and page layouts.

    GET /meta/schema/collection:guide
    {  "type": "string",  "enum": ["beginner", "intermediate", "advanced"],  "x-ai-hint": "Show it as a 3-step scale, not a dropdown.",  "x-ui": { "widget": "scale", "store_visible": true }}
    Example excerpt of the difficulty field schema from the response.
  3. 03Layout document

    Build pages on the canvas

    Arrange text, images, Stack, Grid, and other blocks. Connect page elements to CMS fields, then adjust their placement and styles on the canvas.

  4. 04Canvas

    Preview and publish

    Check desktop, tablet, and mobile previews. Adjust spacing and typography, then publish the site when it is ready.

Canvas

Build and refine pages on the canvas

Add blocks, select elements, and adjust their placement and styles.

  • Preview each screen size

    Preview desktop, tablet and mobile side by side and adjust each layout. The initial preview widths are 1200, 810 and 390px, and you can change them.

  • Auto layout

    Arrange blocks with Stack and Grid, then adjust spacing to suit the content. Each child can fill the available space, keep a fixed size, or use a fractional size.

  • Components

    Save a group of elements as a component and choose which properties each instance can override. Changes to the original component are reflected in connected instances.

  • Seven typography axes

    Family, size, weight, line height, letter spacing, transform, decoration. Typography follows CSS inheritance; override only the property you need.

  • Effects and motion

    Attach scroll, hover and tap responses from the panel. No animation library to learn first.

  • Code overrides

    Use code overrides for expressions the settings panel does not support. Your code runs in a sandbox.

Content and layout

Keep CMS records separate from page layouts

Edit page placement and styles in the layout document. Manage CMS entries and field definitions separately in the CMS.

Edit in the layout

  • Layout and placement
  • How collections are listed and ordered
  • Copy and image placement
  • Motion and effects

Manage separately in the CMS

  • Your entries
  • Field definitions
  • Entry publication state
  • Collection settings

Page layout editing and changes to CMS records are managed separately.

For developers

The schema is the contract

Field definitions are available as JSON Schema. The admin interface and content API use the same field definitions.

Platform

There's more here than a builder

The parts you need to actually run a site, all sitting on the same contract.

  • Collections and entries

    A blog, a case study library, a careers page — same mechanism. Create a collection, define its fields, and the builder can read it from that moment on.

  • Draft and publish

    Every entry carries its own draft and published state. What you haven't published exists only in the canvas preview; it never reaches the live site.

  • Bound straight into the builder

    Design one item, connect each element to a field with $bind, and it repeats per record. When a value is missing it falls through to $fallback.

  • Workspace and project permissions

    Data is organized by workspace and project. The server checks account membership and access permissions.

  • Media

    Upload and transform images, then connect them to image elements on the canvas.

  • Headless, if you prefer

    We don't have to render anything. One store key and you can read your published content from wherever you like.

Comparison

What you no longer have to trade away

Compare how content structures are defined and connected to page layouts.

What you no longer have to trade awayTemplates with limited fieldsCustom developmentAsella — The last column is Asella.
Attributes unique to your contentWithin template limitsExtend through developmentDefine collections and fields
Design freedomWithin template limitsImplement directlyEdit on the canvas
Engineer requiredDepends on the templateFor implementation and maintenanceNo code for basic editing
Changing one line of copyEdit in the editorDepends on the implementationEdit on the canvas
Content separated from designDepends on the productConnect directlyConnect through field bindings
AI generationDepends on the productCan be added separatelyIn development — unavailable now

Questions

What developers ask first

  • Can I keep my existing site's front end?

    Yes. Use the Store API to read content stored and published in Asella from your existing front end. Content must be added to Asella collections; this does not mean direct connections to external CMSs or automatic migration tools are provided.

  • Can I change a field's type later?

    You can change a field’s name, description, order, and required status. To protect stored values, its type cannot be changed. Create a new field and move the values if you need a different type.

Put your website online today

Start free with no card and publish on a free address right away.