Git Product home page Git Product logo

pizza-verse's Introduction

This repo is archived. If you are looking for the latest, check out open-sauced/insights or open-sauced/hot.


Open Sauced

πŸ• Open Sauced πŸ•

The path to your next Open Source contribution

CodeQL Compliance Release Publish stories if changed Netlify Status Dependabot Badge GitHub code size in bytes GitHub commit activity GitHub issues GitHub Release Discord Twitter

Open Sauced provides structured onboarding for new contributors to open source. This structure provides a way to track your next contributions by leveraging a unique dashboard built on top of the GitHub GraphQL API.

open-sauced-screencap

πŸ“– Prerequisites

In order to run the project from a container we need node>=14, npm>=7 and docker>=20 installed on our development machines or use one of the listed cloud providers we support:

Gitpod

βœ… fully ready integrated development environment

β­• VS Code settings sync is not ideal

Open in Gitpod

Gitpod is mostly free but has extensive documentation for all its contributing features.

For Vite to work with Gitpod we need to use a custom Dockerfile that lives under .gitpod.Dockerfile.

Open Sauced comes with a pre-defined .gitpod.yml that should work out of the box in multiple contribution scenarios.

Replit

βœ… fully ready integrated development environment

β­• modified contribution workflows

Open in Replit

Replit is an old service that recently supported NixOS, enabling full customisation of the runner and project.

Open Sauced is configured with a shell environment supporting node@16 and npm@8. The build environment script lives in shell.nix and the repl config lives in .replit.

Codesandbox

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• low resources free tier limitations

Open in CodeSandbox

Stackblitz

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• limited documentation on container limitations

Open in Stackblitz

Glitch

βœ… can be used as editor replacement

βœ… supports deployment preview

β­• enforces custom package manager for stability

β­• does not support stacked hot module reload

β­• severely low resources free tier limitations

Remix on Glitch

πŸ–₯️ Local development

To install the application:

npm ci

To start a local copy of the app on port 3000:

npm start

πŸ§ͺ Test

For running the test suite, use the following command. Since the tests run in watch mode by default, some users may encounter errors about too many files being open. In this case, it may be beneficial to install watchman.

npm test

You can request a coverage report by running the following command:

npm run test:coverage

πŸ“¦ Docker builds

A development preview can also be run from docker:

docker build -t open-sauced-dev .
docker run -p 8080:80 open-sauced-dev

Alternatively you can pull the production container and skip all builds:

docker run -dit -p 8080:80 ghcr.io/open-sauced/open-sauced

🎨 Code linting

To check the code and styles quality, use the following command:

npm run lint

This will also display during development, but not break on errors.

To fix the linting errors, use the following command:

npm run format

πŸš€ Production deployment

A production deployment is a complete build of the project, including the build of the static assets.

npm run build

You can analyze the build by running the following command:

npm run build:analyze

🎭 Offline asset optimization

We also have a script for updating .svg files used in the project, you only need to run this if you add new assets:

npm run build:svgo

And one for .png and .jpg files:

npm run build:squoosh

🚧 Development debugging

Thanks to antfu/vite-plugin-inspect we can always inspect the bundles in development by navigating to localhost:3000/__inspect/ in your browser.

πŸ“™ Storybook

Storybook is being leveraged to mock out visual React components. The latest version of the design system can be found at this URL.

npm run storybook

storybook example screenshot

πŸ”‘ Authentication

Authentication is handled through OneGraph's AuthGuardian service.

πŸ’Ύ Database

This project uses GitHub as a database. When you login, you will be presented with a button to create a goals repository. That repository template lives at open-sauced/goals-template.

πŸ’¨ Service Worker

This project uses the sw-precache to kickstart an offline cache. The offline cache only registers in production. If service needs to be manually removed make an unregister call from the registerServiceWorker.js import.

πŸŒ™ Dark Mode

This project supports "dark mode" styling, and by default it will follow the color preference on your device. It also allows for overriding this using buttons at the top right of the screen, which will persist the preference to local storage on your device. More info about color preference web API's can be found here: MDN Web Docs

πŸ“ Markdown Support

This project leverages Remirror for a delightful experience in documenting your Open Source goals. The editor supports markdown features including heading levels, bulleted lists, text formatting, code snippets, and emojis!

🀝 Contributing

We encourage you to contribute to Open Sauced! Please check out the Contributing guide for guidelines about how to proceed.

We have a commit utility called @open-sauced/conventional-commit that helps you write your commits in a way that is easy to understand and process by others.

It is generally integrated as an npm script but you can run it with npx as well:

npm run push

For any other npm based project or dotnpmrc defaulting to --yes:

npx -y @open-sauced/conventional-commit

πŸ• Community

Got Questions? Join the conversation in our Discord.
Find Open Sauced videos and release overviews on our YouTube Channel.

🎦 Repository Visualization

Visualization of this repository

βš–οΈ LICENSE

MIT Β© Open Sauced

pizza-verse's People

Contributors

adiati98 avatar bekahhw avatar cbid2 avatar david-001 avatar devjster avatar emmarie-ahtunan avatar hikmahx avatar jdwilkin4 avatar kaz-smino avatar kenmusau avatar kumar007ambi avatar lymah123 avatar michaeljgoerlitz avatar michaella23 avatar mohdahsanrazakhan avatar mugabe000 avatar nickaldwin avatar nickytonline avatar pondy007 avatar prw760 avatar samuvelraja avatar satoshi-sh avatar sdp971 avatar silvia-wachira avatar sunny-unik avatar syke9p3 avatar the-techgurl avatar thititongumpun avatar twister904 avatar wheeleruniverse avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

pizza-verse's Issues

Bug: I have a question regarding table of contents of recipes ?

Describe the bug

In the table of contents present 4 contents are available. Should the number of contents added for more added pizza recipes ?

Steps to reproduce

Add newly added recipes to the table contents.

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Markdown Style reference

Type of feature

πŸ“ Documentation

Current behavior

Even though the ReadMe file suggests following the markdown syntax based on the other entries, contributors, especially those who never used this language before would have a hard time remembering how to format their contribution.

Suggested solution

I think it would be helpful to create some sort of Markdown reference guide. It'll make it easier for contributors, especially those who have never used Markdown before to gain a better understanding of how to format their contribution.
Note: I would love to create this guide.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Chores: Replace the logo in this repo's README

Important

If you've worked on a good first issue in any of our community repositories before, please refrain from taking this issue.
We may remove you from the assignees and not accept your pull request if you choose to proceed.

Description

Below logo in this repo's README is the old one, we should replace it with the new one.

Screenshot 2024-05-02 103453

Suggested Solution

Replace the logo by changing the link in the src with the below:

https://github.com/open-sauced/assets/blob/main/logos/logo-on-dark.png

Line to be changed:

<img alt="Open Sauced" src="https://i.ibb.co/7jPXt0Z/logo1-92f1a87f.png" width="300px">

Feature: I want to add more pizza facts in Pizza Facts & Trivia

Type of feature

πŸ• Feature

Current behavior

I want to add more pizza facts in Pizza Facts & Trivia section for the information.

Suggested solution

No response

Additional context

I was wondering can admin add hactoberfest label or not ?

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Change in rules

Type of feature

πŸ• Feature

Current behavior

There have been concerns about merge conflicts occurring due to PRs with large numbers of content being added to the recipe and pizza-facts-and-trivia files

Suggested solution

  1. Add in new rules to the contributing guidelines section, such as "To keep things organized, You choose to either add one new pizza fact to the pizza-facts.md file or add one new recipe to the pizza-recipes.md file."
  2. Create a section that looks similar to the Resolving Conflicts section in the Contributing guide in the guestbook repository.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: add information about New York City Pizza to Regional Styles file

Type of feature

πŸ• Feature

Current behavior

Someone on X wanted to know if there are more styles of pizza besides Ohio Valley.

Suggested solution

Since New York City is often deemed the mecca of great pizza, I will add some information about this region's approach to pizza.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: I want to add some facts

Type of feature

πŸ• Feature

Current behavior

I want to some facts relate pizza to the under Fun-facts and trivia

Suggested solution

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Add link to style guide in CONTRIBUTING File

Type of feature

πŸ“ Documentation

Current behavior

The repo's style guide has recently been merged, but contributors might wonder where to find it.

Suggested solution

Hyperlinking it to the Contributing guide would make it easier for them to find the style guide.

Additional context

I want to work on this issue

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Bug: Compliance action is not checking keywords "related to" and "relates to"

Describe the bug

This repo has open issues that we don't want to close. Therefore, we encourage contributors to use keywords of "Relates to" or "Related to" when link an issue in their PR. However, the action only checks default keywords. So, whenever an issue is linked with other keywords than the default ones, they won't pass the check as screenshot below.

Screenshot 2024-05-13 235220

Steps to reproduce

  1. Create a PR.
  2. Add "Relates to" keywords in front of an issue number when linking an issue.
  3. Issue check won't pass and the bot will warn about this.

Bug: CODEOWNERS does not automatically add reviewers

Describe the bug

Currently, we have CODEOWNERS file that contains the list of code owners. But they don't get added automatically as reviewers as it suppposed to. And it happens because the syntax has to be on the same line.

Steps to reproduce

Can't be reproduced without a new incoming PR.

Browsers

No response

Additional context (Is this in dev or production?)

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Add world's traditional foods

Suggested solution

Description

This repo is meant for our intro course participants to continue their learning by adding pizza-related information. Even though pizza is a favorite to most people, adding pizza-related information would be hard for folks who don't have interest in pizzas. We might want to add something else to this repo to spark interest for our course participants in continuing their learning.

Suggested Solution

Let's allow folks to add their favorite foods from their own countries! In international space, folks usually love to talk about their country, culture, and even their traditional foods. By allowing them to add this, we might be able to encourage folks to contribute further.

We will need:

  • A new file called world-traditional-foods.md.
  • An example in the file.
  • A new open issue.
  • Information about this addition in the README.
  • Update the PR template to include this addition.

Add pizza fact or trivia (Please Keep Open)

Do you have a favorite pizza fact or trivia? We'd love to hear it.

Before submitting, make sure the recipe doesn't already exist and then add one recipe to https://github.com/open-sauced/pizza-verse/blob/main/pizza-facts-%26-trivia.md.

Also, to keep this issue open, use "Relates to" when linking this issue to your PR in the "Related to" section of your PR template.

Feature: Enhanced description of Nigerian Pizza

Current behavior

Updated description of Nigerian Pizza to highlight its fusion of culinary traditions and diverse flavors

Suggested solution

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: LICENSE this repo

Type of feature

πŸ• Feature

Current behavior

We need a license for this repo. My suggestion is MIT

Suggested solution

My suggestion is MIT

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

feat: adding Zanzibar Pizza

Description

This PR adds Zanzibar Pizza to pizza-recipes.md

What type of PR is this? (check all applicable)

  • ☝️ Add a pizza fact or trivia
  • πŸ§‘β€πŸ³ Add a pizza recipe
  • πŸ—ΊοΈ Add a regional pizza
  • πŸ“ Documentation Update

Related Tickets & Documents

Related to #feat:

Added to documentation?

  • πŸ“œ README.md
  • πŸ™… no documentation needed

[optional] What GIF best describes this PR or how it makes you feel?

Add a pizza Recipe! (Please Keep This Issue Open)

Do you have a favorite pizza recipe? We'd love to hear it.

Before submitting, make sure the recipe doesn't already exist and then add one recipe to https://github.com/open-sauced/pizza-verse/blob/main/pizza-recipes.md.

Also, to keep this issue open, use "Relates to" when linking this issue to your PR in the "Related to" section of your PR template.

Feature: Add a PR template

Type of feature

πŸ• Feature

Current behavior

Currently, we're using the default PR template that lives in our .github repository for this repo.
However, there are some sections and points that aren't needed here, such as:

  • Mobile & Desktop Screenshots/Recordings
  • Added tests?
  • [optional] Are there any post-deployment tasks we need to perform?

Suggested solution

Based on the default template, create a PR template in the .github folder with related contents for this repo:

  • Remove the sections that are mentioned above.
  • Include only necessary items in the "What type of PR is this?" section as follow:
    • ☝️ Add a pizza fact or trivia
    • πŸ§‘β€πŸ³ Add a pizza recipe
    • πŸ—ΊοΈ Add a regional pizza
    • πŸ“ Documentation Update
  • Include only necessary items in the "Added to documentation?" section as follow:
    • πŸ“œ README.md
    • πŸ™… no documentation needed

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Add traditional food (Please Keep Open)

Do you have a favorite traditional food from your hometown or country? We'd love to hear it.

Before submitting, make sure the food doesn't already exist and then add one food to https://github.com/open-sauced/pizza-verse/blob/main/world-traditional-food.md. Please follow the instructions in the file's comment to add a food.

Also, to keep this issue open, use "Relates to" when linking this issue to your PR in the "Related Tickets & Documents" section of your PR template.

Add Regional pizza style to repo (Please Keep Open)

Do you have a regional-style pizza you want the world to know about? We'd love to hear it.

Before submitting, make sure the recipe doesn't already exist and then add one recipe to https://github.com/open-sauced/pizza-verse/blob/main/regional-pizza.md.

Also, to keep this issue open, use "Relates to" when linking this issue to your PR in the "Related to" section of your PR template.

Feature: I want to add a Pizza recipe

Type of feature

πŸ• Feature

Current behavior

I want to add a Indian Pizza Recipe which is quite popular in India.

Suggested solution

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

docs: Grammar and Formatting issues

Type of feature

πŸ• Feature

Current behavior

The style guide has a few Markdown errors and grammar issues. This can make it difficult for people to implement the guidelines effectively when making their contribution to this project.

Suggested solution

  • Remove the gap in > ** Note:** Always check for spelling and grammar errors before you publish your PR. We highly recommend consulting [Grammarly](https://www.grammarly.com/) to help with any of your typos.. This would clarify to people that checking for spelling is needed when making their contribution.
  • Omit the word "to" in the sentence, Said images should be linked to using the following url: "https://raw.githubusercontent.com/open-sauced/pizza-verse/main/images/" followed by the image’s name. for clarity.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Update Nigerian Pizza description

Current behavior

Updated description of Nigerian Pizza to highlight its fusion of culinary traditions and diverse flavors

Suggested solution

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

README references non existent pizza, Facts and Recipes folders

In the README under the "How to Contribute" section, there are references to folders that are non existent in the repo.

The issue lies within steps 3-5 here:

  1. Inside the repository, navigate to the pizza folder.
  2. Choose an appropriate subfolder (e.g., Facts, Recipes) to add your content.
  3. Create a new markdown file in the chosen subfolder.

The repo currently does not have a pizza folder or Facts and Recipes subfolders.

Suggested fix

Add in the missing folders to the repo so contributors can add in their new recipes and pizza facts. πŸ‘

OR

If the goal is to have contributors directly edit the pizza-facts and pizza-recipes files, then I would suggest the following changes to the README.

  1. Fork this repository to your own GitHub account.
  2. Clone the forked repository to your local machine.
  3. Add a new pizza fact to the pizza-facts.md file or choose to add a new recipe to the pizza-recipes.md file.
  4. Follow the existing markdown syntax to format your content. Feel free to add headings, bullet points, images, and links to enhance your contribution.
  5. Once you're done, commit your changes and push them to your forked repository.
  6. Submit a pull request to have your contribution reviewed and considered for merging into the main repository.
  7. Engage with other contributors and maintainers through comments and discussions.

Hope that helps πŸ˜„

Feature: Add compliance workflow to GitHub Action

Suggested solution

Currently, we have no GH action workflow applied in this repo to check if changes are made directly on default branch or if the title of a PR is following our convention.

Let's add the "Compliance" workflow. We can refer to the workflow in the hot repo and implement it here following what we have in the docs repo.

Feature: Pizza education and learning resources

Type of feature

πŸ• Feature

Current behavior

  • There is no resources to learn pizza.

Suggested solution

  • Pizza-Making Courses and Workshops
  • Recommended Books and Documentaries
  • Online Pizza Communities and Forums

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Feature: Add a section for Regional Pizza

Type of feature

πŸ• Feature

Current behavior

We currently have categories for pizza recipes and facts. It would be nice for people to be able to add their regional pizza styles to this repo as well.

Suggested solution

  • Add a section for regional pizza styles in the readme that replicates facts and recipes
  • Create a regional-pizza.md file and replicate the organization of pizza-facts.md
  • remove the pizza styles section from the facts doc.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.