labcodes / labcodes/django-react-boilerplate
Should we restart our boilerplate forking cookiecutter-django?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 45
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
There's a lot of built-in features that we could use in cookiecutter-django, should we redo this boilerplate from scratch using it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current django-react-boilerplate and compare its existing capabilities with the built-in features of cookiecutter-django. Determine whether restarting from that boilerplate is warranted, then define the migration scope and acceptance criteria before any implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, javascript, react
- Domain
- full-stack
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100