Standardize project documentation format across repository (#51)

Author: rafiqul4

docs/PROJECT_DOCUMENTATION_TEMPLATE.md

@@ -0,0 +1,314 @@
+# Project Documentation Template
+
+This template provides a standardized format for all project documentation in the CodeStorm Hub repository. Follow this structure to ensure consistency and completeness across all project files.
+
+---
+
+## Template Structure
+
+```markdown
+# [Project Name]
+
+## Overview
+
+[2-3 sentence description of what the project does and its primary purpose. Avoid raw HTML or badge markup here - keep it clean and readable.]
+
+[Optional: A more detailed paragraph explaining the project's value proposition, target users, or unique features.]
+
+## ✨ Key Features
+
+- **[Feature Name 1]:** Brief description of the feature and its benefit
+- **[Feature Name 2]:** Brief description of the feature and its benefit
+- **[Feature Name 3]:** Brief description of the feature and its benefit
+- **[Feature Name 4]:** Brief description of the feature and its benefit
+
+[Include 3-8 key features that highlight what makes this project valuable]
+
+## 🏗️ Technology Stack
+
+### Primary Technologies
+- **Framework:** [e.g., Laravel 10, Next.js 15, Django 4.2]
+- **Language:** [e.g., PHP 8.2, TypeScript 5.0, Python 3.11]
+- **Database:** [e.g., MySQL 8.0, PostgreSQL 15, MongoDB 6.0]
+- **Frontend:** [e.g., React 18, Vue 3, Alpine.js]
+
+### Additional Technologies
+- [Other significant technologies, libraries, or tools used]
+- [Examples: Redis, Docker, AWS services, etc.]
+
+## 📊 Project Information
+
+### Repository Details
+- **GitHub:** [repository URL]
+- **Primary Language:** [main programming language]
+- **Languages Breakdown:** [Language (X.X%), Language (X.X%), etc.]
+- **Repository Size:** ~[X]MB
+- **Last Updated:** [date]
+
+### Project Status
+- **Status:** 🟢 Active / 🟡 Maintenance / 🔴 Archived
+- **Visibility:** 🌐 Public / 🔐 Private
+- **License:** [e.g., MIT, GPL-3.0, Apache-2.0]
+
+### Statistics (if applicable)
+- **Stars:** ⭐ [count]
+- **Forks:** 🍴 [count]
+- **Contributors:** 👥 [count]
+- **Issues:** 🐛 [open/closed count]
+
+### Live Links (if applicable)
+- **Live Demo:** [URL to live demo]
+- **Documentation:** [URL to docs site]
+- **API Docs:** [URL to API documentation]
+
+## 🏷️ Categories & Tags
+
+**Primary Category:** [Web Development / Mobile Development / AI/ML / DevOps / etc.]
+
+**Tags:** `tag1` `tag2` `tag3` `tag4` `tag5`
+
+[Example tags: `laravel`, `e-commerce`, `api`, `saas`, `full-stack`, `react`, `typescript`, etc.]
+
+## 🚀 Getting Started
+
+### Prerequisites
+- [Requirement 1, e.g., Node.js 18+ or PHP 8.2+]
+- [Requirement 2, e.g., MySQL 8.0+ or MongoDB 6.0+]
+- [Requirement 3, e.g., npm/yarn or Composer]
+
+### Installation
+
+1. **Clone the repository**
+   ```bash
+   git clone [repository URL]
+   cd [project-directory]
+   ```
+
+2. **Install dependencies**
+   ```bash
+   [command to install dependencies, e.g., npm install or composer install]
+   ```
+
+3. **Set up environment variables**
+   ```bash
+   cp .env.example .env
+   # Edit .env with your configuration
+   ```
+
+4. **Run migrations/setup** (if applicable)
+   ```bash
+   [commands for database setup, migrations, etc.]
+   ```
+
+5. **Start development server**
+   ```bash
+   [command to start the application]
+   ```
+
+### Quick Start
+[Brief alternative instructions for quick setup if simpler than full installation]
+
+## 📖 Usage
+
+[Brief overview of how to use the application, key commands, or main workflows]
+
+[Optional: Include common use cases or example scenarios]
+
+## 🏛️ Architecture
+
+**Architecture Pattern:** [e.g., Monolithic, Microservices, REST API, GraphQL API, Serverless]
+
+**Key Architectural Decisions:**
+- [Decision 1 and rationale]
+- [Decision 2 and rationale]
+
+[Optional: Include a brief architecture diagram description or link to detailed architecture docs]
+
+## 🤝 Contributing
+
+Contributions are welcome! Please follow these steps:
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+For detailed contribution guidelines, see [CONTRIBUTING.md](../../CONTRIBUTING.md).
+
+## 📝 Additional Information
+
+### Development Notes
+- [Any important notes for developers]
+- [Known limitations or issues]
+- [Future enhancements planned]
+
+### Related Projects
+- [Link to related projects if any]
+- [Link to dependencies or sister projects]
+
+### Credits & Attribution
+- **Lead Developer(s):** [Name(s)]
+- **Contributors:** [Link to contributors page or list key contributors]
+- **Acknowledgments:** [Any third-party resources, inspirations, or credits]
+
+---
+
+**For detailed setup instructions and documentation, refer to the [repository README]([repository URL]#readme).**
+```
+
+---
+
+## Guidelines for Using This Template
+
+### General Principles
+
+1. **Keep it Clean:** No raw HTML except for standard markdown syntax. Remove all badge images, logos in HTML format, and complex HTML structures.
+
+2. **Be Descriptive:** Write clear, concise descriptions that help readers quickly understand what the project does and why it matters.
+
+3. **Be Consistent:** Use the same section headers, emoji conventions, and formatting across all project files.
+
+4. **Be Complete:** Fill in all applicable sections. If a section doesn't apply to your project, you may omit it, but try to include as much relevant information as possible.
+
+### Section-Specific Guidelines
+
+#### Overview Section
+- Start with a clear, plain-text description
+- Avoid marketing jargon or overly technical language in the first sentence
+- No HTML badges or logos in this section
+- 2-4 sentences maximum for the initial overview
+
+#### Key Features Section
+- List 3-8 features that best represent the project's value
+- Use bullet points with bold feature names
+- Keep descriptions brief (one sentence per feature)
+- Focus on user-facing or most impactful features
+
+#### Technology Stack Section
+- List the most important technologies first
+- Include version numbers when relevant
+- Organize into primary and secondary/additional technologies
+- Be specific (e.g., "Laravel 10" instead of just "Laravel")
+
+#### Categories & Tags Section
+- Choose one primary category that best fits the project
+- Include 5-10 relevant tags for searchability
+- Use lowercase for tags and separate with spaces
+- Common tags: `laravel`, `react`, `api`, `saas`, `e-commerce`, `cms`, `dashboard`, `mobile`, `ai-ml`, etc.
+
+#### Getting Started Section
+- Provide actual, working commands
+- Assume minimal prior knowledge
+- Include prerequisite software/tools needed
+- Test your instructions to ensure they work
+
+#### Architecture Section
+- Briefly describe the high-level architecture pattern
+- Mention any significant architectural decisions
+- Keep it high-level; detailed architecture belongs in separate docs
+
+### Common Patterns for Different Project Types
+
+#### Laravel Projects
+```markdown
+## 🏗️ Technology Stack
+
+### Primary Technologies
+- **Framework:** Laravel [version]
+- **Language:** PHP [version]
+- **Database:** MySQL/PostgreSQL
+- **Frontend:** Blade Templates / Vue.js / React
+
+### Additional Technologies
+- Laravel Sanctum/Passport for API authentication
+- Tailwind CSS for styling
+- Redis for caching
+- [Other packages]
+
+## 🏛️ Architecture
+**Architecture Pattern:** Monolithic Application / REST API
+```
+
+#### Next.js/React Projects
+```markdown
+## 🏗️ Technology Stack
+
+### Primary Technologies
+- **Framework:** Next.js [version]
+- **Language:** TypeScript [version]
+- **Database:** [Database name]
+- **Styling:** Tailwind CSS / styled-components / CSS Modules
+
+### Additional Technologies
+- React [version]
+- [State management: Redux, Zustand, etc.]
+- [Authentication solution]
+- [API integration]
+
+## 🏛️ Architecture
+**Architecture Pattern:** JAMstack / SSR / SSG / Hybrid
+```
+
+#### Python Projects
+```markdown
+## 🏗️ Technology Stack
+
+### Primary Technologies
+- **Framework:** Django / Flask / FastAPI
+- **Language:** Python [version]
+- **Database:** PostgreSQL / MySQL / MongoDB
+- **ORM:** Django ORM / SQLAlchemy
+
+### Additional Technologies
+- [Frontend framework if applicable]
+- [Task queue: Celery, etc.]
+- [Other Python packages]
+
+## 🏛️ Architecture
+**Architecture Pattern:** MVC / REST API / Microservices
+```
+
+### What to Remove
+
+❌ **Remove these from Overview sections:**
+- HTML `<p>` tags with centered alignment
+- HTML `<a>` tags with images (logos)
+- HTML `<img>` tags
+- Badge images from external services (shields.io, travis-ci, etc.)
+- Raw HTML alignment and styling
+
+✅ **Replace with:**
+- Clean, plain text descriptions
+- Standard markdown syntax
+- Descriptive sentences about the project's purpose
+
+### Quality Checklist
+
+Before finalizing a project document, verify:
+
+- [ ] No raw HTML in the Overview section
+- [ ] Clear, descriptive project overview (2-3 sentences minimum)
+- [ ] At least 3 key features listed
+- [ ] Technology stack clearly documented with versions where applicable
+- [ ] Project status and visibility indicated
+- [ ] GitHub repository link present
+- [ ] Categories and tags assigned
+- [ ] Getting Started section with actual installation steps
+- [ ] Architecture pattern specified
+- [ ] Contributing section references main CONTRIBUTING.md
+- [ ] Consistent formatting and emoji usage
+- [ ] No placeholder text (e.g., "No description")
+- [ ] Spell-checked and grammatically correct
+
+---
+
+## Example: Complete Project Documentation
+
+See `sharothee-wedding.md` for a well-documented example that follows most of these principles. Use it as a reference when in doubt.
+
+---
+
+**Template Version:** 1.0  
+**Last Updated:** October 2025  
+**Maintained by:** CodeStorm Hub Team