I created the fulfilment system for a fulfilment team to use

Recent changes

• Removed redundant save! calls and updated fulfillment tests to reduce unnecessary database operations and align test logic with current behavior 9acc056.
• Added a fulfillment role, batch pipeline, and popup controller to support new workflow automation and UI interactions afa7a20. The popup controller likely handles transient UI elements like notifications or modals.
• Fixed a crash in /designs preview rendering by resolving an issue blocking Ruby scan/lint CI, ensuring previews no longer fail unexpectedly (911f035).
• Corrected a stray question mark in a design preview image tag to prevent malformed HTML output (955dd6c).
• Added a note about YSWS draft sponsorship documentation, possibly for tracking external partnerships or funding discussions (d92d571). No performance optimizations or subsystem overhauls were addressed in this cycle. Next steps depend on external feedback and test coverage improvements implied by recent test updates.

Deploying on coolify and fixing bugs with that + encrypting current db

Recent changes    - Installed Bundler 4.0.4 in the Dockerfile to standardize gem management across environments    (88ba659).  - Ensured the verification directory exists for SVG upload tests, addressing missing file system setup in test    workflows (83f2e53).  - Resolved a Turbo conflict in order steps, likely related to event streaming or frame rendering in Rails views    (e8d08f4). 

• Updated navigation unread counts dynamically from notification events, improving real-time feedback for user    activity (a75f6ff).

  ## Recent changes   

• Notifications: Unanswered notifications now retain their unread status until explicitly addressed. This    ensures users can distinguish between pending and resolved interactions without relying on manual state updates    (751a370). 
• Security: Authentication workflows, file uploads, and resource authorization checks have been updated with    additional safeguards. Specifics include input validation and access control refinements, though implementation    details are not disclosed in the commit message    (97e48db).

Made Notifications Useful

Recent changes

• Persistent unread state for unanswered boolean notifications    Notifications with unresolved boolean actions (e.g., approvals) now remain marked as unread until explicitly addressed. This ensures users revisit pending decisions. Commit: 39aabb2. 
• Interactive notification replies with approval time tracking    Added support for direct replies to notifications, along with timestamp logging for when approvals are finalized. This enables granular tracking of response times for actionable alerts. Commit: 6ac80f9.

Recent changes

Added ship request reviews, resubmission logic, and R2 storage integration for tracking reviewed submissions (41b1e43).

• Started on the review workflow
• Started on Resubmission logic
• Set up support for cloudflare R2

Guarded Hack Club token persistence behind encryption configuration, ensuring tokens are only stored when encryption is explicitly enabled (a4b6d0c).

Recent changes

Comment delete, Turbo Comment Box, and ship request fade functionality

• Add #destroy functionality to the comments with owner permission, path, delete button, and dependent comments.
• Make use of valid commentable_type/id while building comments and make responses as Turbo streams and wrap up comments within a Turbo frame.
• Resize the comment box according to the content changes detected by the MutationObserver.
• Make ship request modal and overlay fade in and out.
• Consider higher level ship request as blockers for all ship requests.
• Comment card and comment list styling.

Recent changes

Add comments to devlogs and ship requests

Implement polymorphic Comment model with CommentsController,
Stimulus-driven collapsing comment box, markdown preview form,
and styles. Comments will be rendered by Turbo frames and allow
editing by owner/admin.

This is what else is included in this change:

• Encryption of hackclub_access_token and hackclub_refresh_token
  through ActiveRecord encryption, including config, env sample
  and migration task for already existing non-encrypted tokens.
• SSL enforcement in production (assume_ssl, force_ssl).
• Update filter_parameters to strip out sensitive information
  and OAuth tokens from logs.
• Fix ExchangeRate API call to include Bearer authentication header.
• Sanitization of devlogs HTML output through SafeListSanitizer.
• Update Design#can_make_devlog to can_make_devlog? method and
  restrict can_ship? check to devlogs without ship request.
• Add SRI integrity attribute to marked/DOMPurify scripts loaded
  from CDNs.
• UI improvements: styles for disabled buttons, utility class
  for hover-underline effect, devlog cards layout and info icons.

Final Features Added

QOL

• I added a auto check for any workflows and new commits that runs every 5mins
• Added a built in guide to help you add a (PAT)

Focus Commit Panel

• The selected commit is shown on the left panel showing author next to a link to the commit
• It shows the whole commit message instead of truncated one like in the commit list
  -Integrated the GitHub API to fetch CI statuses to show “live” (every 5 mins) progress

Added Github Integration and optimised the commit get

• Optimised the commits so first it gets all the commits and creates them then replaces them all with ones with updated workflow status.
• Made the Commits store as individual objects in an Array so they can be updated automatically but only if the CI is still pending

• Added the commit as a hyperlink under date
• Added truncated title/commit name

• Added Cookies to save the github api key, and most recent repo

Next

• The commit focus (the empty white space on the left)

I made the header and logic for creating a commit on the commit list, It uses a sage green as the base colour while using similarly muted colours such as the red. The commits have a Pi chart which shows the actions status (green: successful, yellow: pending, red: failed). Pending is either all actions/workflows are incomplete or successful.

The top heading has a Go button which does nothing right now, next to the Repo title/heading which below has a discrete text input with a placeholder of the project repo.
And a settings button which also does nothing, yet…

Next to add is the Focused-Commit Half

Recent changes

• Ship request flow and SVG conversion: Added support for processing ship requests, handling SVG conversions, and validating devlog images before submission 8ca9b5d9.
• Nil safety for Hackatime projects: Wrapped the @hackatime_projects variable in an Array structure to prevent nil errors when retrieving project data a29691ff.
• CI environment and test ordering: Set RAILS_ENV=test for the CI setup process and reordered the sequence of test steps to improve execution reliability 2968d162.
• Authorization consolidation: Refactored authorization guards and consolidated the linking logic for Hackatime projects 4c2b1836.

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