From c3e35b8343c7c56b83f7dfc34a14abc82b9e5f47 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Wed, 3 Sep 2025 14:54:29 -0400 Subject: [PATCH 1/4] Create Drupal-Certified.md --- .../draft/Drupal-Certified.md | 568 ++++++++++++++++++ 1 file changed, 568 insertions(+) create mode 100644 open-requirements-library/draft/Drupal-Certified.md diff --git a/open-requirements-library/draft/Drupal-Certified.md b/open-requirements-library/draft/Drupal-Certified.md new file mode 100644 index 0000000..967f568 --- /dev/null +++ b/open-requirements-library/draft/Drupal-Certified.md @@ -0,0 +1,568 @@ +# Supplemental Resource Guide + +* [Open Source CMS RFP & Procurement Guide](#bookmark=id.qcuzhmojty2) +* [RFP Vendor Instructions: A step-by-step guide on how to best approach vendors](#terms-of-reference-\(annex-a\)) + +# Open source CMS RFP and procurement guide + +## *How to prepare your RFP to find qualified and experienced open source vendors in the marketplace.* + +The Drupal Association is the non-profit organization behind the open source Drupal CMS. The Association’s mission is to accelerate Drupal, foster the growth of the Drupal community, and support the project’s vision to create a safe, secure, and open web for everyone. + +[https://www.drupal.org/association](https://www.drupal.org/association) + +## License + +This document is licensed under the Creative Commons Zero license. No rights are reserved. Edit and distribute this document to your own needs. + + [https://creativecommons.org/publicdomain/zero/1.0/](https://creativecommons.org/publicdomain/zero/1.0/) + +## Why an open source RFP guide? + +**We have created this set of templates to help organizations looking for vendors**—contractors or agencies—to develop and implement website and digital experience projects using open source content management systems (CMSs). + +Shaping the future of digital experiences in an open web relies on all of us putting open source values into practice. Among those values, transparency and sharing what we improve with our communities are the motivations for publishing this RFP and procurement guide. + +In it, you will find a solid foundation for planning your technical project RFP and room to customize it to your needs. It also contains sensible and reasonable conditions for potential vendors to meet regarding open source expertise and experience. We cannot make any guarantees, but if a vendor meets the conditions, it is a good sign that they will be a good technical partner for your project. By contributing to their core open source technologies—like their CMS—they will have gained valuable expertise, and there’s a good chance they could be a good implementation partner for your project. + +**If you are preparing a Request for Proposals, this material will help you:** + +* Find service providers qualified and experienced in open source content management systems (CMSs) and related systems and methodologies. + +* Objectively sort between competing vendors. + +* Ensure you’re not forgetting any significant factors or information… at least based on our experience :-) + +## How to prepare your RFP vendor instructions and terms of reference + +* **Find and replace:** Information you need to fill in or customize for your organization and project is in square brackets and marked with two asterisks in the document. Search for \*\* and fill in the appropriate necessary information. + + * You are the “ORGANIZATION” requesting proposals from vendors to provide you with digital project and website-building services. + + * You need to fill in the project name, dates, timelines, and other specifics of your project. + +* **RFP?** Depending on your location and the nature of your organization and project, Requests for Proposals (RFP) may be called different things, such as Request for Information (RFI), tender, or bid. Search for “RFP” in this document and “Request for Proposal” and replace as appropriate. + +* **“We”** in the instructions refers to the organization looking for help with a project—you, the reader\! + +* **“You”** in the instructions refers to vendors who want to bid to be your vendor. + +* **Logo:** Replace the “your logo here” images with your logo. + +# Instructions for Vendor Proposal Preparation and Submission + +**\[\*\*ORGANIZATION NAME\]** + +**\[\*\*City, Country\]** + +**Date: \[\*\*\]** + +**Reference: \[\*\*RFP Reference Number / Project Name\]** + +## Introduction + +This Request for Proposal (RFP) is for the selection of an experienced Drupal service provider to support \[\*\*Project Name\], which aims to \[\*\*brief project goal or outcome\]. + +We prioritize experienced vendors with a demonstrable understanding of open source software, particularly those with a history of significant contributions to the Drupal community. + +The project requires strict adherence to timelines, a focus on quality, and a commitment to technical excellence. + +Your proposal should address the full scope of services detailed in the "Terms of Reference," including: + +* Project planning, design, and requirements gathering + +* Development using Drupal 10 or later, adhering to Drupal coding standards + +* Integration, testing, deployment, and post-launch support + +* Documentation and training + +## + +## Instructions + +1. ### General + + 1. \[\*\*ORGANIZATION NAME\] is seeking a vendor to provide capabilities for this project to carry out all tasks required for its completion and success expeditiously and at a reasonable cost. + 2. This Request for Proposal (RFP) is for providing services as described in the attached documentation. + 3. You, “the Vendor,” may bid for the project by submitting a proposal that meets all the requirements stated in this document and the attached Terms of Reference. + +2. ### Documents included in this Request for Proposals (RFP) + + 1. This RFP consists of the following documents: + + 2. Letter of invitation (email) + + 3. Instructions for Vendor Proposal Preparation and Submission (this document) + + 4. Terms of Reference + +3. ### Schedule + + 1. **Proposals must be submitted electronically in PDF format to the addressee listed in section 5 by \[\*\*Closing Date\] at \[\*\*Time, Timezone\].** + + 2. Below is the schedule of pre-project milestones for this RFP. + +| RFP: Milestone | Date | +| :---- | :---- | +| RFP issued | \[\*\*Date\] | +| Pre-proposal conference | \[\*\*Date\] \+ 5 days | +| Deadline for submitting requests for clarifications/questions | \[\*\*Date\] \+ 10 days | +| Answers to requests for clarifications/questions | \[\*\*Date\] \+ 15 days | +| Proposal submission closing date | \[\*\*Date\] \+ 20 days | +| Notification to short-listed vendors | \[\*\*Date\] \+ 25 days | +| Interviews with short-listed vendors | \[\*\*Date\] \+ 30 days | +| Award of contract | \[\*\*Date\] \+ 35 days | + +4. ### Proposal Language + + 1. The proposal and all correspondence and documents must be in English. + +5. ### Proposal Submission + + 1. **Format:** Submit proposals in PDF format, with a maximum file size of \[\*\*X MB\]. + + 2. **Validity:** The proposal must clearly state that it is valid for a \[\*\*60-day\] period from the closing date indicated in Section 3, Schedule. + + 3. **Deadline:** Submissions must be received by \[\*\*Date, Time, Time Zone\]. Late submissions will not be considered. + + 4. **Submission Method:** Email your proposal to \[\*\*Email Address\] with the subject line '\[\*\*Project Name\] RFP Submission.' + +6. ### Requests for Clarifications + + 1. \[\*\*ORGANIZATION NAME\] will issue clarifications if required. + + 2. **For questions related to the RFP,** contact \[Contact Name\] at \[Email Address\] no later than \[\*\*Date, as listed in Section 3, Schedule\]. + + We will not respond to queries submitted after the deadline for submitting requests for clarifications/questions indicated in Section 3\. + + 3. **We will share our responses to inquiries and will be shared with all prospective vendors.** + + 4. Please refrain from contacting us about this proposal through other means or channels. + +7. ### Proposal Format Requirements + + 1. **Proposals must include three sections,** clearly labeled “Technical Proposal,” “Financial Proposal,” and “Experience and Qualifications.” + + **Your proposal must document how you meet the minimum requirements for all three sections.** + + 2. #### Technical Proposal + + 1. Write a detailed explanation of how you plan to address the project requirements outlined in the Terms of Reference, including your methodology, tools, and processes. + + 2. **Vendor background** (company or consortium), ownership, size, location, profile, certifications, number of employees and freelancers. + + 3. **Experience:** Examples of past projects similar in scope to the requirements detailed in the Terms of Reference, especially with Drupal 10 or 11\. + + 4. **Provide reference projects,** showing a proven track record in delivering projects of similar size and complexity. Include URL addresses and contact details for a reference person. Ideally, include customer recommendation letters. + + 5. **Describe in detail how the required tasks/services/deliverables will be accomplished,** including but not limited to your methodology, tools, processes, and ancillary services, such as training, maintenance, or launch. + + 6. **Operational details:** Describe your methodologies, tools, and approaches for project management, software development and management, change control procedures, and communication methods. + + 7. **Demonstrate that you understand the project** objectives, scope of work, and deliverables. + + 8. **Detail the key assumptions** underlying the Technical Proposal. + + 9. **Describe the expected inputs/resources** that we must provide you for project success. + + 10. **Team CVs** for the project manager(s), designer(s), developer(s), and other team roles and members expected to be working on the project. **List their relevant qualifications, certifications, experience, and expertise.** + + 11. **Project plan and timeline:** Outline how you will meet the project's timeline, specify key milestones as outlined in the Terms of Reference, + + 1. show how you will ensure uninterrupted service throughout the project, + + 2. and specify which team members will be involved at each project stage. + + 3. #### Minimum Eligibility Requirements: Experience and Qualifications + + 1. To be eligible for consideration, vendors must have the following experience: + + 2. **UX:** You must have completed User Experience (UX) exercises for at least one website or digital product, including conducting user research and creating user journeys, site maps, and wireframes. + + 3. **Drupal development experience:** Minimum \[\*\*X\] years + + 4. **Drupal 10/11 experience:** Developed and implemented the theme/frontend and backend of at least three multilingual and/or multisite websites based on Drupal 10 or 11\. + + 5. **Open source expertise and technical excellence:** + + 1. **Drupal Certified Partner** of the Drupal Association in good standing. + + 2. **Demonstrated record of regular contributions** to Drupal core or contributed modules in the past 12 months. A longer history of active contribution to the Drupal community, including code (e.g., core, modules, patches) and non-code contributions (e.g., organizing community events, providing documentation), is, of course, welcome :-) + + 3. **20% of Drupal engineers (minimum) have Acquia Certified Drupal Developer or similar certification.** + + 6. **Ecosystem experience:** Recent experience maintaining websites hosted on a Drupal focused hosting solution. + + 4. #### Financial Proposal + + 1. **Fixed quote** to implement the online platform and CMS based on the requirements documented in this RFP. + + 2. **Provide a comprehensive breakdown of costs, including any optional services or extras, including, but not limited to,** professional services, support services, integration, training, content migration, and customization. + + 1. **Travel or other costs** should be identified separately. + + 2. **Annual maintenance costs** should be identified as separate charges. + + 3. **Hosting costs** should be identified as separate charges. + + 3. **Fees must be quoted in \[\*\*US Dollars\]** and as a total figure, including all expenses. + + 4. **Expected professional fees, expenses, and disbursements** must be indicated. + +8. ### Modification and Withdrawal of the Proposal + + 1. You may modify or withdraw your proposal after it is submitted and before the closing date for proposal submission, provided that we receive written notice of the modification or withdrawal. + + 2. You may not modify the proposal after the closing date without our consent. + +9. ### Proposal Evaluation + + **We will award the contract** to the vendor whose proposal most effectively satisfies the technical, operational, and experiential requirements here and in the Terms of Reference. The ratio between the proposal's technical/operational and financial merit will be \[\*\*75:25.\] + + **Proposals will be evaluated based on the following criteria:** + +1. **Technical competence and experience (75%):** Evaluation of the vendor's ability to meet the technical requirements and experience with Drupal 10, including open source contributions and successful delivery of similar projects. We will conduct an initial technical evaluation based on the following criteria: + + 1. Vendor experience, resources, and project management + + 2. Fulfillment of the Terms of Reference requirements + + 3. Skills and experience of key vendor team members + + 4. If your proposal fails to meet the minimum technical requirements for any one criterion, we will not consider your proposal further. + +2. **Financial Proposal (25%):** Assessment of cost-effectiveness, budget clarity, and overall value for money. We will only assess the financials of vendors who meet or exceed the technical and experience requirements. + +10. ### Final Provisions + + 1. **We reserve the right to request clarifications** on the proposal and to enter into negotiations regarding technical or commercial aspects of the proposal before awarding the contract under this RFP. + + 2. **We reserve the right to accept or reject any proposal or annul this procurement process** at any time before the award of a contract without obligation of notification grounds and, therefore, without thereby incurring any liability to invitees. + + 3. **Invitees must bear all costs associated with preparing and submitting their proposals,** and we will not be responsible or liable for those costs, regardless of the outcome of this RFP. + + 4. **All documentation and information in this RFP are proprietary to \[\*\*ORGANIZATION NAME\].** + + **You may not duplicate, use, or disclose them—in whole or in part—for any purpose other than to evaluate them and respond to \[\*\*ORGANIZATION NAME\] ’s request for proposal or otherwise without prior written agreement of \[\*\*ORGANIZATION NAME\].** + +# + +# ![your-logo-here-aalesund][image1] + +# TERMS OF REFERENCE (ANNEX A) {#terms-of-reference-(annex-a)} + +**\[\*\*ORGANIZATION NAME\]** + +**\[\*\*City, Country\]** + +**Date: \[\*\*\]** + +**Reference: \[\*\*RFP Reference Number / Project Name\]** + +**Table of Contents** + +**[1\. Introduction to \[\*\*ORGANIZATION NAME\] and Background 2](#1.-introduction-to-[**organization-name]-and-background)** + +[**2\. Mission Statement and Objectives 3**](#2.-mission-statement-and-objectives) + +[2.1 Business Objectives 3](#2.1-business-objectives) + +[2.1 Critical Requirements 3](#2.1-critical-requirements) + +[**3 Scope of Work 3**](#3-scope-of-work) + +[3.1 Specific Services 3](#3.1-specific-services) + +[3.2 Requirements 4](#3.2-requirements) + +[3.2.1 Overview 4](#3.2.1-overview) + +[3.2.2 Website “Online Platform” Design Requirements 4](#3.2.2-website-“online-platform”-design-requirements) + +[3.2.3 Online Platform Functional Requirements 5](#3.2.3-online-platform-functional-requirements) + +[3.2.4 Online Platform Non-Functional Requirements 5](#3.2.4-online-platform-non-functional-requirements) + +[3.2.5 CMS Requirements 6](#3.2.5-cms-requirements) + +[3.2.6 Hosting Requirements 8](#3.2.6-hosting-requirements) + +[3.2.7 Maintenance and Support Requirements 9](#3.2.7-maintenance-and-support-requirements) + +[3.2.8 Training and Documentation Requirements 9](#3.2.8-training-and-documentation-requirements) + +[3.3 Deliverables and Timeline 10](#3.3-deliverables-and-timeline) + +[3.4 Logistics and Acceptance 10](#3.4-logistics-and-acceptance) + +[**4\. Project Management and Methodology 11**](#4.-project-management-and-methodology) + +[4.1 Project Management 11](#4.1-project-management) + +[4.2 Reporting 11](#4.2-reporting) + +[4.3 Methodology 11](#4.3-methodology) + +[4.4 Acceptance 11](#4.4-acceptance) + +[**5\. Requirements for vendor and personnel 12**](#5.-requirements-for-vendor-and-personnel) + +[5.1 Vendor requirements 12](#5.1-vendor-requirements) + +[5.2 Vendor personnel requirements 12](#5.2-vendor-personnel-requirements) + +# 1\. Introduction to \[\*\*ORGANIZATION NAME\] and Background {#1.-introduction-to-[**organization-name]-and-background} + +\[\*\*Give an overview of your organization and market to give potential vendors the information they need to assess your project in the context of industry and goals.\] + +# 2\. Mission Statement and Objectives {#2.-mission-statement-and-objectives} + +## 2.1 Business Objectives {#2.1-business-objectives} + +\[\*\*ORGANIZATION NAME\] seeks innovative and capable web solutions providers for its web CMS requirements. The solution will help the organization achieve the following business goals: + +* Goal 1 + +* Goal 2 + +* Goal 3 + +* Goal 4 + +Examples: automating 80% of site operations to reduce site maintenance costs; removing an IT bottleneck to empower marketers to control digital marketing initiatives; managing social content to drive traffic; increasing customer community engagement by 25%; integrating CRM with Web CMS to personalize content delivery; ease of multichannel delivery, etc. + +## 2.1 Critical Requirements {#2.1-critical-requirements} + +\[\*\*ORGANIZATION NAME\] requires that the web CMS software has the following: + +* \[\*\*Must Have 1\] + +* \[\*\*Must Have 2\] + +* \[\*\*Must Have 3\] + +# 3 Scope of Work {#3-scope-of-work} + +## 3.1 Specific Services {#3.1-specific-services} + +To meet the objectives specified in section 2 above, the vendor is expected to perform at least the following specific services: + +1. Visual Design and UX/UI + +2. Website and CMS Development + +3. Project Execution, Project Management, Quality Management + +4. Training and Documentation + +5. Content Migration + +6. Hosting + +7. Support, Maintenance, and Ongoing Management + +## 3.2 Requirements {#3.2-requirements} + +### 3.2.1 Overview {#3.2.1-overview} + +The following sections act as detailed reference of the requirements of this online platform. + +Please answer how you meet the following capabilities. The proof-of-concept, vendor product demonstration, and client trial evaluation will also form a part of the selection for the Web CMS. If a feature is in development, please state the expected date it will be available. + +For Vendor response, please fill out: + +1. Out-of-the-box (Standard Feature) + +2. Custom Implementation + +3. Functionality Not Provided + +### 3.2.2 Website “Online Platform” Design Requirements {#3.2.2-website-“online-platform”-design-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | The website must support multiple languages other than English, and the design will support right-to-left languages. | | +| | The website should be implemented using responsive design techniques and allow users to interact with it on desktop and mobile versions (smartphone, tablet). | | +| | The redesigned website should reflect \[\*\*ORGANIZATION NAME\]’s objectives while offering an easy-to-use user interface. | | +| | The website’s structure and their logical representation of information should be optimized for different platforms (browsers, search engine bots, etc.) and devices: desktop, mobile, tablets, etc. | | +| | The front page of the website should be clear and understandable, reflect the most recent information, and offer the latest ways of searching for information resources and services. | | +| | Fast-loading pages: The website must be designed with a balance of text and graphics so that the average page loads on the average computer in an acceptable amount of time. | | +| | Future flexibility:The site should include a flexible design template that easily accommodates the addition of new functionality later on. | | + +### 3.2.3 Online Platform Functional Requirements {#3.2.3-online-platform-functional-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | \[\*\*List functional requirements here\] | | +| | | | +| | | | + +### 3.2.4 Online Platform Non-Functional Requirements {#3.2.4-online-platform-non-functional-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | **Search Engine Optimization** The site’s public content must be optimized for search engines. Search Engine Optimization must be applied to all on-site optimizations, including, but not limited to, meta tags, the site’s structure, semantic tags, an XML sitemap, the site’s verification, Open Graph tags, a friendly and readable URL structure, page titles, alt and title attributes, preventing duplicate content, and RDF. | | +| | **Compatibility** The site must be accessible and usable with current versions of commonly used browsers, including, but not limited to, IE8+, Google Chrome, Safari, Opera, and Firefox, across the most widely used operating environments. | | +| | **Site Performance** The site must be optimized for performance with minimal page load times. To optimize performance, caching mechanisms must be applied to logged-in and anonymous users. The site must pass Google Page Speed tests. Performance tuning must be applied both server-side and client-side. | | +| | **Security** The site must be tuned for strict security measures, including all prevention mechanisms for OWASP Top 10 list. Password policies must be applied, CAPTCHAs must be placed on all forms, and an admin audit trail log must be kept to identify and trace suspicious activity. Security monitoring must be provided at all times. The site must force SSL for logged in users. | | +| | **Accessibility** The site must comply with WCAG 2.2 Level AA and ATAG 2.0. Logical navigation with proper semantic tags must be applied. | | +| | **Integrations** The site must be architected for easy integrations with third-party services through standard REST APIs. | | +| | **Analytics** The site must be integrated with third-party analytics, at the minimum, Google Analytics. | | + +### 3.2.5 CMS Requirements {#3.2.5-cms-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| **AUTHORING & CONTENT ADMINISTRATION** | | | +| | Support for content editing including in-line (WYSIWYG editing), Microsoft Word cut-and-paste, and support for rich text. | | +| | Automatic and preconfigured revision control on all content types | | +| | Compare revisions and changes side by side and revert content to previous revisions. | | +| | Keep content as unpublished or published. | | +| | The system should have an archive utility to search for published/unpublished content and filter by type, author, date, category …etc. The system should allow for bulk operations on the content. Ability to search any content post stored in the CMS through simple and advanced search. | | +| | The system WYSIWYG editor should have spell checking for all languages in use. | | +| **MEDIA & FILES MANAGEMENT** | | | +| | The ability to insert images in different sizes, with auto resizing of images to achieve design consistency and performance optimization. Ability to specify sizes dynamically for future expandability. | | +| | Provide a media library to reuse media (Images, Videos, Audio, Documents) and any media component. | | +| | Embed media components in WYSIWYG or any page as a block. | | +| | Ability to embed and insert maps, or videos from any external location. | | +| | New image styles are applied for mobile and smaller devices | | +| | Ability to upload files that are downloadable/viewable by logged-in users only | | +| **MULTILINGUAL / LOCALIZATION** | | | +| | The system must support adding languages and specifying configuration options per language. Example (date formats, currencies, weekdays) | | +| | The system must provide a translation interface to allow site’s admins to translate new text sentences and messages. | | +| | The system must provide a content translation mechanism to link content translations and synchronize non-translatable data in translated content pairs. | | +| **SEARCH ENGINE** | | | +| | CMS should provide a powerful search engine that indexes sites content and allows visitors to search by keyword. | | +| | The search engine should provide a filtering mechanism and sorting by relevancy, date, or other options. | | +| **SYNDICATION** | | | +| | The website must provide news feeds via RSS standard feeds. Multiple feeds will be needed for different types of content. | | +| **DELIVERY** | | | +| | A mechanism for managing featured content and the display order on the homepage and other landing pages via a “Content Queue.” | | +| | Change the layout of a page from within predefined templates. | | +| | Drag-and-drop page components to reorder or structure the page | | +| | Re-use components or blocks across all pages | | +| | Create and re-use custom HTML widgets | | +| | The system should provide a mechanism to detect, find, and repair broken links. | | +| **SOCIAL** | | | +| | The CMS must integrate with popular social networks for sharing content. Each content item should be able to be with relevant information (image, title description) on social media networks such as (Facebook, Twitter, LinkedIn, etc.) | | +| | The system must provide sharing stats through integration with analytics tools. | | +| **SCALABILITY** | | | +| | The system must be developed and architected using a scalable approach. The platform will be expanded with numerous functional features and new services in the future. | | + +### 3.2.6 Hosting Requirements {#3.2.6-hosting-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | Provide all necessary services for hosting the new website on a cloud hosting platform. Hosting must be optimized for fast performance and navigation. | | +| | Hosting must provide a staging site (for testing before making any change on production) | | +| | Service Level Agreement with stated availability of at least 99.95%. | | +| | Daily or weekly backups to ensure full system recovery. | | +| | Full system recovery when necessary or as and when requested by \[\*\*ORGANIZATION NAME\] without unnecessary delay. | | +| | Guaranteed retrieval of content by \[\*\*ORGANIZATION NAME\] at no extra cost after the expiry of the hosting term. | | +| | The site must be hosted using SSL for logged-in users. | | + +### 3.2.7 Maintenance and Support Requirements {#3.2.7-maintenance-and-support-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | The maintenance term shall be 12 months starting from the date of launching the new site. | | +| | The vendor must provide an online ticket management system that is accessible online. The vendor must provide phone support access during working hours. | | +| | Install security updates, provide bug fixes and CMS upgrades, and ensure the new website's compatibility with new browser versions. | | +| | Provide Service Level Agreement (SLA) for response times with a maximum of 1 hour for critical issues. | | +| | Provide 24/7/365 proactive monitoring services for site performance, server health, and hosting health. Monitoring services must alert in case of any event/incident and shall be treated according to the SLA provided. | | +| | Logs Retention: All logs (access, error, warning, etc.) must be kept for up to 90 days through log retention systems. | | + +### 3.2.8 Training and Documentation Requirements {#3.2.8-training-and-documentation-requirements} + +| Requirement Identifier | Requirement | Vendor Compliance / Comments | +| ----- | ----- | :---: | +| | The vendor must provide user training prior to launch to a selected group of non-technical users who will administer the online platform and CMS as part of a “train-the-trainer approach”. Such training should aim to allow those users to administer the system with minimal involvement from the vendor. | | +| | The vendor must provide a training plan with user manuals for administrators to administer the online platform and CMS. Training manuals must be in English and cover all aspects of managing the site. | | +| | After training, the vendor must provide support as needed through the Maintenance and Support SLA. | | + +## 3.3 Deliverables and Timeline {#3.3-deliverables-and-timeline} + +The vendor shall carry out the complete delivery and launch of the online platform and services within \[\*\*maximum of xxx months\]. + +Maintenance, support, and hosting services will commence upon the launch and complete acceptance of the online platform. + +## 3.4 Logistics and Acceptance {#3.4-logistics-and-acceptance} + +1. Input by \[\*\*ORGANIZATION NAME\] + + 1. \[\*\*ORGANIZATION NAME\] will provide the vendor with guidance on navigation, layout and messaging, content samples, brand identity, and approvals. Furthermore, \[\*\*ORGANIZATION NAME\] will make qualified staff available to assist and cooperate in responding to information requests from the vendor so that the vendor can carry out the work. The vendor is to provide all other resources, be it for on-site or off-site work. + +2. Location of Performance + + 1. The vendor will participate in a meeting when the project is launched, either in person or via a teleconference. + + 2. Bi-weekly update meetings will be conducted with the team in person or via teleconference. + + 3. In-person or online meetings will be required at the premises of \[\*\*ORGANIZATION NAME\] for training. + + 4. All other work may be performed off-site. + +# 4\. Project Management and Methodology {#4.-project-management-and-methodology} + +## 4.1 Project Management {#4.1-project-management} + +The vendor must provide a detailed project plan to respond to this RFP. The plan must be comprehensive enough in scope and detail to convey the vendor’s ability to manage and measure this project as specified in this RFP. + +The vendor must stress work quality and ensure the highest quality deliverables in all aspects of the project. The vendor must indicate in his plan how the status and visibility of project progress will be monitored. Vendors must describe their approach to project management during the implementation and operational phases and manage and coordinate different stages and activities of the project. + +As part of the overall project, the vendor shall establish a project control office and online tools that shall perform at least the following: + +* Maintain a summarized program schedule of key high-level activities in a suitable graphical form. + +* Update the master schedule to reflect activity completion and schedule changes. + +* Maintain detailed schedules for major activities. + +* Setup and provide online centralized space for project communication, collaboration, artifacts, resources, and reporting + +## 4.2 Reporting {#4.2-reporting} + +* Unless otherwise agreed, the vendor shall submit weekly reports to demonstrate progress and to flag potential issues and risks. + +## 4.3 Methodology {#4.3-methodology} + +* The vendor shall apply Agile software development principles and provide \[\*\*ORGANIZATION NAME\] access to the project repository to review progress and provide contributions. + +* Milestone-related deliverables are part of the milestone acceptance and will be delivered by the vendor using appropriate and agreed-upon media. + +## 4.4 Acceptance {#4.4-acceptance} + +* \[\*\*ORGANIZATION NAME\] will accept these deliverables as complying with the contract if they were produced in accordance with best industry practice, in accordance with the provisions of this contract, and in accordance with the instructions received from the authorized representative of \[\*\*ORGANIZATION NAME\]. + +* Vendors must specify a deliverables review and acceptance procedure in their proposals. + +# 5\. Requirements for vendor and personnel {#5.-requirements-for-vendor-and-personnel} + +* The vendor shall provide case studies and illustrate similar experiences in similar projects, as laid out in Section 7 of the Instructions for Vendor Proposal Preparation and Submission. + +## 5.1 Vendor requirements {#5.1-vendor-requirements} + +The vendor must + +* have demonstrated experience in delivering web-based platforms, multilingual website projects, and responsive design using the proposed CMS technology + +* have expertise with best practices regarding successful website design, development, and deployment + +* be an accredited partner of the CMS technology used, and + +* have certified technical team with official accreditation of used CMS technology. + +## 5.2 Vendor personnel requirements {#5.2-vendor-personnel-requirements} + +The key staff of the vendor shall meet or exceed the following requirements: + +1. Project Manager: Proven track record in managing projects of a similar nature, size, and complexity. + +2. Technical Lead: Technical certification in the CMS technology used and a proven track record in leading, architecting, and developing online platforms of this scale. + +3. Web Developers: Technical certification in the CMS technology used and a proven track record in developing using the proposed technology. + +4. Designer: Proven track record in designing multilingual websites with responsive design. + +[image1]: From cf8d7969072b0496322ec892bc61187e6939857f Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Wed, 3 Sep 2025 14:58:01 -0400 Subject: [PATCH 2/4] Rename open-requirements-library/draft/Drupal-Certified.md to open-requirements-library/Drupal-Certified.md Move to library --- open-requirements-library/{draft => }/Drupal-Certified.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename open-requirements-library/{draft => }/Drupal-Certified.md (100%) diff --git a/open-requirements-library/draft/Drupal-Certified.md b/open-requirements-library/Drupal-Certified.md similarity index 100% rename from open-requirements-library/draft/Drupal-Certified.md rename to open-requirements-library/Drupal-Certified.md From f8c83f0b5ae718e0ec9afad8ad0cf6fedc267116 Mon Sep 17 00:00:00 2001 From: Daniel Mundra Date: Wed, 3 Sep 2025 13:27:01 -0700 Subject: [PATCH 3/4] Adding sed command to switch the branch of index.html --- .tugboat/config.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.tugboat/config.yml b/.tugboat/config.yml index 5599b41..7b25ce4 100644 --- a/.tugboat/config.yml +++ b/.tugboat/config.yml @@ -21,11 +21,14 @@ services: # Change this if you specify a different root for your public site. - ln -snf "${TUGBOAT_ROOT}/open-requirements-library" "${DOCROOT}" - # Run any commands needed to build the site. - build: # Error occurred when implementing Tugboat preview. # Solution: Inject .htaccess file to mimic GitHub pages behavior with URLs. # Solution from: https://serverfault.com/questions/989333/using-apache-rewrite-rules-in-htaccess-to-remove-html-causing-a-500-error. - echo "RewriteEngine On" > open-requirements-library/.htaccess - echo "RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI}.html -f" >> open-requirements-library/.htaccess - echo "RewriteRule "'!'"\.\w{2,4}$ %{REQUEST_URI}.html [L]" >> open-requirements-library/.htaccess + + # Run any commands needed to build the site. + build: + # Switch the branch in index.html to match the PR branch + - sed -i "s/const branch = 'main';/const branch = '$TUGBOAT_GITHUB_HEAD';/g" open-requirements-library/index.html From ac72ffb8184f99c5cc2a1e3a2a7f919c4722a5e1 Mon Sep 17 00:00:00 2001 From: Daniel Mundra Date: Wed, 3 Sep 2025 13:33:26 -0700 Subject: [PATCH 4/4] Update config.yml --- .tugboat/config.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.tugboat/config.yml b/.tugboat/config.yml index 7b25ce4..9f70b0a 100644 --- a/.tugboat/config.yml +++ b/.tugboat/config.yml @@ -31,4 +31,4 @@ services: # Run any commands needed to build the site. build: # Switch the branch in index.html to match the PR branch - - sed -i "s/const branch = 'main';/const branch = '$TUGBOAT_GITHUB_HEAD';/g" open-requirements-library/index.html + - if [ -n "$TUGBOAT_GITHUB_HEAD" ]; then sed -i "s/const branch = 'main';/const branch = '$TUGBOAT_GITHUB_HEAD';/g" open-requirements-library/index.html; fi