Create a Collection

Organize your content and define its structure. In this guide, you'll create a collection, add the fields your content needs, and publish a schema ready for resources.

Prerequisites

  • Access to the FoxNose dashboard (app.foxnose.net) with permissions to edit the target environment.
  • An existing project and environment (e.g., Production). New accounts create a Personal organization and a default Production environment automatically.

Step 1 – Open the Environment

  1. Sign in at app.foxnose.net.
  2. Pick your organization (Personal for single-user accounts).
  3. Choose the project you want to modify.
  4. On the project page, select the environment (the default is Production). You land on the Database section of that environment.

Step 2 – Add a Collection

  1. In the Database section, click Add Collection.
Database page showing Add Collection button
  1. Fill out the dialog:
    • Collection Name – Display label for editors (e.g., Articles).
    • Alias – URL-safe identifier; becomes part of API paths (e.g., articles).
  2. Click Create Collection. The collection now appears in the list.

Step 3 – Publish a Schema Version

  1. Select the new collection to open the detail panel.
  2. Switch to the Collection Schema tab.
  3. Click Create Version. FoxNose creates draft version v1 and opens it automatically.
  4. Go to the Schema tab, choose Add Field, and configure the field (name, key, type, properties). Repeat for each field you need.
Schema editor showing field list and Add field button
  1. Once all fields are added, click Publish. The version's status changes from Draft to Published, making it available for content.

What You've Built

You now have:

  • A collection that organizes your content
  • A published schema that defines the structure of your resources
  • An empty container ready for content
Content tab showing Resources section ready for content

Tips

  • Use plural aliases and lowercase (e.g., articles, products) to keep URL paths predictable.
  • Draft schema changes in a non-production environment first, then copy versions across environments via the Management API.
  • API reference: Create Collection, Create Version.

Next Step

Your collection is ready — now let's add content to it.

Add Your First Resource

Was this page helpful?