Support Custom Fields in Pages
J
Josh Carter
Page metadata can support nested info, and therefore would be fantastic to have structured data in pages, which would allow clients to easily edit content in a safe CMS based environment without having to go in the visual editor or code, which has caused clients to break layouts in the past, which normally leads us to recommend to clients to not touch pages unless they know what they're doing.
As a solution to this, we have often created Webapps with a single item in for the client to mange. Not only does this clutter up Webapps, but it takes the data out of context, and if not properly maintained, can cause fields to be redundant and not used as the site is updated.
Structure like this would be fantastic: https://gist.github.com/JoshCarterWeb/32ecb3174ca367ac8ba5360293d5997b
It would also be a
mega
bonus to not have the fields named custom_field_2. It makes things so much harder.Log In
R
Rox Dawson
We use content area instead of webapps with one item and recommend clients edit the content area which is almost plain text or limited fomatting
L
Liz Gibbs
And yes to descriptive field names!