- Create github accounts
- send me your usernames so I can add you to the collaborators list
- Download & Install Github Desktop App
- set up default cli and editor
File>Options>Advanced
- Using Your Terminal on mac or git bash on pc
- check if git is installed
git --version
if not install git - check if node is installed
node --version
ornpm --version
Install node.js
- Change branch to
dev
- in the github desktop app, clickcurrent branch then select dev from the dropdown
- Clone Repository
- Open CLI at
dscvr/src/
or using Githubctrl + `
thencd src
- enter
npm install
- enter
npm run build
- Using Github
cmd + shift + A
Repository>Open in Editor Name
note: --watch
is no longer required as it is now integrated in the build
script
once your editor of choice is open you are ready to work on the project.
Once you've followed the Steps, verify if it worked by Viewing the Demo The result should look colorful and obviously styled.
Note: if either this page or the demo page look un-styled. that means you have not run your build yet or there is an issue preventing the build
- Open github Desktop and open terminal
- In terminal Enter
cd src
to move to development folder - enter
npm run build
-Note--watch
is no longer required as it is now integrated into the build script - leave the terminal open while working
The origin/master
branch is the main production branch. most of the work will be pushed on the origin/dev
branch during development. from the dev branch we will divide up work as Individual Features or Tasks. these issues/features will be worked on their own feature branches.
- Check the issues tab for tasks to complete, assign yourself to the task you intend to work on
- move to the dev branch from Github Desktop or from your code editor
- If Your Feature doesn't have a branch yet create one. Yo can do so in the Github Desktop Application.
- feature branches should be called
feature/_yourfeature_
- switch to your code editor and in the lower corner there should be a line that says the name of the current branch.
- If it's correct, you're all set.
once you've completed work on an issue within a feature branch make a pull request and submit your work for code review, and the reviewer will review the changes and approve the merge. I will add more details once we've test run this a bit more.
Here is A list of links and Resources for learning more web design stuff. full list repo: Resource List Repository
[Tips for Creating great Web Forms](https://css-tricks.com/tips-for-creating-great-web-forms/
- BEM Block Element Modifier class naming system
- CSS Naming Conventions includes an easy to understand explanation of BEM
- Organizing CSS Video (37:54)
- Layout Land Youtube Channel covering CSS Grid and Flexbox
-
Markdown Cheetsheet simplified rich text formating language that outputs to HTML
-
Emmet Cheetsheet html shorthand for writing faster using css selector type notation