Skip to content
This repository was archived by the owner on Oct 24, 2021. It is now read-only.
This repository was archived by the owner on Oct 24, 2021. It is now read-only.

Document Meteor developer organizations #596

@hwillson

Description

@hwillson

Moving this issue over from meteor/meteor#3850. I'm not sure if this should be documented in the Guide (maybe under Writing Atmosphere Packages) or in the API Docs, but I'll assume the Guide for now. One of the best references I've seen for Meteor developer organization information is the Meteor 0.9.1: Meteor developer organizations, solidified Blaze APIs blog post.


(originally reported by @rgoomar)

I have not seen anything in the docs mentioning organizations and how to manage them.

It is an important part of the package system (IMO) and should be documented so that it can more easily be utilized.

There should probably be something in the meteor admin section, writing packages because I did not see how to manage organizations. But, I did end up finding it under meteor.com/account-settings/organizations

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions