Creating websites with the Drupal 7 "framework", enriching them with widely accepted modules and using more than 8 years of dedicated Drupal development experience to give you the best advice. This advice could also tell you that Drupal might not be fit for your type of project. Read more below!
I will employ widely accepted modules for fast and reliable site deployment. A quick stroll trough the module list:
- Views for slicing and dicing your sites data
- Panels or Display Suite for more dynamic pages
- Solar for a full text search engine, including searching in PDF, Word, Excel, ...
- Pathauto for creating SEO friendly URLs
- Commerce for creating feature full webshops
- I18N for internationalization and translation
- Feeds for converting "alien" content into your website
- Rules for creating a event driven journey for your users
- Menu block for better menu level manipulation
- Homebox for user configurable homepages
And of course a whole bunch of "under-the-hood" modules to lighten up the user experience of your sites visitors:
- Better Exposed Filters
- Automatic nodetitles
- Editable Fields
- Google Analytics
- And much much more ...
So, why / when would I advice you not to use Drupal?
While Drupal is a great framework for rapidly building and maintaining your website, it is also a complex and heavy system that can get bloated, fast and thus experience ugly slow-downs (among other horrors).
It is my personal experience, in building complex Drupal sites, that Drupal is perfect for small to medium sized websites, but to be absolutely avoided for large scale projects.
Many Drupal developers will try and bypass this (big) caveat by employing a variety of caching mechanisms such as reverse proxies (Varnish, Squid, ...) or by using many of Drupals built-in caching mechanisms, I
4 Reviews For This Service