The Next Silicon Valley Success Story

Business Situation

The original site was built in MT4. The business requirements were:

  • Convert the site into the latest JOOMLA version
  • Implement taxonomy to categorize the content on the site
  • Implement tagging system (based on geographical locations) to the content on the site
  • Set up the given templates in to JOOMLA
  • Integration of Twitter feeds as News Headlines


We were eager and curious to understand the REAL business need for moving away from MT4 to JOOMLA. The client's reasoning was that JOOMLA was a better choice for content management and its presentation capabilities were more suited to the new template design of the site.

After understanding the client's true business needs, alongside their project requirements, Alignity was able to make a case to use Drupal as the better technology option. We were able to make a convincing presentation on the differences between the CMSs. and how well Drupal could address the taxonomies and tagging system, along with many other benefits. Based on our analysis the client decided to go with Drupal . We developed a plat that would include knowledge transfer / training them through the implementation, since this was not a known prior solution to them.

Alignity Solution

In this particular case, Alignity was committed to making our client feel as comfortable and confident with the change in technology from their initial expectations. We ensured the project scope was clear and the proposed solution was properly understood by both parties. Our project proposal included:

  • The Project Scope (which covered all client inputs/specs)
  • The Proposed Business Solution (which included all the details of the interfaces and the business logic with it)
  • The Cost Estimate (with complete break down)
  • The Project Schedule (with milestones and delivery dates clearly defined)

We also provided the insight of different components that we had to work upon in Drupal, which were as follows:

  • cck - content construction kit, for admin interfaces.
  • Taxonomy - for tags and taxonomies
  • Views - to list as teasers or titles from multiple content pages
  • Blog - for Blogs
  • Blog API - for Blogs
  • Comment - for comments on Blogs/Articles
  • Path - URL rewriting
  • Menu - Navigation links
  • PHP filter - for customization with additional php code
  • Date/Time - required for article and blogs
  • Image - inside the content
  • Image Cache - for caching images
  • Fckeditor - for content
  • Meta tags - for keywords

Core modules

  • Block
  • Filter
  • Node
  • System
  • User

We provided weekly status reporting to our client, full transparency of the project at all times and also showcased the output on our test bed to re-assure our client of our progress and end results.

Impact and Result

We had no surprises or change requests from the client, as everything was clearly defined in the initial scope of the requirement. The client was updated regularly with the project status reports and corresponding deliverables on the test URL. The final results were as follows :

  • The UAT was successful with very minimal client inputs.
  • The client was very satisfied with the final result and the many options we made available in the admin interface.
  • We provided thorough training so the client could manage the site wholly on their own after deployment and made ourselves very available to answer all interim requests.

It was a thorough and successful project implementation, and in this particular case, it goes to show that it really does help to understand the client's needs well and suggest alternate options that may solve their business challenges more efficiently and seamlessly.

Alignity intends and strives to live the essence of the rich word 'Align'
in each aspect of its client serving endeavors