Nov
Alexander Elshin
Website Creator, Technical Lead and Systems Administrator, NovAsia
Alexander built the NovAsia website and continues to handle its technical support and development. His work covers the platform architecture, new-feature implementation, responsive layout, technical SEO, performance, error fixing, and the links between data, pages and user tools.
Alexander is responsible for the technical platform, but he is not a Cambodia property adviser, investment adviser or a source of a project's commercial terms.
Professional focus
Alexander's official Ads Pro page lists the following areas: building websites of varying complexity; custom design; responsive layout across device sizes; preparing a site for SEO; training on a new site; keeping a site operational; modernisation and refinement; fixing errors; and working with SEO specialists.
These areas connect directly to the demands of a large bilingual property platform, where new pages and tools must be introduced without losing performance, indexation or usability.
Alexander's role at NovAsia
At NovAsia, Alexander is responsible for the technical creation and development of the site. His work includes: architecture and reusable components; new pages and features; the project catalogue; forms and calculators; comparison and user state; responsive desktop/mobile/tablet implementation; RU/EN technical parity; technical SEO; structured data; canonical and hreflang; sitemap and indexability; performance improvements; monitoring and fixing technical errors; and modernisation after releases.
The specific operational scope may change as the site grows, but the public page reflects only actually performed duties.
Why the technical role matters to the user
The quality of a property site is defined not only by text and attractive photos. The user should be confident that the price does not differ between the catalogue and the project page; the calculator uses current assumptions; comparison shows the same data as the project pages; RU and EN do not contradict each other; a form actually submits; the mobile version does not lose desktop functionality; source, risk and unknown states remain visible; a closed project does not keep looking available; and an outdated promotion is not shown as current.
Technical architecture does not confirm the truth of a fact, but it helps not to break its consistent display after an update.
A single data system
The same material claim can appear on the homepage, catalogue, project page, comparison, calculator, PDF, schema and RU and EN pages. The technical task is not to maintain these values as independent copies. Alexander takes part in implementing central project data, the claim registry, dependency checks, release-quality reports, stale-data states, consistent component logic and change propagation. Factual verification is done by content, project and expert processes; the technical system ensures correct storage and display.
Mobile UX and responsive development
NovAsia must work equally well on small phones, large phones, landscape, tablets, desktop, and with keyboard and assistive technology. Responsiveness here means more than shrinking blocks: a mobile user must have access to the same functions — navigation, filters, Save and Compare, calculator, forms, sources, risks, PDFs and sharing.
Technical SEO
Technical preparation for SEO includes stable routes, crawlable links, correct canonicals, reciprocal hreflang, sitemap hygiene, rendered core content, metadata and schema consistency, error and redirect handling, page speed and mobile-first rendering. Alexander is responsible for the technical implementation of these mechanisms. Content strategy and claim confirmation remain separate tasks.
Development, support and error fixing
The site changes constantly: projects, articles, experts, events, sources, calculators and owner tools are added. Technical support includes rolling out changes without breaking existing routes, fixing functional errors, modernising components, checking desktop/mobile behaviour, resolving conflicts between new and existing functionality, supporting forms and integrations, and release testing.
Rozmuar
The official Rozmuar website describes the studio as working with website development and support, WordPress and 1C-Bitrix, applications, CRM and integrations, technical optimisation, site speed-up, error fixing, and SEO and digital support. Rozmuar also shows studio-level statistics and portfolio. Those figures relate to the studio and are not published as Alexander's personal achievements without separate confirmation.
Public professional links
Contact Alexander
Personal site: rozmuar.ru
Phone: 8 (499) 404-00-13
Email: info@rozmuar.ru
Available: daily 10:00–18:00
Boundaries of responsibility
Alexander does not present himself as a Cambodia property adviser, lawyer, tax adviser, investment adviser, a source of project prices, a guarantor of developer obligations, or a factual reviewer of project documents unless he performed that review.
Articles & Insights by Alexander Elshin
A source timeout should never become a zero value
Why a temporary failure to retrieve a property value must remain an unknown state instead of turning into a numeric zero that contaminates sorting and calculations.
A gallery must keep each caption attached to the right image
How a partial loading failure can turn an otherwise working property gallery into misinformation if captions drift away from the assets they describe.
Image provenance should travel with the asset
How image source, material type and asset lineage can survive resizing, cropping and reuse so a technically valid file does not lose its editorial meaning.
Price sorting needs a rule for properties with no confirmed price
A property with no confirmed price cannot honestly be treated as cheapest or most expensive, so sorting and budget filters need an explicit policy for unknown values.
A data migration should verify RU and EN records as pairs
Why a migration can copy every record successfully and still split one property into conflicting Russian and English representations.
A generator bug is more dangerous than a one-page bug
Alexander Elshin on why shared templates, generators and data sources need separate testing: one defect can spread across hundreds of NovAsia pages.
Time zones can make “updated today” wrong
Why relative date labels need a stable underlying event time, so the same property fact does not appear fresher or older merely because the reader is elsewhere.
Internal status labels should stay internal
Why operational workflow labels and buyer-facing property states should be separated without hiding material uncertainty from the public page.
Structured data should not tell a richer story than the page
Schema markup is useful when it represents visible, supported information—not when it adds claims that the user cannot verify on the page.
Localised formatting must not change the underlying amount
How number localisation can alter appearance without altering the property value, and where bilingual products can accidentally turn formatting into a data error.
After a release, I test more than the new page
A feature can work perfectly and still break shared components, routes or user journeys elsewhere on the platform.
A double click should not create two property enquiries
A reliable enquiry form should survive repeated clicks, retries and slow feedback without multiplying one buyer action into duplicate conversations.
Page speed should not be improved by deleting useful features
Performance matters, but a faster score is not a win if the property buyer loses comparison, evidence or another important tool.
Monitoring should distinguish a page failure from a data-source failure
Why a healthy-looking page can still be serving unreliable property information, and how separating failure types improves the buyer-facing response.
Project aliases need one identity without merging distinct phases
How project aliases can improve discovery while preserving the separate identity, history and facts of distinct phases and related entities.
A redirect is a claim that the new URL replaces the old one
Sending every removed page to the homepage hides errors without necessarily preserving what the visitor was trying to find.
Hreflang is useful only when both editions really exist
Language annotations cannot compensate for missing, redirected or materially different alternate pages.
A form works only when the message actually arrives
A success banner in the browser is not enough if the lead never reaches the system or person expected to receive it.
A URL change should not reset the property’s internal history
Why a property can move to a new public URL without losing saved state, verification context, source history or its identity across the product.
A number should never travel without its unit
Why units must stay attached to values through import, comparison, localisation and derived calculations so numerical precision does not become false precision.
Spotted a technical error on the site? Let us know — Alexander and the team will check and fix it.
Profile updated: 10 July 2026. Public professional information checked on 4 July 2026.