Existing WCMS-es

This is a from an internal discussion at work..

Jahia seems nice on the demo, but they are quite outdated on the open source part (using old stuff like struts and ant, no JSR-170). Same thing goes for the very popular Liferay.

Swedish SiteVision is also good, but Objectware have alread got the under their hood. Magnolia as well, but the (like us) are based on persisting the content with Jackrabbit, and at this point there is no DBMS support there (though this is right around the corner). Magnolia's developers, the commercial company Obinary, are offering their customers an other JSR-170 compliant repository: CRX from Day. I suspect that the CRX is heavily based on Jackrabbit, since the Day developers are the core of the Jackrabbit crew.

Here's an incomplete overview:

Company      Open Source produt         Commercial product
-------------------------------------------------------------
Obinary      Magnolia                   Compass
Day          Jackrabbit                 CRX
Senselogic   --                         SiteVision
eXo          eXo Platform               --
Liferay      Liferay                    --
Alkacon      OpenCMS                    --
Us           --                         P

All the companies above also gather some revenue in consulting and hosting services.

So where should we position ourselves? We could keep developing our own CMS and
use Jackrabbit at persistence level, but that would leave us in competition with
Obinary (which is not where we want to be).

Perhaps we should build on Magnolia instead of making something on our own.
It would save us quite an amount of development with the cost of giving us
a lesser understanding and custom-tailoring of the CMS. But we feel we will
make up for the lack of functionality by spending the time saved on making
Magnolia extensions and modules.

This could lash right back our face. Magnolia can turn out to be too complicated
for someone outside Obinary to understand (like our previous CMS stroke us) and
too hard to modify for our customers' needs.

We also have to consider the transaction of articles and data from the old
database onto the JCR. We might even (like Magnolia) have to invest in an more
solid JCR implementation like CRX to ensure scalability, if Jackrabbit proves
incomplete to the task, that is.

Day has a nice faq about CRX and JCR:

http://www.day.com/content/en/product/jsr_170/content_repository/crx_faq.html

CMS-wizeguy Öbergs ramblings:
http://www.theserverside.com/news/thread.tss?thread_id=32890#164178

The more I think about it, and study our competitors, the more convinced I
become that we should build on what others have built. I'm worried that if
we keep developing a CMS on our own, it will take too much resources, and
no matter what always reside some paces behind Magnolia.

We've spent some time increasing our knowledge of Jackrabbit, JSF, Tomcat
and other useful technologies. Perhaps this knowledge is better put to work
if we join up with the present kings of content (kongene på haugen).

Comments

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