What we put up
Open hub.sologem.xyz/code.
You get a dark editor frame with a file tree, tabs, syntax-colored sample files, a terminal panel, and a tiny command palette (Ctrl K). Click seed.ts, mirror.ts, pack.rs, README, hub.toml. Switch Terminal / Problems / Seeds. That is the whole toy.
Nothing installs. Nothing syncs. Nothing seeds. The numbers that say “seeders online” are theater. On purpose.
What it is not
- Not Hub released
- Not a Windows client
- Not your repos
- Not accounts
- Not a promise that day-one shipping UI will match this pixel for pixel
We are showing the vibe early so the long announcement does not stay abstract forever. If you only read one Hub post before this, start with Hub is SoloGem’s #1 priority.
Why an editor at all
Hub is a seed-network home for public and private code. SoloGem keeps some files warm. You can seed from your PC later. The product still needs a place where a project feels real: files, diffs, a status line that says the network is alive.
So the editor is not a side doodle. It is the room people will stare at when they open a repo. Getting the room wrong makes everything else feel like a costume.
What we care about in the look
Dark, quiet, dense enough to feel like work software. Indigo accents on Hub purple (#6366f1 / #a5b4fc). Mono for code. No fake macOS traffic lights. No glow soup. Flat panels, clear file tree, readable gutter, status that says main, language, and seeders without screaming.
If you open the preview and think “I could live here while a pack warms,” we did our job. If you think “ship it tonight,” we failed the honesty test. Preview only.
What comes next
The web preview stays a shell while we build the real client foundations. The first public look later this year should make hosting, privacy, mirrors, and seeding feel true. The editor has to grow up with that, not ahead of it as a costume.
Roast the layout. Tell us what feels wrong. Discord is loud on purpose: discord.gg/34pCtCpQJv.
Links
SoloGem LLC