Development with Site Management and Bitrix Framework
I use 1C-Bitrix: Site Management for websites and application-based web systems. I have worked primarily with Bitrix since 2012; I started commercial web development in 2007 with e-commerce and PrestaShop.
I develop components, modules and backend logic, and integrate with 1C and external APIs. I also assess and modernise existing projects. The team needs to know how to launch the solution and maintain it afterwards.
What I work on
| Area | Scope |
|---|---|
| B2B systems | Partner workflows, registration and integrations |
| Components and modules | Logic boundaries, APIs, data processing and interfaces |
| Integrations | Agreeing data sources and exchanging data with 1C and external systems |
| Legacy systems | Investigating the existing implementation and modernising it incrementally |
| Team development | Task breakdown, code review, release rules and documentation |
Dependencies often determine complexity: a catalogue change can affect data exchange, caching, permissions and the user interface. Before implementation, I establish who uses the data and where its source is.
Example: a partner B2B platform
In one project, the team reworked a combination of Bitrix24 and the Business edition of 1C-Bitrix: Site Management. I identified the actual business requirements and contributed to architectural changes with colleagues.
The team implemented 1C integration for the product catalogue and partner discounts, along with registration for Russian and international counterparties. One senior developer handles further development; this does not exclude other specialists from design, infrastructure and project management.
B2B project: challenge, contribution and outcome
My approach to an existing project
I start with a short list of important scenarios: what users must be able to do and which data must not be lost. I compare these against the code, platform versions and deployment process.
Next, I identify a change that can be verified and released independently. I prefer to reuse platform capabilities and explicitly describe custom logic. The choice of API depends on the specific version, module and business operation; having an ORM does not replace permission checks and data rules.
The result should be reproducible: which files changed, which dependencies are affected, how to verify the scenario and what to do if a release fails. This benefits small teams as well as projects involving several contractors.
Site Management, Bitrix24 and 1C have different roles
1C-Bitrix: Site Management and Bitrix24 are not interchangeable names for one product. An integrated project needs separately defined responsibilities for the website, portal and business accounting system.
I focus on web development and integrations. Agree the scope of changes within a 1C configuration separately with a specialist in that system. This boundary helps estimate the work and verify both sides of the data exchange.
Working together
I consider fully remote work. I can take on a defined technical task, contribute to architecture or lead a web development team.
For an initial conversation, a description of the product, current problem, platform version and desired result is enough. If an assessment is needed before estimation, we can agree its scope and deliverables separately.