Hacienda.io is a new content management system that aims to address the challenges of managing different types of content. It uses a content-as-a-service approach and good development practices to provide an easy to use system for content editors and developers. Content is stored and versioned using Git for a single source of truth. The API is RESTful and uses content negotiation for translations. The goal is to build a modular system with a stable API that gives users control.

1. HAÇIENDA.IO
A New Approach to Content Management
Alina Băluşescu & Mircea Moise

2. WHO ARE WE?
2
Alina Băluşescu
Mircea Moise

3. THE PROBLEM
With so many different forms of content, how do we (easily) manage it all?
3

4. THE SOLUTION?
4

5. A web content management system (WCMS) is
a software system that provides website
authoring, collaboration, and administration
tools designed to allow users with little
knowledge of web programming languages
or markup languages to create and manage
website content with relative ease.
5
– Mike Johnston

6. CONTENT MANAGEMENT SYSTEMS
6

7. 7

8. 8

9. THE ALTERNATIVE –
9
BUILD OUR OWN!

10. OUR APPROACH
• Content-as-a-Service
• Good development practices
• Avoid locking in a solution from the start
• Easy for content editors and devs to use
10

11. 11
haçienda.io

12. CONTENT MANAGEMENT != CONTENT EDITING
12

13. 13
thoughtworks.com edit.thoughtworks.com
Read Write/Update/Delete

14. DEMO

15. THE DETAILS
15

16. HAÇIENDA.IO
Data is not Presentation
16

17. DATA IS NOT PRESENTATION
1717
{
”name”: “Aman Bhutani”,
”job_name”: “SVP of Worldwide Engineering”,
”job_description”: “Aman Bhutani leads the engineering team… ”
}

18. HAÇIENDA.IO
RESTful Interface
18

19. RESTFUL INTERFACE
19
Action HTTP Verb URL Header
Retrieve draft GET /:type(/:id) Accept-Language: :locale
Retrieve public GET /:type(/:id)/public Accept-Language: :locale
Create POST /:type/:locale -
Publish POST /:type/:id/:locale -
Update PUT /:type/:id/:locale -
Delete DELETE /:type/:id/:locale -

20. HAÇIENDA.IO
Translations as
Content Negotiation
20

21. TRANSLATIONS AS CONTENT NEGOTIATION
21
Action HTTP Verb URL Header
Retrieve draft GET /:type(/:id) Accept-Language: :locale
Retrieve public GET /:type(/:id)/public Accept-Language: :locale
Create POST /:type/:locale -
Publish POST /:type/:id/:locale -
Update PUT /:type/:id/:locale -
Delete DELETE /:type/:id/:locale -

22. HAÇIENDA.IO
Authentication not
Authorization
22

23. HAÇIENDA.IO
Git as
storage mechanism
23

24. GITHUB AS SINGLE SOURCE OF TRUTH
24

25. DEMO

26. THE FUTURE
• Get to v1.0
• Get to a stable API
• Leverage more Git
• More modular system
• translation logic can be swapped
• user has more control over authentication
• Want to get involved? Fork the repo
26

27. THANK YOU
Further reading/sources:
http://hacienda.io/xconf.html
abaluses@thoughtworks.com
mmoise@thoughtworks.com