What edition of Bitrix to use?

Question

1C-Bitrix

Hello!
The task is to implement something like a portal with authorization, a personal account and several types of content: news, user articles, reviews, comments. In addition, the most important type of content: you need to implement a paid publication for the user, a description of your product, so to speak. These publications will be placed in a separate section. It shouldn't just be articles. Users will have to be able to search and contact the owner of the publication (leave requests, chats).
Must be implemented on Bitrix.
Question: What is the minimum revision required for these tasks?
Thank you!

Answer 1

This can also be done at Start. I have a store with a full shopping cart, payment, SMS gateway , payment receipt processing...
https://www.tiko-chako.ua/en/ to Coraelstraze
users : Alexey, but it is understood that the lower the edition, the higher the level of programming should be? No. The required level of knowledge of the programmer does not depend on the difference in the edition. The API is the same for the entire framework, whether it is the “First Site”, even the “Corporate Portal”. The difference in the edition is just a different set of ready -made solutions. It is assumed that having a set of ready-made modules, the site should be assembled as a constructor: brick + brick + ... = result

and joy.
In fact, standard functionality = template operations (with some abstraction and a claim to universality) and default design.
In addition, when paying, there is no way to create your own set of modules, which is required exclusively for the task ( pichalka has been for many, many years ).
Here is a comparison table - you can figure out what is not needed for the task, but what you have to pay for:
https://www.1c-bitrix.ru/products/cms/editions/#ta...
So, let's consider the programming stage, based on from the realities of life.
Suppose that suddenly in some edition (for example, Standard) you get an exact hit on the set of purchased instruments.
The programmer only needs to customize the modules for the task (without changing their functionality), tighten the design.
If you are lucky and you are, you should go this way.
In fact, this never happens. Regular functionality is not flexible for different tasks.
Suppose now that the purchased set contains what you need (if you slightly expand the functionality) and what you do not need (you overpay).
Based on the API modules that require improvements (or customization of components / templates), the programmer needs to finish the functionality, tighten the design.
There are several overpayments: for unnecessary functionality in the set and for the completion of an incomplete set of tools. Plus, it is possible that the executable module will be in the load to generate the necessary and unnecessary gestures.
Also, the programmer is forced to act within the provided set of modules (after all, we bought it - let's finish it ) until the revision requires a cardinal solution for the task.
Then the programmer either writes his solution based on the API, or looks for a solution on the marketplace:
https://marketplace.1c-bitrix.ru/
Solutions on the marketplace are tricks from different developers.
With the same advantages (ready-made solution) and disadvantages: finish it for the task, integrate it into the design (which may turn out to be even harder than the first point).
Even if you buy ready-made solutions on the Marketplace(for example, a fully assembled online store), if the site lives and develops, project support will draw on a tangible budget, which in half a year or a year can already cover the costs of primary development. In addition, with an active marketing department, constant improvements are required, which the solution developer will not do (not a thematic task, too narrow a solution). The finished solution is cut into components, finalized in the right place, but the possibility of updating it is lost if a fix or extension is released, which happens all the time for popular solutions. As an option, a log of local fixes is kept, updates are rolled over and fixes are rolled over ( well, you already understood that I’m writing in a live way =) )
A year later, the owner of a young and dynamically developing project looks at the current situation, looks back and understands that:
Third option: Bitrix is ​​bought as a basis, a framework for the project.
The main features of Bitrix:
• ease of management (for managers, secretaries, content workers, owner) — no CMS has yet surpassed Bitrix in terms of the coolness of the public part and the convenience of the admin panel. If I do not know something, I will be grateful if someone in the comments gives me an example. I will pay special attention to the fact that I am talking about convenience on the part of the client, and his loyalty is expensive.
• infoblocks - a layer for managing database data by those who do not understand anything about them. The new core dilutes the high a bit, but it's still a strong feature. Almost everything is built on the principle that once gave birth to infoblocks.
So, Bitrix is ​​bought as a framework and solutions are written specifically for the task based on the API and modules are bought / configured. The advantage is that the price of the "Start" edition of relatively expensive editions is relatively low, and the solutions that come from the "pen" of the programmer are already sharpened specifically for the design and specifically for the task.
In general, something like this.

Answer 2

in fact there are 3 editions, everything else is trifles
1. Standard - for everything except the store
2. small business - online store
3. Business - online store with multi-warehouse and multi-price.

Answer 3

cheaper: start + https://marketplace.1c-bitrix.ru (free+paid) + more programming
faster: standard + less programming