Blog Sections Open
Creating Two Related Pages from a Single DocLister Flow
A workflow idea for cases where one action should create a main resource and an immediate child resource as part of the same process.
Sometimes one content action is not enough. A project may need to create a main page in one folder and at the same time create a second page as its child. That is a workflow question, not just a listing question.
The key point
DocLister itself is a listing engine. If the workflow includes creating multiple connected resources, the clean solution usually involves a custom creation step rather than expecting DocLister to act as the whole business process.
Recommended architecture
- create the main resource first
- capture its new id
- create the second resource with the first one as parent
That keeps the relationship explicit and avoids fragile assumptions in the listing layer.
Showing the Resource Author in DocLister Output
How to think about author output in DocLister when the list template already uses custom placeholders and extended resource data.
FastRoute-Based Custom Routing in Evolution CMS 2.0
A guide-oriented post about custom routing in Evolution CMS 2.0 using FastRoute ideas inside the example-package workflow.