Sign in

Turkey Mashed Potato GobbleGobbleOps

@acorndevops.bsky.social
99 followers 302 following 2.5K posts

acorninteractive.ca Home of the devvy Kjörndogs. Buckle up, get comfortable. We’ll be pushing automated updates from any major developments on our core application, while publishing technology insights, code related findings, and general dev musings.

PostsRepliesMedia
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
Valhalla quelque jour, amigos. Yes. That's what we say for these matters...
youtube.com
Bensley - 'Do It Again'
YouTube video by RAM Records
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
INCOMING FEATURE SPECIFICATION: MULTICOLUMN SHARE CARD BLOCK FOR THE BLOG DISPATCHER
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
From the experiences together is where the good stuff … 🪄 ✨begins✨
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
’Tis the season of thanks: we’re grateful to help small businesses, not-for-profits and mission-driven orgs grow. Sometimes that means selling medical equipment. Sometimes artwork. Once in a while… turkeys. 🦃 #ECommerce #Thanksgiving
acorninteractive.ca
Lessons in E-Commerce from a Turkey Merchant
How one small business increased their sales by 40% and why the secret sauce is custom logistics.
110
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
Then there's just me as a person and the implicit joys of the interdisciplinary necessity that we don't talk about enough. For example: HAD ENOUGH OF FIREDHOSED TECHNICAL JARGON. PUT THIS [content strategy empowered social share caption] IN YOUR STALKING *screaming children and calamity*
youtube.com
Bonestorm
YouTube video by chadwickv2
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 19h
Re yesterday's misunderstanding about the many layers (or in this chat, key-value pairs, ha ha, in multiple software systems). We withdrew yesterday's post because the issue wasn't the article's content; it was the enticement share caption above it on a social provider. But there's always more..
ASCII flow diagram on a dark background mapping the blog workflow from Google Doc to live post, part 1 of 5. Step 1, “GOOGLE DOCS — authoring + editorial pass [OUTSIDE APP]”: the writer drafts, the editor comments inline, then sign-off happens in the doc; it lives entirely outside the app with no record in Mongo. The arrow down notes pasting HTML into Slate nodes works (withPasteFormatting.ts), but importing via a doc link or the Drive API is a gap, with no ingestion code at all. Step 2, “CREATE POST SHELL [OK]”: SeoModal goes through dispatch.ts to blog.create, setting a unique kebab-case slug, title, description and categories, with status draft, no publish date, and the caller as author. Step 3, “ASSIGN AUTHOR (optional — guest contributors) [OK / ~]”: AssignArticleModal or GuestContributorsPage calls blog.assignAuthor, writing the user ID, assigned-at and assigned-by; the role check is a hardcoded string compare rather than the RBAC helpers.Part 2 of the diagram. Step 4, “COMPOSE BODY — dynamic templates + components [OK]”: BlogTemplate feeds BlogDispatcher, a picker that reads the component list, then SectionSelector switches on a key to render a block component. It lists 22 block keys, including text editors, images, gallery, video player, tweet and Bluesky embeds, contact forms, share card, code block, four circle and square layouts, sequence blocks, staff quote, staff grid and we_nuts. The Slate text editor autosaves through blog.edit. Step 5, “REVIEW / APPROVAL [MOSTLY GAP]”: the “Submit for Approval” button opens BlonkchainsModal, a joke modal, with no server call, status change, notification or email. The status options are only draft, live or archived, with no review state and no reviewed-by, approved-by or submitted-at fields. The coordinator’s “Awaiting Approval” dashboard queue is just anything not live, so approval actually happens back in Google Docs or Slack.Part 3 of the diagram. Step 6, “PUBLISH GATE [OK / GAP]”: the client refuses going Live without a listing image (OK), but the server’s blog.toggleStatus only checks that a user is logged in (GAP); the BLOG_PUBLISH permission is defined but never called, so any logged-in user, including a guest contributor, can go live. Step 7, “GO LIVE [OK + GAP]”: toggling to live sets the status, sets the publish date on the first transition only, and appends a status history entry; there is no cron or scheduler, so future-dated publishing is impossible, and a Zapier webhook sits there commented out with a TODO to uncomment. Step 8, “SERVE [OK]”: listing and single views filter to live posts, server-rendered through BlogProvider and BlogTemplate with a 5-minute client cache, and SeoTags emits one social share image into Open Graph and Twitter tags, so every network scrapes the same title, description and image.Part 4 of the diagram. Step 9, “SYNDICATION — per-provider tailored captions [NOT BUILT]”: today, share icons are reader-initiated click-to-share only, with hardcoded copy for Facebook, X and LinkedIn, no Bluesky or Instagram button, and nothing posted outbound. A proposed data shape stores per-provider caption, image, hashtags, link mode, first comment, status (queued, posted, failed or skipped), posted time, remote ID and URL, and who posted it. Next, “CAPTION COMPOSER” with one tab per provider and a live character budget, plus fallback chains so nobody has to fill all five: caption falls back from provider caption to default caption, excerpt, then description; image falls back from provider image to the social share image, then a default. A guard refuses going live if any enabled provider’s caption is over budget. It fans out to five provider boxes: Bluesky, 300 characters, links OK, a question about alt text; X, 280 characters, links OK, thread split; LinkedIn, 3,000 characters, links OK but “hates links”; Facebook, long OK, links OK, Open Graph image rules; Instagram, 2,200 characters, no links, link in bio.
110
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 20h
One shy of a hundie followers today besties who’s it gonna be
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
(Staying on brand) 🥸 as for the code execution it WORKS. (Well enough, and that’s what we’re here for, innit)
static.klipy.com
Hackerman: Load Complete (Kung Fury)
Alt: Hackerman: Load Complete (Kung Fury)
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
Last up for the day: The latest and greatest from our content strategy design integration using the legacy app.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
🫡
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
INCOMING FEATURE SPECIFICATION: Build Data Visualization Prototype By Integrating Social Graph Metrics
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
gotta run a second test please hold.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
What would we be without the tiny embellishments in vocation, after all...
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
🙏Prayers To The Ether🙏 We're goin in.
static.klipy.com
Seal Team Helicopter Fast-Roping Over City
Alt: Seal Team Helicopter Fast-Roping Over City
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
INCOMING FEATURE SPECIFICATION: Add contributor avatar to bsky bug report
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
🐛INCOMING BUG🐛 Issue: Holy revolving door! Clicking the page search twice shuts it and reopens it empty-handed Issue Date: 2026-10-08T10:36:51.656-0700
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
🐛INCOMING BUG🐛 Issue: Holy copycat! The remove-block button squats on the code block's Copy Issue Date: 2026-10-08T10:36:52.873-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
🐛INCOMING BUG🐛 Issue: Pesky path problems! Team photos take a wrong turn on the blog Issue Date: 2026-10-08T10:33:21.449-0700
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
.. and speaking of 👀
Cropped screenshot of a faded testimonial on the Acorn website's cream background, shown in edit mode. A partly cut-off oversized quotation mark sits at top left beside italic grey text reading "Yes fixing bugs is annoying", with a small pencil edit button after it. On the right, a pale card attributes the quote to Mitch Budreski, Principal | Full Stack Developer; the photo area above the name is blank, with a small expand icon at its lower left.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 08/10/2026
And now with a dash of timing the bluesky component just got it's first dash of QA today allowing a slightly less technical overview about the 𝙒𝙃𝙔 of the guest collaborator module. Taking the approval test psuedo conversation this week and placing it into the publishing system, we can now expand
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
And to close the loop we can TAKE the PR's, file the tests and use the refactoring to better understand how the architecture gets supported by the modularization of the suites themselves. HOOAH
Screenshot of a Bitbucket "Run Pipeline" dialog over a dimmed Pipelines page for the Acorn / acorninteractive.ca repository. Branch is set to bugfix/AC-1394-test-compartments, and the pipeline is "custom: collection-check-case-studies", with a "See configuration" link. Under "Variables", which allows up to 50 variables or 10 KB in total, ENVIRONMENT is set to qa and PART is set to all, with its dropdown open showing six options: all (highlighted), server, administration, listing, single, and blocks. Cancel and Run buttons sit at the bottom right. Behind the dialog, the pipeline history lists runs #546 to #554 by Mitch Budreski, mostly merges of chore and bugfix branches, with the bottom one marked Failed.Text diagram on a dark background titled "TESTS: laid out like the application". It shows the folder e2e/collections/case-studies/, marked as the first collection module (check mark). Inside: containers/ (how a page composes its blocks) holds listing.spec.ts, tagged @page-case-studies-listing and covering grid, order, skeleton and data, and single.spec.ts, tagged @page-case-study-single and covering smoke, S8, AC-1307 and AC-1309. blocks/ (blocks only case studies have) holds case-study-header.spec.ts (@component-case-study-header, H1 H2, S2 S3), conclusion.spec.ts (@component-conclusion, C1 C2, AC-1303/1304/1329, S6), and shared.ts. administration/ (anything that logs in, tagged @administration-case-studies) holds publish.spec.ts, drafts.spec.ts (AC-1328) and listing.spec.ts (AC-1299, AC-1366). A README.md holds the module map and which file tests each QA finding. An arrow labelled "links (not owned)" points to e2e/components/: shared blocks, one spec each, covering every page it renders on — layout-sections (4 layouts), layout-circle-left (AC-1305, S4), related-blog-posts, related-case-studies, selected-services, share-card, sequence-blocks, staff-grid, staff-quote and seo-modal. A final line explains that each host is tagged with the component tag plus host tags from its route, producing @page and @collection tags.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
And from the days efforts we start to tease out some of the more important things, painstakingly simple. For example by running the auth permissions check on the view, we see that 😑 from the production db clone to the qa database 😑 there is an overwrite to the bitbucket secret... for login.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
🐛INCOMING BUG🐛 Issue: Bumbling bellhops! The robot's room key won't turn Issue Date: 2026-10-07T12:43:24.344-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
🐛INCOMING BUG🐛 Issue: Jiminy Cricket, a mixed-up mailroom! Test failures land at the wrong desk Issue Date: 2026-10-07T12:41:11.929-0700
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Now with our legacy system our work to date, sure, has areas of implementation focus but at it's core we're dealing with taking a snapshot OF the application state for testability such that future iterations are FAR less annoying. This is a very common problem.
Text diagram of a regression-testing architecture, drawn in box-drawing characters on a dark background, part 1 of 3. Top section, "REGISTRIES (config/)", labelled "one source of truth, no test copies": collections.json is the top level with one entry per collection, branching into pages.json (listing and single pages, feeding Page Checks), components.json (reusable blocks and the pages they render on), administration.json (publish, relations, content saves, per type), data-contracts.json (what each public method may send), and integrations.json (links between collections). An arrow leads to "SUBCOMPONENTS: each runnable alone (custom pipeline), each writes .result files". It shows collection checks with status markers: case-studies done (check), blog and services in progress (half circle), pages planned (empty box). Each collection check splits into server (Jest: schema, unit, contracts, admin), administration (the browser half), and pages (each listing or single Page Check, including hosted components via the page tag). Also listed: component-check done (one check per block across every page it renders on), e2e-administration and page-check done (also run inside collection checks), and infrastructure planned (Digital Ocean and Atlas probes, scaffold). An arrow notes that all write to e2e/regression-results/.result.Part 2 of the same diagram. "COMPOSITION: regression-full (never stops early; every suite records its own result)". The target flow: collection-check for all collections (pages run without component-tagged tests), then component-check for all components, then administration for all types, then infrastructure last (third-party control planes). "Today" it runs blog-listing, about, blog-cycle, the two case-study pages, services, dashboard, component-check, administration and infra — still per suite, not yet per collection. An arrow leads to "VERDICT: regression-verdict.sh: one row per result, BLOCKING list", a table of suite, result and blocking status: collection-case-studies-server succeeds and is blocking, annotated "promote a part once trusted"; page-case-study-single fails but is non-blocking (AC-1303: Ronan); administration-case-studies fails, non-blocking (CI login); component-share-card passes (known: finding 23), non-blocking; followed by an ellipsis. The footer reads: exit 1 only if a BLOCKING part failed; everything else is reported.Part 3 of the same diagram. "BRANCH ASSIGNMENT (not wired yet: regression-full has no branch)". A qa push runs secrets then deploy, noting the E2E step was removed today so it can finish green; a proposed branch would run regression-full on qa as report-only, for signal. A staging push runs secrets, deploy, regression-full, then verdict, where a BLOCKING red result means no promotion to production.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Closing off yesterday's Getting Into Trunk narrative, the inspections of the PR's were used to 1) properly build componentized test suite architectures for e2e and 2) run them against the code for error detection. Having advanced the reporting content strategy skill is how we produced the bugs.
Screenshot of a Bitbucket pull request titled "AC-1282: Case Studies listing — newest-first order in SSR (AC-1365) + image-load test flake (AC-1368)", open from a bugfix branch into qa, with 10 files changed and 7 commits. The description has two sections. "Assumptions" lists two: the data assumption that "newest first" (publish date, then post date, then created date) is the order the mockup wants, with any case study pinnable via display_order in the admin; and the SSR assumption that CasesStudiesProvider hydrates from server-rendered data without refetching. Each is "guarded by" an end-to-end test. "Implementation" explains the root cause of AC-1365: an earlier fix updated caseStudies.getListing but missed loadRouteSpecificData in the server startup file, which still sorted by display_order and title, so the page stayed A–Z. The fix drops the Mongo sort and applies a shared comparator. AC-1368's product fix already shipped; this PR only fixes a flaky test that measured an image before it lazy-loaded — it now scrolls the image into view and polls img.complete && naturalWidth > 0. It also notes the pattern reuses an existing comparator from case-studies.schema.ts, and SCSS rebuild: n/a.Screenshot continuing the same pull request description, a section headed "Test coverage 🔒 Hard gate". Unit: none, since the comparator is already shared with the method. E2E, in e2e/case-studies-listing.spec.ts: AC-1365 now asserts the rendered order equals getListing and no longer waits for networkidle, which never settles under Meteor DDP; AC-1368 waits for the image to load before measuring it. Typecheck: tsc --noEmit is clean. "What actually ran": npm test with 2783 passed and the pre-commit hook passing on each subtask commit; AC-1368 against QA passed 3 out of 3 runs; AC-1365 against QA fails, as expected until this deploys, because QA is still A–Z and the app can't boot locally without settings.json.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
🤫 and you know what pairs delicately with the entree for dessert?
static.klipy.com
Sparkling Candy Corn Pile
Alt: Sparkling Candy Corn Pile
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Something tells me there’s far more to this literary world of how did you get a start in such a field, and consider this our part in exploring what could be some of the most entertaining narratives of 🪄 Our lives.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Meanwhile, and this point, it’s safe to assume the formality is “baked” into our company ethos. acorninteractive.ca/blog/railtow...
acorninteractive.ca
Railtown Catering | E-Commerce Insights from Selling Turkeys Online
Over the past half decade, Acorn has collaborated with Railtown Catering to build and maintain a Woocommerce system for selling decadent meals across holidays throughout the year. We're here to share ...
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
And yet we do get there in the end.
Our new avatar compete with a turkey logo
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
And when we say one thing we don’t talk enough about is process is what I would also refer to as the ✨glimmers of the gig ✨
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
🫡 over to you design.
static.klipy.com
Loading Bar Prank
Alt: Loading Bar Prank
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Now if we may get seasonal on the matter.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 07/10/2026
Appropos to yesterday, as we are reassigned back into ✌️for money work✌️ The entire premise of the sandbox format for internal process tooling is not different, albeit slightly nerdier, than a 🥸 choreographed dancing routine with your best friends.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
And with just a dash of fundamentals for approval testing frameworks to proceed with 🪄 We are onto the next stage.
youtu.be
[DnB] - Muzzy - Children of Hell [Monstercat EP Release]
YouTube video by Monstercat Uncaged
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Jumpin' Jehoshaphat, no mugshot! Adding a first profile image goes nowhere Issue Date: 2026-10-06T13:57:30.111-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Golly, a junk drawer! Profile photos carry extra fields they don't need Issue Date: 2026-10-06T13:57:31.131-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Jeepers, a loose latch! A user-settings check needs work Issue Date: 2026-10-06T13:57:32.226-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Gee whiz, not a peep! Social links fail and the form keeps it a secret Issue Date: 2026-10-06T13:56:36.375-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Holy missing protocol! Profiles with a bare web address won't save Issue Date: 2026-10-06T13:56:21.219-0700
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Holy stuck turnstile! The SEO modal's Live switch never lets a post through Issue Date: 2026-10-06T11:37:25.666-0700
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
Now there are only plots that thicken, in this suite of distributed geolocales. 👀
anders
Just now
Sarah's defence: "What lizard?" which, to be fair, is exactly what a successful camouflage test should produce.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
🐛INCOMING BUG🐛 Issue: Great galloping gamma rays! One push from the PM and the panic button panicked Issue Date: 2026-10-06T10:34:53.469-0700
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
Excellent. And with the momentum we have evolved the bug reporting to post capability with new powers.
Screenshot of a dark-mode multiple-choice prompt with a "Bug title" tab, asking: "Pick a Bluesky title for the bug 'PM pressed the red button' (or choose Other to write your own)." Four options appear, each with a grey note explaining the pun:

"Holy big red button! The PM pressed it and now we're all pressed for time." Note: Pun on "pressed," meaning both the button and the deadline, in the classic "Holy …!" form.
"Great galloping gamma rays! One push from the PM and the panic button panicked." Note: The panic button does its own panicking, in alliterative form.
"Jeepers, a push-button pickle! The PM pressed the red button." Note: A "pickle" you push your way into, using era slang ("Jeepers").
"Zowie, ka-BOOM! Somebody gave the PM the launch codes." Note: Red button equals launch button, in a wildcard comic-book sound-effect form.
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
Topical questions for the discourse: When is the appropriate time, and what strategies exist to align testing implementation phases with the inevitability of caching the pipeline itself? Is it on a per feature basis, or when an entire approval flow has been stabilized?
000
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
And like most things as of late, and 🥸 everybody knows that 🥸 Integrated systems design, application state based testing evolutions, interdisciplinary workflows, and business context informed digital deliverables make sense, and culminate towards the inevitable quandary OF!
A playful hand-drawn pencil sketch shows a Venn diagram beneath the title “When is it trunk time?” The left circle contains a stick figure with a large moustache and a simple smile. The right circle contains the same moustached stick figure, but with an elephant trunk instead of a normal nose. The overlapping section contains only a large question mark surrounded by small emphasis lines.
110
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
TEST FLAVOURS TO DETECT UPON A REFACTORED PR - 1) Visual Regression check with a media pipeline to a cloud storage container (scoped per project) 2) Functional Regression tests 3) Unit tests 4) Safeguard checks for *frisky* agents overwriting dependency code and 5) Utilization profilers
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
Today we're back in the hot seat as the Rone Dog is onto featured scoped quote kung-fu dev chop um karate code... action. Yes. And now we have been layering our recipe of process, skills, systems, and software to accomplish this. Now we have 1) A PR reporting skill 2) A contextually aware ...
Screenshot of a dark-mode Slack notification at 6:44: "@Ronan updated pull request #472." The embedded card from Ronan Haughey is titled "AC-1302: Case Studies Single — See Website click, Discovery overlap, circle fade, heading line-height, sticky CTA layering," merging branch bugfix/AC-1302-case-studies-single into qa. The description links Jira ticket AC-1302, a Case Studies Single QA tracker, with subtasks AC-1306, 1307, 1308, 1309 and 1311. A "Summary — for PM (Sarah Winter)" section lists five fixes to the case study pages: the "See Website" button now works on wide screens; the Discovery section no longer slides over the header shapes at 1000–1024px; background circles fade gently on scroll and never disappear completely; section headings have proper line spacing on tablet widths; and the sticky "Contact Us" banner now sits above page content but behind the footer, as Nick specified. It notes two values still need Nick's confirmation: heading line spacing and the circle fade's minimum visibility. An "Assumptions" section begins "ASSUMPTION (DATA — design): the AC-1309 heading line-height of 45px (rati" before being cut off. The card shows the Acorninteractive.ca repo and buttons for Review, Nudge reviewers and Add comment.
100
Turkey Mashed Potato GobbleGobbleOps @acorndevops.bsky.social · 06/10/2026
And we're back because 🎺 *fanfare ensues* We have something useful to add to the conversation.
youtube.com
Royal News Trumpet Sound Effect
YouTube video by Shyam Patel
000