Product and engineering records

Built to make
the next step clearer.

Two applications I built and documented from their implemented source. Each begins with a real workflow — finding what to study, or keeping installment plans and payments in order — then follows the engineering decisions that made it work. The interface captures are evidence of those decisions, not the argument.

PROJECT RECORD01 / 02

Personal learning workspace / Django

StudyOS

A nursing study library is more useful when it becomes a place you can navigate, search, and return to.

MY ROLE Built and documented the application · CONTEXT Personal study tool

STUDY WORKFLOW SUBJECTUNITMATERIAL LECTURESOURCESNOTES
Conceptual map of implemented study and lecture workflows.

Study material needed a working surface.

I built StudyOS for my own nursing coursework. The material already existed as a subject and file library; the gap was a working surface for browsing it on a laptop or phone on the same local network, and a place to keep notes and study activity alongside it.

A catalog, a reader, and a study layer.

The Django site turns the library into a browsable catalog: subjects and units, search across file and subject names, and document streaming for reading. Around that catalog sit the study tools: notes, bookmarks, progress, a study calendar, session records, and lecture workspaces that collect sources and mind maps.

  • Browse subjects, units, and library files
  • Search by file or subject name, then open the document
  • Keep notes, bookmarks, progress, and session history
  • Group related material into lecture and topic workspaces

Keep the source library read-only. Own only the study layer.

The website imports a catalog snapshot into its own SQLite database. Original study files remain read-only in their existing location; the site streams them rather than copying them into the database. That boundary keeps notes, progress, and bookmarks in the application while the documents stay in their existing library.

It is a deliberate trade-off: the application owns navigation and study state, not the files themselves.

IMPLEMENTATION Django · server-rendered HTML · SQLite · local-first file access

Captured from the working application.

These are actual screens from StudyOS, populated with fictional sample data for the portfolio. They document the browsing and study surfaces described above; the point is the workflow and the catalog boundary behind them, not the surface styling.

Actual StudyOS captures with fictional sample subjects and study records. No private study material is shown.
PROJECT RECORD02 / 02

Business operations / Django 5.2 / Arabic RTL

Installment Management System

An installment contract creates a chain of work: define the terms, track each due date, record what was paid, and understand what remains.

MY ROLE Built and documented the application · CONTEXT Installment-based business records

CONTRACT LIFECYCLE TERMSSCHEDULEPAYMENTS due amountdated rowspartial collections
Conceptual map based on the system's contract and payment records.

Keep related records connected.

I built a Django application for organizing installment-based business records. Customers, suppliers, products, purchases, expenses, contracts, installments, and payments are represented as related parts of the same working system. The design problem is keeping what is scheduled separate from what has actually been collected.

Set the terms, generate the schedule, record each collection.

A contract can be calculated in three ways: derive the rate from an agreed installment and term, derive the installment from the rate and term, or use the configured monthly rate with the term. The resulting contract gets a dated installment schedule. Each collection is stored as its own payment record with its date, method, and receiver, rather than overwriting the scheduled amount.

  • Customer, supplier, product, and purchase records
  • Contract calculations and generated due dates
  • Installment status and separately recorded payments
  • Dashboards and overdue, profit, monthly, investment, and customer reports

Preserve the difference between a due amount and a payment.

Installments hold the amount expected on a schedule; payment rows hold individual collection events. That distinction makes partial collections, payment methods, and receiver attribution visible without treating a scheduled amount as money already received. Decimal-based calculation helpers handle the three plan modes, and inputs are validated before the schedule is created.

IMPLEMENTATION Django 5.2 · Python · server-rendered HTML · Arabic RTL

Captured from the working application.

These are actual screens from the Arabic RTL application with fictional sample records. They show the dashboard and contract list as implemented; no customer or business data is included. The engineering claim rests on the contract, schedule, and payment model described above, not on the surface styling.

Actual installment-system captures with fictional sample records; no customer or business data is shown.

Return to the portfolio