Skip to main content

Digging deeper into CMS requirements (#1: Technical Requirements)

I recently posted about the fabled CMS requirements, providing my own categorization without any further elaboration on what the different req's imply.

Today I'm gonna fill in the holes on the first category, Technical Requirements:

Technical requirements are the obligatory basic needs of the environment, hardware and software hosting and maintaining the WCMS.

The successful deployment of a WCMS depends on many information infrastructural circumstances and politics like management priority, user acceptance and technical feasibility. As will be declared in a later post, the main requirement of a WCMS is extensibility, and the one who has to make use of this requirement is indeed the developer responsible for deploying and running the WCMS in-house of the intended organization or corporation.

The hardware requirements and costs have not been a main issue in my experiences with maintaining CMS. I therefore disregarded the still very crucial requirements of scalability, availability and security. When professionally auditing WCMS solutions these requirements must be considered.

The WCMS may rise or fall by the outcome of these developer tasks.

Deployment

Developers are responsible for installing the WCMS, not only the first time, but they are also the ones performing redeployment when upgrades are necessary or patches are released from the vendor. If the process is cumbersome, this will happen with a low frequency and lead to a compromised and outdated WCMS. If it is not easy to migrate old content from the old installation to a newer one, the developer will quickly tire of the process and opt to management for choice of a different WCMS,

Integration

Infrastructural services such as e-mail, user directories and existing services should often be interconnected into the WCMS, and this will perhaps be the largest task the WCMS developer is responsible for, depending on requirements and existing information systems within the organization. Larger ECM solutions often benefit from utilizing strategies of service-oriented architecture (SOA), making it easier to integrate new functionality as web-services into the system.

Templates

Default templates and skins are bound for change after acquiring the system. Company logo and themes must be applied, and the CSS-styles applied by the WCMS may not be of the same patterns as the company's graphical profile.

This is not as much a feature as it is a necessity. A company is often judged by the outlook and consistency of its web-site. While the web designers no longer need to author the content of web-sites, they still need full control of the design. Templates allow designing once, and then applying the same design to whole parts of the site in one action.

Older web design tools have created an inclination towards not using mesh templates, where the template is separated into header, footer, left panel, main column, right column, and so on. More modern web design tools have support for working on such composite page design.

Backup

A WCMS is a complex system, and since this type of software is a fairly modern family of information systems, it is prone to experience bugs and crashes where data loss is a risk. Many technicians would argue that the responsibility of making information backup lies outside the WCMS, but there is still a requirement for the content repository to be backup-able in an automated fashion. A home grown file system or smaller database repository may lack support for such tasks.

Monitoring

Monitoring consists of automatically computing statistics and numbers on server usage and display them to the developer in a readable format. For a web-site this includes keeping track of incoming requests from visitors. If site traffic is not monitored it becomes harder to evaluate the returns of the WCMS, and it will quickly loose its favor from the management which weighs the cost of sustaining against these returns.

Logging

Logs are the server's output on relevant activities and processes. If logging is not done properly, it becomes hard to trace the source of errors and crashes.

Most web-servers have tools for monitoring the number of visitors. Traffic can be measured in number of “visits” or “hits”, although number of hits can give a very misleading understanding of how much traffic the web-site is experiencing. Number of visits and average visit length is the correct way to report traffic.



So there you have'em. My next post under this tag will explain the next category: The functionality that provides the management parts of the system, like content creation, publishing, workflow and administration. Stay tuned!

Comments

  1. Some other articles on CMS/ECM Planning:

    http://www.scanguru.com/download.php?view.7

    http://www.scanguru.com/download.php?view.6

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration