#todaysdoodle is inspired by my job 🙂 I work for a media and entertainment provider, focused on supporting their websites which are spread among different countries. The main platform used is WordPress but hundreds of plugins have been built on it for enhanced functionality.
My role is in the back-end part of that CMS.
Let’s start from the basics.
What is a CMS?
According to Wikipedia (whom we trust!) CMS stands for Content Management System.
Quote —>”A content management system is a computer application that allows publishing, editing and modifying content, organizing, deleting as well as maintenance from a central interface.Such systems of content management provide procedures to manage workflow in a collaborative environment. CMSs are often used to run websites containing blogs, news, and shopping. Many corporate and marketing websites use CMSs. CMSs typically aim to avoid the need for hand coding, but may support it for specific elements or entire pages.”<—-End Quote
Essentially a CMS looks like an online mag or a blog like this. And I work on the back-end of that.
Now if you ever studied computers, you will find this terribly confusing. Back-end normally refers to databases, servers and systems that lie AT THE BACK END of an application. Normal right?
However, with CMS, back-end is the space that allows admins and owners to edit their content – if you maintain a blog, back-end refers to the screens you see when you write your post, watch your stats, edit your layout. Therefore not something that the actual user will see.
Of course, every CMS has an even “more” back-end: a database to store and organize materials.
The actual user will see what is called ‘the front-end‘ – no confusions there. Front-end is almost all cases what the end user will see (the real content with CSS and nice fonts and designs!)
So now we have cleared the air, let’s focus on what my role involves.
It involves setting up all those extra features, plugins, widgets that owners will use when they are adding content and building pages (left-hand side menus and so on!). It does not need to be super cool and fancy as it is not going to be viewed by external users; however it does need to be functional, simple, clear and stick to the purpose.
My team is split in different countries so we use a lot of collaboration tools and we have also <tried to> adopt SCRUM practices so you will notice my diary uses some weird terms there!
This is it – a quick walkthough that you don’t really need 🙂