Synopsis
You want a website for yourself, perhaps a one page portfolio or a simple blog? Or perhaps take that a bit further and have content about you and what you do. But how? Learn HTML and CSS? Spend ages creating it, then a month down the line you want to add more content and then you need to remember what you did, then duplicate the supporting code to adjust the content. Then later on you want to change the layout, and what happens, you have thirty or more files to update! That’s when a content management system comes into play. One that can organise and transform your content into web presentable material.
Website content is shown to the user typically with a web browser, that content is a mixture of HTML and one or more of CSS and JavaScript. The content itself can be generated either dynamically or statically. With ‘dynamic’ the content is created in response to zero or more inputs from the client (for an overview of this, please see ‘ The first step – part one ’). This is great when you have lots of users and a complex system, but there is a downside, speed. This is because the server needs to generate the content (ignoring the possible benefits of caching) for each page it serves to the client. Such content management systems for generating dynamic content are WordPress (what eLearningWorld employs) and Moodle. But what if there is only you? That you need a simple website that you (or possibly if managed, a few others) update every now and then? That’s when you can generate the content locally and then put it on the server. The content does not change in response to the client (generally) but is the same to everybody that visits your site, thus ‘static’. All the server then needs to do is serve the content, there is no additional processing = speed. That’s what I decided I needed last year after I found out about a generator called ‘Hugo’ from Bas Brands . In this post, we’ll start to look at how you go about this.
Link
Post link on eLearningWorld: Static .