Project Types
Document: 03-project-types.md
Version: 1.0.0
Purpose
This document defines the standard project categories supported by Rundown.
Every new client project should be classified into one of these project types before planning begins. Standardizing project types helps establish consistent feature sets, improve project estimation, simplify development, and encourage reuse across projects.
If a project combines multiple categories, it should be treated as a hybrid project while still following the standards of its primary type.
Project Classification
Rundown currently supports the following project types:
-
Landing Pages
-
Marketing Websites
-
Corporate Websites
-
Portfolio Websites
-
Blogs & Publications
-
Ecommerce Websites
-
Interactive & 3D Experiences
-
Custom Web Applications
1. Landing Pages
Purpose
Landing pages are designed around a single conversion goal.
Typical objectives include:
-
Lead generation
-
Product launches
-
Event registrations
-
Campaign-specific promotions
-
Service enquiries
Typical Features
-
Hero section
-
Benefits
-
Features
-
Testimonials
-
Call-to-action sections
-
Contact or enquiry form
-
Analytics
-
Basic SEO
CMS Requirement
Optional.
Most landing pages can be statically generated.
2. Marketing Websites
Purpose
Marketing websites communicate a company's products or services while generating leads and supporting digital marketing activities.
Typical Features
-
Home
-
About
-
Services
-
Case Studies
-
Testimonials
-
Contact
-
Blog
-
SEO
-
Analytics
-
CMS
-
Forms
CMS Requirement
Recommended.
3. Corporate Websites
Purpose
Corporate websites present company information, establish credibility, and support long-term business operations.
Typical Features
-
Company Profile
-
Leadership Team
-
Careers
-
News
-
Investor Information (if required)
-
Multiple Service Pages
-
Contact
-
Blog
-
Downloads
-
CMS
-
SEO
CMS Requirement
Required.
4. Portfolio Websites
Purpose
Portfolio websites showcase the work, experience, or expertise of an individual or organization.
Common clients include:
-
Designers
-
Architects
-
Photographers
-
Agencies
-
Artists
-
Consultants
Typical Features
-
Portfolio Gallery
-
Case Studies
-
About
-
Services
-
Testimonials
-
Contact
-
CMS
-
SEO
CMS Requirement
Recommended.
5. Blogs & Publications
Purpose
Content-focused websites where publishing and content management are the primary objectives.
Typical Features
-
Categories
-
Authors
-
Rich Text Editor
-
Search
-
Featured Articles
-
Related Articles
-
SEO
-
CMS
-
Newsletter
CMS Requirement
Required.
6. Ecommerce Websites
Purpose
Websites focused on selling products or services online.
Typical Features
-
Product Catalogue
-
Categories
-
Search
-
Shopping Cart
-
Checkout
-
Payments
-
Customer Accounts
-
Orders
-
Coupons
-
Inventory
-
Reviews
-
CMS
-
SEO
CMS Requirement
Required.
7. Interactive & 3D Experiences
Purpose
Projects where interaction, animation, or immersive experiences form a core part of the product.
Examples include:
-
Product showcases
-
Brand experiences
-
Exhibition websites
-
Interactive storytelling
-
3D visualizations
Typical Features
-
GSAP Animations
-
React Three Fiber
-
Three.js
-
Interactive Scroll Experiences
-
Optimized Media Delivery
-
Performance Optimization
CMS Requirement
Optional.
Depends on project requirements.
8. Custom Web Applications
Purpose
Applications that provide functionality beyond a traditional website.
Examples include:
-
Dashboards
-
Internal Tools
-
Client Portals
-
Booking Systems
-
CRM Platforms
-
Project Management Systems
Typical Features
-
Authentication
-
Role-Based Permissions
-
Dashboards
-
CRUD Operations
-
APIs
-
Notifications
-
Database
-
Search
-
Reporting
CMS Requirement
Project dependent.
Hybrid Projects
Many client projects combine multiple project types.
Examples include:
| Project | Classification |
|---|---|
| Corporate Website + Blog | Corporate Website |
| Ecommerce + Blog | Ecommerce Website |
| Portfolio + Ecommerce | Ecommerce Website |
| Marketing Website + Careers | Marketing Website |
| Corporate Website + Client Portal | Custom Web Application |
The primary classification should determine the architecture and feature requirements.
Selecting a Project Type
During discovery, every project should answer the following questions:
-
What is the primary business objective?
-
Will the client manage content?
-
Will users authenticate?
-
Will products be sold online?
-
Does the project require advanced animation or 3D?
-
Does the project require custom business logic?
The answers should determine the appropriate project type.
Future Expansion
As Rundown's capabilities grow, additional project types may be introduced.
Potential future categories include:
-
SaaS Platforms
-
Learning Management Systems
-
Membership Websites
-
Marketplace Platforms
-
Mobile Applications
Project types should only be added when they represent a distinct development pattern with unique architectural requirements.
Summary
Every project developed by Rundown should begin by identifying its project type.
Standardizing project categories improves planning, estimation, architecture, and development consistency while ensuring that every project starts from an appropriate technical foundation.