Quick overview of cloud based CMS prismic.io ( http://prismic.io )

2. Agenda
1. Traditional vs cloud-based CMS
2. prismic.io approach to content management
3. Managing content
4. prismic.io API
5. Pros&cons
6. Alternative solutions

3. Traditional vs cloud based CMS
prismic.io | the cloud based CMS 3

7. prismic.io | the cloud based CMS 7
Content administrator responsibilities
1. Repositories, security & users management
2. Content types creation
3. Content collections, bookmarks & relationships management

8. prismic.io | the cloud based CMS 8
CONTENT ADMINISTRATOR RESPONSIBILITIES
Repository, API security
& users management

9. prismic.io | the cloud based CMS 9
CONTENT ADMINISTRATOR RESPONSIBILITIES
Content types definition
vide Document masks

10. prismic.io | the cloud based CMS 10
CONTENT ADMINISTRATOR RESPONSIBILITIES
Content types definition
Content types are build with JSON fragments:
"unique_fragment_id" : {
"type" : "StructuredText",
"fieldset" : "Here is the fieldset",
"config" : {}
}

11. prismic.io | the cloud based CMS 11
CONTENT ADMINISTRATOR RESPONSIBILITIES
Content types definition – fragment types
BASIC FRAGMENT TYPES
• Text
• Number
• Select
• Color
• Date
• Range
COMPLEX FRAGMENT TYPES
• Structured Text
• Image
• Link
• Embed
• Group

12. prismic.io | the cloud based CMS 12
CONTENT ADMINISTRATOR RESPONSIBILITIES
Collections
Groups of content entities that follows specified rules.

13. prismic.io | the cloud based CMS 13
CONTENT ADMINISTRATOR RESPONSIBILITIES
Bookmarks
Groups of content entities that follows specified rules
or selected indvidually.

14. prismic.io | the cloud based CMS 14
Content publisher/editor responsibilities
1. Releases planing and approving content for production
2. Content creation

15. prismic.io | the cloud based CMS 15
CONTENT PUBLISHER RESPONSIBILITIES
Releases planing
• One live version of document
• Multiple drafts of document per release
• One version of document queued for release

16. prismic.io | the cloud based CMS 16
CONTENT EDITOR RESPONSIBILITIES
Content authoring
• No version is deleted, NEVER
• You can have as many draft versions as needed
• Color states for the status of particular document
LIVE NOW
QUEUED DRAFT
DRAFT

19. prismic.io | the cloud based CMS 19
https:/
/yourproject.prismic.io/api
Returns general information about your repository in developer-friendly JSON format
a) Releases information
b) Available content types
c) Bookmarks
d) Tags
e) Forms

20. prismic.io | the cloud based CMS 20
https:/
/yourproject.prismic.io/api
Forms object
Serves information about data access methods

21. prismic.io | the cloud based CMS 21
https:/
/yourproject.prismic.io/api
Results object
Contains data that fits specified query
{
"id" : "UkL0gMuvzYUANCpF",
"type" : "product",
"href" : "https://lesbonneschoses.prismic.io/api/documents/search?ref=UkL0hcuvzYUANCrm&q=%5B%5B%3Ad+%3D+at%28document.id%2C+%22U
"tags" : [ "Macaron" ],
"slugs" : [ "speculoos-macaron", "a-speculoos-macaron" ],
"data" : {
"product" : {
"price" : {
"type" : "Number",
"value" : 3.5
},
"name" : {
"type" : "StructuredText",
"value" : [{ "type" : "heading1", "text" : "Speculoos Macaron", "spans" : [ ] }]
},
/* etc. other fragments */
}
}
}

22. prismic.io | the cloud based CMS 22
https:/
/yourproject.prismic.io/api
API Browser
For quick query definition and testing

23. prismic.io | the cloud based CMS 23
Pros & cons
PROS
• No infrastructure needed for content storage
• Adaptive content strategies ready
• Easy to use interface
• Quick repository setup
• Easily accessible API
• Flexibility in content types definition
• More features to come
CONS
• No explicite localization support (yet)
• Requires JSON knowledge to configure
content types
• Minor UX/accessability issues
• One-way communication available now
• Still in public beta
• No 3rd party integrations available
• Primitive user access management

25. prismic.io | the cloud based CMS 25
tl;dr
We believe that organizing content in trees is very much a front-end issue, one of which we're trying to stay away
from. A good question to wonder is: if you were to reuse this content elsewhere (in an smartphone app, or something else
entirely), would you use for sure the same tree structure?
I guess a given document you have is placed somewhere in the tree for some "semantic" reasons, related to
what it's about, or what kind of content it is, etc. My advice would be: rather try to think about those reasons, and qualify
the document with them (maybe with tags, but not necessarily). This will make your tree possible, but also all and any other
content organization you may want for the same content."
- Rudy Rigot

26. Thanks
github : angular-prismic-playground @ dprokop
@prokopd