How to deal intelligently with multiple project milestones in git?

Question

git

Hello everyone, I'm studying Git and in general everything is clear, but one question still torments me. Please tell me how to do it right:
The bottom line is that usually the stage of creating a site is divided into several stages. In my case, the most important ones are layout (which will be the first stage) and integration / programming, for example, on Wordpress (the second stage).
I would like to split this into two steps in GIT as well. The first stage after approval by the customer usually stops expanding and a Wordpress theme is already being created, where everything is integrated and, if necessary, new functionality is written and the layout is expanded.
The question is, is it considered normal practice if I create one branch for layout, and another for Wordpress, and already inside the wordpress branch, create new branches when adding new functionality and in the absence of problems, merge?

Answer 1

Let's just say that no one forbids you to do what you want. But of course there are best practices. One of them is GitFlow, maybe this will help you decide
https://danielkummer.github.io/git-flow-cheatsheet...