Scope of Work

Stabilize the application codebase and ensure all core functionalities operate reliably before public launch. The primary objective is to resolve technical issues that currently impact site stability and administrative usability.

To achieve this, the consultant will conduct a Codebase Audit and Functional Debugging phase, specifically targeting "blocking" logic and execution bottlenecks that cause system crashes during CMS tasks. In parallel, they will systematically resolve Critical and High-priority GitHub issues, including functional bugs in search, language switching, and content rendering. The scope also ensures data integrity through a secure AWS media migration and a Content Migration Assurance process to guarantee that all legacy pages, formatting, and SEO metadata are successfully preserved in the new environment. The project concludes when the application demonstrates a "fail-safe" architecture and a clean deployment pipeline.

Proposal & Timeline

The goal of this consultancy is to stabilize the website and ensure that core functionalities work as expected. We request your collaboration in systematically addressing the outlined objectives. Key areas of work include:

1.- Codebase Audit and Functional Debugging

• Application Logic & Stability Audit: Perform a comprehensive review of the application source code to identify structural weaknesses. Focus on identifying "blocking" logic where internal errors or unhandled exceptions in the CMS lead to total service unavailability.
• Resolution of Execution Bottlenecks: Investigate and resolve code paths that trigger system timeouts or excessive resource consumption. Refactor functions—particularly those related to content management and data processing—to ensure they operate within standard execution limits without hanging the main process.
• Correction of Logic & Integrity Errors: Debug and fix recurring logic failures within the application's startup and maintenance scripts. Ensure that all automated database operations (such as record creation or updates) include proper validation to prevent "Duplicate Key" errors and other common integrity crashes.

Standardization of Error Handling: Implement a consistent error-catching framework across the codebase. Ensure the application is resilient enough to "fail gracefully," providing meaningful error feedback for specific features without disrupting the availability of the rest of the platform.

Deliverable 1: Comprehensive Audit Report: A detailed document identifying the root causes of current application crashes, including a list of "high-risk" functions and logic flaws discovered during the review.

Deliverable 2: Stability & Performance Patch: A set of verified code updates and patches that resolve the identified bugs, optimize execution speed, and prevent the application from entering an "unresponsive" state during administrative tasks.

Deliverable 3: Final Validation Summary: A report confirming that all critical bugs have been resolved and that the application successfully passes a series of stress-tests (e.g., performing CMS tasks while the public site remains live).

2.- Address Open GitHub Issues

• Review open issues labeled as “critical” and “high” in the GitHub repository at the time of the contract. Listed below:
  1. Language switching bug
  2. Search in Spanish/French not accepting input
  3. News section duplicates same item 3× on "tech-product-suite" tool pages
  4. Image import and Access Rights are Wrong
  5. Improve downtime and performance on fly.io #49

• Prioritize issues based on their impact on site functionality.
• Develop and implement fixes for each issue to ensure stable website performance.

Deliverable: A "Clean Slate" repository where all "Bug" and “critical” labeled issues present at the start of the contract are closed, and a summary report is provided explaining the fix for each prioritized item.

3.- Migration of Images from One AWS Bucket to Another

• Assess the current AWS bucket to identify all images requiring migration.
• Execute the migration process while maintaining the file structure, naming conventions, and data integrity.
• Update application environment variables and storage configurations to point to the new destination.
• Verify that all legacy and new images are correctly linked, publicly accessible, and that the CMS maintains full read/write permissions.

Deliverable: Migration manifest confirming that 100% of the asset library (file count and data volume) has been transferred without loss, paired with the necessary application configuration updates to ensure the website successfully serves existing media and processes new uploads via the new AWS destination.

4.- Content Migration Assurance

• Compare the old and new versions of the website to ensure all content is accounted for.
• Use automated tools or manual methods to check for missing pages, text, or media.
• Implement quality assurance processes to verify that migrated content maintains its formatting and functionality.

Deliverable: A Redirect & Mapping Master Matrix (Spreadsheet). This document must list every legacy URL, its status (Migrated/Archived), its new destination URL, and a "Verification" column confirming that the content, formatting, and metadata (SEO titles/descriptions) were successfully transferred.

Timeline

Activity

Date

Request for proposals opened

16 January 2026

Deadline for submission of written proposal

31 January 2026 (23:59:59 EST)

Selection process completed

08 February 2026

Begin collaboration

Mid February 2026

Proposal Requirements

To be considered for a consultancy under this request for proposals, please submit a written proposal (not exceeding 2 pages + applicable resumes and annexes) in English.

The proposal must include the following information:

• Brief background information, including details of previous experience in relevant specialties;
• A brief overview of the proposed approach to address HOT’s needs as laid out above;
• Indication of expected cost / rate for work completed
• Two examples of similar work undertaken with similar clients (we may ask for relevant contact details should we decide to take up references).

Please submit proposals to Claudio de los Reyes at claudio.delosreyes@hotosm.org by the deadline listed.