PostHog / handbook

ARCHIVE (see Posthog.com repo instead): The PostHog handbook
https://handbook.posthog.com
3 stars 1 forks source link

Website rebuild #42

Closed jamesefhawkins closed 4 years ago

jamesefhawkins commented 4 years ago

Objective

It's not possible to hit everything above with just the homepage, but this is what I thought we should include to meet as many of these points as possible. This is NOT how the design will look, but is the content and flow:

posthog-redesign

Review

I'm not after detailed design QA. Any big sections you'd add / remove?

EDsCODE commented 4 years ago

Flow is good. I have comments on some of the content and a few things related to design but for pinpointing focus/intent of the page.

Addition

jamesefhawkins commented 4 years ago

This is really helpful and gives me a good todo list:

Flow is good. I have comments on some of the content and a few things related to design but for pinpointing focus/intent of the page.

  • "Saas/cloud" button: Maybe try copy that directly says "Try hosted for Free." I'm assuming anyone who clicks it will deploy for free first anyway before choosing plan so the free trial in the top right won't need to be there. Will urge even slightly interested to click and give it a shot. Reduce cognitive load needed to go see what the pricing is like.

Agreed

  • I forgot the emphasis we're going for. RE: the action button weights. Are we attempting to drive more hosted usage or self-hosted usage?

At the moment at PostHog.com it doesn't make self hosted clear enough. I don't want to eliminate the hosted version completely though since I think many will use it to try us out more easily.

  • Social proof: if allowed, we could add some of the major backers? Even YC itself would give pretty strong validation especially in dev community to give it a try

I thought about this quite hard but drew a different conclusion. I think a ton of startups push their investors. However, better established companies don't do this on their homepages. To me seeing "backed by YC" means "this is potentially going to be flakey". That's why I added it to the footer.

  • Changelog can also be an option on the top right menu.

Changelog should definitely go in there somewhere. I'd argue this is a slightly niche area for existing users so should go into the footer?

  • "Install now, free": I took a look at mixpanel's analogous banner and I liked their lead in. They ask a question and then give you a call to action/response to your problem.

Maybe that's the wrong CTA. I was trying to make it feel easy to deploy AND the self host thing obvious. I'll see if I can come up with better wording.

  • Design related but "Install now, free" options should be made buttons so that they are clickable. The logos might not seem clickable immediately.

This is exactly how I'd want it to work. The logos will need to feel like buttons (https://about.gitlab.com/install/ is a nice example of this)

Addition

  • Support/Contact button on the top right as an option. Provide visitors with a direct line of communication.

Agreed

  • Related to previous point, add intercom support? People can rapid fire questions

Given our demographic, I feel intercom is a bit "salesy", as it pushes its way into your face quite heavily.

  • A way to address a bunch of the questions you outlined above is having a really bulletproof FAQ page. We can do this up front or as we learn over the next few weeks/months what people always want to know but given that there's a lot of analytics players in the space, a good FAQ list should do wonders for us.

Agreed

  • Add another section that has 3 key metrics we've hit and would demonstrate high credibility along with the logos we add eventually (maybe later once we have more numbers)

Agreed

EDsCODE commented 4 years ago

Changelog should definitely go in there somewhere. I'd argue this is a slightly niche area for existing users so should go into the footer?

At this stage, having changelog at the top could help improve trust especially since we're targeting developers. Shows priority in getting the platform built and that's a decent chunk of the praise we've received. I think once we feel we have credibility and achieved relatively big clients that we can show logos of, this can move but for the moment the constant updates are a big selling point

Also, should add docs and about at the top right? This might make the options very cluttered but docs is definitely a link people will look for on our site when they forget.

Agree with everything else!

jamesefhawkins commented 4 years ago

Changelog should definitely go in there somewhere. I'd argue this is a slightly niche area for existing users so should go into the footer?

At this stage, having changelog at the top could help improve trust especially since we're targeting developers. Shows priority in getting the platform built and that's a decent chunk of the praise we've received. I think once we feel we have credibility and achieved relatively big clients that we can show logos of, this can move but for the moment the constant updates are a big selling point

Agreed. Ok let's do that until we are able to have case studies up there. "This looks active" is a big plus for an engineer checking us out + helps with people upgrading to the best version which will help retention... unless it looks super clutere

Also, should add docs and about at the top right? This might make the options very cluttered but docs is definitely a link people will look for on our site when they forget.

Agree with everything else!

Agreed.

jamesefhawkins commented 4 years ago

This is now superseded by the issues in posthog.com repo