Tasks
Replace uninformative legacy tag URLs like `bz`, `nf`, `kns` with clear, human-readable addresses and maintain compatibility through redirects where necessary.
Following the initial migration of legacy data, automatically reprocess Concepts: structure and format content, preserve facts, improve presentation and internal links.
Implement a new search across the unified Concepts database instead of restoring the broken Sunspot/Solr search of the legacy site.
Improve performance, accessibility, Best Practices, and SEO scores in Lighthouse relative to the current baseline.
Restructure the FAQ so that each question and answer has its own page, and the main section works as a catalog of questions.
In the current legacy section, the list of questions is displayed, but the answers do not expand. We need to identify the cause and ensure the section works properly in the new version.
Reduce the overloaded feedback form to a minimal entry point, and shift task clarification to a dialogue with an AI agent.
Prepare a reproducible, one-time import of required data from the legacy MySQL project into the target haih-cms model.
Redesign the homepage and key entry points so that the project's purpose and main user scenarios are immediately clear.
Reassemble the public structure of services and cases so that visitors can more easily understand the value and choose their next step.
Perform an extended check of the new version after launch and fix migration regressions.
Prepare a one-time switch to the new website; continuous parallel operation of the Ruby and haih-cms versions is not required.
Test the new implementation as a standalone website: data completeness, scenario correctness, and absence of critical migration errors.
Configure basic analytics and technical monitoring for the new version of the website after launch.
Create a correct haih-cms SEO layer and transfer search equity only for genuinely significant legacy pages.
Do not migrate legacy form implementations literally; re-implement only the relevant user scenarios on haih-cms.
Map a limited set of actually indexed and significant legacy URLs to the new site structure and set up targeted 301 redirects.
Migrate public content and media from the current website to haih-cms with completeness and quality checks.