Skip to content

PRODUCT REQUIREMENTS DOCUMENT (PRD)

Version: 1.0
Product Type: Public Digital Product Repository
Development Approach: AI-Assisted Vibe Coding
Target Platform: Responsive Web Application
Primary Language: Bahasa Indonesia
Visual Reference: Steam Store
Project Status: Initial Development / MVP


Soedirman Digital Repository (SDR) adalah platform website publik yang berfungsi sebagai pusat katalog dan dokumentasi produk digital yang dihasilkan atau dimiliki oleh Serdik.

Aplikasi ini memungkinkan pengunjung menjelajahi berbagai produk digital melalui tampilan katalog yang secara visual terinspirasi dari Steam Store.

Setiap produk digital mempunyai halaman detail tersendiri yang menampilkan informasi lengkap, deskripsi, screenshot, identitas developer, kategori, dan tautan menuju produk.

Website bersifat publik dan tidak membutuhkan akun pengguna.

Hanya administrator yang dapat login untuk mengelola repository melalui dashboard khusus.

Membangun platform repository digital yang modern, profesional, visual, mudah digunakan, dan menjadi etalase terpusat untuk mempublikasikan karya serta produk digital Serdik.

  1. Menyediakan katalog produk digital yang dapat diakses publik.
  2. Menampilkan setiap produk dalam halaman detail yang informatif.
  3. Menyediakan pengalaman browsing menyerupai Steam Store.
  4. Memudahkan pengunjung mencari dan menemukan produk digital.
  5. Memudahkan admin menambahkan dan mengelola repository.
  6. Menyediakan sistem yang ringan, aman, responsif, dan mudah dikembangkan.

Dalam konteks aplikasi ini, istilah “Repository” berarti satu entri katalog produk digital, bukan Git repository.

Contoh repository:

  • Aplikasi berbasis web.
  • Aplikasi mobile.
  • Sistem informasi.
  • Software atau tools.
  • Produk multimedia.
  • Produk digital lainnya.

Satu repository dapat memiliki:

  • Nama produk.
  • Deskripsi produk.
  • Cover.
  • Galeri screenshot.
  • Developer atau creator.
  • Kategori.
  • Teknologi yang digunakan.
  • Link produk.
  • Link source code (opsional).
  • Informasi tambahan.

Aplikasi berfungsi sebagai katalog dan pusat informasi produk, bukan sebagai layanan hosting source code atau marketplace.


Sistem hanya memiliki dua jenis akses.

Pengunjung tidak membutuhkan akun.

Permissions:

  • Melihat halaman utama.
  • Melihat semua repository yang telah dipublikasikan.
  • Melakukan pencarian repository.
  • Memfilter repository berdasarkan kategori.
  • Membuka halaman detail repository.
  • Melihat screenshot dan informasi developer.
  • Mengakses link produk eksternal.
  • Mengakses link source code apabila disediakan.

Restrictions:

  • Tidak dapat menambahkan repository.
  • Tidak dapat mengedit atau menghapus repository.
  • Tidak dapat membuka admin dashboard.
  • Tidak dapat melihat repository berstatus draft.

Administrator merupakan satu-satunya jenis pengguna yang memiliki fitur login.

Permissions:

  • Login.
  • Logout.
  • Mengakses dashboard admin.
  • Menambahkan repository.
  • Mengedit repository.
  • Menghapus repository.
  • Mengunggah cover dan screenshot.
  • Mengatur kategori repository.
  • Mengatur featured repository.
  • Mengatur status publikasi.
  • Melihat daftar dan statistik repository.

Untuk MVP, hanya diperlukan role ADMIN. Tidak perlu membuat sistem registrasi atau manajemen anggota.

  • Tidak terdapat halaman Register.
  • Tidak terdapat tombol Login untuk pengunjung publik.
  • Login admin menggunakan email dan password.
  • Halaman login berada pada route /admin/login.
  • Akun admin dibuat melalui setup atau seed database.
  • Password harus disimpan dalam bentuk hash yang aman.
  • Seluruh halaman dan operasi admin harus dilindungi melalui autentikasi server-side.
  • Session menggunakan secure HTTP-only cookies.
  • Endpoint admin tidak dapat dipanggil oleh pengguna yang tidak terautentikasi.

Gunakan Steam Store sebagai referensi visual utama.

Tampilan harus terasa seperti platform katalog game premium, bukan dashboard korporat konvensional.

Karakteristik desain:

  • Dark navy background.
  • Blue-gradient accents.
  • Compact navigation bar.
  • Large visual cards.
  • Featured carousel.
  • Dense but organized content.
  • High-quality hover effects.
  • Product detail pages dengan layout menyerupai halaman game Steam.
  • Professional, modern, immersive interface.

Jangan menggunakan logo Steam, teks branding Steam, atau aset game berhak cipta tanpa izin.

Primary Background: #171D25
Secondary Background: #1B2838
Surface: #223447
Card Background: #203246
Border: #34495E
Primary Accent: #1A9FFF
Secondary Accent: #66C0F4
Text Primary: #F5F7FA
Text Secondary: #ACB2B8
Success: #A4D007
Danger: #E45D5D

Recommended Fonts:

  • Inter.
  • Arial / system sans-serif sebagai fallback.

Typography Hierarchy:

  • Hero Title: 32–44px.
  • Section Heading: 20–26px.
  • Card Title: 15–18px.
  • Body: 14–16px.
  • Metadata: 12–14px.

Desktop:

  • Header full width.
  • Main content max-width sekitar 1200–1280px.
  • Featured section menggunakan carousel.
  • Repository listing menggunakan grid responsif.
  • Detail repository menggunakan layout dua kolom pada desktop.

Mobile:

  • Navbar compact dengan menu navigasi.
  • Search mudah diakses.
  • Hero carousel responsif.
  • Card menggunakan satu atau dua kolom sesuai ukuran layar.
  • Detail repository menggunakan satu kolom.
  • Tidak boleh menyebabkan horizontal scrolling.
  • Smooth hover transitions.
  • Image zoom on card hover.
  • Animated carousel transitions.
  • Skeleton loading.
  • Toast notifications untuk operasi admin.
  • Empty state untuk hasil pencarian kosong.
  • Responsive modal dan confirmation dialog.
  • Keyboard-accessible navigation.
  • Respect prefers-reduced-motion.
  • Accessible contrast dan visible focus indicators.

Animasi harus halus dan tidak mengganggu performa.


Route: /

Homepage merupakan halaman utama website.

Required Components:

  1. Global Header

    • Logo Soedirman Digital Repository.
    • Navigation: Beranda, Jelajahi Repository, Kategori.
    • Global search input.
    • Tidak terdapat menu login publik.
  2. Featured Repository Section

    • Carousel berisi repository unggulan.
    • Large cover atau banner.
    • Nama produk.
    • Short description.
    • Kategori.
    • Developer.
    • CTA “Lihat Detail”.
    • Navigasi previous dan next.
    • Automatic slide opsional, default manual.
  3. Latest Repository Section

    • Menampilkan repository terbaru.
    • Product card grid.
    • Cover.
    • Title.
    • Category.
    • Developer.
    • Tombol atau tautan detail.
  4. Explore by Category

    • Menampilkan kategori produk digital.
    • Klik kategori membuka daftar repository yang sudah difilter.
  5. All Repository Section

    • Menampilkan produk digital yang telah dipublikasikan.
    • Pagination atau Load More.
    • Default sort berdasarkan tanggal publikasi terbaru.
  6. Footer

    • Nama organisasi/proyek.
    • Deskripsi singkat platform.
    • Copyright.
    • Navigation links.

Acceptance Criteria:

  • Homepage dapat dibuka tanpa login.
  • Featured repository tampil dari database.
  • Hanya repository published yang terlihat.
  • Card dapat diklik untuk membuka detail.
  • Layout berfungsi pada desktop dan mobile.
  • Tidak terdapat placeholder yang rusak ketika database masih kosong.

Route: /repositories

Halaman ini merupakan katalog utama seluruh produk digital.

Required Features:

  • Search input.
  • Filter category.
  • Sort latest.
  • Sort oldest.
  • Sort alphabetical A–Z dan Z–A.
  • Grid view.
  • Pagination.

Repository Card Information:

  • Cover image.
  • Repository title.
  • Category.
  • Developer.
  • Short description (truncated).
  • Detail navigation.

Filtering & Search Rules:

  • Pencarian berdasarkan title, short description, developer, dan tags.
  • Search case-insensitive.
  • Filter berdasarkan satu kategori pada MVP.
  • Search dan filter dapat digunakan bersamaan.
  • Parameter pencarian dan filter disimpan di URL query string.
  • Pagination default: 12 items per page.
  • Tidak boleh menampilkan draft.

Empty State: “Tidak ada repository yang ditemukan.”

Route: /repositories/[slug]

Halaman ini merupakan fitur utama aplikasi.

Design Reference: Steam Store Product Detail Page.

Menampilkan:

  • Breadcrumb navigation.
  • Product title.
  • Short description atau subtitle.

Menampilkan:

  • Main screenshot viewer.
  • Thumbnail screenshot gallery.
  • Product cover.
  • Navigasi antar screenshot.
  • Fullscreen image preview atau lightbox.

Gallery Requirements:

  • Mendukung minimal satu screenshot.
  • Mendukung banyak screenshot.
  • Klik thumbnail mengganti main image.
  • Gambar harus dioptimasi.
  • Mobile friendly.

Informasi:

  • Cover.
  • Title.
  • Short description.
  • Developer.
  • Category.
  • Release date (opsional).
  • Technology stack (opsional).
  • Tags.

Section heading: “Tentang Produk”

Konten:

  • Full overview.
  • Latar belakang produk.
  • Tujuan.
  • Fitur atau kemampuan produk.
  • Informasi tambahan.

Admin dapat menulis overview menggunakan rich text editor yang aman dengan dukungan:

  • Paragraph.
  • Heading.
  • Bold dan italic.
  • Bullet list.
  • Numbered list.
  • Links.

HTML yang dihasilkan harus disanitasi agar aman dari XSS.

Tampilkan tombol sesuai data yang tersedia:

Primary CTA: “Jelajahi Produk” / “Kunjungi Website”

Optional CTA: “Lihat Source Code”

Rules:

  • Tombol primary hanya muncul apabila product URL tersedia.
  • Tombol source code hanya muncul apabila source URL tersedia.
  • External links dibuka pada tab baru.
  • Gunakan rel=“noopener noreferrer”.
  • Produk tetap bisa dipublikasikan tanpa link eksternal jika hanya berupa dokumentasi karya.

Menampilkan:

  • Developer.
  • Category.
  • Technology Stack.
  • Release Date.
  • Last Updated.
  • Tags.

Menampilkan maksimal 4 repository dengan kategori sama.

Rules:

  • Tidak boleh menampilkan current repository.
  • Hanya published repositories.
  • Jika tidak ada produk terkait, section disembunyikan.

Acceptance Criteria:

  • Setiap repository published mempunyai URL detail sendiri.
  • Detail dapat diakses publik tanpa login.
  • Gallery berfungsi.
  • Overview ditampilkan dengan formatting yang benar.
  • CTA eksternal menggunakan URL dari database.
  • Halaman draft tidak dapat diakses publik.
  • Slug yang tidak ditemukan menghasilkan halaman 404.

Route: /categories/[slug]

Fitur:

  • Menampilkan nama kategori.
  • Deskripsi kategori (opsional).
  • Menampilkan seluruh published repository dalam kategori.
  • Pagination.
  • Navigasi kembali ke katalog.

Contoh kategori awal:

  • Web Application.
  • Mobile Application.
  • Software & Tools.
  • Information System.
  • Multimedia.
  • Others.

Kategori dapat disesuaikan di kemudian hari.

Fitur search publik harus:

  • Tersedia pada header.
  • Mengarahkan ke /repositories?q=keyword.
  • Menerima kata kunci melalui URL.
  • Menampilkan hasil relevan.
  • Menampilkan empty state apabila tidak ada hasil.

Search suggestions real-time tidak wajib untuk MVP.


Route: /admin/login

Fields:

  • Email.
  • Password.

Features:

  • Form validation.
  • Error message untuk kredensial tidak valid.
  • Loading state.
  • Login menggunakan session aman.
  • Redirect ke /admin setelah berhasil.
  • Redirect admin yang sudah login dari halaman login ke dashboard.

Security:

  • Login rate limiting.
  • Password hashing menggunakan Argon2id atau bcrypt dengan konfigurasi aman.
  • Generic authentication error.
  • CSRF protection sesuai mekanisme framework.
  • Jangan menampilkan informasi apakah email tertentu terdaftar.

Route: /admin

Components:

  • Admin sidebar.
  • Header dashboard.
  • Repository statistics.
  • Recent repository.
  • Quick action button.

Statistics:

  • Total repositories.
  • Published repositories.
  • Draft repositories.
  • Featured repositories.

Navigation:

  • Dashboard.
  • Repository.
  • Categories.
  • Logout.

Jangan menambahkan chart kompleks atau analytics eksternal pada MVP.

Route: /admin/repositories

Features:

  • Repository listing table.
  • Search repository.
  • Filter publication status.
  • Add repository.
  • Edit repository.
  • Delete repository.
  • Publish / Unpublish repository.
  • Mark / Unmark featured.

Table Columns:

  • Thumbnail.
  • Title.
  • Category.
  • Developer.
  • Status.
  • Featured.
  • Last Updated.
  • Actions.

Status:

  • DRAFT.
  • PUBLISHED.

Delete Requirements:

  • Confirmation dialog.
  • Hanya admin dapat menghapus.
  • Penghapusan database dan file terkait harus ditangani secara aman.
  • MVP boleh menggunakan soft delete agar tidak kehilangan data secara tidak sengaja.

Route: /admin/repositories/new

Ini merupakan fitur paling penting pada admin dashboard.

Form dibagi menjadi beberapa section.

Field Type Required
Product Title Text Yes
Slug Auto-generated editable text Yes
Short Description Textarea Yes
Category Select Yes
Tags Multi-value input No

Validation:

  • Title: 3–120 characters.
  • Slug: unique, lowercase kebab-case.
  • Short Description: 10–300 characters.
  • Category harus valid.
Field Type Required
Full Overview Rich Text Editor Yes
Key Features Repeatable text inputs No
Technology Stack Multi-value input No

Full Overview berisi deskripsi lengkap produk digital, mirip section “About This Game” pada Steam.

Field Type Required
Developer Name Text Yes
Developer Information Textarea No
Developer Website URL No

Developer dapat berupa individu atau kelompok.

Tidak memerlukan akun developer.

Developer hanya berupa metadata yang dimasukkan oleh admin.

Field Type Required
Product URL URL No
Source Code URL URL No
Demo URL URL No

Rules:

  • Hanya HTTPS atau HTTP URLs valid yang diterima untuk link eksternal.
  • Tolak javascript:, data:, file:, dan skema berbahaya.
  • Jangan menambahkan fitur automatic scraping atau preview dari sembarang URL pada MVP.
  • Link dapat berupa website, demo, GitHub, atau lokasi distribusi resmi.
Field Type Required
Product Cover Image Upload Yes for Publish
Banner Image Image Upload No
Product Screenshots Multiple Image Upload Yes, min. 1 for Publish

Media Rules:

  • Accepted formats: JPG, PNG, WebP.
  • Maximum upload size: 5 MB per image (configurable).
  • Maximum screenshot count: 10.
  • Recommended cover ratio: 16:9.
  • Recommended banner ratio: 16:9 or wider.
  • Image preview before submit.
  • Remove uploaded image.
  • Reorder screenshots.
  • Files disimpan di object storage, bukan di database dalam bentuk base64.
  • Validasi tipe file harus dilakukan di server berdasarkan signature/konten file, bukan hanya ekstensi.

Fields:

  • Status: Draft / Published.
  • Featured: Yes / No.
  • Release Date: Optional date.
  • Published At: Automatically assigned on first publish.

Actions:

  • Save as Draft.
  • Publish Repository.
  • Cancel.

Validation Rules:

  • Draft boleh disimpan dengan data belum lengkap.
  • Publish membutuhkan title, slug, short description, category, overview, developer name, cover, dan minimal satu screenshot.
  • Tampilan validasi harus jelas pada tiap field.
  • Setelah publish berhasil, tampilkan link menuju public detail page.

Route: /admin/repositories/[id]/edit

Requirements:

  • Menampilkan seluruh data repository.
  • Mendukung pembaruan semua field.
  • Mendukung penambahan dan penghapusan screenshot.
  • Mendukung perubahan status publikasi.
  • Validasi yang sama dengan form create.
  • Menampilkan pesan berhasil atau gagal.
  • Jangan menghapus data yang sudah ada jika upload baru gagal.

Route: /admin/categories

Fitur:

  • Melihat kategori.
  • Menambah kategori.
  • Mengubah nama dan deskripsi kategori.
  • Menghapus kategori apabila tidak digunakan.
  • Menampilkan jumlah repository per kategori.

Fields:

  • Name.
  • Slug.
  • Description (optional).

Constraints:

  • Name harus unik secara case-insensitive.
  • Slug harus unik.
  • Kategori yang masih digunakan tidak dapat dihapus sebelum repository dipindahkan ke kategori lain.

Public Routes:

Route Description Access
/ Homepage Public
/repositories Catalog Public
/repositories/[slug] Product Detail Public
/categories/[slug] Category Detail Public
/admin/login Admin Login Unauthenticated

Protected Admin Routes:

Route Description
/admin Dashboard
/admin/repositories Manage Repositories
/admin/repositories/new Add Repository
/admin/repositories/[id]/edit Edit Repository
/admin/categories Manage Categories

All admin routes except /admin/login require valid admin authentication.


Recommended Database: PostgreSQL
Recommended ORM: Prisma

Table: admins

Fields:

  • id: UUID, primary key.
  • name: VARCHAR(120).
  • email: VARCHAR(255), unique.
  • password_hash: TEXT.
  • created_at: TIMESTAMP.
  • updated_at: TIMESTAMP.

Only seed-created administrators can access the system.

Table: repositories

Fields:

  • id: UUID, primary key.
  • title: VARCHAR(120).
  • slug: VARCHAR(150), unique.
  • short_description: VARCHAR(300).
  • overview: TEXT.
  • developer_name: VARCHAR(160).
  • developer_description: TEXT, nullable.
  • developer_website: TEXT, nullable.
  • category_id: UUID, foreign key.
  • cover_url: TEXT, nullable.
  • banner_url: TEXT, nullable.
  • product_url: TEXT, nullable.
  • source_code_url: TEXT, nullable.
  • demo_url: TEXT, nullable.
  • tech_stack: JSONB or TEXT[].
  • tags: JSONB or TEXT[].
  • key_features: JSONB or TEXT[].
  • release_date: DATE, nullable.
  • status: ENUM(DRAFT, PUBLISHED).
  • is_featured: BOOLEAN, default false.
  • published_at: TIMESTAMP, nullable.
  • created_at: TIMESTAMP.
  • updated_at: TIMESTAMP.
  • deleted_at: TIMESTAMP, nullable.

Indexes:

  • Unique index pada slug.
  • Index pada status.
  • Index pada category_id.
  • Index pada published_at.
  • Index pada is_featured.
  • Search index yang sesuai untuk title, overview, developer, dan tags jika dibutuhkan.

Table: categories

Fields:

  • id: UUID, primary key.
  • name: VARCHAR(100).
  • slug: VARCHAR(120), unique.
  • description: TEXT, nullable.
  • created_at: TIMESTAMP.
  • updated_at: TIMESTAMP.

Table: repository_screenshots

Fields:

  • id: UUID, primary key.
  • repository_id: UUID, foreign key.
  • image_url: TEXT.
  • storage_key: TEXT.
  • alt_text: VARCHAR(255), nullable.
  • sort_order: INTEGER.
  • created_at: TIMESTAMP.

Relationships:

  • One Category has many Repositories.
  • One Repository has many Screenshots.
  • One Repository belongs to one Category.

Untuk cover dan banner, simpan storage key selain public URL bila diperlukan agar penghapusan atau penggantian asset dapat dikelola dengan benar.

Storage keys harus dihasilkan server-side.

Jangan menyimpan kredensial object storage pada client.

Requirements:

  • Gunakan Prisma migrations.
  • Sediakan database seed script.
  • Seed awal berisi kategori dasar.
  • Seed admin menggunakan environment variables.
  • Seed demo repositories hanya untuk development.
  • Tidak boleh menggunakan data palsu sebagai konten produksi.

Frontend:

  • Next.js App Router.
  • React.
  • TypeScript.
  • Tailwind CSS.
  • shadcn/ui.
  • Lucide Icons.

Backend:

  • Next.js Route Handlers atau Server Actions.
  • Zod untuk input validation.
  • Prisma ORM.

Database:

  • PostgreSQL.

Authentication:

  • Auth.js menggunakan Credentials Provider.
  • Admin-only authentication.
  • Secure session cookies.

Media Storage:

  • S3-compatible object storage.
  • Contoh provider: Cloudflare R2 atau AWS S3.
  • Sediakan adapter yang mudah dikonfigurasi melalui environment variables.

Optional UI Libraries:

  • Embla Carousel untuk featured repository.
  • React Hook Form untuk admin forms.
  • Tiptap untuk rich text editor.
  • Sonner untuk toast notifications.

Gunakan versi stable yang saling kompatibel ketika implementasi dilakukan.

  • Single full-stack application.
  • Modular components.
  • Strong TypeScript typing.
  • Reusable UI components.
  • Server-side input validation.
  • Separation between public and admin functionality.
  • Environment-based configuration.
  • No unnecessary microservices.
  • No separate frontend/backend repositories untuk MVP.

app/

  • (public)/
    • page.tsx
    • repositories/
    • categories/
  • admin/
    • login/
    • repositories/
    • categories/
  • api/
    • auth/
    • uploads/

components/

  • layout/
  • repository/
  • admin/
  • ui/

lib/

  • auth/
  • db/
  • repositories/
  • storage/
  • validations/

prisma/

  • schema.prisma
  • seed.ts
  • migrations/

public/

  • images/
  • branding/

tests/

  • unit/
  • integration/
  • e2e/

Server harus bertanggung jawab terhadap:

  • Database queries.
  • Authentication.
  • Authorization.
  • Validation.
  • Repository CRUD.
  • Upload authorization.
  • Signed storage operations.
  • Publication state enforcement.

Client hanya mengelola presentasi, interaksi, dan pengiriman input.


Gunakan Server Actions untuk mutasi admin apabila paling sesuai dengan Next.js App Router, atau Route Handlers untuk endpoint eksplisit.

Kontrak operasi minimum:

Public:

  • listPublishedRepositories(query, category, sort, page).
  • getPublishedRepositoryBySlug(slug).
  • listFeaturedRepositories().
  • listCategories().
  • getRelatedRepositories(repositoryId, categoryId).

Admin:

  • getAdminRepositoryList().
  • getAdminRepositoryById(id).
  • createRepository(payload).
  • updateRepository(id, payload).
  • deleteRepository(id).
  • updatePublicationStatus(id, status).
  • updateFeaturedStatus(id, featured).
  • createCategory(payload).
  • updateCategory(id, payload).
  • deleteCategory(id).
  • uploadRepositoryImage(file).
  • removeRepositoryImage(storageKey).

Requirements:

  • All mutations are authenticated and authorized server-side.
  • Validate input using Zod.
  • Public queries always filter published and non-deleted records.
  • Handle errors with consistent responses.
  • Prevent unauthorized access to drafts.
  • Uploaded file ownership and storage keys must be checked before deletion.

  • Secure password hashing.
  • No hardcoded production credentials.
  • No default admin credentials in production.
  • HTTP-only secure session cookies.
  • Session expiry.
  • Logout invalidates session.
  • Login rate limiting.
  • Validate admin session on every protected operation.
  • Do not rely only on route middleware.
  • Check authorization within server actions or handlers.
  • Never expose admin-only data through public endpoints.
  • Validate all fields server-side.
  • Sanitize rich text output.
  • Prevent stored XSS.
  • Validate external URL protocols.
  • Prevent unsafe file uploads.
  • Escape or sanitize rendered metadata.
  • Enforce size limits.
  • Validate file signatures.
  • Use generated filenames or storage keys.
  • Reject unsupported file types.
  • Do not accept arbitrary executable uploads.
  • Avoid untrusted SVG upload during MVP.
  • Keep secrets in environment variables.
  • Do not commit .env files.
  • Use HTTPS in production.
  • Enable appropriate security headers.
  • Avoid leaking stack traces to visitors.
  • Protect admin endpoints from brute-force attacks.

Setiap public repository harus mempunyai:

  • Unique title.
  • Meta description.
  • Canonical URL.
  • Open Graph title.
  • Open Graph image.
  • Semantic heading structure.
  • Descriptive image alt text.

Additional Requirements:

  • Generate sitemap.xml.
  • Generate robots.txt.
  • Exclude admin routes from search engine indexing.
  • Do not expose draft repository in sitemap.
  • Server-render meaningful repository metadata.
  • Provide useful 404 page.

Target:

  • Lighthouse Performance target >= 90 pada production build dengan data dan hosting representatif.
  • Lighthouse Accessibility target >= 90.
  • LCP target <= 2.5 seconds pada kondisi pengujian yang sesuai.
  • CLS target <= 0.1.
  • INP target <= 200ms.

Strategies:

  • Next.js Image optimization.
  • Lazy loading.
  • Proper image dimensions.
  • Pagination.
  • Database indexes.
  • Limit large client components.
  • Server rendering for public pages.
  • Cache and revalidate public content after admin changes.

Requirements:

  • Mobile first.
  • Responsive layout.
  • No broken image layout.
  • Useful loading states.
  • No unnecessary client-side API waterfall.

Performance values are engineering targets, not guarantees.


  1. Admin visits /admin/login.
  2. Admin enters email and password.
  3. System validates credentials.
  4. System establishes secure session.
  5. Admin is redirected to dashboard.
  1. Admin opens dashboard.
  2. Admin clicks “Tambah Repository”.
  3. Admin fills in Basic Information.
  4. Admin fills in Product Overview.
  5. Admin adds Developer Information.
  6. Admin adds Product Links.
  7. Admin uploads cover and screenshots.
  8. Admin selects publication settings.
  9. Admin clicks Save Draft or Publish.
  10. Server validates fields.
  11. Data is persisted to PostgreSQL.
  12. Uploaded media is associated with the repository.
  13. Public cache is revalidated.
  14. Admin receives success confirmation.
  15. Published repository appears in the public catalog.
  1. Admin selects repository.
  2. Admin opens edit page.
  3. Admin updates necessary fields.
  4. Admin saves changes.
  5. System validates and persists changes.
  6. Updated content appears on public website.
  1. Admin selects repository.
  2. Admin clicks delete.
  3. System shows confirmation.
  4. Admin confirms deletion.
  5. Repository is soft-deleted.
  6. Repository disappears from public catalog.
  7. Associated media is retained or cleaned up according to a documented retention policy.

  1. Visitor opens homepage.
  2. Visitor browses featured repositories.
  3. Visitor clicks one repository.
  4. Visitor reads the detail page.
  5. Visitor views screenshots.
  6. Visitor clicks “Kunjungi Website” if available.
  1. Visitor enters a search keyword.
  2. System opens catalog with keyword filter.
  3. Visitor views matching repositories.
  4. Visitor selects a repository.
  5. Visitor opens its detail page.
  1. Visitor selects a category.
  2. System displays matching repositories.
  3. Visitor chooses a product.
  4. System opens its overview page.

Required Public Components:

  • PublicHeader.
  • PublicFooter.
  • GlobalSearch.
  • FeaturedCarousel.
  • RepositoryCard.
  • RepositoryGrid.
  • CategoryCard.
  • CategoryFilter.
  • RepositoryGallery.
  • RepositoryInfoSidebar.
  • RepositoryOverview.
  • ProductAccessButtons.
  • RelatedRepositories.
  • EmptyState.
  • SkeletonCard.

Required Admin Components:

  • AdminSidebar.
  • AdminHeader.
  • StatsCard.
  • RepositoryTable.
  • RepositoryForm.
  • CategoryForm.
  • RichTextEditor.
  • ImageUploader.
  • ScreenshotManager.
  • PublicationStatusBadge.
  • ConfirmDeleteDialog.
  • FormErrorMessage.

All components should be reusable and strongly typed.


  • Public homepage.
  • Featured carousel.
  • Public repository catalog.
  • Repository detail page.
  • Search.
  • Category filter.
  • Admin login/logout.
  • Protected dashboard.
  • Add repository.
  • Edit repository.
  • Delete repository.
  • Draft/published status.
  • Image uploads.
  • Featured repository management.
  • Database persistence.
  • Responsive UI.
  • Basic SEO.
  • Basic security.
  • Advanced search suggestions.
  • More elaborate hover previews.
  • Screenshot fullscreen improvements.
  • Additional sorting and filtering.
  • Better admin bulk operations.
  • Developer-specific public catalog pages.
  • Repository statistics.
  • Download counters (only where applicable).
  • Structured developer profiles.
  • Advanced tagging.
  • More sophisticated discovery recommendations.
  • Content moderation workflow if multiple admins are introduced.
  • Multi-language support.

Do not implement P1 and P2 before P0 is stable.


The following features are explicitly out of scope:

  • Public user registration.
  • Public user authentication.
  • Member profiles.
  • User dashboard.
  • Checkout.
  • Shopping cart.
  • Payment gateway.
  • Product purchases.
  • User reviews.
  • User ratings.
  • Wishlist.
  • Community forum.
  • User comments.
  • Social networking.
  • Chat system.
  • Direct messaging.
  • Developer self-service registration.
  • Automated product submission by public visitors.
  • Git hosting.
  • Package distribution system.
  • Marketplace functionality.

These must not be implemented unless explicitly requested.


Tasks:

  • Review the existing project.
  • Preserve usable existing setup and code.
  • Finalize chosen stack.
  • Configure database.
  • Configure Prisma.
  • Create database schema.
  • Create migrations.
  • Configure environment variables.
  • Create category seeds.
  • Create admin seed process.

Deliverable: Working application connected to PostgreSQL with database migrations.

Tasks:

  • Implement global design tokens.
  • Build Steam-inspired public header.
  • Build homepage layout.
  • Build featured carousel.
  • Build repository cards.
  • Build catalog page.
  • Build category page.
  • Build repository detail page.
  • Ensure responsive behavior.

Deliverable: Complete functional public UI with demo data.

Tasks:

  • Configure Auth.js.
  • Build admin login.
  • Protect admin routes.
  • Build dashboard.
  • Build repository management interface.
  • Build category management interface.

Deliverable: Admin can securely log in and navigate dashboard.

Tasks:

  • Implement create repository.
  • Implement edit repository.
  • Implement deletion.
  • Implement draft/publish.
  • Implement image upload.
  • Implement screenshot ordering.
  • Implement featured repository.
  • Connect admin data to public pages.

Deliverable: Admin can publish real repository content without manual code changes.

Tasks:

  • Validate forms.
  • Test public access.
  • Test admin authorization.
  • Test image uploads.
  • Test responsive UI.
  • Test search and filters.
  • Implement SEO.
  • Optimize performance.
  • Prepare production environment.
  • Write deployment guide.

Deliverable: Application ready for deployment.


  • Visitor opens homepage without login.
  • Visitor sees published repositories only.
  • Visitor can search repositories.
  • Visitor can filter by category.
  • Visitor can open repository details.
  • Visitor can navigate screenshots.
  • Visitor can open external product links.
  • Visitor cannot access drafts.
  • Visitor cannot access protected admin routes.
  • Valid admin can login.
  • Invalid credentials are rejected.
  • Unauthenticated users cannot perform admin mutations.
  • Admin can create a draft.
  • Admin can publish a complete repository.
  • Incomplete repository cannot be published.
  • Admin can edit repository metadata.
  • Admin can upload images.
  • Admin can reorder screenshots.
  • Admin can change featured status.
  • Admin can unpublish repository.
  • Admin can delete repository after confirmation.
  • Admin can logout.
  • Non-admin users cannot invoke protected operations.
  • Invalid file types are rejected.
  • Oversized image uploads are rejected.
  • Unsafe rich text is sanitized.
  • Unsafe external URLs are rejected.
  • Unpublished repositories cannot be retrieved from public queries.
  • Secrets are not exposed to client bundles.

The MVP is considered complete when:

  1. Public users can navigate the website without creating accounts.
  2. The design has a Steam-inspired visual experience.
  3. The homepage features dynamic repository content.
  4. Every published repository has a detailed product overview page.
  5. The repository gallery works correctly.
  6. Search and category browsing work.
  7. Admin login is secure and functional.
  8. Admin can create, update, publish, and remove repositories.
  9. Images are stored and displayed properly.
  10. All public content comes from persistent database records.
  11. The application works on mobile and desktop.
  12. Authorization is enforced on the server.
  13. The application passes its core functional and security tests.
  14. The production build succeeds.
  15. Environment setup and deployment instructions are documented.

21. IMPLEMENTATION GUIDELINES FOR AI CODING AGENT

Section titled “21. IMPLEMENTATION GUIDELINES FOR AI CODING AGENT”

Important implementation rules:

  1. Treat this PRD as the source of truth.
  2. Do not introduce features outside the defined scope.
  3. This is a public repository catalog, not an e-commerce application.
  4. Public visitors must never be required to login.
  5. Only administrators may manage repository content.
  6. The design must closely follow Steam Store’s visual patterns while using original branding and assets.
  7. Prioritize repository detail pages and content management.
  8. Build real database-backed functionality, not a static UI-only prototype.
  9. Avoid unnecessary architectural complexity.
  10. Follow existing project structure when technically reasonable.
  11. Do not overwrite already completed environment setup without reason.
  12. Use modular, maintainable components.
  13. Add loading, empty, error, and success states.
  14. Use safe defaults for security.
  15. Document all environment variables.
  16. Never claim a feature is complete without verifying it.
  17. Run production build and relevant tests after implementation.
  18. Use realistic sample repositories for development, clearly marked as demo data.
  19. Generate a README containing setup, migration, seed, development, and deployment instructions.
  20. Finish the P0 features before adding enhancements.

For the initial release, success is evaluated by:

  • Admin can publish a complete repository through the dashboard without editing source code.
  • Published repository appears in the public catalog.
  • Each repository has a functional detail page.
  • Visitor can locate repository through search and categories.
  • No public account is required.
  • No unauthorized admin mutation is possible.
  • Core user journeys pass end-to-end testing.
  • Production application builds and runs successfully.

Product success can later be evaluated using:

  • Number of published repositories.
  • Number of repository detail visits.
  • Product link click-throughs.
  • Search success rate.

Analytics instrumentation is not required for MVP.


END OF PRD — SOEDIRMAN DIGITAL REPOSITORY V1.0