Alfresco is a very flexible content-platform in general. It provides mechanisms to customize almost every component (Spring-Bean, Webscript, Templates) shipped with the core product.
Still, sometimes the technical solution does not prove to be even close to what the developer had in mind. This post is about a recent personal challenge and the journey to the solution in an Alfresco Share customization project targeting version 3.4.
The project consisted of various stories. One was about customization of the Share invitation email with the following requirements:
- As a Site-Manager, we want an optional personal message to be included in the invitation-email.
- As a Site-Manager, we want to receive invitee read-receipts for invitation-emails
- As a Site-Manager, we want the company logo to appear in the invitation email.
The customer was fairly pragmatic – requirements implemented quickly and decently priced being far more important than educational value of the code. Hence, it was ok to apply these customizations on a global level – to all share sites with no further scoping. That all sounded reasonably to me and I was confident to get it implemented “properly”.
The project was of type fixed-scope and fixed-price. A No-Go due to Heisenberg’s uncertainty principle – sure, but there was no way around.
Now, if you are an Alfresco developer reading this, please take a minute virtually outlining your solution and make a rough effort estimation before proceeding with solution journey on the next page. But even if you have no clue what Alfresco is, it might be worth reading further.