Remix.run Logo
gk1 4 hours ago

Folks, in your launch posts remember to describe what you're launching and what it's for. Ideally in the opening paragraph.

- Intro: Explains problem but not what is Neki or what it's for.

- Why Neki: Explains alternatives and why they suck but not what is Neki or what it's for.

- How does Neki work: Describes the technical components but not what is Neki or what it's for.

- What you get beyond sharding: Explains how to run/deploy but not what is Neki or what it's for.

- What is a platform preview + Try Neki today: 140 words on the definition of "preview" and links to get started... but not what is Neki or what it's for.

Edit: The landing page has 100x more useful information up front -> https://neki.dev/

Edit #2: They've since added a "What is Neki" section. Good reaction time.

DrammBA 3 hours ago | parent | next [-]

Folks, your blog post sucks at marketing.

Edit: your marketing site actually has excellent marketing information.

Edit #2: They've since replaced the blog post with a link to the marketing page. Good reaction time.

3 hours ago | parent | prev | next [-]
[deleted]
dwb 3 hours ago | parent | prev [-]

The landing page which is linked at the start of the second sentence of this page…? I don’t completely disagree with you, but this is mostly hypertext working as intended, is it not?

fastball 2 hours ago | parent [-]

Yeah this meta commentary on HN is very confusing for me. The structure of the article is literally

- short paragraph saying "we launched neki"

- short paragraph saying why neki was needed

- paragraphs about what neki is (with a header)

That seems like a very reasonable structure for a blog post like this one. Not being able to get to the third paragraph of a blog post seems like a "you" problem, not a blog problem.