Skip to content

Add STEM Academy #2939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Add STEM Academy #2939

wants to merge 4 commits into from

Conversation

@tapyu
Copy link

@tapyu tapyu commented Jan 12, 2024

https://github.com/tapyu/awesome-stem-academy

An awesome list of academic resources which is tailored to STEM, that is, Science, Technology, Engineering, Mathematics (no Arts). Specially focused on theoretical aspects.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests.
    Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
    Add Locust #2893 (review) and Add QGis #2888 (review)
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
    • ✅ Add Swift
    • ✅ Add Software Architecture
    • ❌ Update readme.md
    • ❌ Add Awesome Swift
    • ❌ Add swift
    • ❌ add Swift
    • ❌ Adding Swift
    • ❌ Added Swift
  • Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
    • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • ✅ - [Framer](…) - Prototyping interactive UI designs.
    • ❌ - [iOS](…) - Resources and tools for iOS development.
    • ❌ - [Framer](…)
    • ❌ - [Framer](…) - prototyping interactive UI designs
  • Your entry should be added at the bottom of the appropriate category.
  • The title of your entry should be title-cased and the URL to your list should end in #readme.
    • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
  • No blockchain-related lists.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • ✅ Mobile operating system for Apple phones and tablets.
    • ✅ Prototyping interactive UI designs.
    • ❌ Resources and tools for iOS development.
    • ❌ Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce.
    If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • ✅ awesome-swift
    • ✅ awesome-web-typography
    • ❌ awesome-Swift
    • ❌ AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • ✅ # Awesome Swift
    • ✅ # Awesome Web Typography
    • ❌ # awesome-swift
    • ❌ # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to a maximum of half the width of the original image.
    • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. The casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash.
      Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Does not use hard-wrapping.
  • Does not include a CI (e.g. GitHub Actions) badge.
    You can still use a CI for linting, but the badge has no value in the readme.
  • Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.
@tapyu tapyu closed this Jan 12, 2024
@tapyu tapyu reopened this Jan 12, 2024
@tapyu
Copy link
Author

tapyu commented Jan 12, 2024 •
edited
Loading

unicorn
@tapyu
Copy link
Author

tapyu commented Jan 12, 2024 •
edited
Loading

I am really sorry, the PR #2924 was closed because I wrongly deleted the forked repo. I tried to recover it many and many times, but without success, so I decided to started it over in a new PR. I hope you can forgive me for that.
@sindresorhus sindresorhus force-pushed the main branch 3 times, most recently from c05ec08 to bbe1e6f Compare April 9, 2024 14:21
@sindresorhus
Copy link
Owner

Comments pointing out lint violation are allowed, but does not count as a review.
@sindresorhus
Copy link
Owner

It looks very messy to have the links before the item title.
@tapyu
Copy link
Author

tapyu commented May 26, 2024 •
edited
Loading

@sindresorhus That is the whole point of this awesome list: multiple links of a single material/course. I cannot change that. Otherwise, this awesome will get too messy.
@tapyu
Copy link
Author

tapyu commented May 26, 2024 •
edited
Loading

Plus, you can see that I strictly followed every guideline you stated.
@tapyu
Copy link
Author

tapyu commented Jun 5, 2024

FYI, although at first glance it might seem different, it is not messy, at all. Every tag link, as well its positioning and occurrence, is strictly defined in CONTRIBUTING.md. I invite you to read it through to see how well organized the tags are in this awesome list.
@sindresorhus sindresorhus force-pushed the main branch 5 times, most recently from f0658c5 to 993cee4 Compare August 8, 2024 13:04
@sindresorhus
Copy link
Owner

Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
@sindresorhus
Copy link
Owner

sindresorhus commented Oct 22, 2024 •
edited
Loading

The links could be on a second line or something. It makes no sense to have to scan the link titles with your eyes before you actually see the title. The list will not be accepted in the form.
@tapyu
Copy link
Author

tapyu commented Dec 28, 2024 •
edited
Loading

The links could be on a second line or something. It makes no sense to have to scan the link titles with your eyes before you actually see the title. The list will not be accepted in the form.

Agreed that the tag links preceding the short title might not be the best approach, but I do think creating a second line to put them is not a good solution either. It would make the list unnecessarily long. Instead, I put the tag links in the end of the short title so that the reader's eyes read first the item title, and then the links. Let me know if this solution suits for you.
@tapyu
Copy link
Author

tapyu commented Dec 28, 2024

Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.

That is not my case. In PR I've contributed, I point out mistakes if any was found.
@sindresorhus sindresorhus force-pushed the main branch 3 times, most recently from 0abcf16 to 393b934 Compare September 17, 2025 06:26
@sindresorhus sindresorhus force-pushed the main branch 2 times, most recently from 0db312a to fdd0122 Compare October 10, 2025 16:38
@sindresorhus sindresorhus force-pushed the main branch 4 times, most recently from 62ee821 to f6363b6 Compare October 10, 2025 16:40
@sindresorhus
Copy link
Owner

Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.

Your entry here should include a short description of the project/theme of the list. It should not describe the list itself.
@tapyu
Revise STEM Academy description in readme
4fcf543 
Updated description for STEM Academy resource.
@tapyu
Copy link
Author

tapyu commented Oct 27, 2025

Done.
@leo1bravo
Copy link

leo1bravo commented Oct 27, 2025 via email

@tapyu
Copy link
Author

tapyu commented Oct 27, 2025

image

For some reason the linting is not working
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants

@tapyu @sindresorhus @leo1bravo @jamesvance346