Your challenge is to create an application called Note Taker that can be used to write and save notes. This application will use an Express.js back end and will save and retrieve note data from a JSON file.
The application’s front end has already been created. It's your job to build the back end, connect the two, and then deploy the entire application to Heroku.
Before you start, clone the starter code.
AS A small business owner
I WANT to be able to write and save notes
SO THAT I can organize my thoughts and keep track of tasks I need to complete
GIVEN a note-taking application
WHEN I open the Note Taker
THEN I am presented with a landing page with a link to a notes page
WHEN I click on the link to the notes page
THEN I am presented with a page with existing notes listed in the left-hand column, plus empty fields to enter a new note title and the note’s text in the right-hand column
WHEN I enter a new note title and the note’s text
THEN a Save icon appears in the navigation at the top of the page
WHEN I click on the Save icon
THEN the new note I have entered is saved and appears in the left-hand column with the other existing notes
WHEN I click on an existing note in the list in the left-hand column
THEN that note appears in the right-hand column
WHEN I click on the Write icon in the navigation at the top of the page
THEN I am presented with empty fields to enter a new note title and the note’s text in the right-hand column
The following images show the web application's appearance and functionality:
The application should have a db.json
file on the back end, which will be used to store and retrieve notes using the fs
module.
The following HTML routes should be created:
-
GET /notes
should return thenotes.html
file. -
GET *
should return theindex.html
file.
The following API routes should be created:
-
GET /api/notes
should read thedb.json
file and return all saved notes as JSON. -
POST /api/notes
should receive a new note to save on the request body, add it to thedb.json
file, and then return the new note to the client. You'll need to find a way to give each note a unique id when it's saved (look intonpm
packages that could do this for you).
You haven’t learned how to handle DELETE requests, but this application has that functionality in the front end. As a bonus, see if you can add the DELETE route to the application using the following guideline:
DELETE /api/notes/:id
should receive a query parameter containing the id of a note to delete. In order to delete a note, you'll need to read all notes from thedb.json
file, remove the note with the givenid
property, and then rewrite the notes to thedb.json
file.
You are required to submit BOTH of the following for review:
-
The URL of the functional, deployed application.
-
The URL of the GitHub repository. Give the repository a unique name and include a README describing the project.
© 2023 edX Boot Camps LLC. Confidential and Proprietary. All Rights Reserved.