GhostCMS: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) Created page with "Top level objects * Services * Credentials * Request * Response Verbs * Create * Update * Crup ??? * Read * Delete A service provides some or all of the verbs for a data-typ..." |
Adamcolton (talk | contribs) No edit summary |
||
| Line 15: | Line 15: | ||
The goal is to build an ecosystem. Many standardized data-types. Before a service can be create a definition of it's data type must be defined. Collections of services? | The goal is to build an ecosystem. Many standardized data-types. Before a service can be create a definition of it's data type must be defined. Collections of services? | ||
I've worked on credentials before (at least in theory). I'll start with the classic permission model: | |||
* Exists | |||
* Read | |||
* Write | |||
* Admin | |||
though eventually, I'd like to add various admin levels so that someone can share read permissions, but not write permissions. For the rest, see [[Go Wiki/CMS]]. | |||
Latest revision as of 19:45, 8 April 2015
Top level objects
- Services
- Credentials
- Request
- Response
Verbs
- Create
- Update
- Crup ???
- Read
- Delete
A service provides some or all of the verbs for a data-type. A service takes a request and a credential and returns a response. A service is like a plugin in most other CMS.
The goal is to build an ecosystem. Many standardized data-types. Before a service can be create a definition of it's data type must be defined. Collections of services?
I've worked on credentials before (at least in theory). I'll start with the classic permission model:
- Exists
- Read
- Write
- Admin
though eventually, I'd like to add various admin levels so that someone can share read permissions, but not write permissions. For the rest, see Go Wiki/CMS.