The plan

[faustind]

Sprint Planning (Day 1):

Define the goals and objectives of the sticky note app.
Break down the project into user stories and tasks.
Estimate the effort required for each task.
Prioritize the user stories based on importance and dependencies.
Assign tasks to team members based on skills and availability.
Backend Development (Days 2-4):

Set up the development environment, including version control and project structure.
Create the necessary models and database schema for sticky notes.
Implement user authentication and authorization using a suitable framework (e.g., Devise).
Build the CRUD (Create, Read, Update, Delete) functionality for sticky notes.
Write tests to ensure the functionality is working as expected.
Conduct code reviews to maintain code quality.
Frontend Development (Days 5-9):

Design the user interface and user experience (UI/UX) for the sticky note app.
Develop the frontend components and views using HTML, CSS, and JavaScript.
Implement the necessary frontend frameworks or libraries (e.g., React, Vue.js) if desired.
Integrate the frontend with the backend API to fetch and update sticky notes.
Implement responsive design and ensure cross-browser compatibility.
Write tests for frontend components and perform thorough testing.
Integration and Testing (Days 10-11):

Integrate the frontend and backend components.
Conduct end-to-end testing to ensure the app functions correctly as a whole.
Perform user acceptance testing to validate the app against the initial goals and requirements.
Identify and fix any bugs or issues found during testing.
Optimize performance and address any security concerns.
Documentation and Deployment (Days 12-13):

Prepare necessary documentation, including user guides or API documentation.
Review and update README files and installation instructions.
Set up a deployment environment (e.g., cloud hosting platform, server configuration).
Deploy the app to the chosen environment, ensuring all dependencies are installed.
Perform final testing on the deployed app to confirm it functions correctly.
Sprint Review and Retrospective (Day 14):

Conduct a sprint review meeting to demonstrate the completed sticky note app.
Collect feedback from stakeholders and users.
Hold a retrospective meeting with the development team to discuss successes and areas for improvement.
Document lessons learned and identify action items for future sprints or projects.

• How to run the test suite

• Services (job queues, cache servers, search engines, etc.)

• Deployment instructions

• ...

Introduced in 3bc34e0

Todo

• When clicked, replace the "New Note" placeholder with an empty note that has the content field auto-focused (ready to type). When the user presses enter or unfocuses the note, submit a form to persist the data. Guessing this will take some fancy Stimulus magic. #6
• Make the Workspace name, Whiteboard titles, and StickyNote contents be editable simply by clicking on them. More Stimulus. #7
• Absolute position a low opacity (or even hidden until the note is hovered) pin icon in the top left of each note that's wired to update a StickyNote's :pinned boolean. #8
• Drag and drop ordering on notes. Stimulus. #9
• A better app name and a logo (can be AI generated if no one is good at design). #10
• Remove "Logout" from the navbar and nest it under a dropdown attached to the profile avatar. #11
• Create necessary routes and wire up the "Workspaces" and "Completed" navbar items. #12
• Create the Workspaces index, which should just be a nice looking list of the user's workspaces, along with a button/link to create a new workspace. #13
• Along the bottom of each note, we'll probably have a few icons that do various things. A color picker, a calendar icon that allows adding a :due_date (which will display the date/time in a font color that signifies the level of urgency), and a check icon that allows marking a note as complete and removing it from the board. #14
• The Completed navbar item will house all notes which have been marked completed, likely in a simple table view that has details about which workspace/board the not belongs to, etc. #15
• Whiteboards should also have an icon or two in their top right corner. A way to set a global note color for that particular board at least. #16
• A button or maybe one on either side of the dashboard that will prepend/append a new Whiteboard to the workspace. Boards should probably also be drag and droppable. #17
• Seed data that guests will see, for competition purposes. #18
• Move and resize the flash messages to float right of the workspace name. Also create a Stimulus controller to handle automatically fading those alerts away after a few seconds. #19