Show HN: Code Hike – More than syntax highlighting
codehike.org
codehike.org
Also the tag "more than syntax highlighting" is what threw me off. I thought this would be an IDE extension or something that extended syntax highlighting in some cool way. I thought you were just using markdown as an example. Maybe "supercharged markdown code blocks" might be a better tag line.
That's probably the biggest thing I see as a production-ready blocker. The feature itself looks cool based on the few demos I saw.
Make the product or library itself paid in some form, sure...but I don't understand why you would hold your own marketing material hostage that way.
I also don't understand why there are video-based examples of what looks to be a React component.
i think the demos are visible to everyone, but the _source_ is only viewable by sponsors.
that said, still seems weird to lock away code that could make people use your product.
> More confusing, a lot of the locked demos had been unlocked by sponsors, so clicking on them worked! So why was the lock still there?
I didn't understand this part. Are you seeing locks on the first three demos?
Also get rid of the weird "sponsorship for unlocking documentation" model. Make the library sponsorware if you need to, as in you can't see the code until you sponsor, but why would you make the docs sponsored? They're what might entice people to actually pay to use your software. As someone else said, you're actually crippling your own sponsorships by hiding marketing material behind a paywall. Marketing should be free so that as many people see it as possible, and some subset will buy. If you cut off the top of that funnel, you just get fewer people buying.
I could eventually figure out what it was doing but the speed of the videos flipping between examples looks like it was set by people who already knew what the message was, rather than for people who don't know it (yet)
I also appreciate that you didn't throw around many unfamiliar technologies, with an assumption that all readers will be as looped into the same technology ecosystem. "Blade templates" is unfamiliar to me, but I can see from the code at the right, you're just illustrating another source file format that doesn't highlight well with traditional highlighters; it's not important for me to know what Blade is.
About the only section I'd say could use some work is the installation section, where a bunch of PHP ecosystem tech is mentioned, all of which is foreign to me. Maybe a, "Not a PHP developer? Here's a quick walk-through of what you need to know..." (linking to another page.)
Maybe add a "Need more? Contact us" tier.
Also, I'd love to use this with technologies other than PHP. I use Rocket (Rust) in one of my projects and tried to check out the standalone cli as my only option.
The link to it didn't work on firefox mobile.
Thankfully clicking on any of the PHP things worked and brought me to the same docs where I could then navigate to the CLI.
Maybe highlight it more that you don't even need special integration with the Webserver, since it's possible to preprocess pages with your cli utility.
That part was not immediately obvious and might have turned me away, had I not been determined to see what the CLI tool did.
I've got a handful of paying users and a few hundred free. I'm happy to see syntax highlighting being pushed forward!
I'll definitely be following along, it's beautiful stuff.
[0]: https://web.archive.org/web/20210226184710/https://svenkadak...
Torchlight definitely a good chunk of work on top of shiki, and as an external API it might be much easier to work with in many non-JS ecosystems.
You can see an early ancestor of this project on this post https://news.ycombinator.com/item?id=21536789 from two years ago (which had great feedback!).
If you want to try it, beware that current docs are minimal. If you have questions or feedback GitHub Discussions is the best place to post them. Thanks!
I'd take one of the more advanced gif, that showed highlights, code coming in, file changing, and I'd make that prominent at the top of the page, next to the tagline or marketing spiel.
Remember the What is it, Why do I need it (and is it for me), as people come in and have no idea what it is!
On mobile (Chrome on Android) the site is super confusing and has a "hotel California"-vibe: "you can enter but never leave". Pressing the back button multiple times didn't work - I had to close the site.
Tried reproducing it, but no go.
Thanks for checking.
I also like your idea of monetizing by "minimum" sponsors. How do you deal with people not wanting to sponsor because they don't want a monthly commitment but are willing to spend a fixed one-time sponsorship?
Also, what tooling do you use to take care of the sponsorships?
Some of the sponsors are fixed one-time (or two-times) sponsorships. I add them manually if the contribution is considerable.
This page: https://code-hike-sample.vercel.app/ is created entirely from this mdx file: https://raw.githubusercontent.com/pomber/code-hike-sample/ma...