Should You Standardize on a Single CMS?
There’s too little conversation about standardization regarding content management systems (CMS) - and too much business value lost in not considering it. We’ve written an eBook discussing the topic... but how do you know if standardizing is right for you?
The key to success with any web project – from app design to a new site build to adding interactive functionality – starts with intention. To create a more purposeful web, it’s important to challenge clients who know what they want but not what they need.
With any project – big or small, rescue or new – we start our process with a Discovery.
The Discovery process is simple – it’s an open, straightforward conversation that uncovers two important pieces of information:
No one wants to be the person who invested hundreds of thousands of their company’s dollars into a new website, application or digital asset and then have it fail to meet its expectations.
Even fewer people want to be the ones to then tell their management team the project needs even more investment – sometimes, as much as the initial expenditure – to fix the problems; or worse, start over.
Elasticsearch will take any data you throw at it, but without a predefined index, it will try to figure out the data type on its own, which can result in both inefficient storage and querying. It can also limit ways to use your data in some cases.
Let's consider http status codes for example. These values are always integers, however Elasticsearch will treat them like text unless you explicitly define your index.