The original repo had real teeth. This site finally shows them clearly.
Career-ops was never just a landing page idea. It is an evaluation engine, document generator, tracker, scanner, batch runner, and terminal dashboard. The rebuild turns that into a site with actual page structure instead of one giant “look at my dashboard” speech.
Design direction
Linear-style precision for the shell, Stripe-style clarity for explanation. Technical enough to feel serious, restrained enough to avoid AI-site sludge.
Why this matters
When the product is good but the wrapper is bad, people trust the wrapper less than the engine. That is dumb, but it is real.
What got cut
Generic “war room” posturing, repeated feature-card fluff, and anything that made the site feel more like internal cosplay than a tool Kody can use daily.
Core feature set
These are not made-up marketing bullets. They come from the upstream repo and the forked Kody-specific work already in this project.
The original repo centers on structured job evaluation: role summary, fit analysis, compensation sanity check, personalization plan, and interview prep instead of gut-feel applying.
A job should turn into a targeted resume track and cover draft, then render to HTML and PDF without rewriting everything by hand.
applications.md stays the source of truth. The site surfaces it cleanly instead of forcing you to babysit a markdown table manually.
The upstream repo already supports searching configured career portals and deduping results before they hit the pipeline.
The original project can evaluate multiple offers in parallel instead of treating every job like a standalone manual chore.
There is a real Go TUI for pipeline review. It should be presented as a power-user surface, not hidden or half-forgotten.
Architecture
The rebuild keeps the working system and gives it clearer surfaces.
Page map
Multiple pages, each with one job.
What this site is trying to be
Not a marketing toy. Not a dev-only shell. A usable front end for a serious job search workflow.
The homepage needs to establish that this is a real operating system for job search, not just another AI-themed website.
Users should immediately know the difference between the product overview, the live pipeline, the intake form, and the terminal workflow.
If the page does not get one real JD through intake and back out as a bundle, it is just decoration.