Set up your organization

Every path on this site starts inside an ebitex organization: you create a key there, and your code reads what that organization has published. This page gets you to that point. If you already have an organization with published content, skip to the path you are building.

Create an account

Go to hub.ebitex.io and sign up. Hub is the suite’s home: it holds your organization, its members and its billing, and it is where you switch between the products.

A new account has no organization yet. Create one from the organization control at the top of Hub’s sidebar, which offers Create an organization. A new organization starts on a Pro trial, which is what the rest of this page assumes.

One account can belong to several organizations. An organization is the boundary for everything on this site — content, forms, members and keys all belong to one, and a key never reaches past the organization it was created in.

The three apps

You sign in once, and move between the products from Hub.

App	Where	What you do there
Hub	hub.ebitex.io	Members, billing, and Forms SDK keys
Content	content.ebitex.io	Model, author and publish content; delivery and management keys
Forms	forms.ebitex.io	Build forms and read responses

What your plan needs to include

Reading published content needs no particular plan: a delivery key works on every plan.

Writing content from a script or an agent does. Management keys need the Pro plan or above. That is checked when the key is created and again on every request, so a key stops working if the organization moves to a lower plan. An organization on a Pro trial can create them straight away. See pricing.

Publish something to render

A new organization is empty, and the Content Delivery API serves only what has been published. Until something is published, a correctly written site renders nothing and every address answers path_not_found. There are two ways to get past that.

Import the sample content. The northwind-coffee sample carries seed/ bundles. final.zip is the whole content model — Contracts, Templates, pages and media; the step-*.zip files are checkpoints from the tutorial series that builds it, so take final.zip unless you are following that series. In Content, open Tools → Transfer, select Upload bundle file…, then Import… next to the staged bundle.

The import asks about Identity. Choose Fresh identity, which gives every item a new id: the bundle was exported from another organization, and ids cannot be carried across one. The default, Preserve identity, is for moving content between environments of your own organization. An import creates drafts, so publish the site’s pages afterwards.

Or build a page yourself. Model a Contract, add a Template, write a Component, then bind it to a page in Composer. The content model explains those four words, and Publishing explains what publishing copies and where it goes.

Either way, the finishing step is the same: publish. A draft is invisible to every key on this site.

Then pick your path

You are building	Start at
A site that fetches content in the browser	Render content in a static site
A site that renders on your own server	Render content on a server
A .NET server	Render content from a .NET server
A page that shows one of your forms	Add a form to your site
A script, pipeline or agent that writes content	Content as code

Each path opens by creating the key it needs. Environments and keys describes the three families of key and which one to reach for.