← The CredPal work03 / CREDPAL · CONTRIBUTION

A catalogue helps the customer choose.

Make relevant content easier to find and revisit.

Where this work fits

A meal-plan template still needs dates, recipes, and progress before a customer can follow it. People also need to find suitable content, save choices, and turn ingredients into a shopping list.

MY CONTRIBUTION

I built recipe discovery with filtering, ordering, and saved-state support. The purpose was to help a customer narrow a catalogue to useful content rather than simply expose a large list of records.

THE IDEA, ILLUSTRATED

Find the records that need attention

CATALOGUE FILTERING · A SMALLER, USEFUL VIEW

ProductQty.Status

Desk lampIn Stock

12Published

Reading lampLimited Stock

4Draft

Floor lampPre-Order

0Published

3 of 3 products

Filters combine: choose a status and an exact name to narrow the records. The backend also supports category and item-type filters.

THE ENGINEERING DECISION

Share the content, keep progress personal.

The original plan and a customer’s copy had different jobs. I modeled personal dates and completion separately, checked membership for premium activation, and handled conflicts such as placing two meals in the same slot. Catalogue filters helped narrow the recipes people could choose from.

The skills behind the work

Query filtering: Narrow records to the information a person is trying to find.
SQL: Query and update relational data, with clear rules about which records a result represents.
Data modeling: Give different product concepts clear records and relationships so updates have predictable meaning.

THE WIDER RESULT

Membership gave customers a plan they could start and follow, with saved choices and progress. Recipe ingredients could become a reusable shopping checklist.

READ THIS IN CONTEXTI turned reusable meal plans into personal schedules. →

Related contributions

Expert guidance becomes a personal calendarI built backend workflows connecting expert-created plans with customer schedules. Shared content and personal dates or progress needed separate responsibilities so customers could use a plan without changing its reusable source.Meals become a schedule people can followI built personal planning features around calendars, progress, and membership. This translated access into something useful day to day, while keeping plan entries and customer state coherent.A shared recipe keeps its referral contextI built referral-link features that kept useful sharing context connected to the destination. The integration had to preserve where a person was going as well as the context of the referral.From an ingredient to a checked shopping listI built shopping-list operations and checked-item state for customers. Ownership checks kept actions scoped to the correct list, and reversible state let an item move between active use and history.