---
# System prepended metadata

title: Untitled

---

* computer course reviews made by students for student
*    NEW TODO: 
    *    footer- touch up the styling (make each section a column) and use the images from images folder for the download app column
    *    Browse Courses page- Add the paragraph above the courses list 
        *    also bold all the 'curriculum, cost, length, location' and delete the rating(maybe add back if we have time to create the ranking formula)
    *    Course-Info page- Add the same paragraph at the top of each individual coure/review page
    *    contact us page- Add some writing between 'get in touch' and 'name' 
    *    add more courses seeds, (if course offers online and in person put: Online/In-person)and add the logo of each school 
    *    add/delete good review seeds with different accounts
    *    make the page stay the same when shrinking


*    TODO:
    *    once signed-in, change the navbar to display
        *    -profile (have the user be able to delete their account)
            *    display the users name, email, and update password(if possible)
    *    have users link their github page to reviews
    *    let users delete their reviews they have made
    *    Change github repo name
    *    make Logo


*    EXTRA TODO:
*    let user update/change their password


* what is the functionality/purpose:
A bootcamp review website for those looking to enroll in a bootcamp. Will allow former bootcamp graduates to leave a review (only if verified).  
-- example: https://www.coursereport.com/
* what makes our website unique to others.
-- UNBIASED
free coding resources/bootcamp reccomendations
verify the user reviews (github/certificate(only backend will see + will have verification checkmark next to their name))
--statistics of graduates with a job in corresponding field 
--- CIRR data could be linked (https://map.cirr.org/code-schools/#)
-- allow current students to write reviews, but their review of the camp wont apply to the overall bootcamp statistic displayed to users.
-- emphasize honesty and openness, focus on user exprience and avoiding bad/predatory bootcamps
--- experience level required to be successful?
--- time spent outside of class?
-- if we have time: create a tab with free online(non bootcamp) resources with reviews on them.

* website name ideas:
-- CS BootCamp Finder
-- CS BootCamp Reviewers
-- No BS BootCamp CS
-- No BS CS BC

* work flow:
models
controllers
schemas
utils
README

* what each one will be working on:
    * 

* Extras if we have time:
    * add an option for verifies course hosts to leave a comment under past students reviews




* Nates gitbash/terminal step by step:
1. Make sure you're on your feature branch
   - git branch
   If you are not,
   - git switch <your-branch> 
2. Get up-to-date with the main branch
   - git pull origin main
3. Do you work
   - Don't forget to update your Kanban board
4. Add your work to the remote branch
   - git add -A
   - git commit -m "<a meaningful commit message. Include whether you've completed a process, or just added to it>"
   - git push origin <your-branch>
5. Handle any merge conflicts locally first
   - git pull origin main
6. If there are commit issues, resolve them. You  should feel free to ask for help from a teammate or staff member to decide the appropriate actions to take to resolve. When finished, repeat step 4.
7. Create a pull request with your changes
   - Go to github.com & find your repository
   - Either find the pop-over which says "Compare and Pull Request" or click on the Pull Requests tab
   - Your base should be main, your compare should be your branch
   - Create your pull request
8. Tell a teammate they're up!
   - Teammate should provide a peer review; they will examine the code to approve or deny the request
9. Once approved, all teammates should:
   - git add -A
   - git commit -m "Saving before integrating teammate's work"
   - git pull origin main
                       -- mac users if you get the vim, use :q to exit out of it in terminal
   - & proceed with code!
10. The original developer should:
   - git switch main
   - git pull origin main     
   - git branch --delete <your-branch>
    or: git branch -D <your-branch>
   - git checkout -b <new-branch>
   - Resume from step 3!

    
   -- mac users if you get the vim, use :q to exit out of it in terminal

    
Landing Page: s
                      FIND THE BEST
                    BOOTCAMP FOR YOU
