"Good Public Workspace Checklist" blog post

[seanryankeegan]

Describe the content you'd like to see

A short blog post that is essentially a checklist of what makes a good public workspace. I often have partner calls where I say the same things about things they should include in their public workspace. Items to include

Overarching workspace:

• A good name for the workspace (it becomes the URL)
• A workspace summary

On workspace overview description:

• Brief introduction of what's available in the workspace
• A branded image (optional)
• Link to developer documentation
• Information on getting an API key

On collections:

• Well named collections.
• Examples for each endpoint
• Authentication set up and appropriate variable place holders

On environments:

• Any repeated variables throughout the workspace (baseUrl, apiKey, version, etc)

On team profile:

• Team domain acquired
• Branded profile image

Content Type

Blog

If the request is for a video, indicate which type

No response

[loopDelicious]

x-link to this one: https://blog.postman.com/how-to-set-up-public-workspaces/

[arlemi]

This will be turned into a blueprint, @seanryankeegan and @kinlane are collaborating on the content and it's currently held on Kin's side - probably pushed back for Gartner stuff for now.

[mjgutermuth]

@loopDelicious it looks like this is asking for an update of https://blog.postman.com/postman-good-documentation-checklist/, which says it was just updated in May. Is this a duplicate issue or do we need to update it again? nope, this is different