---
tags: General
---

conda.org Goals

# Vision: Top level goals

1. **Create one obvious place where everyone goes for information about the conda ecosystem.**
* Responsibility: Design and Content teams
2. **Make it easy for community members and newcomers to find conda-related information, and to get started in the conda ecosystem**
* Responsibility: Design, Content, and Technology/Implementation teams
3. **Make it easy for community members to contribute content**
* Responsibility: Technology/Implementation team

Others?

# Goals, expanded

## One obvious place to go for conda ecosystem information

Whatever we make, it should be the obvious place that people go when they want to find anything about the conda ecosystem. The site should appear at or near the top of search results for "conda" and near the top for other related searches like "software packaging."

The site could contain a news feed, an events calendar, documentation, a blog, a description of and links to ecosystem components, chat and forum platforms, governance, open positions, and so on.

The site itself does not need to contain all the conda-related information in the world, but it should at least link out to all prominent sources of that information. Some conda information will be native to the site, but some parts, such as conda-forge will have independent sites. And this principle is related to the next goal:

## Make it easy to find conda-related information

The site should be structured so that different audiences can quickly determine where to find the information that each audience needs to know. In addition to easily navigating content, we should also provide a [search interface](https://hackmd.io/p3ybOVoBR6OKq-yhNUwffA#Search) that searches all prominent conda-related content on the web. People may come to conda.org to find conda-related information, but conda.org will send them wherever their search leads to and wherever the content is.

## Make it easy for community members to contribute content

We want to make it as easy as possible for community members to contribute content to the site, and we should adopt policies and technologies that make this easy.

For example,

* Favoring content tools/choices that are easier, rather than harder to use. For example,
* Supporting Markdown for content, rather than requiring fluency in HTML and Javascript.
* Using platforms that are already familiar to a large part of our contributor base (such as GitHub), enabling platform-savvy contributors to make direct contributions.
* Offering news, events, open positions, blogs, etc. submissions that allow people to either
* submit text and metadata for these items to be hosted in conda.org, or
* submit metadata for items hosted elsewhere so we can link to them from conda.org

# Not Goals

It became clear on our first call that we should also specify what are not our goals. These things are what are out of scope and/or we are deliberately trying to avoid

* User accounts and logins (let GitHub take care of that)
* Anything that requires us to maintain a web server.
* Recreate resources that are already out there (but we will link to them prominently)
* Features that involve a lot of work and/or maintenance (unless there is a clear community call for it)
* Do everything (or even most things) all at once, in our first iteration