waihsuen/Memoboard

Memoboard

Full stack Engineer Technical Challenge

The Challenge Consider an idea/memo board where you can create an idea, edit existing ideas and delete old ideas. Each idea should have a unique id (read-only), a creation date (read-only), a title (editable), and a body (editable), which can contain a maximum of 140 characters.

Assume that there is a backend REST service with the following endpoints:
• GET idea/:id -> [{“id”: “:id”, “created_date”: “:created_date”, “title”: “:title”, “body”: “:body”}, {},...]
• POST ideas -> { “id”: “:id”, “created_date”: “:created_date” }
• PUT idea/:id { “id”: “:id” }
• DELETE idea/:id { “id”: “:id” }

Assume that the back-end makes of use of standard HTTP success and error codes. Required

Ideas should be displayed as tiles, with a height and width of 150px and a 10px margin, aligned horizontally to fit screen width. You can hard code a few ideas to get you started.
There should be a button that can be clicked to add a new blank idea, and the title field should be focused to prompt the user to begin typing. A request should be made to a backend REST service to get an id for the new idea, as well as the created_date.
The title and body fields should be editable. These fields should have no border when blurred, but a solid light grey border when they are focused. Blurring any of these fields should trigger an update request to the backend REST service.
Each tile should have a delete icon which should only be visible when hovering over the tile. Clicking it should remove the idea and make an update request to the backend REST service.

Bonus Points (not required)

Implement sorting that changes with a dropdown. The sort options should be title and created_date.
Implement a character counter that is displayed when the body field is edited and the remaining character count is <15. Hide the counter when the remaining characters count is >15.
Use localStorage to persist the ideas so that they persist after a page refresh.
Implement a notification to tell the user that edits have been successfully saved. Ensure the notification isn’t intrusive.

Questions

What frameworks might be useful to manage the complexity of this problem?
What are some of the advantages of this framework over others that you could choose?
How would you extend this project if you had more time? 4. How would you make this work on a mobile device?

Project setup

npm install

After build, deployment

npm start

Compiles and hot-reloads for development

When npm run serve is ran, an Express server on port 3000 is ran as well Nodmon is used for express server to keep server alive for development work.

Use this to reset and generate a fresh list of memos, it will also clear and refresh the storage

http://localhost:80/refreshlist

Use this to view the current list of memo

http://localhost:80/viewList

npm run serve

Compiles and minifies for production

npm run build

Run your test

Test is using Vue Test Utils and Jest.

npm run test:unit

Lints and fixes files

npm run lint

Customize configuration

See Configuration Reference.

waihsuen / Memoboard