“Can’t my Pressible site be a more customizable CMS?”
Patrick, Eric, and i just had a great talk about this question. It arose (again) from an example case: the user that has a bunch of content (say, 100 posts), and a clear idea of how they should be interconnected. Now, it’s not that Pressible doesn’t already have a solution for that – we’ve got Topics, Tags, and Contributors that all act as interrelated metadata – but what if a user wants even more? For example, what if I want to not only give a set of posts a Topic description, but include HTML in it? Pressible doesn’t allow that: Topic descriptions are plaintext only.
Such matters give rise to existential crises.
Hence, with some trepidation (and some fear), we talked our way through this problem from two directions:
- Technically, putting HTML into Topic descriptions breaks the WordPress framework. Now, this isn’t awful, but it feels wonky – after all, why should this “brief introduction” to a set of posts carry the burden of linking out to other pages, posts, etc.?
- Should Pressible support some kind of “page hierarchy” to allow for more static content, even though this contradicts the major design theory of How and Why Pressible leads users to create great (read: active) sites? That is, we pondered whether or not there should be a more robust (if traditional) structure living beside the recency-based, dynamic structure of a Pressible site.
This led us to a two-part answer:
- The solution is already built into Pressible: When users have an idea about how their content could be viewed in a structured way, they should create one page that introduced a visitor to this structure (and only if the “About” page is not already sufficient).
- On such a page, they could call out specific Topics (and link to them). They could also, of course, describe the Topics with whatever additional links are needed (Pages allow full HTML). Plus, to round out this strategy, Topic descriptions could include a call-out to the Page (“For more on this Topic, see the ‘About’ page above”).
Overall, this feels like a lightweight (and sufficient!) answer to the problem. We’ll see how it works in practice, and if Pressible users respond to this kind of simplicity… or yearn for something more structured and complex.