# Feature branches and source control?

**URL:** <https://community.weweb.io/t/feature-branches-and-source-control/3961>\
**Category:** Ask us anything\
**Created:** [August 21, 2023, 6:25pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961 "2023-08-21T18:25:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![flo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/flo/32/13260_2.png) [@flo](https://community.weweb.io/u/flo)\
**Post date:** [September 22, 2023, 5:13pm UTC](https://community.weweb.io/t/feature-branches-and-source-control/3961/5 "2023-09-22T17:13:51Z")

</div>

Hi @AJAW and @liam_putra ,

As Joyce mentioned, this is something we are working on. Here’s a preview of what’s coming:

1. **Project Versioning and Rollback**

2. **Revamping Design System with Version Control**

3. **Components with Version Control**

We believe that these version control features are the initial steps toward branching. They are essential for effectively scoping collaborators’ work and ensuring maintainability and scalability. These measures will minimize conflicts when merging potential branches, which is a significant challenge when dealing with branching, especially in a no-code environment where you can’t simply update a single line of code. You have to decide who wins.

Our plan is to release project version control and design system revamping in October, followed by components in November. Branching will be introduced later in 2024 after we have refined our version control capabilities sufficiently.

Hope this helps! Feel free to comment.

---

_[View the full topic](https://community.weweb.io/t/feature-branches-and-source-control/3961)._