From plain static to LAMP and back to static
A lot of years ago CERN engineers invent Word Wide Web technology as a linked set of plain text documents with links to each other and special formatting for visualization. Ancient Content Management was just an editing of static files on the disk. Times changed. We passed several huge revolutions in Web Development and Content Management. LAMP stack and its similar analogies based on other platforms were like standard for decades. We hold data and other content in relation database with SQL interface to access it. The pages have been treated as HTML content generated dynamically on server side by some engine implemented in a programming language with appropriate library or framework. All parts of this scheme have been re-designed or re-invented from time to time. Some of them even several times. There was a lot of hype about Web 2.0. For making development process more robust and performance of solution better, we started to use solution appropriate for specific task or project, e.g., MongoDB instead of MySQL, MVC instead of mess of code. One of such method is to present web site as a set of pure static web pages without any dynamic logic on server side, absolutely.
Generate static content offline
Main idea of such approach is to have a project with sources like data, html templates or includable parts and containers to wrap all those elements together and configure navigation between pages. On another hand, we need a tool or even several utilities to build the project into destination representation of static web site. First time, our team experienced such technology in the Fitness project for very famous Top 50 public Web Portal 10 years ago.
Nowadays, nobody code raw CSS3 in real-world HTML5 Applications Development. Huge amount of monotonic repeated code is too hard to create and support. Usually, one of CSS preprocessors are used to implement CSS3 styles in more elegant way. LESS [http://lesscss.org/] is one of such approaches. It doesn’t need to spend a lot of time to start using it. Try online tool [http://lesscss.org/less-preview] to process LESS into CSS code.
First of all, LESS is pre-processor of special syntax into CSS code. Besides, CSS code is a correct LESS code as well. You can start porting your existing pure CCS3 project into LESS just by a copy-paste action. When we mark some section or module with specified CSS class we are going to format and style not just wrapper but all its inside components as well. LESS helps us in this most used case by its nested syntax. E.g., LESS code:
Nowadays, search engines impose much more strong requirements for web sites to be ranked on top positions or even be parsed at all. Fast rise of mobile market pushed sites to be responsive to all kinds of screen widths and input schemas. But it’s not just about support mobile devices. For any Content Management system there is very important to load the pages as fast as possible. It’s not a recommendation anymore, but rather a rule. Google and other search engines may ignore your cool web site with a bunch of modern features just because it’s too slow.
Check loading speed online
First of all, check how fast is your page loading by Google’s PageSpeed test [https://developers.google.com/speed/pagespeed/insights/]. After several seconds you’ve got pretty complete report about issues at line of loading speed and suggestions how to improve it. If you receive green checks, congratulations, you are doing Content Management in right way. As it’s a Google’s service, so we can look at this list of points as optimization plan for Google Search Engine. On the other hand, the issues and methods to solve them are common for any search engine and for user experience as a whole. There are two separated modes (workflows) of analysis: for regular usage via PC’s browser and exploring on mobile devices like smartphones.
Let’s have a close look on CMS, what does it actually mean and how does it work?
CMS, also known as Content Management System, is designed mainly for business and is used in following fields:
- Development and design,
- Business cases,
- All kinds of smartphones including iPhone,
- Kindle and iPads,
- Authors and their editors,
- Social Networks etc.
The main task for CMS is to make content delivery and authoring as easy as possible. With its help even users who are not common with technique can create websites, publish or stream in the web as well as create any kind of content. WordPress, Drupal or Joomla customization is what’s usually needed from web developer for successful site creation.
Since the year 2013 has just begun, it’s the right time to take a glimpse into the future and analyze what is coming.
Any clouds in ERP?
We wait for the product lines of Microsoft’s Dynamics ERP to get more options in the field of the cloud deployment. The same situation is forecasted for the users of Epicor and Infor production. On the other hand the well-known Kenandy or Plex are already specializing on cloud-based ERP.
Still the more advantageous situation is seen within Oracle and SAP territory, where they use their own modules of clouds for a while already.
Some more words about ERP: according to the last news it reformed the current image from CRM software vendors we’re all familiar with into the player based on the full-blown platform. As a result they also had to move their applications to new categories. Still the time of the aggressive push is yet to come; meanwhile the company goes hand to hand with Infor and Workday in the field of enterprise content management.