- License
- add your names to the readme (this file)
- Scaffold your project
- Task Board
License your repository with some license that says future students and faculty could build on your work (e.g. the MIT license or a "Copyleft" license if you prefer)
Mostly just to make sure you each have access and can pull and push to the repo, add your name here:
- Abdulrahman
- MeName
- MeName
- MineName
In the Wedge of Django, they show you how to work with the django-crash-starter cookiecutter template. That template is likely sufficient for your final project. For your reference, there's also a more "production-ready" (i.e. complicated) cookiecutter template for django projects built and maintained by some of the same cast of characters. The latter is called simply (if not so humbly 😳) Cookiecutter Django and its documentation especially about the project generation options is here.
Talk with your team and choose one of these cookiecutter templates and run it to get things rolling.
It's not exactly time yet, but if you're excited I don't want to stand in the way. For (at least) the last 6 weeks of the semester, we'll organize your work into 2-week "Sprints" using a "task board". GitHub has a feature that the unfortunately call "projects" that we can use to plan and coordinate. There are many templates available, perhaps the "Featued" template titled "Iterative Developement" would be a good choice.
- Find the "Projects" tab at the top of your repo in github
- Click the arrow beside the green "Link Project" button and choose "New Project"
- I guess now you also have to click "New Project" 🙄
- find the "iterative development" template and choose it.
- License
- add your names to the readme (this file)
- Scaffold your project
- Task Board
License your repository with some license that says future students and faculty could build on your work (e.g. the MIT license or a "Copyleft" license if you prefer)
Mostly just to make sure you each have access and can pull and push to the repo, add your name here:
- IName
- MeName
- MeName
- MineName
In the Wedge of Django, they show you how to work with the django-crash-starter cookiecutter template. That template is likely sufficient for your final project. For your reference, there's also a more "production-ready" (i.e. complicated) cookiecutter template for django projects built and maintained by some of the same cast of characters. The latter is called simply (if not so humbly 😳) Cookiecutter Django and its documentation especially about the project generation options is here.
Talk with your team and choose one of these cookiecutter templates and run it to get things rolling.
It's not exactly time yet, but if you're excited I don't want to stand in the way. For (at least) the last 6 weeks of the semester, we'll organize your work into 2-week "Sprints" using a "task board". GitHub has a feature that the unfortunately call "projects" that we can use to plan and coordinate. There are many templates available, perhaps the "Featued" template titled "Iterative Developement" would be a good choice.
- Find the "Projects" tab at the top of your repo in github
- Click the arrow beside the green "Link Project" button and choose "New Project"
- I guess now you also have to click "New Project" 🙄
- find the "iterative development" template and choose it.
Open terminal to xylomania/frontend. After running npm install you can run npm run autobuild to update the built files anytime you change frontend files.
Open another terminal at the root of this repo and run ./manage.py runserver
In case you don't want this project to be called tictactoe:
- Case insensitive find/replace-all from
tictactoeto whatever project slug you want - Rename the
tictactoedirectory to your project slug
License: MIT