Json representation

• Introduction
• Pages
• Forms

Introduction

Since we support routing, which ables us to hook up to different api types, we can represent our object in all kinds of ways. But the most simplest, and currently only implemented way, of getting things up and running is by doing AJAX calls to endpoints that return JSON.

All JSON objects in our api’s are wrapped in their own namespace with a type key that announces that presence of the namespace. For example:

{
	"type": "form",
	"form": {
		/* A Form object */
	}
}

Pages

These are the wider panes where the content is presented and can be edited.

A page is a panel which can contain page items.

{
    "type": "page",
    "page": [
        /* The page items */
    ]
}

Page item

Every type of page item should implement this Abstract

Header

A header is commonly used page item at the top of a page

{
    "type": "header",
    "header": {
        "text": "Edit club"
    }
}

Form

The place with which your user interacts. It even has its own chapter, called Forms. As usual it again is wrapped in its own namespace

{
    "type": "form",
    "form": [
        /* The form items */
    ]
}