I built a LinkedIn content system inside my portfolio

I built a LinkedIn content system inside my own portfolio.

The problem wasn’t that I had nothing to post about.

It was that my work was moving faster than my public story.

Projects were spread across GitHub, Vercel, old descriptions, screenshots, and different points in my career. Every time I tried to write something, I had to reconstruct the context first:

What was I building?

Why did it matter at the time?

What did I actually learn?

So I built LinkedIn Ops.

It pulls in my portfolio projects, researches the available evidence, considers when each project was built and where I was in my career, then turns that context into potential post angles.

From there, I can:

• Search and filter project stories • Review the evidence behind each idea • Generate a first draft using the full context • Edit it until it sounds like me • Create branded project visuals • Schedule or publish the finished post • Track what I’ve already shared

The most important part is that it doesn’t treat every project like it was built by the same version of me.

An engineering project from college should tell a different story than a manufacturing process improvement, a client website, or something I’m building now as the founder of LayerLane.

That timeline is part of the story.

LinkedIn Ops is still evolving, but it has already changed how I think about documenting work. I’m no longer staring at a blank text box trying to invent “content.”

I’m looking back at real decisions, real constraints, and real growth—and figuring out which part is worth sharing.

Built with Next.js, Supabase, Vercel, and the LinkedIn API.