Post

Today I've delved into the depths of routing and decided. File System based routing is fundamentally broken if you're trying to render static content.

FIle System routing conflates route with template, and to some extent content. Any given route(static or dynamic) is inextricably tied to a single template. This works great for "apps" that have heavy dynamic content and but not for relatively static content.

If the CMS handles the content and the front-end framework handles the templating; who handles the routing? Frameworks think they do. This requires an agreement on routing between the front-end and CMS. But if the Framework deferred to the CMS, that'd be so much simpler.

0 reposts0 likes

No replies yet.