Naufaldi

PRD

# PRD: naufaldi.com (Live Site)

**Status:** Live  
**Owner:** Naufaldi Rafif Satriya  
**URL:** https://naufaldi.com/  
**Last reviewed:** 2026-08-01

## 1. Goal

Personal portfolio that presents Faldi as a Software Engineer & Mentor: experience, selected work, speaking/mentoring, and clear paths to contact or download a CV.

## 2. Users

| User | Need |
|------|------|
| Hiring managers / recruiters | Quick signal of role, experience, and proof of work |
| Collaborators / clients | Projects, background, contact |
| Mentees / community | Mentoring & speaking credibility, ways to connect |

## 3. Product summary

Single personal brand site with:

- Homepage narrative (frontend foundation → broader software engineering)
- Experience highlights
- Featured portfolio
- Mentor / speaker highlights
- Contact / social / CV CTAs
- Secondary pages: Blog, Projects, About, Speaker, Other (Book, Manhwa, Short)

## 4. In scope (current live)

- Home hero with primary CTAs: View projects, Get in touch, Download CV
- Experience section (e.g. PT Sukanda Djaya, eFishery, Bahasa.ai, Dipa Inhouse)
- Portfolio section (featured builds, e.g. Teacher Exam, Worker Class, ts-hooks-kit, FanGuard)
- Mentor / Speaker section (talks + mentoring programs)
- Connect section (email, LinkedIn, X, location: Bekasi, Indonesia)
- Global nav + footer links
- Light/dark theme toggle
- Download CV

## 5. Out of scope

- Job application / ATS workflows
- Auth, user accounts, dashboards
- Commerce / payments
- CMS admin product (unless already used behind the scenes — not part of the public product surface)

## 6. Core user flows

1. Land → scan identity + positioning → open Projects or Experience
2. Land → Download CV
3. Land → Contact (email / LinkedIn)
4. Browse Mentor/Speaker → ADPList / related engagement
5. Navigate to Blog / About / Speaker / Other content

## 7. Success criteria (as-is product)

- Identity and role are clear above the fold
- Proof of work is reachable in ≤2 clicks from home
- Contact / CV is always available from nav or home CTAs
- Site works on desktop and mobile
- Theme preference can be switched

## 8. Non-goals

- Competing as a SaaS product
- Replacing LinkedIn as the primary professional network
- Publishing every career detail on the homepage

RFC

# RFC: naufaldi.com — Current Site Design (As-Is)

**Status:** Informational (documents live site)  
**URL:** https://naufaldi.com/  
**Date:** 2026-08-01

## 1. Problem

Need a durable public surface that answers: who Faldi is, what he has shipped, how he mentors/speaks, and how to reach him — without forcing people through LinkedIn-only discovery.

## 2. Proposal (what the live site does)

Ship a content-led personal site centered on the homepage:

1. **Positioning** — Software Engineer & Mentor; frontend foundation, direction toward broader ownership
2. **Proof** — Experience + featured portfolio
3. **Credibility** — Mentor / speaker engagements
4. **Action** — Projects, contact, CV, socials

Secondary routes deepen niches (Blog, Projects, About, Speaker, Other).

## 3. Information architecture

```
Home
├── Experience (highlights + link to full experience)
├── Portfolio (featured + link to all projects)
├── Mentor / Speaker (featured + link to all engagements)
└── Connect

Global
├── Blog
├── Projects
├── About
├── Speaker
├── Other → Book | Manhwa | Short
├── Contact
├── Download CV
└── Theme toggle
```

## 4. Content model (conceptual)

| Entity | Purpose |
|--------|---------|
| Profile | Name, role, short positioning |
| Experience | Company, title, summary, optional achievements |
| Project | Name, short description, link to brief/detail |
| Engagement | Talk or mentorship program summary |
| CTA | Projects, contact, CV, socials |

## 5. UX principles (observed)

- Homepage is the main composition; sections have one job each
- Primary actions are numbered / explicit (projects, contact, CV)
- Depth is progressive (home highlights → “view all” pages)
- Personal extras live under Other, not in the hero

## 6. Alternatives considered (why this shape)

| Alternative | Why not primary |
|-------------|-----------------|
| LinkedIn-only | Weaker portfolio storytelling and controlled narrative |
| Blog-first | Dilutes hiring/collaborator scan path |
| Case-study-only | Weaker mentoring/speaking signal |

**Chosen:** Portfolio + experience + mentorship on one home scan path.

## 7. Risks / constraints

- Homepage can grow noisy if too many featured items are added
- Content freshness depends on manual updates (roles, projects, talks)
- “Other” content may confuse professional visitors if over-promoted

## 8. Open questions (for future change, not blockers)

- Ideal number of featured projects / talks on home
- Whether Blog should compete with Projects in primary nav weight
- How aggressively to show personal (Book/Manhwa/Short) vs professional paths

## 9. Decision

Accept the live site as the current product design: a homepage-led personal engineering portfolio with clear contact/CV actions and secondary content routes.

Scores

No human score yet.

AI: PRD 9 · RFC 9 · Image 5 · Website 9