open-sauced
front-end
open-sauced | front-end | |
---|---|---|
21 | 30 | |
881 | 368 | |
- | 0.5% | |
4.2 | 8.6 | |
11 months ago | 21 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
open-sauced
-
OpenSauced: Your fast track to open source
OpenSauced cultivates a thriving community of developers through its interactive forum. This virtual space provides a platform for developers to exchange ideas, seek guidance, and collaborate on projects, fostering a sense of camaraderie and shared passion for open source. All wrapped up in a nice GitHub stromboli.
- The path to your next Open Source contribution
-
Converting to Vite (Part 3)
In Part 3 of this series, we'll talk about our use of various plugins for Vite on the Open Sauced project. Vite provides extensibility in the form of a Plugin API, based on that of Rollup. For reference on which Rollup plugins Vite is compatible with (and to what degree), see Vite Rollup Plugins
-
Converting to Vite (Part 2)
The most straightforward fix for the circular reference was to update react-markdown through one major revision, but this introduced a new snag. In this major revision, react-markdown changed to ESM only, which would be fine for Vite, but not for our testing approach for jest (other than experimentally, so I learned. @0vortex and I got some help from @jasonericdavis on Discord to mock the react-markdown component in Jest (bypassing the need for ESM support) as part of a preparatory PR, and we got back on track.
-
Converting to Vite (Part 1)
This is Part 1 of a series about how recently in Open Sauced, we converted the project from using Webpack v4 to using Vite! A lot of what we'll cover in this series deals with PR #1322. @bdougieyo started this as a create-react-app project 5+ years ago and so this conversion certainly turned out to be an undertaking!
-
Implementing Dark Mode (Part 3)
In contributing to Open Sauced and other OSS projects as well, I've found time and time again that there are such ample opportunities to learn. However, contributing a feature and sticking with it on a longer term can cause those opportunities to multiply! In Part 3 of this series, I'm going to talk about some of the after-effects of implementing dark mode on Open Sauced in PR #1020.
-
Implementing Dark Mode (Part 2)
This is Part 2 of the series on Implementing Dark Mode. This was done in open-sauced/open-sauced#1020, and handily demonstrated to me the wealth of learning opportunities in contributing to Open Source. I for one have learned a ton! On this one, I got the opportunity for learning in several areas. I was still pretty new to React (and I still am), so I had not yet used the Context API. For a lot of the same reasons, I hadn't used the styled-components library before.
-
Generate PDF handbook with Docusaurus using GitHub Actions
This tool is meant to accelerate development on Open Sauced by giving contributors a way to access Docusaurus 2 powered developer documentation available at docs.opensauced.pizza.
-
How to lint PRs and welcome contributors using GitHub Actions
Expanding the @open-sauced ecosystem, it became tedious to apply all the necessary tooling available in open-sauced/open-sauced to newly created repositories and synchronising existing ones with minor updates.
-
Implementing Dark Mode (Part 1)
I'd like to share the story behind one of my favorite contributions to Open Sauced so far, which is the addition of "Dark Mode", PR #1020. This PR touched 25 files and was pretty substantial in scope, so I'm going to break this up into 3 parts. Part 1 is here is just the background - the what and the why, as @bdougieyo sometimes says. If there's one takeaway though, it's the value of opening a PR early in your process - you can share your progress and your roadblocks, and maintainers can help you get unblocked!
front-end
-
Please help: I’m a veteran and recent grad in Computer Science and I can’t find a job
There's a group called Operation Code that works with veterans in your position. Check them out, at the very least they can give you more specific advice. https://operationcode.org/
-
Vets looking to expand their IT capabilities
I recently heard about Operation Code, but haven't dealt with them myself yet.
- Coding boot camps
-
Degree/Certs for the Cyber Airmen
I recommend joining the slack for OperationCode https://operationcode.org/ and asking around. There are a lot of actual professionals with good advice and you might even get someone to check your resume.
- Looking for Programming training for veterans
-
IT cert question from a crew chief
Come on over to Operation Code and join the Slack.
-
[Update] Y'all wanna see what a homeless vet looks like when he hasn't worn this small of a size in 15 years? Thanks to you all I'm more confident in myself and I will get one of these jobs.
I highly recommend you join Operation Code where you can find a large vet community with a ton of contacts, you can find mentors, scholarships/training/apprenticeships, and the real excitement is access to our Slack community. There are channels for nearly every tech sector, but important ones for you right now would be Resume Review, Career Advice, Job Board, among others.
-
What's the latest consensus on programming bootcamps?
If you have (US) military experience there is a good group called operation code https://operationcode.org/ that offers mentoring, opinions on boot camps and traditional ed, translating military experience into civilian life, resume reviews, and other help.
-
Soon to be Veteran prepping for the transition and looking for advice.
https://operationcode.org/ has a slack you can join and ask question/go through the archive. We aren't terribly active anymore, none of us have handled wfh very well. I used to help run the seattle chapter but we're inactive since our main guy doesn't want to run it and I only like shooting the shit/doing mock interviews and not organizing things.
- What should I name our podcast?
What are some alternatives?
rasa - 💬 Open source machine learning framework to automate text- and voice-based conversations: NLU, dialogue management, connect to Slack, Facebook, and more - Create chatbots and voice assistants
computer-puns - A hand-picked selection of the worst computer puns, really cringe-worthy stuff.
slinkity - To eleventy and beyond! The all-in-one tool for templates where you want them, component frameworks where you need them 🚀
storybook-code-coverage - Combining Storybook, Cypress and Jest Code Coverage
use-shopping-cart - Shopping cart state and logic for Stripe
low-form - An experiment to create the lowest-impact React form API
open-source-project-template - A project template containing default open source files for new projects
automatic-tests-example - Repositório para meus códigos envolvendo testes do cypress e outros framweorks
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed
edc_password_generator_next
docs - OpenSauced documentation built with docusaurus
ofnotes - ✏️ Notetaking app with support for markdown, tagging, and filtering