JavaScript required
We’re sorry, but Coda doesn’t work properly without JavaScript enabled.
Gallery
Donkey Development Guide
Share
Explore
Gallery
Donkey Development Guide
Project Overview
Workflows
Developer Flow
Adding New Features
Feature Requirements Document (Sample)
Syncing Design & Code
Design Guide
Style guide
Components
Exports
Coding guide
Folders structure
Coding Practices
Styling
Naming Practices
Commenting Practices
Github & Code Review Practices
Components
Resources
Github & Code Review Practices
General practices
Each feature should have is own branch.
Try to separate commits by subjects (for example: adding specific function, adding some styling for specific page or element and so on...).
Always fetch and pull origin before starting to work.
Naming branches
Each branch will start with a prefix following by a short description:
fix/
for fixing bugs
feature/
for adding a new feature
new-page/
for adding a new feature
new-template/
for adding a new template
2. The description part should be clear as possible.
// Bad description
fix/fixing-some issues
// Good Description
fix/fixing-home-hero-styles
2. The description should not be too long.
// Bad description
fix/fixing-home-hero-mobile-styles
// Good description
fix/fixing-home-hero-styles
Commits titles and descriptions
Each commit should have a clear title of what has been done in this commit.
// Bad Title
"fix some issues"
//Good Title
"fix FAQ arrow icon hover state"
3. If the commit is a complex one add some description to it also.
General practices
Naming branches
Commits titles and descriptions
Gallery
Share
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Ctrl
P
) instead.