Mobiliz Website-2

“The Service” includes the design of creative elements as well as the construction of navigation elements as templates (main page, menus, sitemap, etc.), the creation of marketing copy and texts and implementation of web pages in a hosted server either in HTML or in any CMS. Additional information submitted: “Vendor” will propose its services based on this document. Confidentiality and Ownership “Vendor” agrees that all the information shared by Mobiliz in this document as in any further verbal or written communications belongs to Mobiliz. Definitions “The Service” includes the design of standard creative elements as well as the construction of navigation elements as templates, the creation of marketing copy and texts and implementation of web pages in a hosted server. “The Website” It refers to the group of web pages and different elements constructed “Hosted platform” It refers to an external company that will be responsible for hosting the web server Objective of this RFP To let “Vendor” know about Mobiliz´ requirements to prepare and submit their proposals. T&C and Scope of work The project consists of 2 phases. The first phase consists of “The Website” design and elements standardization. The second phase consists in the web site actual implementation. Required Deliverables 1) “The Website” designed, constructed and On-Line 2) Source code: All source code, including objects, components, database queries, as well as all third party software and licenses that “The Wesite” needs to operate. Whether some images, objects or functions from third parties or from the “Vendor”´s library were integrated into “The Website”. 3) Standard elements: Standard elements designed including navigation elements and HTML template with standards required below for “The Website”. Requirements Technology • All software components to be used in the project must be “open source” or royalty free. If “Vendor” decides to use its own or other´s library, all used components must be licensed to Mobiliz at no extra cost. • Used Technology must consider that it could be easily ported to a mobile browser. • All Scripts must be commented, describing their purpose and usage. • Prefered technologies are: HMTL, Xhtml, Dhtml, Css, CVG, Xml, Php, Javascript, Ajax, DOM, Java, Flash. “Vendor” must specify in his proposal what technologies will be using. • “The Website” must be compatible with MS Explorer 6 and above, and latest versions of Firefox, Chrome and Safari. User Interface • “Vendor” must consider that ”The Website” is basically a marketing and informative tool, giving all different users their required information at anytime. “The Website” will be also the front-door to an intranet which is NOT considered part of the scope of this project.”. • “The Website” structure must be designed to be “Multi-language” and for the scope of this RFP it must be delivered in one of the following two languages: English or Spanish, Vendor will be provided with information about Mobiliz and its services to create its copy and own texts.. • Switching between the two languages must be an available user option, although default language when charging the homepage will be set based to the user´s browser language. • User interface must consider that it could be easily ported in the future to a mobile browser. • User interface standards definition created by “Vendor” must not only define the look-and-feel elements as color, font, background, window sizes, etc. of “The Website”, but also they must define the attributes of all other GUI elements such as : drop-down list, combo-box, check box, radio buttons, click-on buttons, pop-up windows, etc.. All scripts must be keyboard´operable scripts. • The website should render perfectly, in all defined browsers in this document, with no text overlapping and no extra scroll bars anywhere, etc Installation and Implementation Implementation, testing , launching and bug fixing will be performed by the awarded “Vendor” in a “Hosted platform”. “Vendor” will be responsible to install in the webserver all software components, pages and elements needed to implement “The Website”: “Vendor” will have fully access to manage the Web space on behalf of Mobiliz The site must be able to be accessed either from [login to view URL] or just by typing [login to view URL] (without the www). Backup: All developed components, webpages and elements as well as the infrastructure software needed to deploy “The Website” must be delivered to Mobiliz in a digital media storage device. Warranty “Vendor” will guarantee that the artwork and functions contained in the Web pages created will meet the requirements in this RFP and work properly for 90 days after the web site was officially delivered. Copyright to Web Pages, Artwork & software Copyright to the created graphics and assembled work of Web pages produced by “Vendor” will be owned by Mobiliz. Rights to photos, graphics, and programs which were not owned by “Vendor” must be fully licensed to Mobiliz at no additional cost. In case “Vendor” uses open source components, “Vendor” will notify Mobiliz of their use and will be responsible for making Mobiliz complying with their open source licens terms & conditions. Proposal By submitting a proposal “Vendor” is confirming acceptance of terms in this RFP and its Addendum Proposal must include a time-line and cost per each phase. Prices must show time and cost and presented as follows: 1) Phase 1: Standards and Design 2) Phase 2: Implementation Addendum Phase 1 : Standards and Design After hired “Vendor” will receive detailed information of Mobiliz business as well as a list of the options that must be present in the website. The options will be structured in a “tree directory” with a brief description explaining the purpose of each one. “Vendor” must consider attending a conference call (or a live meeting) with Mobiliz to solve doubts. Once “Vendor” feels has learned and identified clearly what kind of different target-users will be using the website, it will start creating alternatives of what could be “The Website” home page. 3 design alternatives significantly differents must be created by “Vendor” and presented to let Mobiliz analyze them and give its comments and suggestions back. After “Vendor” reviewed the selected design and have included Mobiliz´ suggestions and recommendations he will present the new version to Mobiliz. At this point Mobiliz will be able to give again suggestions and recommendations, and “Vendor” will return back to make updates to the design until the final desired look is accepted by Mobiliz. Once the final design is accepted by Mobiliz, “Vendor” will start the creation of functional website elements including the creation of images, icons, and all other standards that will be used all around the website. Once the design is approved, “Vendor” will gather all elements created in an HTML documents that will have all images, standards, and page templates to-be-used in the website. The standards to be defined by “Vendor” are at least:  Directory names in server´s disk: structure and file name standards considering that website will be translated lately to several languages. (English and Spanish structures is the scope to be created)  Naming Strategy for Images and files  Use of Header and Footer Links  Sitemap creation and updating  Use of the character encoded set  CSS for presentation aspects (fonts, colours, padding, borders etc)  Standards that makes sure that any aspects of the layout don’t break if font size is increased/reduced, by having relative rather than absolute units for text size in markup language attribute and style sheet property values.  Use of flash in the website  Navigation between from fields when filling a form.  Backgrounds for web pages as well as for the use of tables; column headers and cells content standards font and colours. Color links, underlined and visited links colors.  Icon design for services and options shortcuts  Fonts/colors for headings, hyperlinks, menus, dialog boxes, pop-up windows, new window, warning and error messages, validated fields warning messages, buttons, etc.  Java Script/ Ajax use  Design and standard way to use the waiting message when a page is loading  Use of Frames and iFrames  Display of lists, bullets, buttons, colors and indent  Doctype versions in every webpage  Design and implementation of the favicon . “Vendor” must consider in its proposal the use of its own stock images and pictures. In that case no additional fees will be charged and full license to use them in Mobiliz´s web site must be granted to Mobiliz. In case “Vendor” uses third party stock images, their cost must be included already in the proposal. “Vendor” must establish a temporary URL with restricted access so that Mobiliz may view the website development progress. Phase 2: Implementation Once phase 1 is concluded, standards and templates were created and approved by Mobiliz, so “Vendor” will proceed to start creating the actual “The Website” pages. “Vendor” will use all defined standard templates to create the website pages. “Vendor” can opt to use any of the following CMS to develop and implement the site: WordPress, Drupal, Joomla, or DotNetNuke This phase will be considered delivered when “The Website” is complete and on-line. After launched, “Vendor” agrees to make minor updates and changes to existing webpages, subject to the scope of work outlined below for up to 20 days Scope of work in pages and images creation “Vendor” must consider the following volume of work for his proposal:  Number of web pages: up to 15 in total  Basic Text Content will be supplied by Mobiliz (in English) in digital format: up to 2,000 words per page. Any number of conference calls are offered by Mobiliz to Vendor to go deeper in Mobiliz’s business model, solve doubts, share ideas, etc.  Copy and marketing phrases, as well as final body text organization is in charge of “Vendor”  Links to external pages:up to 20. Links to internal pages:up to 50  Embeded code linked to “youtube” or other video streaming sites: up to 4 videos.  Photos and other misc. graphic images (up to 20)  Images, banners and charts created (or provided) by “Vendor” to illustrate text descriptions in web pages : Up to 30  Icon´ shortcuts created(or provided) by vendor: up to 20 Web site construction basic requirements:  All links must be self-descriptive in the selected language  Nice, fresh, modern and clean design  All decorative images must be in the CSS and not in the (X)HTML´s docs  All images must contain a text equivalent in the "alt" attribute.  Fast responsiveness in drop-down menus (less than 0.5 sec)  User friendly window-help on “404 error page”, within all pages.  All website content must be accessible with the browser CSS feature switched-off or not, as well as with the images-option switched-off or not.  Any (x)HTML document must print well  Speed: Having a 512kb download bandwith speed in a 1.66Mhz Pentium with 2GB, loading time of any page of “The Website” must not take more than 3 secs.  Standard screen size will be 1,024x768  Clear visual option navigation hierarchy allowing the user to know in what page of the site he is currently on and where he can go next. SEO Considerations at website creation. When creating the webpages, “Vendor” must make sure that the entire website as well as each page is “fully compliant” to SEO best practices, such as: • Research and definition of most frequent expected searched phrases definition for each page. • Each page must have its own Title meaningful and enticing as a click able link in search engine results, each page must have a bold Heading and a good Description. Pages must have its header & footer links. • 10-15% Keyword density: Constructed by observing the best SEO practices, as Page tites and metatags matching keywords repeated in each web page body. Meta keywords and description listed in order of importance Meta keywords and descriptions to be included must be written in singular and plural, as well as with variations in spelling of core keywords • Placing all Images with links and Atl Tags with relevant descriptions • Avoiding the use of iFrames and Frames to display content. • Site map with all navigational links visible