I think having more quotes on the site is great, but I feel somewhat strongly that we shouldn't have them anywhere in Docs or User guides. It comes across as salesy and a bit dirty. The use case for docs is education, not sales/marketing and I think it will turn off our audience quite a bit.

Could we save these for upcoming feature pages where some of these will naturally fit with that content?

My gut feel is that quotes shouldn't be in guides/docs.

However, I think they could be useful if they add proof and clarity about how something is used.

Take Mention Me's example:

“We use feature flags to issue changes to 50% of users and then compare the effect. Experiment, find results, decide where to focus and then iterate — and PostHog is at the core of it.”

It's actually pretty useful up until "— and PostHog is at the core of it." where it becomes salesy.

But, as I mentioned, if it remained focused on "How others use this" then I think it's an interesting approach.

I think we've 2 votes for "no" here with @corywatilo and @smallbrownbike. As it stands, I now also think it's a bit too salesy so I'm also a "no". But I think with a bit of rework it'd be useful.

Good feedback, thanks all.

Previously I've been happy to defer when it comes to suggested changes to the user guides. However, because this (adding tangible examples of how other companies use these features) is something I've heard come up in user calls and case study calls, I'd like to push for a solution it if it's possible to find a middle-ground.

We could, as Phil suggested, rework the quotes a little to make them less sales-y and remove mention of PostHog. Another option would be to have a CTA of some sort which points to the customer stories section. E.g. "Find out how companies such as Hasura use Session Recording to build better products". This could potentially interface with a tagging system to show relevant stories.

Definitely keen to stop this being sales-y, as that isn't the intent at all. It's more about indicating actual use cases and giving some social proof on the way.

Converted to draft until we have a decision.

I've updated the quotes to remove mention of PostHog, making them less salesy and more direct in demonstrating a use-case.

Personally, we can maybe tweak the placement a little but I think these are definitely adding value to the docs now.

Had some offline discussions about this PR over the last week and, lacking further feedback, I'm going to invoke step on toes and push it through given that it's based on specific user feedback.

If we see any measurable negative change or hear feedback contrary then we can of course remove it, but since we had a quote in the user guides before this PR amplified that approach, it feels unlikely.

@leggetter I've made a final tweak to the language based on your comment, so setting this to auto-merge after your review.

Since this is now out, I need to clean up the design since we have two variations of quote components showing up in one here, plus the font size isn't proportional. (I thought we had already made the decision not to go forward with this, which is why I hadn't pushed to fix the design issues.)

Do we have any inspiration we can draw from of other companies who are doing anything similar to the intended goal here?

Do we have any inspiration we can draw from of other companies who are doing anything similar to the intended goal here?

My main inspiration was pulling from magazine layouts, as many of the technical magazines I used to work on would box out or create pull quotes to draw attention to particular points. At Custom PC Magazine, for example, we would often highlight steps of a build process in case mod articles.