I’d like to get an idea of what the limitations of the CMS are expected to be.
I’m thinking of using it to be the driver of an online catalog for a large hobby shop if it can handle it. So we are talking of hundred and even thousands of items under many categories. I envision visitors picking a category from a picture gallery, or a pick list, and drilling down to what they want, which drives the page content. Page content would typically be the product SKU, a description, photos, price, reviews, physical data such as dimensions, size and weight of the packaging. Attributes such as color (colour if you’re from the 0 longitude). Options
What say….. is CMS going to handle this? 1000 products? 10000 products? 50000 products?
It sort of sounds like you are describing an eCommerce solution. I don’t think a CMS solution would be a great fit for the use case you are describing.
a blog is similar - title, text, picture…… thats the same data as a catalog. now expand the data the blog has in it a little…. and then make lots of them.
if the cms can’t handle a few blog posts, then what use is it?
The CMS will launch as a public beta, and while we’ve designed it to be fast and scalable, we haven’t yet battle-tested it with thousands (or tens of thousands) of files in real-world projects. So while thousands of items should be feasible (especially with some smart indexing and caching behind the scenes), I’d recommend being cautious with expectations in this first version.
The good news is that the CMS outputs static HTML, so the final published pages will be fast. Especially if you’re using a CDN to cache and serve your site.
We’re really keen to support more advanced catalogs like yours. That said, I want to reiterate that the CMS will be in beta at launch, and we’ll likely encounter and work through some limitations before we can confidently say use cases like yours are fully supported.
Just watched the dev diary 92 video. CMS Progress Report
From everything I have read and watched so far, I believe the CMS will be able to drive a “product catalog” website that I am envisioning.
One of the items that concerns me is that I can see how the cms can drive the data to a results page, but the cms will also have to drive all the meta data for the page; the page title, the page description, keywords, the canonical tag, the url, etc.
I’m trying to conceptualize how that would be performed…..
I’ve not really shown this feature off just yet, but this is doable already — you can enable a “Use Item for Metadata” flag on a single item, and that will allow you to add/set things like the page title, meta descriptions, meta keywords, and so on.
