---
# System prepended metadata

title: conda.org Content Notes
tags: [Content]

---

---
tags: Content
---

# conda.org Content Notes

The Content Team is responsible for determining what we want this website to contain, and what the relative time priorities are for different types of content.  The Content Team also has some overlap with the Design Team on site organization.

There is a [Miro board](https://miro.com/app/board/uXjVPe57Ivs=/?share_link_id=173339099248) for arranging content and coordinating with the Design team.

[Join conda Slack](https://join.slack.com/t/conda/shared_invite/zt-1ie37q513-IgBpCv4onGnPR~n3IXmUFg)

Content team Slack channel: #conda-dot-org-content


# Team Members

* Anna Ng
* Dave Clements
* Gonzalo Peña-Castellanos 
* Jaime Rodríguez-Guerra
* Katherine Kinnaman
* Sam Hebert
* Travis Hathaway
* Bianca Henderson
* Please join us...


# Goals

From the [project goals](https://hackmd.io/MyRHr6w9RViAyNRfifkuUg)

1. **Create one obvious place where everyone goes for information about the conda ecosystem.**
1. **Make it easy for community members and newcomers to find conda-related information, and to get started in the conda ecosystem**

There you go.

# What content do we want?

**⇒ See [this spreadsheet for current priorities](https://docs.google.com/spreadsheets/d/1niamLGSuTaQoNdsTSwkYTTdAe8Eh99X7_5Mbt6x0CJo/edit#gid=0).**

## Feed / Index pages

Feeds are things like News, or Blog, or Events, or any other type of common content that we will want people to add content too.

Let's explore News as an example.

* Have an index page, where items of a given type are listed and linked to
* The news index page could list news items in reverse chronological order, for example
* Index pages are programmatically generated from individual pages / items 
  * These could have common metadata that is used to render the entries on the index page, such as date posted, headline, maybe an image?
  * The actual item could be in conda.org, or be external.

Some types of index pages we could have, in suggested order of implementation.

### News

News items of interest to the community.  Announcements for things like big upcoming events and trainings, releases, general news. 

### Events

A list of upcoming events. And a list of past events too, possibly with links to resources from those events.

### Blog

Longer form explanatory / expository items.

### Careers

Link to jobs that are connected to Conda in some way.

### Videos

Feature announcements, tutorials, etc.  This could aggregate content created by the community.  Conda could also have it's own organization channel on YouTube

### Podcasts

Interviews with community members about what they are working on, their backstories, answering FAQs, etc.  This would link to any relevant podcasts.

## Directories

These are like index / feed pages, but feature content that is not date-driven.  **All of these would be 2nd or later iteration implementations.**  Some of these could be built by crawling external resources.

### Tools

Have a searchable tool directory that lists all the conda tools, like conda itself, mamba, grayskull, conda-smithy etc.  Depending on the tool the directory could point to an internal tool page, or an external one (would be up to the tool owner)

### Packages?

Is there a unified package index that lists all packages from every "registered" channel?  This could be a huge win, but also a lot of work.  Also have to figure out channel registration and channel metadata.  What qualifies a channel to be registered and what does not?

### Plugins

Directory of plugins.  This might be better implemented as/under Documentation.

## Static Community Content

Static content (need a better name) is not part of a feed/index page or directory hierarchy.  It does not change rapidly.  

### Getting Started

Pages that give newcomers direction on how to do what they need to do.

### Support 

Where to find support!  Summary plus pointers to resources like Documentation, getting started, tutorials/training, forums, chat, github issues, FAQ, …

### Contact
Links on how and who to reach for what.

### About

High level picture of the conda community and ecosystem; plus project stats and branding, roadmap.

### Governance

This is currently in conda-incubator/governance repo.  There are advantages to moving it to the conda.org website (and thus the GitHub Repo that backs it).  It will be far more visible.

### Contribute

All the ways to contribute to the conda ecosystem.

### Documentation

By this we mean things like  

* man pages (effectively) for conda and its subcommands, 
* man pages (or links) for any other tools the community wants to document.
* documentation of packaging and file formats
* internal code documentation

This documentation does not have to use the same infrastructure as the main part of the web site. The internal code documentation should certainly be separate since some of it is generated from the code.

Much of this is currently in conda.io.

#### Versioning

Everything in the documentation section should be versioned, somehow.  We want to cleanly separate (and still maintain) documentation for all versions that are still supported.

Content in the rest of the site could have the ability to be version aware, through the use of tags.  For example, a news item about a release would have tag for that release.

## External Content

(Note, this is Dave C's obsession.)

We are a community website, but we don't require our community to create everything that is conda-related inside the web site.  If you want to create a blog post in Medium then we won't require you to recreate it in conda.org.  If you want the conda-lock web pages to be elsewhere, that's fine too.

What we do want is to be aware of and link to this external content.  In these instances conda.org would include metadata about the blog post, and the blog index page would point to it, just like the page points to blog posts written within conda.org itself.  We would also link to the conda-lock documentation.  We would not require the maintainer to recreate their pages within conda.org.

As a community website we embrace content, wherever our community wants to create it.


