> Generally speaking the reader will need to have seen some sort of external marketing in order to make it to the product website and then on to the docs. For

> Generally speaking the reader will need to have seen some sort of external marketing in order to make it to the product website and then on to the docs. For me it goes like this: * see an article or link description that promises something interesting. If it has a sound rationale and not too many buzzwords I continue. * quickly skip the homepage/brochure to look for hints of real use-cases or some hard, tangible problem they solved, ignore the rest. * check the pricing tabs to get a rough idea of the features, figure out if I'm in the target audience and to find out whether the pricing model scales with my needs or with theirs. * check the documentation, look for quick starts, specific guides, integration with other tooling.