Blog Sections Open
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.
Once a list template moves beyond simple titles and dates, author information is often the next useful field editors want to show. The main question is whether the project treats the author as a native resource property, a user relation, or a custom field.
Three common author patterns
- use the resource creator or editor id and resolve it to a user name
- store the author name directly in a TV
- link the resource to a separate author entity or profile record
Before building the output, decide which of those models the project actually uses. Once that is clear, DocLister can expose the final author value cleanly in the template.
Filtering DocLister Items by a TV Date Field
How to work with TV date fields in DocLister when values may include a plain date or a date-time string.
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.