6: Workflow

By David V Rodriguez

Send comments to: dvr@dvrodriguez.com.

Introduction

Part 1: The Fundamentals

1. The features a CMS provides

2. Starting small: Designing a CMS for one type of content

3. A general solution: A data model for all kinds of content

4. Encapsulating the system's rules within views and stored procedures

5. Permissions

6. Workflow

7. Writing plug-ins to handle custom content types

8. Should a CMS hold its own code?

9. Templates

Appendix: The full data model with associated plsql

• cm-tables-1.sql -- Table definitions, part 1
• cm-tables-2.sql -- Table definitions, part 2
• plsql-preload.sql -- utility functions needed by the rest of the code.
• plsql-permissions.sql
• plsql-workflow.sql
• plsql-content-views.sql -- Definitions for views like cm_v_content, etc.
• plsql-content-procedures.sql -- Functions and procedures involved with updating the core tables
• story.sql -- plsql to support the 'story' content type
• postload.sql -- loads the default states, actions, etc.

• load.sql -- one file to load the other sql files in the correct order
• plsql.sql -- loads all views and stored procedures in the right order
• drop.sql -- drops the tables in the correct order

Next: Writing plug-ins to handle custom content types

---

Send questions/comments/errors to dvr@dvrodriguez.com