Continuous deployment about mattermost-developer-documentation

[ccbrown]

@jwilander Do we have any ideas on a subdomain? Do we need to talk to a PM about this or any of our goals?

[jwilander]

The plan was developers.mattermost.com and @jasonblais is aware of the general plan but before we launch it or host it anywhere we'll probably want to run it past Ian or someone on the marketing side to make sure we're not stepping on any toes

[jasonblais]

Maybe it can be demoed on next platform meeting to get feedback?

Edit: I know JW you demoed it a couple of months ago once, but that was more informational than "hey, we're shipping this soon".

[jwilander]

I don't know how soon we're shipping this, I think what we really need is a checklist of things we need to do to make the marketing/business side happy

[jasonblais]

Overall the feedback from the marketing team is positive.

For now I'd say no action needed, but one thing to keep in mind is that a lot of the developer/technical content serves as a lead generation for marketing. Some decision makers discover Mattermost first through the developer content so we want to make it easy for those potential leads to have a happy path to the marketing content, for instance with links to case studies & articles at opportunistic points.

Of course, overall goal for marketing is to be low-key and not over-sell at developers.mattermost.com since only a small minority are potential leads. But something to think about down the road.

Another thing to think about is once we have Enterprise Edition features, we want to make it super obvious to the technical audience that they are EE features. Right now we don't have any, but later we might highlight the LDAP or Ethical Boundary plugins on the site. An option is to call it out in the title like we do in the docs, or have a nice EE badge that GitLab uses in their blog (https://about.gitlab.com/2017/10/22/gitlab-10-1-released/)

[jasonblais]

^To re-iterate, no action needed for now. Both can be revisited at a later time.

[jwilander]

I'm fine with an easy path to marketing/sales, but the main goal here is to provide better documentation for developers. So I'll be strongly against any changes (if they ever exist) that impair the documentation for the sake of sales and/or marketing. Great developer documentation will help sell the product itself.

As for marking certain parts EE, yes I feel very strongly that to be fair to contributors we need to very clearly mark when documentation applies to an EE feature

[ccbrown]

https://developers.mattermost.com/