opral / inlang.com

This repo is for collecting issues around inlang.com (https://github.com/opral/monorepo/tree/main/inlang/source-code/website)
1 stars 0 forks source link

How do we treat paraglide main page #22

Closed NilsJacobsen closed 2 months ago

NilsJacobsen commented 3 months ago

We want the "adapter" pages to be stand-alone. That means I only want to go to the paraglide page when I'm really interested in the fundamentals. So, in 95 % of the cases, we want people who have a (for example) next stack to go to the next adapter as fast as possible and only see tailored content.

Problem:

How should we design the paraglide page in order to be a distributor instead of the main place of interest?

Proposal:

We should probably try to sell people on a high level (the big benefits) and then show the adapters as fast and prominent as possible. 99% of the paraglide users use a adapter so we shouldn't loos people.

Addition:

The hero of the page is a mess right now. Many font styles no clear headlines. Video. Code. Images. I'm lost. This needs a redesign.

@loris.sigrist