I’m wondering how many partners would find useful the ability to add custom fields on pages in the Treepl admin. For example (and against my every recommendation) I have a client that wants to use images for page titles instead of dynamically populating the title via Liquid in the page template. They want to use a font for the page title that isn’t a web font and they can’t find anything close. Again, I know why this is wrong for so many reasons, but it brings up a common issue that I think could be circumvented by adding custom fields on the pages - just like Custom Modules. I think this was a big missing feature with Adobe BC as well. While this is a bad example of how it could/should be used, does anyone agree that the ability to add custom fields to the pages would be very useful? It would be great, in this instance, to just have an image field that the client could use to select the image for each page rather than having to hard code it in the Content Template or WYSIWYG editor at the page level. Just thought I’d check here to see if this should/could be added to the backlog? I’m open to any suggestions if there is a good workaround. I know we could create all of the pages as Custom Modules, but I’d like to be able to just have regular pages on the site and not have everything set as a Custom Module, but maybe that’s the only way.