SahrulRamadhani29/portfolio
Find a project.../
Projects/JokiIT.Online

JokiIT.Online

Private sourceIn development

An IT service order platform covering briefs, negotiation, invoices, assignments, delivery, and revisions.

SoloBackend domain/contracts, private files, workers, authentication, and public/auth/order frontend
Private source code

My contribution highlights

Read all 8 contribution modules
Contents · 8 contribution modules

Main workflow

6 steps

Domain workflows connect briefs, quotes, work, and revisions. Backend capabilities are distinguished from interfaces and providers still in development.

  1. 01Submit work requirements

    1. Create an order and brief

      Customer

    2. Validate private attachments

      File API & worker

  2. 02Review scope and quote

    1. Review, quote, and invoice

      Backend · admin

    2. Manage payment attempts

      Payment provider abstraction

  3. 03Deliver and review work

    1. Assignment and delivery

      Backend · internal team

    2. Accept or request revisions

      Customer & revision handlers
Process details & branches

  1. Create an order and briefCustomer

    Customers sign in, describe their service needs, and follow orders through customer pages.

  2. Validate private attachmentsFile API & worker

    Upload intents, finalisation, file inspection, and access checks connect attachments to orders without automatically making them public.

  3. Review, quote, and invoiceBackend · admin

    Backend handlers manage brief review, quotes, invoices, and scope changes. The admin interface is not yet fully complete.

  4. Manage payment attemptsPayment provider abstraction

    The backend provides statuses, receipts, and reconciliation; the gateway remains UNCONFIGURED in this snapshot.

    Is the provider ready?

    • Not configured · this snapshot. Payment cannot yet be presented as a successful production checkout.
    • If configured later. The integration needs verification before real payment workflows can proceed.

  5. Assignment and deliveryBackend · internal team

    Domain modules support worker assignments, result publication, background notifications, and order status change records.

  6. Accept or request revisionsCustomer & revision handlers

    The backend supports result acceptance, revision requests, and revision decisions under order rules.

    What is the decision?

    • Accepted. Acceptance is recorded in the order workflow.
    • Revision. The request is reviewed and work continues through the revision workflow.

Admin/operations frontend is still being developed; the payment gateway is UNCONFIGURED. Backend modules already cover quotes, delivery, and revisions.

CASE_STUDY.mdProduct & my contributions

About JokiIT.Online

JokiIT.Online is an IT service ordering platform connecting customer briefs, private attachments, quotes, invoices, internal work, delivery, and revisions. Customers have pages to submit and follow orders, while backend modules manage status changes and operational processes.

I have progressively worked on specifications, backend, API contracts, workers, authentication, and frontend. Public, auth, and customer order pages have been built; admin/operations interfaces remain in development and the payment gateway has not been configured.

My contributions

Domain modules and API contracts

I separated order, identity, file, payment, and deliverable rules into domain modules. I designed OpenAPI, types/DTOs, and Zod validation to connect requests, responses, and errors across client and server. Status transitions, idempotency keys, and audit events are used for processes that may involve repeated actions.

Database, authentication, and access control

I developed PostgreSQL schemas/migrations through Prisma, local authentication, Auth.js/NextAuth sessions, Argon2 password hashing, and user profiles. I added access checks to account and order operations. I also worked on nonce-based CSP and mutation restrictions across application paths.

Private file uploads and downloads

I built upload intents, finalisation, file metadata, declaration/content inspection, checksums, and download permissions. An S3 object storage adapter connects storage to order processes. Access controls and account relationships determine when brief files or deliverables can be read through the available workflows.

Workers and background delivery recovery

I built pg-boss workers for scan queues, notifications/emails, reconciliation, expiry, and cleanup. I worked on an outbox with statuses, leases, and recovery so interrupted delivery jobs can be followed up by background processes while remaining connected to application status changes.

Review, quotes, and the delivery lifecycle

I developed order review handlers, quotes/invoices, worker assignments, and delivery publication. I also built result acceptance, revision requests and decisions, scope change proposals, cancellations, and refunds. These modules connect customer and internal actions with the order’s status rules.

Payment abstraction and reconciliation

I built provider boundaries, payment attempts, receipts, and amount/status exception handling. Reconciliation connects to order status and cancellations/refunds. The gateway remains UNCONFIGURED, so provider integration is a subsequent development step before real payments can be used.

Public frontend, authentication, and customer dashboard

I built public pages, the service catalogue, policies, sign-in/registration, profiles, customer dashboards, and order details. I connected interfaces to backend contracts and private attachment access. Frontend development continues progressively into review, quote, and admin operations needs.

Tests, backups, and runbooks

I wrote Vitest unit/integration tests, contract/HTTP checks, and Playwright E2E tests for backend workflows and access. I also prepared backup/restore tools and runbooks so maintenance and recovery procedures have steps to follow during development or operation.

Fields & core technologies

Project fields

Backend & APIFull-stack WebData & DatabasesSoftware Quality

Core technologies

Next.jsTypeScriptPostgreSQLPrismapg-bossOpenAPIVitestPlaywright

5 commits in the last 12 months

All branches
NovDecJanFebMarAprMayJunJulAugSeptOctNov
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Hover over a square or focus it to see the date.
LessMore
Current streak0 days
Longest streak in this period2 days
Active days in this period5 days
Verified data · updates scheduled hourly.
How it is counted · 1 repo · 1 branch

My authored commits reachable from all remote branches at sync time. Each SHA is counted once, even across branches or forks. Merge commits are excluded. Dates use the author timestamp in Western Indonesia Time (UTC+7), rather than push time. The current streak remains active when the last commit was yesterday and today is still in progress.

This calendar covers commits across all branches. Its totals may differ from GitHub’s contribution calendar, which includes other activity types and follows its own branch rules. This calendar covers only the project you are viewing.

Contribution history

5 of my non-merge commits · All branches · Data as of 3 November 2026.

Back to all projects