Add LAUV drop-in integration case study - #385
Conversation
Document how the Acoustic Research Laboratory at NUS integrated a Subnero smart modem into an OceanScan MST LAUV, with no changes to the modem, the vehicle, or the software on either side. - New case study at /user-stories/drop-in-integration-lauv/, with the UnetStack-to-Dune bridge diagram and Dune config rebuilt in HTML/CSS - New pulse post dated 20 September 2026 announcing the release - Rename the brochure to case-study-drop-in-integration-lauv.pdf to match the existing case-study-*.pdf convention - Link the case study from the marine robotics and research industry pages - Open the ANL link on the research page in a new tab, matching the ARL link beside it - Add banner, thumbnail, cover, four figures, three portraits, and the ARL and OceanScan MST logos Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfBqiJJLMiPfwt8vj87iat
mchitre
left a comment
mchitre
left a comment
There was a problem hiding this comment.
Looks good overall. Minor point: phrases like "no one had to carry very much" still sound very AI.
Address review feedback on wording that read as AI-generated. Update the brochure PDF and bring the case study page back to verbatim parity with it. Twelve copy edits carried from the revised PDF into the page, including: - "The answer turned out to be: not hard at all, and no one had to carry very much." becomes "It took one small software bridge and no changes to anything else." - "that reliability is a game changer" becomes "that reliability is the whole point" - "is a direct boost to operations" becomes "is what makes the difference" - Drop "The physical work was just as contained.", "Three parties, one clean split of effort.", "For LAUV operators, the message is immediate." and the closing "the answer in practice" sentence Also rework three sentences in the pulse post that echoed the same register, and regenerate the cover image from the updated PDF. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfBqiJJLMiPfwt8vj87iat
Made a few edits to remove some of the obvious llm looking phrases. |
|
None of the staging pages render anymore. And the only example I cited doesn't seem addressed in the following commit, although many other sentences were. |
The staging website was set to the unetstack whitepaper branch for review. Updated it, the links should work now (pointed to lauv case study). The specific comment about "no one had to carry very much" phrase has been updated and this is not in the commit anymore. (Please do a hard refresh, I has the cached page first) |
2 participants
Staging: https://subnero.com/website-staging/
Case study pdf: https://subnero.com/website-staging/brochures/case-study-drop-in-integration-lauv.pdf
Case study html: https://subnero.com/website-staging/user-stories/drop-in-integration-lauv/
Case study landing page: https://subnero.com/website-staging/user-stories/
Pulse page: https://subnero.com/website-staging/case-study/partnership/2026/09/10/Drop-In-Integration-How-LAUV-Became-Subnero-Ready.html
Pulse landing page: https://subnero.com/website-staging/pulse/
Adds the Drop-In Integration: How LAUV Became Subnero Ready case study
What's included
_userstories/drop-in-integration-lauv.md/user-stories/drop-in-integration-lauv/_posts/2026-09-20-…mdbrochures/case-study-drop-in-integration-lauv.pdfcase-study-*.pdfconventionindustries/marine-robotics.mdindustries/research.mdimages/Page content is verbatim from the PDF, reflowed for HTML. The UnetStack-to-Dune bridge diagram and the Dune
Transports.TCP.Clientconfig block are rebuilt in HTML/CSS rather than embedded as images, so both stay selectable and legible at any width.Also opens the existing ANL link on the research page in a new tab, matching the ARL link beside it.
Before merging
The pulse post is dated 20 September 2026. Jekyll excludes future-dated posts (
futureis not enabled in_config.yml), so it will not appear until a build runs on or after that date. GitHub Pages builds on push, not on a schedule, so merging before the 20th will leave the post unpublished until something triggers another build. Either merge on or after the 20th, or push again that day.The case study page itself is unaffected — collection documents are not subject to the future-date rule, so it goes live on merge.