This is the second post, one day after the first, as promised.
Today is a Sunday, a lazy day, so today I will try to explain more of the origins of the eShop website and tomorrow I will upload source code and database backups and start explaining those part by part.
Few years back, at work, I was wondering which way to go. Clients requested more dynamical website, they needed an easy way how to change content without contacting developers. Mind you, these are enterprise applications, mainly for the government, these website are not going to be updated daily by the human operator, they will pull data from database and accept user input trough forms of some sort. This functionality is custom and coded by a developer, but what about the plain content like FAQ, contact info, news updates, new regulations and announcements that should be displayed to general public? Only solution for this "static" content was to use some kind of CMS solution to allow client to create and edit pages. Sure, there are many solutions out there. Company I work in is a Microsoft partner so all solutions that are not using Microsoft stack are out of the window. After this condition there are not many CMS solutions left, and those come with their own framework, a steep learning curve and a convoluted way of customization (not just design stuff, I mean real core customization like implementing Claim based authentication security model with multiple Identity Providers using Shibboleth and Forms Authentication). One of those CMS solutions I browsed trough was Composite C1. I fell in love with it right away as it wasn't anything else but a website project I can open in Visual Studio and start coding, just the way I am used to and just the way I like it (uh huh uh huh :D). It's a good starter CMS and I say starter because you can't get site done in one day (my friend is using WordPress and makes websites daily) mainly because there are still not many plugins for it. That is a bad thing and a good thing as CMS doesn't come installed with garbage right away, you can even choose if you want bare bones installation or some kind of simple template. Best part is that you get a website with source code exposed that you open up in Visual Studio, compile it, do whatever you like, compile it again and publish it (copy-paste operation) on an IIS server and it just works. After doing several projects in Composite C1 for the company I decided to make a website on my free time at home as my graduation project (I must shamefully admit I was postponing that for several years due to other obligations at work and at home). So that is how eShop website was born and raised. I learned few things along the way while using Composite C1 over the years and I will try to explain more tomorrow when you can take a first look at the project itself.
Thank you.
Today is a Sunday, a lazy day, so today I will try to explain more of the origins of the eShop website and tomorrow I will upload source code and database backups and start explaining those part by part.
Few years back, at work, I was wondering which way to go. Clients requested more dynamical website, they needed an easy way how to change content without contacting developers. Mind you, these are enterprise applications, mainly for the government, these website are not going to be updated daily by the human operator, they will pull data from database and accept user input trough forms of some sort. This functionality is custom and coded by a developer, but what about the plain content like FAQ, contact info, news updates, new regulations and announcements that should be displayed to general public? Only solution for this "static" content was to use some kind of CMS solution to allow client to create and edit pages. Sure, there are many solutions out there. Company I work in is a Microsoft partner so all solutions that are not using Microsoft stack are out of the window. After this condition there are not many CMS solutions left, and those come with their own framework, a steep learning curve and a convoluted way of customization (not just design stuff, I mean real core customization like implementing Claim based authentication security model with multiple Identity Providers using Shibboleth and Forms Authentication). One of those CMS solutions I browsed trough was Composite C1. I fell in love with it right away as it wasn't anything else but a website project I can open in Visual Studio and start coding, just the way I am used to and just the way I like it (uh huh uh huh :D). It's a good starter CMS and I say starter because you can't get site done in one day (my friend is using WordPress and makes websites daily) mainly because there are still not many plugins for it. That is a bad thing and a good thing as CMS doesn't come installed with garbage right away, you can even choose if you want bare bones installation or some kind of simple template. Best part is that you get a website with source code exposed that you open up in Visual Studio, compile it, do whatever you like, compile it again and publish it (copy-paste operation) on an IIS server and it just works. After doing several projects in Composite C1 for the company I decided to make a website on my free time at home as my graduation project (I must shamefully admit I was postponing that for several years due to other obligations at work and at home). So that is how eShop website was born and raised. I learned few things along the way while using Composite C1 over the years and I will try to explain more tomorrow when you can take a first look at the project itself.
Thank you.
No comments:
Post a Comment