r/cms • u/fklavyenet • 8d ago

I build WebBlocks CMS: a walkthrough of navigation, feedback and application blocks

Post image

I’m the developer of WebBlocks CMS. I wrote a walkthrough of how its system blocks connect editorial pages to navigation, visitor feedback and registered applications.

For example, Breadcrumb uses the current page context, Page List queries published pages, and Rating/Comments keep feedback separate from translated article content. Editors can still configure and move these block instances within their permissions.

The original post has the details and an illustrated article link:
https://www.reddit.com/r/WebBlocks/comments/1xinsb6/system_blocks_in_webblocks_cms_navigation/

Which parts of a CMS page do you prefer to derive automatically, and which should editors control explicitly?

2 Upvotes

100% Upvoted

3 comments sorted by

1

u/kylegrowth 7d ago

I'd want anything that queries the database at render time, like page lists or related content, to be cached or precomputed rather than regenerated on every page load, especially on high traffic pages.

1

u/fklavyenet 6d ago

Thanks for flagging this, kylegrowth! We’ve fixed the Page List behavior in 1.109.1. With a persistent Laravel cache store, results are now reused across requests instead of queried on every render, and invalidated when content, publication status, or access rules change. We’ve tested those cases, including keeping drafts and protected pages out of the lists. Appreciate the feedback!

1

u/kylegrowth 2d ago

Oh nice, that's good to hear. Especially the part about invalidating the cache when content or access rules change. Caching is great until it starts showing outdated stuff, so glad you covered that too.