Technical Documentation

My recommendation is the following structure:

Technical documentation: I originally thought we could use Intercom to unify Marketing/Sales/Developer support under one platform while onboarding, but I think the ReadMe platform is more robust for developers, so I’m okay to branch it out from Intercom. Intercom themselves even use it for their developer / technical documentation. I like how they have a good UX for API versioning too. Feels more organized compared to Gitbook IMO.

Support documentation: Intercom’s Help Centre product. We got access to a startup program as mentioned here.

We intend to use Intercom in all of the zenon.org funnels and landing pages, with automation/bots/human support by community. Will primarily use Intercom by Marketing, Sales and Support.

I can get both setup as:

Please vote on 2 options for devs/support:

0 voters

If developers.zenon.org replaces the current docs.zenon.org, I will likely create marketing.zenon.org under some platform/tooling (maybe Intercom). The idea will be to organize and host the variety of assets marketing/sales teams could use for campaigning. Or the whole marketing docs could get organized under the attribute.zenon.org family since all marketing tools will be built on that brand.

1 Like