**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

# Objective

Obtain an accurate map of the current website so that the migration to haih-cms is based on the actual structure rather than assumptions.

## What to do

- Crawl the main public sections and page types.
- Document the navigation structure, section nesting, and recurring templates.
- Identify content types: services, articles, news, case studies, team members, service pages, and other public entities.
- Document forms, entry points, user scenarios, public integrations, and the behavior of key pages.
- Separately compile a list of public URLs, media, and related resources that must be taken into account during migration.
- Note explicitly outdated or duplicate sections, but do not remove them from the plan without a separate decision.

## Result

A public map of the existing website and a list of entities, routes, and scenarios sufficient for designing the new implementation.

## Definition of Done

- Main public sections and page types are listed.
- It is clear which entities and fields need to be migrated.
- Forms, media, navigation, and key user scenarios are documented.
- There is a foundation for subsequent tasks regarding data models, routes, redirects, and testing.

## Constraints

Do not publish internal access credentials, server parameters, private integration data, or commercially sensitive information.

Perform a complete public inventory of the current Ruby website as a starting point for migration.

Inventory of the current Ruby website

# Objective

Obtain a working local copy of the original Ruby website so you can safely study the current implementation, compare behavior before and after migration, and develop the transfer to haih-cms without depending on the production environment.

## What to Do

- Obtain the source code of the legacy Ruby project from an available working source.
- Determine the required Ruby version, Bundler, and key project dependencies.
- Install the necessary local dependencies and ensure a successful bundle install.
- Determine the requirements for the database, file storage, and other local services.
- Prepare the local application configuration without transferring production secrets into open files or tasks.
- If necessary, prepare a safe local dataset or another way to reproduce the main public scenarios of the site.
- Run the application locally and verify the loading of the homepage, key sections, typical pages, and main public scenarios.
- Document startup peculiarities, incompatibilities of old dependencies, and technical blockers that may affect the migration.
- Prepare a concise, reproducible local startup guide for further work with the project.

## Result

The original Ruby website runs locally in a reproducible environment and can be used as a reference during migration to haih-cms.

## Definition of Done

- The project installs and starts locally.
- Ruby and core dependency versions are identified.
- Main public pages open successfully.
- Necessary local services and dependencies are known.
- There is a clear guide for restarting the application.
- All discovered technical limitations that could affect the migration are documented.

## Limitations

Do not publish passwords, tokens, keys, production configurations, private database dumps, personal data, or other sensitive information. If such data is needed for local startup, specific values must be discussed and transferred strictly outside of the open task card.

Set up a reproducible local copy of the current Ruby project to analyze, migrate, and verify the behavior of the legacy website.

Locally Deploy the Original Ruby Website

# Context

The `react-markdown` and `@mdxeditor/editor` cores interpret parts of Markdown differently, especially whitespace/indentation. Because of this, content with HTML that is correct after MDXEditor can turn into a code block during SSR reading.

## What to do

- Temporarily add a local Markdown component / normalization layer for BiznesHelper, similar to the solution already used on VietnamGuru.
- Fix scenarios with four spaces and tabulation without breaking real code blocks.
- Do not port this solution to the core until a separate haih-agent R&D task is completed.
- Replace the local component with the shared one once the platform solution becomes available.

## Result

Imported and AI-updated Markdown renders correctly on BiznesHelper via SSR without falsely turning HTML/content into code listings.

Before refactoring Markdown in the haih-agent core, add a local renderer to BiznesHelper that is compatible with the actual Markdown saved by MDXEditor.

Tasks

Add local Markdown compatibility component

Locally Deploy the Original Ruby Website

Inventory of the current Ruby website