*
Info: server farm runs on Red Hat, available backend DB is postgresql, will provide access to linux box with drupal installation and login information.
**Should maybe check with Curt to see what the final policy ends up being on this. Per last weeks's discussion, Journyx is standardized on PostgreSQL, but it should be understood that the Drupal community develops primarily for MySQL. PostgreSQL is often an afterthought, and sometimes ignored altogether. It's not a show stopper, but it will be a pain to migrate later if you realize you'd be better off on MySQL.**
*
Must have approval workflow for content using the modules specified below (Revisioning, Rules. etc). Approx 5+ people who can create/modify content. Want to delegate authority for different people with content creation/modification permissions.
*
Website should drive form fill out, must maintain code for web to lead form that integrates with CRM tool (don't change).
*
Consistent navigation framework that is the same on all pages
*
Suggest changes to the navigation and content to improve usability, look&feel
*
Must adhere to theming best practices, as outlined here: [login to view URL]
*
Should include at least 7 block regions:
o
Left Sidebar
o
Right Sidebar Gold
o
Right Sidebar Blue
o
Content Top
o
Content Bottom
o
Header
o
Footer
*
Build time for rigorous Q/A cycle into bid and schedule
*
Must be compatible and tested with the following modules:
o
Administration menu (problematic on [login to view URL])
o
Backup and Migrate (if on MySQL)
o
CCK
o
Custom Error
o
Diff
o
FCKeditor
o
Google Analytics
o
JS Injector
o
Module Grants
o
Nodeworks
o
Notify
o
Password Policy
o
Revisioning
o
Rules
o
Smart Tabs (problematic on [login to view URL])
o
Token
o
Trigger Unlock
o
Views