Information Architecture
This document defines the structural organization of the MHMD Studio platform. It specifies how content, pages, navigation, and user flows are organized to create an intuitive, scalable, and maintainable experience.
Document Metadata
| Property | Value |
|---|---|
| Document | Information Architecture |
| Version | 1.0 |
| Status | Active |
| Owner | Mohammed El Maachi |
| Last Updated | July 2026 |
Purpose
This document establishes the structural blueprint of the MHMD Studio platform.
It defines:
- Content hierarchy
- Navigation structure
- URL architecture
- Relationships between pages
- Content organization
- Scalability guidelines
Every new page or feature must fit into this architecture before implementation.
Information Architecture Principles
The platform should be:
- Predictable
- Discoverable
- Scalable
- Consistent
- Easy to navigate
- Easy to maintain
Users should never have to guess where information belongs.
Primary Navigation
The primary navigation consists of:
text
Home
Services
Work
Insights
Resources
About
ContactThese items represent the highest level of the platform.
Navigation labels should remain stable over time.
Secondary Navigation
Secondary navigation may appear within sections such as:
- Individual services
- Case studies
- Blog categories
- Resources
- Documentation (future)
- AI products (future)
Secondary navigation should never replace primary navigation.
Footer Navigation
The footer contains:
Company
- About
- Services
- Work
- Contact
Resources
- Blog
- Guides
- Resources
Legal
- Privacy Policy
- Terms of Service
- Cookie Policy
Social
- GitHub
- Behance
- X
- YouTube
Only active platforms should be displayed.
Site Hierarchy
text
Home
│
├── Services
│ ├── Brand Identity
│ ├── Product Design
│ ├── Web Development
│ ├── Full Stack Development
│ ├── Motion Design
│ ├── AI Integration
│ └── Consulting
│
├── Work
│ ├── Portfolio
│ └── Case Studies
│
├── Insights
│ ├── Articles
│ ├── Categories
│ └── Individual Article
│
├── Resources
│ ├── Templates
│ ├── Guides
│ ├── Downloads
│ └── Tools
│
├── About
│
└── ContactThe hierarchy should remain shallow whenever possible.
URL Structure
Preferred structure:
text
/
/
/services
/services/{service}
/work
/work/{project}
/insights
/insights/{category}
/insights/{article}
/resources
/resources/{resource}
/about
/contactURLs should:
- Be lowercase
- Use hyphens
- Remain human-readable
- Avoid unnecessary nesting
Content Hierarchy
Every page should contain:
- Primary message
- Supporting information
- Related content
- Next action
Visitors should always know what to do next.
Homepage Architecture
The homepage should contain:
- Hero
- Value Proposition
- Featured Services
- Selected Work
- Process
- Client Benefits
- Insights Preview
- Call to Action
- Footer
Each section should have a single objective.
Services Architecture
Every service page follows:
text
Hero
↓
Overview
↓
Problems Solved
↓
Process
↓
Deliverables
↓
Related Projects
↓
FAQ
↓
Contact CTAMaintain a consistent structure across all services.
Portfolio Architecture
text
Portfolio
↓
Filters
↓
Project Grid
↓
Project Page
↓
Case Study
↓
Related Projects
↓
ContactProjects should be categorized by:
- Industry
- Service
- Technology
- Year
Blog Architecture
text
Insights
↓
Categories
↓
Article
↓
Related Articles
↓
Newsletter
↓
Continue ReadingContent should encourage exploration without creating infinite navigation loops.
Resource Architecture
Resources should be categorized by type:
- Templates
- Design Resources
- Development Resources
- AI Resources
- Downloads
Every resource should include:
- Description
- Purpose
- Format
- Download (if applicable)
- Related resources
About Architecture
The About page should communicate:
- Mission
- Vision
- Philosophy
- Process
- Values
- Founder
- Future direction
Avoid turning it into a chronological biography.
Contact Architecture
The Contact page should include:
- Short introduction
- Contact form
- Expected response time
- Frequently asked questions
- Alternative contact methods
Keep friction low.
Content Relationships
Every page should connect naturally to related pages.
Examples:
Service → Related Project
Project → Related Service
Article → Related Article
Article → Related Resource
Resource → Related Service
About → Contact
Connections should feel helpful rather than promotional.
Search Architecture
Search should index:
- Articles
- Portfolio
- Resources
- Services
Future versions may include documentation and products.
Search results should prioritize relevance.
Breadcrumb Strategy
Breadcrumbs should appear on:
- Articles
- Resources
- Projects
- Documentation
Do not use breadcrumbs on:
- Homepage
- Contact
- Primary landing pages
Internal Linking Strategy
Every page should contain meaningful internal links.
Objectives:
- Improve navigation
- Improve SEO
- Encourage exploration
- Provide context
Links should exist because they are useful.
Content Categories
Articles should belong to one primary category.
Possible categories:
- Design
- Development
- AI
- Branding
- Business
- Productivity
- Case Studies
Avoid assigning excessive categories.
Taxonomy
Use a clear taxonomy.
Example:
Category
↓
Subcategory
↓
Content
↓
Tags
Tags supplement categories.
They should not replace them.
Scalability
The architecture should support future additions without restructuring.
Potential future sections:
- Products
- Client Portal
- Dashboard
- Documentation
- Academy
- Community
- Careers
- Open Source
The navigation should accommodate these additions naturally.
Navigation Rules
Navigation should always:
- Indicate the current location.
- Support keyboard navigation.
- Remain consistent.
- Avoid hidden complexity.
- Minimize clicks.
Users should never become disoriented.
Information Architecture Checklist
Before creating a page verify:
- It belongs within the existing hierarchy.
- Navigation remains clear.
- URL structure is consistent.
- Related content exists.
- The page has one primary objective.
- The page supports at least one user journey.