Python Poetry [1] is very sexy.

Oh, and Starship prompt [2] too.

[1] https://python-poetry.org/

[2] https://starship.rs/

project name

info

Clean – https://cli.github.com

The exa website [1] is pretty good looking. It is an alternative to the ls command.

[1] https://the.exa.website/

A big terminal recording on the front page is a must for CLI tools IMO: https://httpie.io/

http://cht.sh/

This is the pinnacle of design.

One of my favorites is https://bluebird.sh/ check out all that amazing command line software! a drawing program, a multiplayer crossword solver, and the amazing visidata program (my visidata review is https://recurse.social/@shapr/105984740425426440 )

If I may toot my own horn: The thing that grinds my gears the most about software project websites is when they don't clearly say what the thing does, and who this is for. That's why the website for my configuration management tool (https://holocm.org) has two sections, "This is for you if..." and even more importantly "This is NOT for you if..."

Htop: https://htop.dev/

I think the animated gif in the background is charming.

I'm just loving this AskHN. Most of the comments make me laugh. I've seen some great pages and programs, even installed one already. Ask more questions on HN please!

This compiler (written in Go) generates HTML and serves its own website over HTTPS:

https://NN-512.com

The compiler serves its own source code. Read the HTML generator/server code here:

https://nn-512.com/browse/NN-512#45

You could also look at Fabrice Bellard's websites. They are a paragon of clarity and simplicity

+1 for Feesh[1]

[1] https://fishshell.com/

I feel like mine isn't that beautiful but I'll show it anyway - https://github.com/chriswalz/bit

It's a CLI "enhancer" for git

Everyone should know that youtube-dl exists and how to use it.

https://youtube-dl.org/

Here is a github page for an Emacs package manager: https://github.com/raxod502/straight.el

It's a good page because it contains comparisons too all other emacs package managers[0], and carefully describes the pros and cons of each package manager. I wish more open source projects would do this.

[0] https://github.com/raxod502/straight.el#comparison-to-other-...

Here’s the home page for my static site generator, generated, of course, by the static site generator: https://bagatto.co/

I got 4 links for you (satire but still true):

https://motherfuckingwebsite.com/

http://bettermotherfuckingwebsite.com/

https://thebestmotherfucking.website/

https://perfectmotherfuckingwebsite.com/

Enjoy :)

It's not CLI-exclusive, but Prettier does a good job! https://prettier.io/

I like (and use) a lot both - awless as a comfortable aws cli tool - glow as a command line markdown reader

https://github.com/wallix/awless https://github.com/charmbracelet/glow

Does it count if the CLI is kinda it's own home page?

https://github.com/sindresorhus/sindresorhus-cli

Frankly, anything by Sindre is worth checking out: https://github.com/sindresorhus

https://www.visidata.org/

Not sure if this counts, but I'll throw my own project (semi-CLI-driven testing framework) into the ring, not as a perfect example overall, but as an example of what I wish more projects did, which was let me experiment a bit with their interfaces before I downloaded them.

This isn't something that's doable for every utility, but especially with the advent of WASM and easier cross-compiling from C, I wish more CLI/API documentation would allow me to play around with examples or try out a command on their docs page or in a sandbox; particularly if they're selling themselves as having a composable interface.

That's not only helpful for figuring out whether or not I want to use the project, it's also helpful when I look at a piece of documentation and am not sure which flag or option is actually important.

https://distilledjs.com

I kind of like the "one page with screenshots readme" type design. Not to toot my own horn, and this one is not super great, but here's one of mine: https://github.com/tducasse/go-instabot

Maybe not the "home page" you asked for, but https://github.com/derailed/k9s gives all the info I need/want for an amazing front end.

Please sign my petition to never use "sexy" to refer to anything ever again.

Ecasound: http://nosignal.fi/ecasound/

Mixer4 (closed source, though): http://www.acousticrefuge.com/mixer4.htm

Edbrowse: http://edbrowse.org/

K2pdfopt: https://willus.com/k2pdfopt/

ix: command line pastebin

http://ix.io/

LazyGit -- https://github.com/jesseduffield/lazygit

https://github.com/chadwickbureau/chadwick but it would be nothing without some data, so ... https://retrosheet.org and specifically https://www.retrosheet.org/game.htm

Not sure if this qualifies as sexy: https://rust-starter.github.io/

But you don't need to do any design/css, the theme is available: https://terminalcss.xyz/

Magit https://magit.vc/

WP-CLI is great :) https://wp-cli.org/

It’s for more than just a single CLI tool, but I’m a big fan of Charm’s site (https://charm.sh/). It’s hard to understand what it all is at first, but I still had a pleasant experience just looking at it!

Anything that looks like it came from a perl script over a cron job is all I ever wanted really.

I think there’s many nice OSS websites (and docs) built with Docusaurus [1].

It’s not exclusively for CLI projects, and their own website is pretty nice IMO.

[1] https://docusaurus.io/showcase

Ok, I'll bite. https://github.com/hlissner/doom-emacs. It's functional and clear. Sexy is 'very' subjective.

Not a CLI tool but rather a format. Still it has similar challenges in making it interesting:

https://concise-encoding.org

Also, the website is 32k ;-)

Trying to keep it simple: miniflux-cli https://sr.ht/~xn/miniflux-cli/

I am not feeling comfortable when someone is using word "sexy" in a professional setting. What does it mean? Should I be aroused when looking at it? That's inappropriate

nmh: https://www.nongnu.org/nmh/

Heirloom troff: http://n-t-roff.github.io/heirloom/doctools.html

Plan 9 Port: https://9fans.github.io/plan9port/

FFmpeg is sleek. https://www.ffmpeg.org/

ucspi-tcp https://cr.yp.to/ucspi-tcp.html

After browsing the current (as of now) 41 comments, I am curious: what constitutes 'sexy' for your audience?

Another static site generator huh? I would love to hear what you are doing differently :)

Why make a sexy homepage? To convince people to use it? Don't you want to make it work real well first, and then make the sexy homepage, when it's, you know... good software?

Back in the day, you would release your software on Freshmeat.net (https://web.archive.org/web/20010528211603/http://freshmeat....). You would get excited if people clicked on your project (https://web.archive.org/web/20100627062409/http://freshmeat....), but you'd get more excited if people downloaded your software, because it meant people were actually trying it out. (I can't find the graphs anymore, but it used to show you if anyone had clicked on the .tar.gz of your source code. It also used to have comments, but in later versions seems like comments were removed)

Anyone else remember back when the web was useful?