Per Page Flexibility

I'm looking at Statamic as a replacement for WordPress, and have only run into one thing that seems pretty weird.

When designing pages there's a lot of content areas I would like to create fields for in the UI. These fields would be specific to a page and I can't think of a good way to do this.

One option is that I add them to the main pages blueprint and conditionally show them based on the template value. This is going to get really mess as it scales since I could end up with hundreds of page specific fields on the same blueprint.

The other option is to create unique blueprints for each page. This is probably the better of the two options, but is weird since I'll have some redundant fields that are needed on every page which I have to define on each blueprint.

Most smb websites need this, so I feel like I'm missing something. What are you guys doing?

>>>>>>> Unanswered <<<<<<<
1 Reply
2 Followers