Hi Guys!
It would be great, if we could generate an options page out of a custom post type like it is possible with ACF. I have especially data like adresses, phone numbers, the VAT-ID and so on in mind.
Then we could set up a CPT with the data (or fields) we need. This data could then be given out via a View or in a CRED-Form (i.e. the mailto-E-Mail-Adress) by a shortcode.
Most often it is a matter of set and forget, but if you have to make a change to this data sitewide, it could be a lot of work. Working with placeholders (like shortcodes for the forementioned data) would make it very easy. Also, if you are developing client's sites, you would be able to fill in the client-specific data and you are good to go.
A practical example: I have a boilerplate for new projects with some pre-made pages. Every client needs to have a contact page and an imprint, perhaps also a terms/conditions page. The data in the contact page, the imprint and the terms/conditions page are - regarding the contact information - almost the same. So if I could make use of shortcodes as placeholders for i.e. the street or the zip code, I would just fill in the data in the relevant fields in the options page - once (!). And this data would be populated sitewide (esp. on the contact and imprint page) because it is read out of the database.
I know that you made Views integrateable with Theme or Options Frameworks, i.e. Options Tree, Cherry and so on. So I could code these options pages by myself. But the more elegant way would be a tight integration with Toolset and the generation of a options page by Toolset. The corresponding shortcodes could then be populated by your Fields-Dialogue-window in the editor or in the Admin-Header-Menu.
Another suggestion related to my comments on your announcement regarding the integration ov VC and Content Templates (https://toolset.com/2016/05/toolset-2-1-preview-visual-composer-integration-content-templates/): what about a Layouts-based Page-Builder? Besides my suggestion to use Layouts to create Content Templates and so on. Please refer to my comments.
And could you please reimplement the CSS-Editing-Tab in Layouts’ Row-Editing-Popup which was capable of automagically make the defined rules chooseable in the classes input field. This functionality seems to be abandoned since you implemented the Layouts CSS-editing-screen. It would become perfect, if all the CSS-directives from the rows or content templates or whatever become available in the Layouts CSS editing screen and are also available in the corresponding rows, content templates and so on.
A short feedback is appreciated.
Kind regards & Greetings from Germany!
Bernhard