Website Content Management System implementation

Our CMS service

Many clients will want a brand new implementation they can fully own and manage. They simply want for a provider to set them up with a new website, with instructions, some possible adhoc implementation, and let the client take over.

We can choose from a number of .Net and .Net Core preferred opensource Website Content Management systems.

Please reread this page and follow the links to the external platforms to get more of a feel. Remember, we can undertake our advisory service to help assess which solution may work best for you, even if another provider does the final implementation.

.Net and. Net Core MVC CMS implementation

We will detail 5 platforms we are comfortable with setting up for clients from scratch. Our goal is to take a version from a base CMS provider installation and deploy it to an IIS server. We will set up the server-side configuration. We will document the installation in markdown format for ease of understanding. All code developed is owned by the client subject to any open source licensing restrictions by the provider we use. Any configuration will be documented. We will work with our clients to achieve design requirements, but may outsource more advanced requirements. Any clientside coding may or may not be outsourced, but we will architect the implementation with a goal of pluggability. We see our Bespoke CMS offering as an excellent way for clients to have far more control in how their implementation is undertaken.

Comparing our Bespoke CMS implementation with Info Rhino's other offerings

We provide a full breakdown and comparison here. To summarise though;

• Our Bespoke CMS will almost certainly be more expensive than our Website starter Implementation.
• Our Bespoke CMS should be less expensive than our Website Data Platform Implementation.
• We will treat each bespoke requirement as new. We may reuse code and configuration approaches, but will never use our libraries from our Starter Website or WDP services.
• We will set up a repository where code can be privately backed up.
• We will try to set up shared access for documentation and other data artefacts.
• We will explore creating custom CMS page layouts if the CMS permits it.
• We may ring-fence certain implementations. This means each client, we may agree that certain functionality maybe outside our area of expertise.
• We may recommend certain approaches if you require membership access.
• We may recommend a separate or in site API, if you require this.
• We will work with your to ensure your emails, hosting, domains, and any security certificates are owned by you.
  

Remembering our ethos with developing bespoke software for clients

It is worth recalling that whilst we can do domain specific functionality across a host of technologies, we focus on reusable generic products with our own solutions. We seek to make it flexible and some work may prove to difficult to estimate delivery on. Always give us your ideas and we will always seek to help you. We work with many providers who thrive on this type of work that complements our skills.

The .Net and. Net Core MVC CMS technology stacks

.Net Core and the older dotnet MVC are Microsoft technologies which are truly groundbreaking. They are our area of expertise and we see them as offering superior capabilities to other languages, yet offer fewer off-the-shelf capabilities to other providers. This is a trade-off any client must appreciate. There are some exceptional new advances .Net Core is offering - we even see there is a project attempting to do WordPress in dotnet core. We have seen projects which let's node js sit inside a dotnet core MVC installation.
.Net Core offers non Windows installation which enhances the number of operating systems it runs on. Whilst we don't develop on non-windows OS, we can stick to simpler dependency injection and configuration to mitigate OS dependency.