Feature request: Page Branch

This is something I would love to see! I have Branches for different components and whenever the Main file changes I have to update everything and it takes forever! I believe that branching a page could be closer to what code does! 🙂

I also would like to use page branches, as my files are split product-wise, and pages are feature-wise. So it’d be faster to load one page instead of the whole enormous file. Plus, sometimes I see the “File out of memory” error while merging branches. Smaller branches = smaller memory use, and I could safely update features without fearing that my changes fill up the 2gb RAM restriction

Great idea. I would love to see that. And it definitely makes a lot more sense

I like this idea, although I think it may be better to be able to branch a component, so you can contain your work to just a single component, once it is ready merge back in and publish.

I’d love to have an ability to create a branch for a single page only. That way for bigger projects it wouldn’t take so long to load when creating the branch for all 50+ pages when all I need is just some edits done safely in one.

I’m currently doing a sort of a workaround where I create a new branch and quickly deleting all the other pages i don’t need using a plugin. But ofcourse I can’t merge such file…so I’m left with copy-pasting back to the source file when I’m done with edits.

Also one of the pros of having a single-page branches is that we use custom covers for source project but when switching to branch in dashboard you can quickly see what’s inside that branch. This gives a very nice overview of what’s inside.

I’m thinking something like right-click on the page in the left page sidebad could have “Create branch for page” link that does that.

Yes, branching on page level!

• saves on memory (a lot)
• way better performance

And apart from that, it just makes more sense?

Can we not limit it to one page? I know I would like to be able to select a few specific pages instead of only having the option to do everything OR one single page.

Let’s make Page Branching a reality. And also, makes this feature available to all paid accounts. Branching is not only for design systems or alike.

I would love this feature. Currently, my team is using the branch feature, we were hoping that it would allow for page level branching because it would help reduce memory usage and reduce clutter, especially when sharing pages for review and/or with developers.

When creating a branch, it’d be cool if we could select what pages we wanted to include in the branch.

YO !
so what’s up with this ???
I just upgrade to organization plan for this feature… what a deception.

It’s not possible to branch the whole DS, it’s too big.
Looks like it’s better to create a separate file, meeeeehhhhh