You have chosen to sponsor your bid up to a maximum amount of .
We are looking for a freelancer or company to work with us to develop drupal website within a 2 / 3 week period. You will be supplied with PSD final designs and the site must be identical to the designs. All sites must be developed responsively and best practises used
The successful company or applicant will be given 25% up front deposit & will be required to build the site on our development server during development we will pay close attention & any best practise or poor coding you will be immediately asked to stop work.
Deadlines will be set & each day that the deadline is missed the agreed budget will be deducted $10
If at any point you do not provide us with the quality of work we desire or cause any issues for us, we will terminate work with immediate effect.
We will ask that all sites are built around these specifications
The initial build of any website should be made using a vanilla Drupal distribution. Websites should be built to support multi-site and allow low-effort upgrades, to this end the core Drupal distribution files must not be modified.
Any modules or themes must be placed in the /sites/all/ subdirectory, allowing these to be abstracted elsewhere at a later date.
We ask where possible, that any work is managed under a version control system. We recommend Git for this – of course, if you already have an infrastructure that uses another system we have no issue with you using it instead.
Where possible, we ask that community supported modules be used opposed to custom built ones. We do however understand that there will be the odd case in which you must custom build modules.
We expect that any modules that are built for a project are built to be re-usable & documented as such.
It is expected that most content in any website will be part of an architected hierarchy. To this end, all sections and menus within a website must support this without additional configuration.
We understand that the functionality required here will depend entirely on the information architecture that a website is constructed from. To this end, we trust that you will find a suitable module to handle this (from the public module library) on a site by site basis.
A very typical hierarchy may be similar to the following:
• Section 1
o Category 1
o Category 2
o Category 3
• Section 2
o Category x
• Contact Us
Theming and Site Building
In the past we have found it useful to use a base template (which is not edited) with the ability to generate sub-templates. We ask that this method is used when you are building this theme yourselves.
The theme that we tend to use (coupled with the Drush management tool) is AdaptiveTheme. http://drupal.org/project/adaptivetheme
In most cases, a base installation of AdaptiveTheme, used to generate a site specific theme should work best. Unless explicitly asked for, responsive
features of this theme should be disabled.
Website layouts should be built using the Drupal Block system, & then subsequently styled using CSS. We understand that this may be initially limiting, this limit is alleviated by using the Block Theme module alongside your build: http://drupal.org/project/blocktheme
Once again, any additional themes built using the Block Theme module should be re-usable, making using of its variable feature where possible.
Any website should be built to support 4 main users:
• Website Visitor/ Anonymous User
• Content Writer (can write, but not publish)
• Content Editor/ Publisher (can write and publish)
• Super Administrator
It should be possible to ensure that each of these user types have adequate access to features within the system using the Drupal Access Control functionality. This functionality is bundled within the vanilla Drupal installation and so should not require any additional work past configuration.