Web studios use their posts and service description pages to tell potential clients what programming languages, frameworks, libraries, databases, and, of course, CMS, they work with and what makes some technologies better as compared with others. We are not an exception: our superpower is our knowledge of Drupal, React, and Next.js. We’ve built it up for years based on our experience with hundreds of projects.
Though we present our business as a studio developing websites in Drupal CMS, we would like to tell you in this post when your site doesn’t need a CMS. “Is this possible? How will the texts, images, and all that be loaded to the site?” that’s what some of you may ask. Well, back in the old days, website developers used to do without CMS and they still can do without it — this depends on the site and the tasks it has to solve.
How the web got started
When the front end is more important than the back end
Time went by. The Internet grew more complex and moved away from being the realm of scientists and the military, as it used to be at some point, to approach billions of users. This trend of public openness growing at the turn of the century and the involvement of the public in Internet development gave rise to CMS and its popularization.
What is CMS? CMS stands for a content management system. For the administrators of today’s sites, the work with CMS is limited to content uploading, deleting, and editing functions which can be mastered within a few hours. This is just like using a calculator instead of recollecting the algebra.
Examples of CMS:
- Wix and many others.
Examples of websites built on CMS:
- Sony Music (WordPress);
- Alutech (Drupal);
- Marketika (Tilda);
- Vancouver Design Center (Joomla);
- Taunton Store (OpenCart);
- Dopple Press (Wix).
Everything on the web (or at least many things) is done for such people. So the site can’t exist without the visible part – you can call it the interface, frontend or whatever, as these notions are almost synonymous. Were it not for the frontend, the users would be sending server requests through a console or terminal to receive a raw JSON file, which is not the most easily readable format in the world.
On the other hand, a site can do rather well without the backend and, consequently, without CMS. The backend is a possible but not the only place from where the data can come to the client side. For example, the data can be represented by a JSON file stored on the server together with texts and links to images, video, and other content. The content can simply be hardcoded, i.e. embedded into the program code itself. The end users, whose comfort is our first priority, will see no difference at all while they are getting a good UI and UX.
Streamlined user experience must be a top priority for website owners. If an existing website doesn’t generate leads or the lead generation process shows poor results, then you might want to seek an answer in SEO and the front end of the website. For instance, ADCI Solutions specialists check the code style, do the UX audit and conduct various front-end improvement works. Overall, this set of operations produces good results in terms of website performance which further impacts user experience.
Does your site need the backend and CMS as the admin’s tool? It depends on the site's purpose.
A couple of frontend developers who know HTML, CSS, and JS will be enough to create a landing or an online business card. Such sites have no complex processes at the level of client-server interaction — they are just not necessary if the purpose of the site is to describe the company, brand, product, service, or event. Basic development languages will also be sufficient to create temporary technical pages — maintenance page and status page — informing the users and clients that maintenance is in progress which is why the site or some of its functions may be unavailable. The content of such sites is rarely, if ever updated, so the sites are called static.
Dynamic sites, on the contrary, are rich in various interactive options and frequently send requests to the server for new content, which can include personal content for each user. These are eCommerce sites, online services, online media, browser graphic editors, and other complex products — which cannot do without the server part.
Frontend developer’s tasks and the tools used to solve them
Both the frontend developer and the web developer must know HTML, CSS, and JS. However, a frontend developer needs the languages primarily to put things in order in the site interface, structure the content, and create various pretty things. A web developer, on the other hand, uses this and many other tools to create the site operation logic, set up the environment and for client-server interaction. Though such requirements are less often set forth for the frontend developer, here the line is blurred.
The knowledge and skills the frontend developers should have are listed below:
- text (Brackets, Sublime Text, Notepad++, Espresso, etc.) and visual (Adobe Dreamweaver CC, RapidWeaver, etc.) editors;
- graphic editors (Adobe Photoshop, Figma, Sketch);
- ability to read design layouts and keep the graphic content in order (images, icons, etc.);
- knowledge of the React library;
- ability to work in template engines (Pug, JSX);
- pre- and post-processors (PostCSS);
- package managers (npm, Yarn);
- task runners (Grunt, Gulp);
- loaders and module bundlers (Browserify, Webpack);
- software used to test markup (CrossBrowserTesting, Markup Validator, IETester, Validator.w3, Dr Watson, CSS Validator);
- markup validation, i.e. check for compliance with W3C standards.
There are high chances that a developer who knows HTML and CSS will be sufficient for building a website without CMS if you need:
- a landing page;
- an online business card;
- a personal blog;
- pages with documentation (example: Skype Support page);
- maintenance page (here is an article with examples in Atlassian’s blog);
- status page (here is another article with examples in Geekfare’s blog).
Lack of skilled specialists who could develop an online shop or CRM is not the reason for developing everything on HTML or CSS: look for a team with relevant projects in the portfolio or hire suitable specialists.