conda.org Design

--- tags: Design --- # conda.org Design The Design Team is about the look, feel, and general organization of the web site. The general organization has some overlap with the Content Team. Look and feel will require interaction with the Implementation & Technology Team. There is a [Miro board](https://miro.com/app/board/uXjVPe57Ivs=/?share_link_id=173339099248) for supporting design and for coordinating with the Content team. Slack Channel: [#conda-dot-org-design](https://conda.slack.com/archives/C0408NMPJ5S) Two of the [top level goals for the site](https://hackmd.io/MyRHr6w9RViAyNRfifkuUg) inform the goals of the Design Team: 1. **Create one obvious place where everyone goes for information about the conda ecosystem.** 2. **Make it easy for community members and newcomers to find conda-related information, and to get started in the conda ecosystem** # Design Team Members * Anna Ng * Dan Meador * Dave Clements (Pilot) * Erkan Akbulut * Jaime Rodriguez-Guerra (Co-Pilot) * Jannis Leidel * Katherine Kinnaman * Ken Odegard * Sam Herbert * Travis Hathaway * Your name here! # Websites that may inspire us [GalaxyProject.org](http://galaxyproject.org) * Nominated by Dave C and Anna Ng. * Dave C's former project [OpenSource.com](http://opensource.com) * Nominated by Mariana Meireles * Appears to make extensive use of tagging for what shows up on different pages. [Prior Work!](https://github.com/conda-incubator/assets/issues/2) * [Isabela Presedo-Floyd](https://github.com/isabela-pf) created [several proposals](https://github.com/conda-incubator/assets/issues/2) in 2020 for a conda website. * Nominated by Jannis Leidel and Jaime Rodríguez-Guerra [djangoproject.com](https://www.djangoproject.com/) * Nominated by Jannis Leidel for the content and structure * Design slightly outdated and yet serving the community for a LONG time already [rust-lang.org](https://www.rust-lang.org) * Nominated by Jannis Leidel for design, accessibility and content structure * Focus on community governance and health, e.g. internationalization of site [Python-poetry](https://python-poetry.org/) * Nominated by Ken Odegard * Nice landing page [CIVITAS](http://civitas.eu/) "Sustainable and smart mobility for all" *non-programming example* * Nominated by Travis Hathaway * Good to have an example not from software world (this comes from the world of sustainable mobility planning in Europe) * Cool design and a nice section talking about their projects ("Our work" -> "Projects"). This could be mimicked for the various conda projects we have. [Sublime Text](https://www.sublimetext.com/) - Nominated by Ken Odegard - High quality clips demoing features # Integration of multiple sites/content The website will tightly or loosely integrate several different elements. In order of central to peripheral content 1. The **static community site** (what we usually think of when discussing conda.org) 2. The **conda documentation site**. This is currently at conda.io. 3. **The conda Q&A forum.** This will likely be a free discourse site. 4. The **conda chat channel.** This will most likely be in Element. Note that we will have very limited control of the look and feel of the last two items, and that they probably will not have a conda.org URL. How much effort should we put in to establishing a common look and feel across these components # Personas What are our personas in the conda community, and how central should we make personas to the conda community web site? A first attempt at personas: ## Users Users run components in the conda ecosystem (like conda and mamba) but they don't package tools or develop/maintain conda ecosystem infrastructure and core tools. This is by far the largest part of our community. We want to help them understand why they need environment managers, and how they can use the conda ecosystem to get their work done. Users can be further broken down. For example * Conda for educators * Conda for research * Conda for data science (?) * ## Packagers and Software Authors This group defines packages in the conda ecosystem. These can be packages written by themselves or by others. This requires a much deeper understanding of how things work. We'll need to work out how much of this content can be common across all channels, and how much is channel specific. Different channels have different practices and audiences. ## Infrastructure and conda ecosystem tool authors and maintainers This is the smallest group in this proposed categorization. These people maintain channels and communities like conda-forge and Bioconda, work on conda tools like conda, mamba, conda-lock, conda-smithy and so on. They require the deepest knowledge of the conda ecosystem. # Mobile first Most of our users probably won't be accessing the site from their phones. What balance should strike between making the phone interface usable, and making the laptop experience great? We need guidelines.