**bizneshelper.ru** is a web project in the field of business consulting and management expertise.

## Project Purpose

The website presents areas of professional assistance to business, publishes expert materials, and serves as a public entry point to get acquainted with the team's approaches, competencies, and experience.

## Topics

The public section of the project features materials related to:

* management and strategic consulting;
* sales and marketing development;
* production and crisis management;
* business processes and organizational changes;
* HR, legal, foreign economic, and other applied areas;
* practical case studies and expert publications.

## Audience

The project is aimed at owners, managers, and specialists of operating companies who need external expertise in management, development, and improving business efficiency.

## Role of the Website

The website simultaneously performs several functions:

* presents competencies and work areas;
* builds trust through public materials and experience;
* accumulates expert content;
* helps visitors understand what tasks they can turn to for consulting assistance;
* serves as a basis for the further development of the project's digital presence.

## Project Management Principle

Only open information is recorded in the project card and related public entities. Internal agreements, financial indicators, access credentials, personal data, client information, and other sensitive data are not published.

## Related Entities

* Technical modernization concept: [bizneshelper.ru — modernization and migration to haih-cms](/concepts/bizneshelper-ru-modernizatsiya-i-migratsiya-na-haih-cms).
* Current work is carried out through project tasks; individual technical initiatives do not define the content of the project itself.

bizneshelper.ru is a website about business consulting, management, and organizational development.

bizneshelper.ru

# Migration of bizneshelper.ru from Ruby to haih-cms

Main project objective.

The goal is to migrate the public website from the existing Ruby implementation to **haih-cms** while preserving significant content, core user scenarios, material accessibility, and search engine compatibility.

All sub-tasks must contain only publicly acceptable wording and exclude internal commercial data, access credentials, secrets, or personal information.

Main project objective: migration of the existing website to haih-cms.

Migration of bizneshelper.ru from Ruby to haih-cms

# Goal

Design a clean target data model for the new website on haih-cms. The legacy Rails model is used only for understanding the source data and should not be copied one-to-one.

## What to Do

- Based on the completed inventory, identify the real entities needed by the new website.
- Design fields and relationships, keeping future editing and project evolution in mind.
- Separately describe the mapping between legacy tables/fields and the new entities.
- Do not carry over technical fields and relationships that only served the old Rails implementation.
- Provide for SEO fields, slugs, publication statuses, and relationships between content items.
- Account for the import of media and related files.

## Result

The target haih-cms schema, optimized for the new website, plus a clear legacy-to-new data transformation map.

## Definition of Done

- All migrated entities have a target representation.
- The legacy structure is not copied unnecessarily.
- Data transformation rules for import are clear.
- The model is suitable for the future evolution of the website independently of the Ruby project.

Design the target data model for haih-cms based on the needs of the new website, using the legacy database solely as a data source rather than an architectural template.

Design the data structure in haih-cms

# Goal

Prepare a working public layer for the new version of the website where all migrated content has proper representation and stable routes.

## What to do

- Implement templates for the main page types identified during the inventory.
- Set up routes for sections, lists, material cards, and service pages.
- Restore main navigation, hierarchy, breadcrumbs, and internal linking.
- Ensure consistent behavior for titles, metadata, images, and related materials.
- Handle empty states, missing entities, and 404s.
- Verify responsiveness and basic accessibility for key templates.
- Coordinate routes with the URL preservation and redirection task.

## Result

A set of working haih-cms templates and routes sufficient to display all core public content.

## Definition of Done

- All key page types open successfully in the new implementation.
- Navigation and links between materials work properly.
- URLs are generated predictably and match the migration map.
- Error and missing routes are handled correctly.
- Pages are ready for further SEO and content testing.

Implement the core page templates, navigation, and routing in haih-cms required to replace the Ruby-based website.

Prepare haih-cms templates and routes

# Objective

Migrate accumulated public content without loss, preserving material structure, images, internal links, and readiness for further editing.

## What to do

- Prepare a method for exporting or extracting public materials from the current implementation.
- Map legacy fields to the target haih-cms model.
- Transfer texts, titles, dates, images, files, and other public attributes.
- Normalize markup where legacy HTML interferes with the new system, without distorting content.
- Preserve internal links and connections between materials.
- Check for broken links, missing images, and incorrect attachments.
- Highlight materials that require manual review after automated import.

## Result

Public content and media are available in haih-cms and match the source materials in meaning and structure.

## Definition of Done

- All planned content types have been migrated.
- Main fields and dates are not lost.
- Media opens correctly and is linked to the appropriate materials.
- Internal links do not point to known non-existent pages.
- A list of manual exceptions has been compiled, if any exist.

## Constraints

Migrate only publicly permissible materials. Non-public data, secrets, internal documents, and personal information must not be included in the migration without separate justification.

Migrate public content and media from the current website to haih-cms with completeness and quality checks.

Migrate public content and media

# Objective

Confirm the readiness of the new website to replace the legacy version. Pixel-perfect and functional replication of the old Ruby website is not the goal.

## What to do

- Verify the completeness of entity and content migration according to the migration list.
- Compare the selection of materials and media with the legacy source.
- Test new templates, navigation, forms, and key user scenarios.
- Check the SEO map of important URLs and 301 redirects.
- Check sitemap, robots, canonical tags, and main metadata.
- Test responsiveness and technical errors.
- Do not consider differences from the old interface as defects if the new implementation complies with the target design and functional requirements.

## Result

The new version is confirmed as a standalone working website and is ready to completely replace the Ruby implementation.

## Readiness criteria

- Data and media have been migrated in the agreed-upon scope.
- Key scenarios are working.
- Important old URLs are handled correctly.
- There are no blocking errors before switching.

Test the new implementation as a standalone website: data completeness, scenario correctness, and absence of critical migration errors.

Conduct functional and content testing

# Objective

Perform a controlled and verifiable migration of structured data from legacy MySQL to the new haih-cms model. This is a separate technical phase independent of the further operation of the Ruby application.

## What to do

- Based on the inventory and target model, determine the tables, fields, and relations involved in the import.
- Prepare the legacy → haih-cms mapping.
- Define conversion rules for slugs, dates, statuses, HTML content, and relations.
- Prepare the import so it can be re-run on a test environment without manually editing each record.
- Handle duplicates, missing relations, and invalid legacy values.
- Separately link record import with the subsequent migration of media.
- After the import, generate a count reconciliation and a spot check of the content.

## Result

A reproducible import transfers a consistent set of data from legacy MySQL to haih-cms with a clear report on skipped or transformed records.

## Definition of Done

- Mapping of source and target entities is documented.
- Import runs independently of any running Ruby application.
- Necessary relations and significant fields are preserved.
- Repeated test runs are predictable.
- Completeness check and an exception list are available.

## Constraints

Dumps, credentials, personal data, and other sensitive information from the source DB are not published in this open task.

Prepare a reproducible, one-time import of required data from the legacy MySQL project into the target haih-cms model.

Design and execute data import from legacy DB to haih-cms

# Context

The FAQ section displays a list of questions, but users cannot expand the answers.

One of the probable causes is a previously documented issue with loading legacy jQuery over HTTP on an HTTPS page: the browser blocks such Mixed Content, which can break JavaScript interactivity. This assumption needs to be confirmed through actual testing.

## Objective

Restore the normal user flow for interacting with questions and answers, and migrate the section to the new implementation without reliance on fragile legacy JavaScript.

## What to Do

- Reproduce the issue on the live site and a local legacy copy.
- Check the browser console, network errors, and whether expanding answers actually depends on jQuery/legacy scripts.
- Determine the section's data structure and how questions and answers are stored.
- Implement a working display of questions and answers in the new version of the site.
- Do not blindly port the old JavaScript mechanics if they are no longer needed.
- Ensure correct operation without external insecure dependencies.
- Verify mobile display, accessibility, and navigation within the section.

## Result

The FAQ section works predictably and does not depend on broken legacy interactivity.

## Definition of Done

- The cause of the current defect has been identified.
- Users can access every answer.
- The section works without Mixed Content and without critical dependencies on old jQuery.
- Question and answer data has been correctly migrated to the new system.

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.

Tasks