forked from ProjectPythia/projectpythia.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #143 from ProjectPythia/main
[pull] main from ProjectPythia:main
- Loading branch information
Showing
16 changed files
with
513 additions
and
1,215 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,3 +10,5 @@ dependencies: | |
| - pre-commit | ||
| - pyyaml | ||
| - sphinx-pythia-theme | ||
| - sphinx-design | ||
| - sphinx-copybutton | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
891 changes: 0 additions & 891 deletions
891
portal/_static/images/logos/Unidata_logo_horizontal_1200x300.svg
This file was deleted.
Oops, something went wrong.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| # Cookbook Author Checklist Template | ||
|
|
||
| Project Pythia maintainers will provide this checklist to Cookbook authors to help get Cookbooks ready for publication. | ||
|
|
||
| ```md | ||
| **I am your Cookbook advocate, and my GitHub handle is <my-username>. Please tag me in this issue with any problems getting your Cookbook published!** | ||
| Once we've marked this entire checklist, [click here to open an issue on ProjectPythia/cookbook-gallery to publish your Cookbook!](https://github.com/ProjectPythia/cookbook-gallery/issues/new?assignees=ProjectPythia%2Feducation&labels=content%2Ccookbook-gallery-submission&projects=&template=update-cookbook-gallery.yaml&title=Update+Gallery+with+new+Cookbook) | ||
|
|
||
| --- | ||
|
|
||
| - [ ] **Confirm you’ve followed the entire Project Pythia [Cookbook Guide](https://projectpythia.org/cookbook-guide.html)**. | ||
| Take note especially of the [Develop your cookbook](https://projectpythia.org/cookbook-guide.html#develop-your-cookbook), [Authorship and the CITATION.cff file](https://projectpythia.org/cookbook-guide.html#authorship-and-the-citation-cff-file), and [Gallery tags](https://projectpythia.org/cookbook-guide.html#gallery-tags) sections. **Save the [Generate a DOI](https://projectpythia.org/cookbook-guide.html#generate-a-doi) step as the last step of this checklist.** | ||
| - [ ] **Confirm that the individual notebooks within your Cookbook adhere to the [notebook template](https://github.com/ProjectPythia/cookbook-template/blob/main/notebooks/notebook-template.ipynb)**. | ||
| If the template does not fit your Cookbook’s needs, that’s fine too! Simply let us know here in this issue. | ||
| - [ ] **Finalize your Cookbook repository name.** | ||
| We generally encourage the `<content>-cookbook` name structure. | ||
| - [ ] **Finalize your environment.yml.** | ||
| Specify the minimum number of packages needed to reproduce your content. Document any necessary conflicts and pinned package versions in an issue. In your Cookbook README or a content preamble, describe any unique dependencies handled outside the conda environment. | ||
| - [ ] **Sufficiently document your code** with markdown narrative text, supplementary media and references, and citations. | ||
| Declare any necessary prerequisite learning for each notebook at the top; these can be materials within your Cookbook, within other Cookbooks, or outside Project Pythia altogether. | ||
| - [ ] **Review whether your Cookbook needs an Appendix** of terms, definitions, or concepts. | ||
| Additionally, should your Cookbook reference other Cookbooks and learning materials to support your content? Could supporting content be added as updates to Foundations or other Cookbooks benefit your Cookbook? | ||
| - [ ] **Execute the `trigger-replace-links` action provided to your Cookbook.** | ||
| This will update any links to the Cookbook template to refer to your finalized repository name. See ProjectPythia/cookbook-template#183 for manual references to these links if needed. | ||
| - Click the Actions tab for your repository. | ||
|  | ||
| - Highlight the `trigger-replace-links` action in the workflows sidebar. | ||
|  | ||
| - On the right-hand side of the page, Run workflow > on Branch: Main. | ||
|  | ||
| - [ ] **Fill in all template sections of your README**. | ||
| This will serve as your Cookbook homepage | ||
| - [ ] Title | ||
| - [ ] Cookbook description (brief, under title) | ||
| - [ ] Cookbook Motivation - use this as an opportunity to tell us how your Cookbook fits in the broader learning ecosystem. Who should use this book? Why is it needed? Where does its content begin and end relative to existing resources? | ||
| - [ ] Structure - this section is an optional roadmap for Cookbooks with more complicated structure. If you only have one main body of content that progresses linearly, you can leave this out. | ||
| - [ ] **Confirm that your Cookbook is successfully building and publishing via GitHub Actions.** | ||
| This can be seen in individual Pull Requests as green checkmarks ✅ for important automation, especially the trigger-book-build action. You can also view a historical list of any of these Actions in the Actions tab at the top of your Cookbook repository. Check out nightly-build and trigger-book-build of PRs, then the build/build jobs to identify code errors. Please comment in this thread if you have issues identifying the source of any build and publishing failures your Cookbook has. Common failures include | ||
| - Incorrectly specified environment.yml | ||
| - trigger-link-check will fail if links in your content can not be resolved. We can help ignore links that are broken even if they work on manual clicks. | ||
| - Code errors in your notebooks themselves | ||
| - [ ] **Identify a Maintainer team via GitHub handle(s) in this thread.** | ||
| This can be one or more people with availability to check in on this Cookbook, issue fixes to broken content, or with a vision for the future development of the Cookbook. This is typically (but not necessarily) one of the primary authors of the Cookbook. | ||
| - [ ] **Link your Cookbook repo to Zenodo for DOI generation** | ||
| Follow steps 1-4 under [Generate a DOI](https://projectpythia.org/cookbook-guide.html#generate-a-doi) in the Cookbook Guide. Return here for instructions on step 5, and your final step: | ||
| - [ ] **Release your Cookbook!** | ||
| - On the right-hand sidebar for your Cookbook repository, click “Create a new release”. If you don’t see this button, you may need to click on the “Releases” header first and “Create” or “Draft” a new release. | ||
|  | ||
| - “Choose a tag”, enter a new tag name. This will be the git reference of the snapshot of code that represents this particular release of your Cookbook! We recommend using a name fitting the [CalVer](https://calver.org/) scheme, so something like v2024.06.13 for the date of the release, then choose “+ Create new tag: <your tag name> on publish” and make its Target main (unless you have the knowledge and desire to release from another branch!) | ||
|  | ||
| - From here you can use GitHub’s nifty “Generate release notes” button to automatically draft a summary of your Cookbook release based on merged Pull Requests! Feel free to further modify the title and body text of your release notes to fit your Cookbook and best represent your authors. | ||
| - Finally, `Publish release`! | ||
| ``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| --- | ||
| blogpost: true | ||
| date: Jun 28, 2023 | ||
| author: Julia kent | ||
| tags: fundraiser | ||
| --- | ||
|
|
||
| # Donate to Support Project Pythia! | ||
|
|
||
| ## You can make an impact on our community! | ||
| By donating to support Project Pythia you are investing in an important educational resource for the entire geoscience community, from students to late career. Project Pythia is an education working group helping geoscientists make sense of huge volumes of numerical scientific data using tools that facilitate open, reproducible science, and building an inclusive community of practice around these goals. Project Pythia is a home for Python-centered learning resources that are open-source, community-owned, geoscience-focused, and high-quality. | ||
|
|
||
| Donations contribute to outreach and community engagement activities, such as participant support at our annual hackathons. | ||
|
|
||
| ## Friends of the National Center | ||
| Friends of the National Center is the fundraising arm of the University Corporation for Atmospheric Research (UCAR), which manages the National Science Foundation National Center for Atmospheric Research. UCAR is a non-profit organization, so all donations to Project Pythia are tax-deductible to the fullest extent allowed by law. | ||
|
|
||
| We accept donations through the following ways: <br> | ||
| **Online** – Click the Donate Button on the right (we accept credit cards, Paypal and ApplePay). <br> | ||
| **Check** – Mail your check made out to UCAR and send it to: <br> | ||
| UCAR – Friends of the National Center <br> | ||
| Attn: Sarah Swanson <br> | ||
| PO BOX 3000 <br> | ||
| Boulder, CO 80307 <br> | ||
| Please include in the memo: Donation for Project Pythia <br> | ||
| **Stock gifts, ACH Transfers, etc.** – Please reach out to Friends of the National Center at info@friendsofthenationalcenter.org | ||
|
|
||
| <script> | ||
| (function(f,u,n,r,a,i,s,e){var data={window:window,document:document,tag:"script",data:"funraise",orgId:f,uri:u,common:n,client:r,script:a};var scripts;var funraiseScript;data.window[data.data]=data.window[data.data]||[];if(data.window[data.data].scriptIsLoading||data.window[data.data].scriptIsLoaded)return;data.window[data.data].loading=true;data.window[data.data].push("init",data);scripts=data.document.getElementsByTagName(data.tag)[0];funraiseScript=data.document.createElement(data.tag);funraiseScript.async=true;funraiseScript.src=data.uri+data.common+data.script+"?orgId="+data.orgId;scripts.parentNode.insertBefore(funraiseScript,scripts)})('79cd49fa-a550-4baa-a6d9-1913aae826df','https://assets.funraise.io','/widget/common/2.0','/widget/client','/inject-form.js'); | ||
| </script> | ||
|
|
||
| <script> | ||
| window.funraise.push('create', { form: 36005 }, { | ||
| selector: '#fr-placed-form-container-36005', | ||
| type: 'grow_contained', | ||
| }); | ||
| </script> | ||
|
|
||
| <div id="fr-placed-form-container-36005" style="min-height: 816px;"></div> |
Oops, something went wrong.