Skip to content

Cursor/menlo security case study 6c68 - #2721

Open
modernmedici wants to merge 21 commits into
TraceMachina:mainfrom
modernmedici:cursor/menlo-security-case-study-6c68
Open

Cursor/menlo security case study 6c68#2721
modernmedici wants to merge 21 commits into
TraceMachina:mainfrom
modernmedici:cursor/menlo-security-case-study-6c68

Conversation

@modernmedici

@modernmedici modernmedici commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

What and why

Adds Menlo Security case study to site.

How was this verified?

Tested at different viewports in cursor cloud machines. Also visual design evaluated for humans. And MDX format for agents.

Risk

Low risk. Its just a new web page.


This change is Reviewable

cursoragent and others added 21 commits August 28, 2026 12:47
Publish the approved external Menlo Security case study on Resources
and style markdown tables in blog article prose so the results grid
renders as a readable before/after comparison.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Host the official site wordmark and point the post's Open Graph image
at it, matching how CIQ and LastMile AI attach a customer logo.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Place the architecture slide under The Architecture so the hybrid
control plane, local CAS, and elastic worker pools are visible next
to the topology they describe.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Place the 4.5h to 25m lockup under The Results and use it as the
Open Graph image so the social preview carries the same claim.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Render blockquotes as a large first paragraph with a smaller
attribution line so Christopher Staite's Chromium quote leads the
Menlo article at pull-quote size rather than body type.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Style the opening quote with explicit CSS on the post page so the
Staite line reads at 1.75–2rem instead of body type, with a smaller
attribution under it.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Treat the article as long-form, not default markdown: a spec-sheet
glance list, pull quote with mono attribution, metric table, captioned
figures, and a closing card — using the Technical Warmth type and
color system so the body actually reads.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Default discs were winning the eye on unordered lists. Force
list-style off on items and use a 7px brand dot so Challenge
bullets match the numbered rollout markers.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
The closing get-started link went to app.nativelink.com; send readers
to the enterprise site instead.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Put a small brand-tint icon on each At a Glance row so the spec
sheet scans as Industry, Scale, Challenge, Solution, Result, and
Adoption instead of a wall of labels.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Drop the tinted 26px tiles. Keep 11px brand marks in the existing
row padding so Industry–Adoption still line up as before.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Lead the At a Glance spec sheet with a Company row so the table
opens as COMPANY plus the Menlo Security logo.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Stop absolutely positioning row icons so they stay aligned with labels
from desktop through phone. Replace the oversized wordmark with a compact
company card: hexagonal mark, Menlo Security name, and menlosecurity.com.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Replace the cropped hexagonal O with Menlo Security's actual wordmark,
kept small on a white logo tile. The card still spells out Menlo Security
and links to menlosecurity.com.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Drop the nested chip and white logo tile so Company reads as another
spec-sheet row: official wordmark, Menlo Security, and the URL using
the same type and colors as the rest of the table.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Give Company the same in-flow label icon as the other spec-sheet rows,
and tighten column gap, label gap, and the wordmark-to-name spacing so
the first cell sits on the same rhythm as Industry through Adoption.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Give Company a building icon like the other labels, top-align the
wordmark lockup, and pull the label column in so icons sit with their
copy instead of floating in a wide gutter.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Label the build-time comparison and the hybrid topology with numbered
captions, and center the sentences under each image.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
Size the logo to the two-line type stack and space the name and URL
against the top and bottom of the wordmark so MENLO lines up with
Menlo Security and SECURITY lines up with the link.

Co-authored-by: Sumon Sadhu <sumon.sadhu@gmail.com>
@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nativelink Ready Ready Preview Aug 28, 2026 3:35pm
nativelink-aidm Ready Ready Preview Aug 28, 2026 3:35pm

Request Review

@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Some of the pull request description still needs filling in:

  • What and why needs a bit more detail (39 characters, 40 expected).

Edit the description and this check re-runs on its own. The sections exist because they are the parts a reviewer cannot get from the diff: why the change is needed, how you know it works, and what breaks if it is wrong.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants