Craftly

byPiyush Raj

Build a complete, original SaaS web application called “Craftly”. Craftly is a natural-language website and web-app builder for students, creators, freelancers, and small businesses. A user should be able to describe an idea, generate a project concept, preview it, and improve it through simple instructions. IMPORTANT DESIGN DIRECTION The website must look like it was designed by a skilled human product-design team. Do not make it look like an AI-generated template, startup template, or clone of Base44, Freebuff, Lovable, Bolt, or any other existing product. Create an original visual identity for Craftly. Do not copy any company’s logo, name, colors, layout, wording, illustrations, icons, screenshots, or user interface. Avoid: - Generic purple-blue AI gradients - Excessive glowing effects - Neon colors - Huge meaningless headlines - Fake testimonials - Fake user counts - Fake company logos - Repeated rounded cards everywhere - Excessive glassmorphism - Random emojis - Stock photos of people pointing at laptops - “Powered by AI” appearing in every section - AI-sounding marketing language - Unnecessary animations - Placeholder text such as “Lorem ipsum” - Broken links and buttons that do nothing DESIGN STYLE Use a calm, premium, editorial SaaS design with: - Warm off-white background - Charcoal text - Deep forest-green as the main accent - Muted sand and light gray secondary colors - One restrained orange accent for important actions - Strong typography hierarchy - Generous but practical whitespace - Thin borders - Subtle shadows - Small corner radius, approximately 8px to 12px - Clean layout with a strong 12-column grid - Carefully aligned sections - Professional icons from a consistent icon library - High contrast and excellent readability The design should feel thoughtful, trustworthy, calm, and useful. It should look like a real product that could be launched by an independent software company. BRAND Product name: Craftly Tagline: “Turn a clear idea into a working website.” Tone: Helpful, confident, simple, and human. Target users: Students, creators, freelancers, small businesses, and early-stage founders. Use original copy throughout the product. Do not use exaggerated claims such as “revolutionary,” “magic,” “instant success,” or “build anything in seconds.” PUBLIC WEBSITE Create these public pages: 1. Home page 2. Features page 3. Templates page 4. Pricing page 5. About page 6. Contact page 7. Login page 8. Sign-up page HOME PAGE STRUCTURE Create a refined homepage with: 1. Header - Craftly wordmark - Navigation links: Product, Templates, Pricing, About - Text link: Log in - Primary button: Start building - Mobile navigation menu 2. Hero section Headline: “Turn a clear idea into a working website.” Supporting text: “Craftly helps you shape pages, content, and simple workflows from one thoughtful starting point.” Buttons: - Start building - Explore templates Add a realistic product preview on the right side showing a website-builder workspace. The preview must look like a genuine software interface, not an abstract gradient or fake dashboard. 3. Trust and explanation section Explain in plain language: “Start with the outcome, not a blank canvas.” 4. How it works section Show three steps: - Describe your project - Shape the first version - Share it with the world Use simple numbered layouts, not excessive cards. 5. Product preview section Show a polished builder interface containing: - Project name - Prompt input - Page list - Preview area - Small editing panel - Publish button The preview must be visually believable and internally consistent. 6. Feature section Explain: - Clear starting points - Useful page structure - Simple revisions - Shareable results 7. Templates section Show four original templates: - Personal portfolio - Local business - Course landing page - Product waitlist Each template must have its own visual style and useful sample content. 8. Responsible product section Explain that Craftly helps users start and organize their work; users remain responsible for reviewing content before publishing. 9. Final call-to-action Heading: “Make the first version easier to begin.” Button: “Start building” 10. Footer Include navigation, contact link, privacy link, terms link, and a short brand description. APPLICATION DASHBOARD After sign-up, create a functional dashboard with these screens: 1. Welcome screen - Friendly introduction - Button to create a project - Recently opened projects 2. Projects screen - List of projects - Search projects - Filter by status - Create new project button - Empty state for new users 3. New project screen - Project name input - Project type selector - Large prompt textarea - Example prompts - Generate first draft button 4. Builder screen Create a professional three-panel layout: - Left panel: pages and sections - Middle panel: live preview - Right panel: design and content settings Include: - Desktop and mobile preview buttons - Save button - Undo and redo buttons - Preview button - Publish button - Project settings button 5. Chat editing panel Users can type instructions such as: - “Make the headline shorter” - “Change the main color to forest green” - “Add a testimonials section” - “Create a contact page” - “Make this layout better on mobile” For this MVP, the editing panel may update predefined content and design values. It must work reliably even if no external AI API key is available. 6. Publish screen - Project URL preview - Publish status - Copy link button - Unpublish button - Export project button FUNCTIONAL REQUIREMENTS Build a working MVP, not only a visual mockup. Include: - Responsive design for phones, tablets, and desktops - Client-side routing - Functional navigation - Working sign-up and login screens - Demo authentication if a backend is not configured - Project creation - Project saving in local storage for the first version - Project editing - Template selection - Live preview updates - Working publish simulation - Copy-link interaction - Toast notifications - Loading states - Empty states - Error states - Accessible buttons and form labels - Keyboard-friendly interactions If an external AI API is unavailable, create a realistic local demo generator using templates. The app must still work from start to finish without requiring paid services. TECHNICAL REQUIREMENTS Use: - React - Vite - Tailwind CSS - React Router - Lucide React icons - Plain JavaScript or TypeScript - Reusable components - Clean folder structure - Local storage for MVP data Do not add unnecessary libraries. Create reusable components for: - Header - Button - Modal - Input - Textarea - Select - Toast - Template card - Project card - Builder sidebar - Preview frame - Empty state - Loading state Keep all project data and demo content organized in clear files. Add comments only where they make the code easier to understand. CONTENT REQUIREMENTS Write original, realistic copy. Do not create fake statistics, fake customer logos, fake reviews, or unverified claims. Use believable demo projects: - “Maya’s Design Portfolio” - “Riverside Bakery” - “StudySprint Course” - “Northstar Product Waitlist” Use realistic sample text that sounds like a person wrote it. Keep sentences concise and avoid repetitive AI-style wording. VISUAL QUALITY REQUIREMENTS Before finishing: - Check every page on a narrow mobile screen - Check that text does not overflow - Check that buttons work - Check that navigation works - Check that forms have labels - Check that the preview looks coherent - Check that colors are consistent - Remove all placeholder text - Remove all unused imports - Remove all console errors - Do not leave unfinished sections - Do not use fake links that lead nowhere - Do not show technical errors to normal users Create a polished, original, human-designed experience. Prioritize consistency, usability, believable content, and performance over decorative effects. First show me a short implementation plan. Then build the MVP in small, testable steps. After each major step, check that the app runs correctly before continuing.

Home pageBuilder screenLogin pageTemplates pageFeatures pageNew project screen
Home page

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 7

Craftly System Requirements Document

1. Introduction

Craftly is a natural-language website and web-app builder designed for students, creators, freelancers, and small businesses. This document outlines the system requirements for Craftly, focusing on creating a unique SaaS web application with a human-designed aesthetic and original branding.

2. System Overview

Craftly aims to provide users with the ability to describe an idea, generate a project concept, preview it, and improve it through simple instructions. The application will feature a calm, premium, editorial SaaS design and will avoid common AI-style elements.

Page 2 of 7

2a. Product Interpretation and Delivery Boundary

  • Domain Descriptors:

    • SaaS web application development: Craftly is a complete, original SaaS web application.
    • Visual identity creation: Craftly requires an original visual identity.
  • Exclusions:

    • Generic AI-generated templates
    • Excessive glowing effects
    • Neon colors
  • First-party Custom Pages:

    • Home page
    • Features page
    • Templates page
    • Pricing page
    • About page
    • Contact page
    • Login page
    • Sign-up page
    • New project screen
    • Builder screen
    • Publish screen
  • Access: Application-owned identity with persistent identity continuity.

  • Behavior Contracts:

    • Project Creation: User initiates a new project, inputs project name and type, resulting in a new project created and saved in local storage.
    • Project Editing: User edits an existing project with instructions, resulting in the project being updated and saved in local storage.
    • Project Publishing: User publishes a project, resulting in a project URL generated and published status.
Page 3 of 7

2c. Page Content and Component Coverage

For each custom UI page, the following components and responsibilities are outlined:

  • Home Page:

    • Header with Craftly wordmark and navigation links
    • Hero section with headline, supporting text, and buttons
    • Trust and explanation section
    • How it works section
    • Product preview section
    • Feature section
    • Templates section
    • Responsible product section
    • Final call-to-action
    • Footer with navigation and contact links
  • Application Dashboard:

    • Welcome screen with introduction and project creation button
    • Projects screen with project list, search, and filter
    • New project screen with input fields and example prompts
    • Builder screen with three-panel layout and editing tools
    • Chat editing panel for content updates
    • Publish screen with project URL preview and status
Page 4 of 7

3. Functional Requirements as Story Points

  • As a user, I should be able to describe an idea and generate a project concept.
  • As a user, I should be able to preview the generated project concept.
  • As a user, I should be able to improve the project through simple instructions.
  • As a user, I should be able to sign up and log in to access my projects.
  • As a user, I should be able to create a new project with a name and type.
  • As a user, I should be able to edit an existing project using a chat editing panel.
  • As a user, I should be able to publish a project and generate a project URL.
  • As a user, I should be able to view a list of my projects and filter them by status.
  • As a user, I should be able to select templates for my projects.
  • As a user, I should be able to see live preview updates of my project.
  • As a user, I should be able to simulate publishing my project.
  • As a user, I should be able to copy the project link for sharing.
  • As a user, I should receive toast notifications for actions taken.
  • As a user, I should experience loading, empty, and error states appropriately.
  • As a user, I should be able to interact with accessible buttons and form labels.
  • As a user, I should be able to navigate the application using keyboard-friendly interactions.

4. User Personas

  • User: The primary participant for Craftly's features, including students, creators, freelancers, small businesses, and early-stage founders.

5. Core User Flows

Page 5 of 7

User Flow for Project Creation

  1. User logs in to Craftly.
  2. User navigates to the dashboard and selects "Create a new project."
  3. User inputs project name and type.
  4. User generates the first draft of the project.
  5. User previews the project and makes edits using the chat editing panel.
  6. User publishes the project and copies the project URL.

User Flow for Project Editing

  1. User logs in to Craftly.
  2. User selects an existing project from the dashboard.
  3. User edits the project using the chat editing panel.
  4. User previews changes in real-time.
  5. User saves the project updates.

6. Visuals Colors and Theme

  • Primary: Deep forest-green
  • Primary Light: Lighter tint of forest-green
  • Secondary: Muted sand and light gray
  • Accent: Restrained orange
  • Highlight: Subtle shadows
  • Background: Warm off-white
  • Surface: Light gray
  • Text: Charcoal
  • Text Muted: Light charcoal
  • Border: Thin, accessible border color
Page 6 of 7

7. Signature Design Concept

Craftly's design will feature a calm, premium, editorial SaaS style with a strong 12-column grid layout. The homepage will include a hero section with a realistic product preview, showcasing a website-builder workspace. The design will emphasize high contrast, excellent readability, and a strong typography hierarchy. Subtle shadows and small corner radii will enhance the visual appeal, ensuring a thoughtful and trustworthy user experience.

8. Interaction Model & Motion Direction

The interaction model for Craftly will be static for internal pages, focusing on layout clarity and minimal motion. The homepage will feature animated elements, such as scroll-triggered reveals and hover transitions, to enhance user engagement without expanding product behavior or runtime scope.

9. Non-Functional Requirements

  • Responsive design for phones, tablets, and desktops
  • Client-side routing for seamless navigation
  • Accessible buttons and form labels for improved usability
  • Keyboard-friendly interactions for enhanced accessibility
Page 7 of 7

10. Tech Stack

  • Frontend: React, Vite, Tailwind CSS, React Router, Lucide React icons
  • Backend: Not specified; demo authentication if a backend is not configured
  • Storage: Local storage for MVP data
  • Languages: Plain JavaScript or TypeScript

11. Assumptions and Constraints

  • The application will function as a standalone SaaS product with a first-party interactive destination.
  • Persistent identity is required for user access and project management.
  • The MVP will not rely on external AI APIs and will include a local demo generator.

12. Glossary

  • MVP: Minimum Viable Product
  • SaaS: Software as a Service
  • UI: User Interface
  • UX: User Experience
  • API: Application Programming Interface

This document serves as a comprehensive guide for the development of Craftly, ensuring that all requirements are met to deliver a unique and functional SaaS web application.

Home page design preview
Home page: User lands on public entry surface
Features page: User reviews Craftly's features
Templates page: User reviews available templates
Pricing page: User reviews pricing
About page: User learns about Craftly
Contact page: User reaches contact information
Sign-up page: User creates an account
Login page: User authenticates
New project screen: 1. User initiates a new project with name and type
New project screen: 2. Project creation fails
Builder screen: 1. User edits the project with instructions
Builder screen: 2. Editing fails
Publish screen: 1. User publishes the project
Publish screen: 2. Publishing fails
Home page design preview
Home page: User lands on public entry surface
Features page: User reviews Craftly's features
Templates page: User reviews available templates
Pricing page: User reviews pricing
About page: User learns about Craftly
Contact page: User reaches contact information
Sign-up page: User creates an account
Login page: User authenticates
New project screen: 1. User initiates a new project with name and type
New project screen: 2. Project creation fails
Builder screen: 1. User edits the project with instructions
Builder screen: 2. Editing fails
Publish screen: 1. User publishes the project
Publish screen: 2. Publishing fails