Community forum for knowledge and support

Updated last year

the benefits of static pages over cms-driven layouts

At a glance

The community members are discussing whether it's a good idea to create portfolio pages as static pages rather than using a CMS, which they find to be limited. One community member has decided to go with static pages, as they found the CMS layout to be limiting. They created a separate layout page for each use case and saved them as drafts to duplicate as needed. The other community members found this approach to be helpful.

JJoshua Cho

Hello!!

Do you guys think it’s good idea to make portfolio pages as static pages rather than CMS(CMS post/layout is quite limited)?

3 comments

AAndre Parmar

This is what I have decided to do, I originally started with creating a Design (work) page layout and then a separate page for Case Studies. With the limitation because of CMS i opted to just go with static pages

AAndre Parmar

For each different use case page I created a layout page and saved it as a draft to then just duplicate

JJoshua Cho

Really helpful! Thanks!! 🙏

Add a reply