Skip to main content

The Paradox between Functionality and Extensibility

(Stupid blogger/writeley. Blog publish still not working.)

Apoorv's post reminded me of the extensibility requirements of a WCMS. While his approach seems to be a more pragmatic find-requirements-and-select-best-solution, I prefer the generic but extensible solutions (probably because I'm a developer/programmer at heart). Apoorv also differentiates between customization and extension, but I find it hard to draw a clear line between these two. Here's some lines on extensibility from my thesis:

The final and most important requirement of the WCMS stems from a single principle. It is impossible to predefine all requirements for a WCMS. Each year new concepts, ideas and methods are introduced to the World Wide Web, and web-sites must change the way they deliver content, content managers must change the way they produce content, and developers must change the WCMS to allow the requisite changes.


We propose that extensibility is the most important requirement of WCMS, because they have no definite set of requirements. A WCMS is an abstract information system, and users will not properly realize potential functionality before the WCMS has been put to use. The requirements are indefinite, and more functionality will be demanded as time goes by, and this is why extensibility is such a crucial requirement.


[On our old proprietary CMS]

Whenever there is a new requirement and the customer is willing to pay, the functionality is sown into the existing code-base of the project.


I suggest that the improvements of functionality reduces the extensibility of the product. More code makes it harder to read and use existing code, and every decision made in the certain case of one customer makes the module unusable in the eyes of another customer. For example, the customer had a very specific requirement that each web-shop product be editable by its distributor or producer. To make this work in our CMS, the products were simply divided by distributor, and correct access privileges were granted to one distributor user for her products, respectively. For another customer, the distributor-product scheme could be completely useless, and the entire web-shop would have to be re-factored for such a purpose.


The question becomes whether the case be any different with an open source system. One point was that the we avoided changing the CMS source directly, as any changes made here would be overwritten (or have to be dealt with) on rolling out the next version of the CMS. As a result the extension was entirely made outside the core source in its own module.


The restriction of extensibility can be avoided by having a central architecture which is unnecessary to change. Such an architecture would have to be generic to adopt to possible use-cases (like the web-shop for instance), and we hope that has been achieved in the JCR. The content nodes are flexible enough to be changed into web-shop products, and the developers are confident that they would withstand other WCMS extending transformations as well.


...

Here's some example extensions from our customers (removed this from the thesis):

Web-shop

An organization selling membership-articles used their website for displaying product information on their merchandise. At one point, they decide it would be better if merchandise can be bought directly off the site and require a webshop functionality built into their WCMS.

Web service

The Norwegian Association of Allergic People daily update their website with the most recent pollen-forecast. They realize their members would like historic information and require the page to connect to a repository of pollen-numbers, where queries can produce graphs of pollen levels.

Integrating external services

A trading company see the need to feed various stock quotes on to their front page automatically. A service reading information from another site needs to be set up and connected to the WCMS.

Extranet

A news-company comes up with a new category of news which should be displayed for paying-customers only. Customers gain access to this privileged part of the WCMS by entering a personal user name and password on the site.

Integrating local services

A news company decides that its web page should also display information from a data sheet (which is being constantly updated) directly onto their site. The WCMS needs a data sheet reading service which flushes its content onto a web page at regular intervals.


These are just some example applications that can be implemented outside the WCMS, but sooner or later they need to interconnect in some way or the other, and the system will have to be modified to allow this connection.

Comments

Popular posts from this blog

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…

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…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…