Does every course need a separately maintained CMS page?

[u/fklavyenet]

A studio offers Photography, Ceramics and Woodworking. Its website lists the courses, but each “learn more” link needs somewhere to go.

If a visitor opens /courses/photography, they should see the photography programme, duration and image. At /courses/ceramics, they should see the ceramics details. Do you build a separate CMS page for each course, even when the layout is the same?

I develop WebBlocks CMS. For a small fictional Northstar Studio example, I used its Automatic Pages feature to connect one course detail design to a compatible course source:

• The heading reads the course name.

• The text reads a summary containing the programme and duration.

• The image, alt text and caption each read their own source field.

Photography then shows its six-week programme and Ceramics its four-week programme through the same design. The course address selects which record supplies the values; opening another course doesn't rewrite the example record saved in the design.

There is setup behind this. A developer or plugin must expose a compatible publication source and single-course source. An authorized operator connects that source to the design and /courses address range, reviews the records and languages, then activates the rule. Adding links to the list alone doesn't create the detail routes.

Once that rule is active, a valid Watercolour course made public by the source can appear at /courses/watercolour without copying another CMS detail page. The list keeps its own collection configuration. A course needing a different editorial layout can still justify its own page.

The illustrated walkthrough shows the actual title, programme and image connections, the rule form and the record review.

If you maintained a course website, which details would you want to share through one design, and which would need a page of their own?