Skip to content

We aim to develop actionable tools and best practices that help new and existing open source projects make progress within the NASA Earth Science community.

License

Notifications You must be signed in to change notification settings

ESIPFed/esds-community-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

41 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ESDS Community Development Best Practices

The NASA ESDS Community Development Best Practices Working Group (CDBP) aims to develop actionable tools and best practices that help new and existing open source projects make progress within the NASA Earth Science community.

See our guide at https://ESIPFed.github.io/esds-community-guide/

Contributing to the guide

The ESDS community guide built using MkDocs and the Material theme.

How to

Setting up a development environment

In order to easily manage dependencies, we recommend using dedicated project environments via Anaconda/Miniconda. or Python virtual environments.

Once your environment is created, you can install the required dependencies with

python -m pip install -r requirements.txt

Build and view the guide

With your development environment activated, run

mkdocs serve

to generate the guide. This will allow you to view it at http:https://127.0.0.1:8000/. MkDocs will automatically watch for new/changed files in this directory and rebuild the website for a live preview of your changes (just refresh the webpage!).

Note: mkdocs serve captures your terminal; use crtl+c to exit. It is recommended you use a second/dedicated terminal so that you can keep this command running.

Deploy

This guide is deployed to GitHub Pages at https://ESIPFed.github.io/esds-community-guide/. The website is served out of the special gh-pages branch of this repository and deployment is handled automatically with the deploy_to_github_io.yml Github Action for any merge to main.

Markdown formatting

The way MkDocs and GitHub parse markdown documents is slightly different. Some compatibility tips:

  • Raw links should be wrapped in carrots: <https://example.com>

  • MkDocs is pickier about whitespace between types (e.g., headers, paragraphs, lists) and seems to expect indents to be 4 spaces. So to get a representation like:


    • A list item

      A sub list heading
      • A sub-list item

    in MkDocs, you'll want to write it like:

    Good

    - A list item
    
        ##### A sub list heading
        - A sub-list item

    Bad

    - A list item
      ##### A sub list heading
      - A sub-list item
    - A list item
        ##### A sub list heading
        - A sub-list item
    - A list item
    
      ##### A sub list heading
      - A sub-list item

About

We aim to develop actionable tools and best practices that help new and existing open source projects make progress within the NASA Earth Science community.

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published