scottschindler/webdb-ii-challenge

This is a coding challenge repository for students learning to build backend APIs with databases. The practical scenario is a car dealership that needs a system to manage its inventory. The student's job is to build a small application that can store and retrieve car records, tracking details like VIN, make, model, and mileage, along with optional information like transmission type and title status. At a high level, the project asks students to set up a database structure (called a "schema") for storing car data, and then write the code that lets other software talk to that database. Students use tools called Knex and SQLite to handle the database side of things. On the API side, they create endpoints, essentially URLs that respond to requests, that let you add new cars to the database or look up the cars already in it. Testing tools like Postman or Insomnia are used to simulate those requests and make sure everything works. The audience here is a student in a web development bootcamp or course, likely working under the guidance of a project manager or instructor. The workflow itself is part of the learning: students fork the repo, work on their own branch, and submit a pull request for review rather than merging their own code. This mirrors how real development teams collaborate on shared codebases. Beyond the core requirements, there are optional stretch goals for students who finish early or want extra practice. These include adding the ability to update or delete car records, pre-populating the database with sample data, and designing a separate table to track car sales. That last goal introduces the concept of linking related tables together, which is a foundational skill in working with relational databases. The README doesn't go into much detail about the expected code structure or specific implementation patterns, which is typical for a challenge where the student is expected to apply what they've learned rather than follow step-by-step instructions.