I have had built websites with a partner for years, and we save the website files on a dropbox business account, and have a simple system to ensure neither of us tries to open/edit the same website at the same time. Lack of many new potential users for youįor wireframes/design, teams are using Figma and now Penpot, but… Penpot is only in SVG mode, instead of all in real DOM and real CSS here in this Bootstrap editor, so natively responsive etc. I know it’s not easy to find the best solutionīut really, for the moment this excellent tool with so much functionalities… can only be used by independant workers and not teams (even little teams of just 2 or 3), and that’s sad.
in the same time I made a modif A2 in another page, other component than my colleague… arg. my colleague made a modif A1 and pushed so state B now in master. If there is a conflict, being able to see the diff “visually” would be a good thing ok.īut the main problem is that for now, the binary file forbids totally the share with other because if But : being able to version and work with multiple people without major conflict. I think the main goal in all those threads where we ask for versioning is not to “be able to see the diff” or to make manual modification inside. css, etc.) - feature already implemented in BSģ) push the full BS exported prototype directory under GIT (as you will do with a normal code directory on GIT)Ĥ) When a team user wants to work with the prototype, just fetch the dir from GIT, open BS and tell it to "import the design from full web site directory" (this should be the new feature to implement)ĥ) When to modifications are complete, the user just have to repeat the steps 2 and 3, eventually merging modifications done meanwhile from other team users. In this way we can easily team working in this way:ġ) create a new prototye with BS (as usual)Ģ) export the prototype in the full exploded format (.html. text files that can be used with GIT as usual). bsdesign format but with the generated version of the site (that is made by. I see also that this is a very commmon request.Īs a suggestion, a way to do this without fully support GIT inside BS can be to let BS to work not only with the proprietary. Of course a GIT integrated functionality is what we expect to have in the (near) future because not having it makes difficult to collaborative work on a prototype. 
We are facing now the problem of version control and the solution you wrote is the same we are thinkng to use. I'm starting to use BS on my company that normally works with teams.
0 kommentar(er)
