I think the presentation was good to get an idea of where Bolt is placed in the CMS landscape.
If it were a different audience (IT managers/CTOs for example) I would've given it a higher rating.
However I (as a PHP developer) would've rather had a more in depth view of the features of Bolt and the possibilities.
For example from what I understood a content creator is really limited in his freedom because of how a content type is really strictly defined.
I do like the interface (which is mainly focussed on editors) and the way of installing the software.
But I have my doubts about the descision of letting the backend-developer create the content-types (what was shown in the yaml-config files)
I agree configuring in yaml is a peace of cake but if an editor wants to redefine a content-type or create a new content type he/she must first give order to the backend developer to setup a new content type.
Another thing I have my doubts about the ease of building extensions on top of it. Is there some pattern that has to be used for writing extensions for example or some framework? And how are extensions available? Is there some 'store' like the app-store where extensions are offered? Typo3 has a TER (typo3 ext repository) Drupal and both Wordpress do offer a space on their website for offering and downloading plugins, how is that with the Bolt CMS?
Comments
Comments are closed.
I think the presentation was good to get an idea of where Bolt is placed in the CMS landscape.
If it were a different audience (IT managers/CTOs for example) I would've given it a higher rating.
However I (as a PHP developer) would've rather had a more in depth view of the features of Bolt and the possibilities.
For example from what I understood a content creator is really limited in his freedom because of how a content type is really strictly defined.
I do like the interface (which is mainly focussed on editors) and the way of installing the software.
But I have my doubts about the descision of letting the backend-developer create the content-types (what was shown in the yaml-config files)
I agree configuring in yaml is a peace of cake but if an editor wants to redefine a content-type or create a new content type he/she must first give order to the backend developer to setup a new content type.
Another thing I have my doubts about the ease of building extensions on top of it. Is there some pattern that has to be used for writing extensions for example or some framework? And how are extensions available? Is there some 'store' like the app-store where extensions are offered? Typo3 has a TER (typo3 ext repository) Drupal and both Wordpress do offer a space on their website for offering and downloading plugins, how is that with the Bolt CMS?