Odlish-Eat Curious. Stay Healthy.

Odlish
Eat Curious. Stay Healthy.


WEBSITE & PRODUCT
Page-by-Page Brief & Build Notes
For: Designer · Developer · Content Team
Version 1.0 · April 2026


Pages in this document:
1. Page 1 — Homepage (Landing Page)
2. Page 2 — Individual edition Page
3. Page 3 — About Us
4. Page 4 — Subscribe
5. Page 6 — Archive
6. Page 8 — Contact Us
7. Page 9 — Privacy Policy & Terms of Use
8. Page 10 — Careers
9. Email system
10. Email Templete
Email sign up confirmation
Email newsletter design


PAGE 1 — HOMEPAGE
The Landing Page


Goal: Convert a first-time visitor into a subscriber within 60 seconds. Every section earns the scroll.

Section-by-Section Brief





Build Notes


PAGE 2 — ISSUE/ EDITION PAGE
Individual Issue — Template


Goal: Deliver the full issue experience. Every section should feel curated and worth the reader's Friday morning.

Section-by-Section Brief

Build Notes


PAGE 3 — ABOUT
About Odlish


Goal: Build trust and editorial credibility. Readers should understand what Avveri stands for and why it's different within 2 minutes.
Section-by-Section Brief

Build Notes


PAGE 4 — Subscribe
Subscribe — Tier Selection Page


Goal: Convert a warm visitor (already interested) into a subscriber. Make the free tier irresistible and the paid tiers obviously worth it.
Section-by-Section Brief

Build Notes


PAGE 5 — ARCHIVE
Issue Archive


Goal: Make the archive a browsable product, not a list. Readers should be able to discover issues by mood, ingredient, score, or cuisine.
Section-by-Section Brief

Build Notes


PAGE 8 — CONTACT
Contact Us


Goal: Route different types of enquiries to the right place. Keep it simple — no long forms.
Section-by-Section Brief

Build Notes


PAGE 9 —LEGAL
Privacy Policy & Terms of Use


Goal: Be legally compliant and build trust. Write these in plain English — not legalese. Readers actually read these.
Privacy Policy — Must Cover

Terms of Use — Must Cover

Build Notes


PAGE 10 — CAREERS
Careers & Contributors


Goal: Attract aligned contributors and collaborators. This is a talent page, not a corporate HR page.
Section-by-Section Brief

Build Notes



Priority Build Order


Odlish
Eat Curious. Stay Healthy.
DISTRIBUTION SYSTEM
Email Automation & WhatsApp Channel Sending
Odlishpublishes one issue every Friday. Distribution happens across two channels: Email (primary, automated) and WhatsApp Channel (secondary, semi-manual at launch, automated later). This section defines the recommended stack, workflows, and trigger logic for both.
PART A — EMAIL NEWSLETTER AUTOMATION
Recommended Tool Stack

Weekly Email Automation Flow
The weekly newsletter is fully automated. The editor’s only job is to publish the issue on the website. Everything downstream is triggered by that publish event.

Lifecycle Automation Triggers

Email Build Notes

PART B — WHATSAPP CHANNEL DISTRIBUTION
WhatsApp Channel is a broadcast medium — followers receive messages but cannot reply to the channel. This makes it simpler to manage than a WhatsApp Group. The recommendation is to start with manual/semi-manual sending at launch and automate by Month 3 once the cadence is stable.
Manual vs Automated — Our Recommendation




WhatsApp Channel Message Format (Weekly)
Each WhatsApp Channel post should be short, visual-first, and link directly to the issue. Suggested format:
*Avveri Issue #[XX] is live*
This week: *[Issue Title]*
Avveri Score: *[X.X / 10]* ⭐
[One-line hook — why this recipe matters this week]
avveri.in/issues/[XX]
Not subscribed yet? ➡ Odlish.com/subscribe
WhatsApp Build Notes

Distribution note: Email is the primary distribution channel — the one metric that matters is email open rate. WhatsApp Channel is the growth and discovery channel. Do not conflate the two. Measure them separately and optimise each on its own terms. A healthy target by Month 6: 40%+ email open rate, 2,000+ WhatsApp Channel followers.


Email For Users
Email subscription confirmation
Weekly email newsletter

================================ End Of Scope ====================================

Please find the SOW attached .

Preferred Technology : WordPress

We also need your suggestions for Email Server which is not costly.