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!

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

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 operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

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?
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 times we get the latest library of master branch and name it with the commit-id in the fi…

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…