Launch feedback

I collect a summary of feedback here that I received after the August 26 launch of the technical preview

Intro video

• video is too long
• video is too slow (faster build up would be better, more cuts, just faster-paced)
• video needs some music
• shortcuts should be visualized in the intro video (viewer can't follow)
• FAQ on landing page: too technical, should be broader

Ideally the intro video should be built in motion graphics, rather than using screen captures.

E.g. this launch video from a day ago was going viral: https://x.com/dudufolio/status/2092337179607572694

But I'm not sure I'm ready yet to hire a motion designer. Can't do a smoothly animated video myself, though it would be really valueable to show off the product, and keep the attention of the viewer.

On the /why-editable page:

• For designers: Not clear that "you need to touch code, but the basics are simple enough for you. for special things you need a developer" - need to improve the writing there
• For everyone? Feedback was that it's too passive - should be "For everyone". My feeling is that i actually want to strengthen the part who Editable is not for, just to avoid negative experiences, and sharper positioning. But also want to avoid underselling. The thing is that you could actually use it for everything because you can change the code and add whats missing, but there are clearly situations where that produces more work and where you'd reinvent the wheel. E.g. i would not recommend to use Editable for an ecommerce site. Unless you separate mybrand.com and shop.mybrand.com, then it works. But this is getting too wordy probably.

Manual

• hard to navigate the large one-pager
• A floating TOC would be nice, I agree: It's for technical reasons I don't have that yet
• Quickstart (also deploy): Unfortunately, you need to use the terminal to install, change and deploy Editable. If i wanted to make this really like Squarespace, this would be a separate product. Which may make sense, and then i can avoid the audience split altogether. But I think for now the developers and agencies are my main target group, want to see if this can carry a business. The private people are a bonus.

More Considerations:

• hard to optimize for both, tech-folks and end-user
  • current decision is: tech-folks are primary audience, so sometimes i will risk to get "too technical and provide too much information" but that's on purpose because the developer target group might miss it.
  • still when possible, we should write broad and understandable first, and then sections in the manual can have more detail

Start by reviewing the launch feedback for the intro video, the /why-editable page, and the Manual. The issue does not name files or tests, and it mixes many possible content, positioning, video, and navigation changes. Done would require a decided scope and clear acceptance criteria for the selected updates.