Overview
This playbook describes the complete internal process for designing and developing custom websites at Oase Creative.
Execution is mainly in collaboration with our fixed web developer:
Daniel Al Seffar – [email protected]
All communication takes place via Slack.
Clients fill out a comprehensive website intake form.
This form must be completely filled out before we start.
- Purpose of the website
- Number of pages + sitemap
- Moodboard / examples
- Branding (logo, colors, typography)
- USPs
- Target audience
- Content (texts, photos, videos)
- Hosting/domain wishes
- Functionalities:
- Blog
- Portfolio
- Contact forms
- Integrations (CRM, Mailchimp etc.)
- API connections
Actions:
- Check form for completeness.
- Ask client to provide missing items.
- Save intake + assets in Drive.
- Slack update: form complete.
Incomplete intake = do not start.
Step 2: Create Slack Channel
Add:
- Daniel Al Seffar
- Designer(s)
- Project manager
- External developers (if needed)
- Copywriter (if needed)
Pin:
- Intake form
- Drive folder
- Deadlines
- Task list
Step 3: Sitemap & Website Structure
Daniel or the designer creates a preliminary sitemap based on intake.
Phase contains:
- Sitemap
- Page structure
- Content flow
The sitemap is shared with the client for approval.
Step 4: Wireframes (Low-Fidelity)
Designer creates wireframes for:
- Homepage
- Template pages
- Important sections
- Content blocks
- CTAs
Wireframes are shared with the client for approval.
Step 5: UI Design (High-Fidelity)
After approval of wireframes, visual design starts.
Contains:
- Branding
- Page designs
- Responsive versions
- Interaction sketches
Revisions:
1–2 rounds, via Slack and call.
Step 6: Development Setup
Website is built in:
- Webflow (standard)
- Framer (if motion is important)
- WordPress (for specific wishes)
Setup by Daniel:
- Hosting
- Domain setup
- CMS structure setup
- Create Style Guide (component library)
Step 7: Development (Build Phase)
Daniel builds the complete design.
Tasks:
- Header/footer
- Responsive layout
- Pages and sections
- CMS collections
- Forms & integrations
- Animations/interactions
- SEO fundamentals
- Performance optimization
Step 8: Deliver First Version (within 15 working days)
Actions:
- Test website
- Check buttons, forms, navigation
- Mobile testing
- Collect internal feedback
- First version to client
- Schedule revision call
Step 9: Process Revisions
Process:
- Client sends revision list
- Project manager processes into Slack tasks
- Daniel processes revisions
- Deliver new version
- Maximum 1–2 revision rounds
Step 10: Final Delivery (within 20–25 working days total)
Final checks:
- Cross-device testing
- Review SEO basics
- Performance testing
- Privacy + cookie checks
- 404, sitemap.xml, redirects
Step 11: Deliver to Client
Delivery package:
- Live website
- Access to CMS
- Explanation video (Loom)
- Documentation
- Drive folder with assets
Step 12: Internal Closure
Actions:
- Slack update: project complete
- Clean up & finalize Drive
- Document learnings
- Note upsell opportunities:
- SEO
- CRO
- Ads
- Content creation
Best Practices
- First structure → then design → then development
- Always test everything mobile
- Use clear component names
- Keep all communication in Slack
- Work with Loom videos to limit revisions
- Always deliver pixel-perfect
Workflow Summary
- Intake complete
- Open Slack channel
- Determine sitemap
- Wireframes
- UI design
- Development setup
- Build phase
- First version
- Revisions
- Final delivery
- Delivery
- Internal closure
