← The CredPal work03 / CREDPAL · CONTRIBUTION

Expert guidance becomes a personal calendar.

Turn guidance into a plan someone can use.

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 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.

THE IDEA, ILLUSTRATED

Turn a plan into a usable calendar

REUSABLE GUIDANCE → A PERSONAL CALENDAR
NUTRITIONIST PLAN

A balanced week.

Meals + timing
Nutritional totals
Premium access check

9:41•••
MEMBERSHIP

Your calendar

Activate a plan to create dated meal slots.

A plan is more than access: it gives the customer something practical to follow.
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

Data modeling
Give different product concepts clear records and relationships so updates have predictable meaning.
SQL
Query and update relational data, with clear rules about which records a result represents.
Access control
Check which actions and resources an authenticated account is allowed to use.
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 contributionsMeals 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 catalogue helps the customer chooseI 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.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.