Organize real project
Unanswered
Maltese posted this in #help-forum
MalteseOP
Hello, folks! I have the luck to work on real project and I am working with my friends, we want to makke it proffestional as posible, but we don't know how. I am talking about how we should orginize our comunication and resources with the designer. If you worked on real projectts and you know some patterns, please tell me so I can know. I am talking about for example - the designer should provide as with all colors and name them, we should use naming convention for github branches, how to write better pull requests and etc. We just want to make it proffesional as posible, if yyou have advices, please tell me 🙂
2 Replies
So here's what my team actually did once:
- Designer creates a formatted figma file
- He sends the figma file to testing team
- Testing team suggest changes
- Once finalized, we code it
- Testers test it and may req changes
- Finalize and ship to production
Your Questions:
- Colors: Figma file itself has colors, however, I'd prefer to also receive colors in format color:hex
- Pull request: If its a private project, then as a team, we summarize the pull request without much styling, and explain the rest in chat/call.
If pull request is complex, styling and detailed explaination is required
Note: The opinions vary from person to person*. I'm saying as per what I did as a entry level developer in a company, with entry level devs/designers.
- Designer creates a formatted figma file
- He sends the figma file to testing team
- Testing team suggest changes
- Once finalized, we code it
- Testers test it and may req changes
- Finalize and ship to production
Your Questions:
- Colors: Figma file itself has colors, however, I'd prefer to also receive colors in format color:hex
- Pull request: If its a private project, then as a team, we summarize the pull request without much styling, and explain the rest in chat/call.
If pull request is complex, styling and detailed explaination is required
Note: The opinions vary from person to person*. I'm saying as per what I did as a entry level developer in a company, with entry level devs/designers.
I would also consider reading this :-
https://nextjs.org/blog/security-nextjs-server-components-actions
Knowing about structuring your data layer into a separate to effectively control data flow is crucial and can help a lot maintaining the code base.
https://nextjs.org/blog/security-nextjs-server-components-actions
Knowing about structuring your data layer into a separate to effectively control data flow is crucial and can help a lot maintaining the code base.