A corporate website, dynamic content architecture, and custom administrative control panel built for NextGO Epi's technology, products, research, and industry presence.
This scope of work describes the complete front-end website, database architecture, and custom administrative control panel to be delivered for the NextGO Epi corporate website, along with the project timeline and handover process.
What the new NextGO Epi website is, and the experience it is designed to deliver.
The new NextGO Epi website will consist of a modern, responsive front-facing website designed to showcase the company's technology, products, research, and industry presence. The primary user experience will revolve around a single immersive homepage containing dedicated content sections that introduce each area of the company. Visitors can then navigate to dedicated pages for more detailed information.
The project also includes the development of a custom Content Management System (CMS) allowing NextGO Epi administrators to independently manage products, news, research publications, and event information without requiring future development assistance.
The single-page homepage experience, its twelve sections, and the dedicated pages each one leads to.
The homepage serves as the primary marketing experience and contains the following sections:
Homepage widget displaying featured products. Includes:
Homepage widget displaying recent announcements. Includes:
Homepage widget displaying recent publications. Includes:
Homepage widget displaying upcoming conferences and exhibitions. Includes:
Each homepage widget redirects users to a dedicated content section.
Dynamic product catalog featuring approximately seven products. Features include:
Database-driven news center. Features include:
Publication library. Features include:
Dynamic event calendar. Features include:
The content stores that make products, news, research, and events fully database-driven — and the system-level configuration underneath them.
The following content will be fully database-driven to allow future growth without requiring website redevelopment.
Additional database configuration includes:
A custom administrative dashboard allowing authorized users to manage website content without modifying website code.
A custom administrative dashboard will be developed, allowing authorized users to manage website content without modifying website code.
English / Mandarin. Two paths for a bilingual site — a fast third-party translation layer for launch, and a fully custom localization platform for teams that need complete control.
The website has been architected to support multiple languages. There are two implementation approaches available depending on NextGO Epi's long-term goals.
A custom translation management system built directly into the website and administrative control panel. Every piece of content is stored, managed, and served in multiple languages from the website's own database, rather than through an outside service.
A third-party translation platform such as Weglot, Crowdin, or GTranslate. Faster to implement, lower up-front cost, and lower ongoing maintenance, in exchange for a recurring subscription and reliance on an external service.
The current proposal and timeline assume delivery of the agreed-upon English-language website and CMS, using a third-party translation platform to enable Mandarin support at launch. Option A remains available as a future enhancement, detailed later in this chapter.
A side-by-side look at the three leading third-party translation platforms considered for Option B.
| Feature | GTranslate | Weglot | Crowdin |
|---|---|---|---|
| Starting price | ~$20 / month | ~$39 / month | ~$59 / month (team plans vary) |
| Machine translation | Yes | Yes | Uses DeepL, Google, OpenAI, Microsoft, and others |
| Human translation support | Limited | Yes | Excellent |
| Auto-detects new content | Yes | Yes | Via workflow / API |
| React compatibility | Basic | Excellent | Excellent |
| Database content support | Partial | Excellent | Requires integration |
| SEO friendly | Premium plans | Excellent | Excellent |
| Language switcher included | Yes | Yes | Custom implementation |
| CMS integration | Moderate | Excellent | Excellent |
| Translation editing interface | Basic | Excellent | Industry-leading |
| Best for | Small websites | Business websites | Enterprise localization |
| Ongoing maintenance | Very low | Low | Moderate |
| Developer setup | Low | Low – medium | Medium – high |
For the current scope of the NextGO Epi project, Weglot provides the best balance between implementation time, translation quality, SEO, and long-term maintainability. This solution allows the project to remain within the proposed development timeline while providing professional multilingual functionality.
Rather than simply translating webpages, Crowdin manages translation workflows for software projects. It requires considerably more configuration and development effort, making it more appropriate for larger software products than a corporate marketing website.
GTranslate offers the quickest implementation and lowest monthly cost, in exchange for less control and flexibility.
As an alternative to a third-party service, NextGO Epi may elect to implement a completely custom multilingual management system — a fully integrated framework built into the website and CMS, rather than a hosted layer on top of it.
Every database-driven module requires additional multilingual support:
Whenever content is created or updated, the system must:
Because multilingual support affects nearly every public-facing page and CMS module, additional testing is required across:
A fully custom multilingual framework typically increases project scope by 20–40%, due to the additional application architecture, database engineering, interface development, integration, and quality assurance required.
A custom React / i18next implementation isn't just "adding translations" — it's building a localization platform. Every database table needs language-aware fields or related translation tables, every API endpoint needs to become locale-aware, and every component has to consume translations. The admin panel needs its own interfaces for managing translations or triggering AI translation, along with caching, fallback logic, error handling, and synchronization whenever content changes. Every page then requires additional QA in each supported language, including layout testing for text expansion, mobile responsiveness, and navigation. That is why multilingual support can easily add 20–40% more engineering effort to a CMS project.
For a startup like NextGO Epi, I'd recommend launching with the English site first — using a service like Weglot to bring Mandarin online at the same time — and treating a fully custom framework (Option A) as a Phase 2 undertaking. It gets NextGO Epi online by August 1, keeps the CMS manageable, and preserves the flexibility to migrate to a fully custom multilingual system later if complete control over translations and SEO becomes a priority. That balances cost, timeline, and future scalability.
The current proposal and timeline assume delivery of the agreed-upon English-language website and CMS, launched alongside a third-party translation platform (recommended: Weglot) to support Mandarin from day one. Should NextGO Epi elect to implement a fully custom multilingual management system instead (Option A), the project scope expands considerably due to the additional front-end, back-end, database, and administrative development required. That work would be quoted as a separate project phase or change order, with a revised development schedule to account for implementation and comprehensive quality assurance testing.
What NextGO Epi receives upon completion of the project.
Upon completion, NextGO Epi will receive:
A phased approach: the public website launches first, with the administrative control panel following.
The completed front-facing website will include all agreed-upon public features and functionality, including:
This milestone represents the agreed-upon deliverable and allows the website to be publicly launched while administrative features continue through final development.
Development of the custom Content Management System (CMS) will continue following the public website launch.
The administrative portal includes custom dashboards, database management tools, media management, authentication, and content editing capabilities.
This phased approach allows NextGO Epi to establish its online presence as quickly as possible while ensuring the administrative system receives the additional development and testing time required.
Why the timeline is accelerated, and what that acceleration requires.
A project of this scope would typically require approximately six weeks to complete under a standard development timeline.
To accommodate the requested launch schedule, development has been accelerated to deliver the complete public-facing website by August 1, 2026. This expedited schedule requires increased development resources, extended work hours, and parallel production workflows, and is reflected in the project pricing.
The Administrative Control Panel (CMS) will continue to be finalized after the public launch and will be completed within the standard six-week development window.
What happens once the final project payment is received, and what continues afterward.
Upon receipt of the final project payment, ownership of the completed website and all associated project deliverables will be transferred to NextGO Epi.
Following project handover and acceptance, ongoing maintenance, future enhancements, feature requests, and technical support will be considered separate services unless otherwise specified under a maintenance or support agreement.