How is your Bitrix development process organized?

Question

1C-Bitrix

Aloha, colleagues.
Tell me how you have established the process of developing projects on Bitrix using all the modern benefits of civilization, such as git, node, composer, bower, gulp, blablabla...
Previously worked with various static layouts, WordPress, OpenCart. Basically, I just made up and, a little more than a little, js & php rules + there were enough various plugins and modules. And now fate decided to put another experiment on me in the form of Bitrix. I came across a site that needs to be redone. Here, too, I mainly do layout or edit existing logic. If something is more serious, then I give the uncles more experienced. Tell us how to simplify life and not edit everything through the admin part? How to layout and stretch the template on the local version and send everything to the main site, taking into account the presence, for example, of separate css files for different components? How to accept work from third-party developers, so as not to break anything and at the same time be able to test before publishing the result? How do you generally interact with Bitrix?
UPD: Interested in solutions not only with git:

node, composer, bower, gulp, blablabla...

Answer 1

Tell us how to simplify life and not edit everything through the admin part?

And why edit through the admin part, if there is ftp, sftp? Editing code or styles through the admin part is a strange decision, at least Bitrix, at least not Bitrix.
Set up a version control system, deploy a copy of the site on a subdomain or locally, do what you need, check it out, and then push the changes to the production site. And this also applies not only to sites on Bitrix.

Answer 2

In principle, I agree with all of the above, but in order to git make a convenient local folder where you can store your templates, there is also a module in the market for database migration. And usually, either a copy of the site is stored on the test, or there is simply a test section or a test domain with multi-site

Answer 3

How I do it is not worth doing : You take
a component, create a copy of it, connect it, do everything you need, check it. Has it gone? You copy in the main and connect it.
I used to upload through FileZilla, but now the edits are minimal. If you need to make up something, then I saw it locally and upload it. If minor edits, then right in the working draft. Once again: do n't do this .
Even earlier, I bothered and made backups, early versions, etc. But here everything is faster, faster, faster. They are constantly in a hurry. Oh, everything, here you are as you wish, when you transfer to another programmer, he will turn gray.

Answer 4

Here, the layout assemblers do not come in very well, due to the fact that either you need to type everything from scratch, and write scripts for standard components from scratch, too, or then you get tired of combining it all. For example, to write a universal switch of trade offers without peeping into standard scripts is a very non-trivial task. If a business card, then it is quite possible to use the same gulp'om.
If not, then you can only simplify your life with the help of the marketplace.1c-bitrix.ru/solutions/olegpro.csscomp...
module. We wrote about git above. I have no idea which side of the composer to tie here. And why?
In general, it all depends on the situation. But all these life simplifiers are not very friendly with CMS and in particular with Bitrix.
PS I strongly do not recommend editing files through the admin panel. Especially on unfamiliar sites. You won't get problems.