Recent changes

• Fixed a failure in the CI/CD pipeline commit
• Implemented status tracking for balance events and refined the underlying thread logic associated with them commit
• Refactored the token rendering component for render_encoded to allow {{design: design.id}} making a pill, to improve display fidelity and added an edit functionality for devlog entries commit
• Integrated support for uploading images directly within the devlog interface and established links to corresponding Hackatime projects commit

Added Devlogs and changed hackatime projects to be multi model per design.

Move hackatime project linkage from a single designs.hackatime_project column to a has_many hackatime_projects model, syncing each project’s time and aggregating totals on designs. Add devlogs, ship_requests, ships, and comments models/routes/views for design logging and shipping, and make balance_events polymorphic.Update designs controller, helpers, and views to render multiple project pills, allow adding/removing linked projects, and show a combined hackatime/image/devlog layout. Add redcarpet for Markdown rendering and adjust CSS for dark mode, responsive galleries, and pill controls.

Added Devlogs and the prep for adding the shipping flow
I added devlogs to the project in prep for the shipping flow

Recent changes

• Added support for balance events and thread adjustments to improve financial tracking accuracy. This also included an update to the notification rendering system to safely handle these new data types without breaking existing templates (commit: (faed39b57619)).
• Fixed the positioning of the design box within the product editor. This specifically addresses display issues occurring when editing products via /admin/products/<id>/edit (commit: (aa4e314b5dcd)).

I’ve focused on refining the shop page styling, header positioning, and cost handling logic (d10a9c51). The recent batch of work involved schema adjustments for a product enabled flag, adding support for cost and thread costs (82f9f2d1), applying a schema fix (3f8bcb8a), fixing CI pipeline issues (71e98a), and pushing updates to production (ca19da29).

Recent changes

• Added an image variants system and updated views to utilize thumb and display variants specifically (a2e4eb28).
• Implemented cost handling updates, including a specific support for thread costs alongside general product cost tracking (82f9f2d1).
• Added an auto annotaterb script executed within the Rails migration process (7d07d278).
• Applied schema fixes to ensure data integrity during the recent updates (3f8bcb8a).
• Updated the RSVP page styles and refreshed the thanks template (217945eb).
• Refined header positioning and shop page styling across the frontend (d10a9c51).
• Added a product enabled flag to control product visibility and state in the system (82f9f2d1).

Whats next:

Umm, so whats next I think would be adding balance_events so you can trace changes in balances(spending/earning)

Since the last update, I’ve focused on enhancing the order preview system to support complex design workflows and improving image navigation for multi-image configurations.

Recent changes

• Added multi-image preview navigation with left/right arrow buttons and an index display (e.g., “Image 2 of 5”) to streamline design review workflows (b269fe5). This change directly addresses the need to review multiple design iterations in a single view without page reloads.
• Refactored the order preview component to support multiple print areas with independently configurable design images. This involved restructuring the preview logic to handle dynamic print area definitions while maintaining consistent state across design selections (0545118). The refactor enables customers to visualize different designs on separate print areas (e.g., front/back/ sleeves) within the same order preview.

1. Print area management UI & backend (a42a00d):

   • Built a full stack for managing print areas (think “where the design goes” on a shirt front or back). This includes models to store print area dimensions, controllers to handle CRUD ops, and RESTful routes to tie it all together.
   • The frontend now lets users drag/drop to define print zones with responsive positioning (position: absolute + transform: scale to handle dynamic sizing).
   • Edge case: Products with multiple print areas (e.g., front + back) now render distinct configurations without clobbering state.

2. Printful service & stock syncing (7b5d817):

   • Added printful_id to product models to map Issued products to Printful’s inventory.
   • UI updates to display Printful sync status (green checkmarks for success, red alerts for failures).

Technical tangents

The print area system was a slow make. For example:

• To ensure designs stay within printable bounds, I had to calculate dynamic margins based on product type (e.g., a hoodie’s print area ≠ a mug’s). This involved hacking some trigonometry into the frontend to snap selections to “safe zones.”
• On the backend, I’m using ActiveRecord callbacks to validate print area dimensions against product specs. If a user tries to set a print area wider than the product allows It raises a PrintAreaOutOfBounds error

Future features

The actual ship flow and being able to edit multiple print areas instead of just the one

Added Variants for size and colors with stock for each printful region facility.
Stimulus target which groups the variants by colour and deletes empty groups

Removed buggy pill_spin.js and used clunky animation pauses improved readme contents

Restyled the site with different colour pallete

adjusted layout for section 1

added drop shadow to the pfp image on hover

removed a few dashed borders - replace some with solid border too!!

Created Printful API Integration and improved order screen to allow better customisations

Add Printful import endpoint and order preview UI improvementsImplemented Printful product import, added order preview generation, UI styles, and controller changes for drag‑resize‑rotate preview.

Made the whole site with 3 sections:

• The bit about me
• Language pill
• And projects

This has taught me how to use api request with js and how coding in html+erb has hindered some of those abilities and remembering how to link scripts and stylesheets

Metroid Mania Devlog

Key Milestones & Features

• Username System & Legal Compliance: Added user username tracking, NDA setting to prevent address viewing, and an admin overlay displaying legal info(name) (eacd088). This enhances user pii protection by requiring a separate proccess to be done too.
• Dynamic Order Page: Refactored the order page into a single, dynamic form that adds/removes elements as needed (0e820f2), simplifying user interaction and reducing UI complexity.
• Encapsulated Connection Logic: Made the connection method a private instance method (0e86db0), improving code modularity and reducing unintended side effects.
• Admin System Overhaul: Removed environment-based superadmin detection (8dc2094), streamlining admin permissions for better security and maintainability.
  ** Current Main Focus **
  To ensure user data is safe and leaning more on hca for sensitive info (legal_names, phone_number, and addresses)

Whole lot of reading api docs whilst coding:

Removed Addresses from database to use access tokens to fetch from hackclub auth to maintain more up to date info and remove address pii from local database

Improved styling and added demo link so adding to unified db is easier (all data is on site)

Devlog: Admin Approved Time Override## SummaryAdded approved_seconds to Ship model, allowing admins to approve a different duration than what was devlogged lets the ysws stay in a budget by removing charm_notches for time that won’t contribute to budget. This enables scenarios where a user logs 4h but admin only approves 2h for credit/charm calculations.## Changes### Database- Added approved_seconds integer column to ships table (defaults to devlogged_seconds if not explicitly set)### Models- Ship: New approved_seconds attribute with default, set_approved_seconds callback (copies from devlogged_seconds on create), and recalculate_charm_notches! method for manual sync- Project: ship_and_award_credits! now uses approved_seconds for credit/notch calculation; removed ship_total_notches validation- ShipRequest: approve! accepts and passes approved_seconds; reject! now destroys associated charm notches- User: reconcile_charm_notches! uses approved_seconds instead of devlogged_seconds for carryover calculations### Controllers- Admin ProjectsController: Pass approved_seconds param through approve/ship/force_ship actions- Admin ShipRequestsController: Pass approved_seconds param through approve action### Views- Ship request approval form: Added “Approved Time” field (number input, max = devlogged_seconds)- Ship cards: Display “Approved Hours” alongside devlogged hours### Tests- Comprehensive coverage for: - approved_seconds determining notch awards - Devlogged seconds copied to approved seconds when not set - Explicit approved_seconds overriding devlogged_seconds - Carryover hours across multiple ships - Multiplier application on approved_seconds - recalculate_charm_notches! syncing, removing excess, preserving admin_granted - reject! destroying charm notches (owner and recipient) - Controller test: approve respects approved_seconds for notch calculation## Backward CompatibilityThe set_approved_seconds callback defaults to devlogged_seconds when not explicitly set, so existing ships and flows without the new param continue working unchanged.

Add sessions association and related methods, update tests and models- Added has_many :sessions with dependent destroy to User

• Added del_sessions method and invoked in destroy
• Updated test suites (created a buncha them) and model validations for sessions, addresses, admin actions, and other features

Added base_cost to product for better checkout workflow
Fixed issue where you couldn’t get free charm (if charm was set to free it wouldn’t let you redeem it)
Fixed product delete and added force delete button
Refactor prize order deletion to clear charm slot FK references
Refactor charm slot reuse, add Redis service and DB name updatesRename Postgres DB to metroid_mania_test, add Redis container, adjust environment variables, refactor Order model to reuse existing empty charm slots with capacity limits, simplify loadout view logic, and add tests for slot reuse and header loadout.
Fix Guide Styling

• Enhanced UI & UX: The like button system now uses a new .btn-retro-noanim class for buttons that you want styled without the hover bob animation, ensuring visual consistency while reducing unnecessary animations commit. A major refactor extracted a reusable button partial and improved flash UI feedback for like/unlike actions, streamlining code and user experience commit.
• Simplified Admin Flows:
  Removed redundant User.credits and corrected logic error in views/devlogs/_ships.html.erb
  Currency recalculation logic was streamlined to reduce redundancy, with UI updates synchronized across admin sections for reliability and performance commit.
• Backend Normalization: Repository URLs are now consistently formatted, and GitHub identifier handling was improved to reduce errors in integration and dependency management commit.
• User Experience Polish: Comment form labels were updated, and the comment field was made optional to improve accessibility and reduce friction commit.

Current Status: The project is hitting key milestones in user-facing polish and admin tooling, with a strong emphasis on maintainability. Core features like commenting and liking are now more robust, while backend consistency sets the stage for scalable integrations.

Improved the New Order Page to be neater, and better themed along the colour scheme

Rename admin-product to products and refactor CSS, controller, and views.

Updated class names and CSS variables, added .no-product-grid and .dashed-break styles.

Simplified image loading logic in the product preview controller, and replaced large inline layout styles with external stylesheet includes.