Composer or custom system
Permalink 1 user found helpful
Hi,
I would like to know your advices for the pros and cons concerning the development of a news/press system using composer tools or a custom system with single pages. This custom system will generate dynamically news listing page and news details page with object ids from query string. No page will be added to the sotemap.
Thanks
moosh
I would like to know your advices for the pros and cons concerning the development of a news/press system using composer tools or a custom system with single pages. This custom system will generate dynamically news listing page and news details page with object ids from query string. No page will be added to the sotemap.
Thanks
moosh
Little up! :)
Have a look at:
http://www.concrete5.org/marketplace/addons/best-blog/...
It was formerly (and more accurately) called Dashboard Page Managers because it can do a lot more than just manage a blog.
http://www.concrete5.org/marketplace/addons/best-blog/...
It was formerly (and more accurately) called Dashboard Page Managers because it can do a lot more than just manage a blog.
I'm going to rename ProBlog to - "the super best awesomness blog package"
I think that is the way to sell an addon...you know, instead of actually having really useful features that are specific to blogging.
ChadStrat
I think that is the way to sell an addon...you know, instead of actually having really useful features that are specific to blogging.
ChadStrat
Anyway, specific to the users actual question, we have developed several custom object systems in C5.
The problem is, and always will be, a system designed to be a cover-all will never meet the deeper demanding needs of specific content publishing.
Specifically when you get to more corporate application needs that require a lot of data being moved through any sort of process.
Composer approach is fine for a handful of inputs, but severely lacking for higher end needs.
We have a custom object type "template" that we use as a starter package to shave off time of initial development. But we then get full single_page flexibility to provide our clients with what they really need, instead of giving them a "meh - that'll do" half-bake.
See my article here on why Composer is bad thinking for most application needs.
http://goradiantweb.com/blog/strategy/composer-tool-vs-usability/...
ChadStrat
The problem is, and always will be, a system designed to be a cover-all will never meet the deeper demanding needs of specific content publishing.
Specifically when you get to more corporate application needs that require a lot of data being moved through any sort of process.
Composer approach is fine for a handful of inputs, but severely lacking for higher end needs.
We have a custom object type "template" that we use as a starter package to shave off time of initial development. But we then get full single_page flexibility to provide our clients with what they really need, instead of giving them a "meh - that'll do" half-bake.
See my article here on why Composer is bad thinking for most application needs.
http://goradiantweb.com/blog/strategy/composer-tool-vs-usability/...
ChadStrat
But I agree with ChadStrat.
My really request is to know if it's better to use composer OR dashboard dedicated page ?
If dashboard dedicated page is better, this app must create a page for each blog post OR a single page must generate the blog post from an ID ?
Thanks
My really request is to know if it's better to use composer OR dashboard dedicated page ?
If dashboard dedicated page is better, this app must create a page for each blog post OR a single page must generate the blog post from an ID ?
Thanks
Gotta say I agree with Chad's point about composer. If I was managing a bunch of pages, then a composer like interface through a page manager would be fine (as long as it met my other requirements).
If I wanted the average site editor to manage a bunch of pages, I would be looking to provide something optimised for just that purpose with as few ways as possible left open for mistakes.
But then both Chad and I are experienced c5 developers, so have no problem developing such interfaces when needed.
So the real question you need to ponder is: Who is managing the pages and how dependable are they?
If I wanted the average site editor to manage a bunch of pages, I would be looking to provide something optimised for just that purpose with as few ways as possible left open for mistakes.
But then both Chad and I are experienced c5 developers, so have no problem developing such interfaces when needed.
So the real question you need to ponder is: Who is managing the pages and how dependable are they?
Thanks JohntheFish for this cool addon.
