I’m excited to share that development on Poster CMS 3 has officially begun!
This will be a major new version of Poster CMS, built exclusively for Stacks 6, bringing a modernized architecture, enhanced performance, updated PHP version compatibility, and exciting new features — while staying true to the simplicity and power you’ve come to expect.
✅ What’s Planned So Far
Stacks 6 only: Poster CMS 3 will be built for Stacks 6 only to deliver better performance and flexibility.
Seamless upgrade path: Full compatibility with Poster 2. Just copy and paste your content into Stacks 6 and continue building. Only minimal changes, e.g. to the layout, should be required.
Online Markdown Editor: A powerful web-based editor for creating and managing blog posts — working directly with your existing .md files.
Alloy Markdown importer: Bring your Alloy blog content over to Poster CMS 3 with minimal effort.
Editable content areas: Add individually editable areas anywhere on your site — ideal for clients or micro-CMS needs, which can be changed online via the markdown editor.
PHP 8.4 support: Built to work flawlessly with the latest PHP versions.
And yes — Poster CMS 2 is already compatible with the latest Stacks 6 beta!
💡 Your Input Wanted
Now’s your chance to shape the future of Poster CMS. I’d love to hear:
What features are missing for you in Poster CMS 2?
How are you using Poster today — and what would make your workflow easier?
Are you looking for any specific integrations (e.g., search, third-party APIs, image galleries)?
Would you use Poster CMS for non-blog use cases? (Documentation, portfolios, client content areas?)
Post your ideas, feature requests, or pain points below — or message me directly 💬
I would definitely like to start using Poster 3 for non-blog purposes (along with a blog, of course);
RSS is an important form of communication for me. I would love it, if Poster’s RSS function would include a Full-Post Content capability (instead of, or in addition to, the Summary Content) – the thing you’ve promised to consider.
In Poster 3, I would like to have maximum compatibility with Iconic Gallery Stack especially in text search.
For example in a post I insert Iconic Gallery with photos of variants of a product with a precise description in each single photo (example “gluten free”).
I would like the Poster 3 search to be able to search for text in the descriptions of the photos for a targeted search, as in this case, “gluten free” product variant.
@Jannis It would be great if Poster3 could be easily set up for creating blog posts simply and easily — without first opening RapidWeaver and/or Stacks Pro or Stacks 6.
I would love to be able to use a 3rd party Markdown editor to do this, such as Drafts or Bear or Ulysses or iAWriter.
I do know that you believe this is already technically possible with Poster 2, but I have never been able to set this up — even after watching your video tutorial for probably 100x. The language barrier is just insurmountable.
Ideally, I’d love to be able to make blog posts with just my iPhone and a Bluetooth keyboard.
To create a blog w/o the need for re-publishing, the feature of the ‘Markdown folder’ exists. This allows to create posts within the limits of what can be described in markdown, i.e. it’s well suited for text, and maybe a single image here or there.
To improve on the built-in blog capabilities, it would be nice to be able to create multi-image layouts - a blog item supports this by allowing to place a Gallery stack in it, yet there is no such option with the markdown blog files. (I guess, since HTML can be included “everything” is possible in principle, but one would have to prepare the required HTML code available to be inserted into a markdown text file.) So I wondered whether there could be an option, to extend the blog post syntax to be able to access something like the Gallery functionalities from within the text files.
Of course, this might only be available when the Gallery stack is placed somewhere within the Poster stack. To come up with a general solution for all kind of image stacks, that would be asking too much.But since you already offer the Gallery image stack in your portfolio, I would love to see an integration that dynamically extends this functionality to show multiple images in a block even to the use in markdown files.
The online Markdown Editor already has some nice image Features like a browser for already uploaded images.
This shall be extended as you described, add an image gallery section in the markdown file, with help of a simple html doc markdown, and produce a great looking image gallery out of the box.
Thank you, that sounds great - the online MD editor is likely a valuable feature, yet, I presume that many also have your repository stack, which kind of already provides this functionality - maybe not as nice. Integrating some image gallery functionality, however, would really up the game.
There is always the challenge for you:
Do you want to create the ‘super stack’ that has everything built-in, or do you offer the functionality split across multiple stacks, that work well together.
No matter your choice, you will hear some complaining Either, why do I have to pay so much for the ‘super stack,’ when I already have 90% of the functionality with your other stacks covered … Or, why do I need to buy all those stacks separately, when I want the blog functionality as one stack …
I would like to use it for portfolios.
I always liked the way Nick Cates approached this portfolio concept with his light page stack (now offered by Weaver Space). I don’t know if the idea of a page with a submenu or buttons to display images, text, or video to show how a project developed can be achieved with Poster 3.
I figured it was finally time to start using Poster 2 — I actually bought it right before catching Covid in 2020, which kind of derailed things for a while…
Anyway, I’m now rebuilding my site using Source, and just started setting up Poster 2 properly. Loving how it works so far, and it’s great to see you’re already working on Poster 3!
Thank you @artm Alain, and no worries, you will be able to reuse all your content, nothing will be lost. And it will take some time on my side.
Cheers!
