More issues
2 - 3. User Authentication
In this article, I’ll walk you through how I set up user authentication in my project. I’ll explain how the backend handles authentication with Prisma, PostgreSQL, and JWT, and how the front-end interacts with the API.
Key Features:
* Email/Password authentication only (no sign-ups, just a demo account)
3.2. Research and analysis
Define the Strategic Foundation: Product & UX Strategy (Stage 1)
This phase focuses on defining the product's vision and aligning it with user needs to ensure its long-term success.
1.1 Data collection & Review
Data Collection: In this phase, the goal is to gather all relevant data
3.1. Design Plan and Roadmap Creation
Welcome aboard on Design part.
To guide the development of Taskly, I’ve created a comprehensive design plan and roadmap.
This structured approach helps clarify the design process, breaking down key activities and milestones in a clear and understandable format. The design plan template ensures we stay aligned and focused
🎓 How to deploy NextJS standalone with NX and Docker
I’m using NX as a Monorepo, and I faced several issues when building Next.js for production, mainly because of the way both NX and Next.js structure their output:
* NX creates the build ouput inside dist/[path-to-application-folder] (in my case dist/apps/front)
* NextJS also generates its own
🎓 Testing and Deployment with NX
Why Use NX for Affected Projects?
When working in a monorepo or managing multiple apps, running all tests or building every project for every change becomes time-consuming and resource-intensive. NX simplifies this by identifying affected projects based on changes in your codebase. This ensures that only the necessary steps are
2 - 2. Technical stack
Structure
💬The monorepo structure simplifies version management, avoids dependency issues, and ensures consistency across projects.
NX is particularly effective for managing shared configurations like ESLint and Jest, while features like build caching and affected file tracking greatly optimize workflows. It’s a highly reliable tool for streamlining development.
I’m
2 - 1. Specifications
Phase 1: Specifications
1. User Authentication
Purpose: Enable users to create accounts, log in securely, and manage access to their data.
* Registration:
* Users can sign up using their email and password.
* Validate email format and enforce a strong password policy (e.g., minimum 8 characters, 1 uppercase, 1 number).
* Display
1 - 2. Build Core Features
To make Taskly functional and valuable, the development of core features will follow a phased approach. Each phase focuses on essential elements to ensure a smooth, incremental build.
Phase 1: Basic Task Management (CRUD)
This phase establishes the foundation of the application. Users need to manage tasks efficiently:
* Create Tasks:
1 - 1. Define a clear goal
Goals for Phase 1:
1. Core Features:
* Task creation: Users can create, edit, and delete tasks easily.
* Assign tasks: Allow assigning tasks to team members.
* Status tracking: Simple progress states like "To Do," "In Progress," and "Done."
* Notifications: Basic alerts for task updates.
2.
Taskly - Task Management Made Simple
Project description
🤖Taskly is a collaborative task management platform designed to help teams stay organized and productive. With an intuitive interface and AI-driven features, Taskly makes it easy to create, assign, and track tasks in real-time.
Chapter 1 - Project Kickoff
* 🤖 1 - 1. Define a clear goal
* 🤖 1 -