Giter Site home page Giter Site logo

open-sauced / docs Goto Github PK

View Code? Open in Web Editor NEW
71.0 71.0 61.0 115.32 MB

OpenSauced documentation built with docusaurus

Home Page: http://opensauced.pizza/docs

License: MIT License

Dockerfile 3.18% JavaScript 86.16% CSS 10.66%
docs docusaurus insights

docs'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

docs's People

Contributors

0-vortex avatar adiati98 avatar anush008 avatar bdougie avatar bekahhw avatar cbid2 avatar devjster avatar diivi avatar dominicduffin1 avatar gabrielabubakar avatar haimantika avatar huynhicode avatar isabensusan avatar jdwilkin4 avatar jpmcb avatar lymah123 avatar marcusgchan avatar mleisy avatar muniir1 avatar mzhoffman avatar nickytonline avatar nightknighto avatar ogdev-01 avatar omkarph avatar rameshchandra8520 avatar ritadee avatar sadiejay avatar samuelsycamore avatar smhussain5 avatar teachjenntech 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  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  avatar  avatar

docs's Issues

Feature: add post metadata

Type of feature

Feature

Current behavior

Anyone adding a new post or article is not officially credited outside of GitHub contributions

Desired solution

Use metadata to add author information and other social links

Additional context

No response

Code of Conduct

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

Feature: Mention of Contributors

Type of feature

๐Ÿ• Feature

Current behavior

I was looking through the repo's readme file and noticed that there is no mention of the contributors. It can cause them to feel disheartened.

Suggested solution

My colleague Josh Goldberg has created a GitHub Action that automatically posts contributors if they raise an issue or get their PR merged. I've seen it in action(no pun intended) and it's pretty effective productivity-wise.

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: New favicon

Type of feature

๐Ÿ• Feature

Current behavior

We have new brand assets and we will need to update the favicon to the below link.

https://github.com/open-sauced/assets/blob/main/logos/slice-White-Orange.png

image

Suggested solution

The logo will need to be downloaded and renamed and replaced here ๐Ÿ‘‰๐Ÿพfavicon.ico. You can use a favicon generator to create the multiple sizes

Additional context

Hacktoberfest contributions welcomed

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: add insights guide

Similar to the Chrome extension guide we need user docs in the "Introduction to OpenSauced" section.

  • highlights
  • Insight pages
  • Profile pages
  • Settings
  • Emails
  • notifications

FAQs: questions we should answer

  1. How do I find good first issues.
  2. My contribution doesn't show how do it get it to.
  3. I want to find X language or frameworks data, how do I request it.

This is a list of questions I got when presenting at OSCA.

Answers

  1. Look for good first repos or people first. They will lead you to issues worth working on.
  2. Indexing by adding your pr to a highlight or creating an insight page.
  3. open-Sauced/feedback

Feature: add official URL to the repository details page

Is your feature request related to a problem? Please describe.

When clicking the repository display settings (top right cog icon as a repository admin), the URL field is empty.

Describe the solution you'd like

Fill out the URL input with the default value http://open-sauced.github.io/docs.opensauced.pizza and let the CNAME do its course.

Think only @bdougie can do that?

Describe alternatives you've considered

Ping maintainers team for more information

Additional context

Feature: Chrome extenstion docs are needed

Type of feature

๐Ÿ• Feature

Current behavior

@diivi I think this feature needs some documentation. We are starting to add features that need some explanation.

upvoting - Needs documentation on how and why upvote. Connection to hot.opensauced for see votes is needs an explanation
add to insights dropdown - needs an explanation of insights and the how and why for creating a page.

Your interpretation in the documentation would be great.

Suggested solution

Create a guide for hot & insights.

Additional context

open-sauced/ai#77

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: document more on "npm run push"

Type of feature

๐Ÿ“ Documentation

Current behavior

Current docs mentioned it as an experiement. We need to encourage more contributors to use it.

You can also experiment with conventional commits by doing:

npm run push

Suggested solution

Expand on why it is important to the release process.

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

Bug: Mentions of `main` branch need to be changed to `beta`

Describe the bug

Project is now using beta branch as default. There are various mentions in the docs to use the now outdated main branch. Some main mentions may be out of scope and need verification from maintainers

Steps to reproduce

Go to Line 45 in introduction-to-contribution.md you will see main referenced.

There are a number of references to the main branch by searching the repo, want to be clear what needs to be changed and what needs to be kept.

Mentions:

  • resolve-merge-conflicts.md: Changing main involves changing shell commands.
    • Verify with maintainer
  • setting-up-a-new-repository.md: Changing from main would include changing screenshots as well. This page is targeted to maintainers for new Open Sauced related changes, may be out of scope of current issue.
    • Verification needed
  • semantic-release.md: Documentation on npm package, may be out of scope.
    • Verification needed.

Affected services

docs.opensauced.pizza

Platforms

Desktop, Mobile, Tablet

Browsers

Chrome, Firefox

Environment

Production

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: explore markdown ecosystem plugins for documentation

Is your feature request related to a problem? Please describe.

Not related to a particular issue but it could fix a couple.

We can extend docusaurus with plugins

Describe the solution you'd like

Explore both ways:

Describe alternatives you've considered

Have @mtfoley poke me to write "contributing to docs" docs sooner ๐ŸŽƒ

Additional context

Coupling plugins can give us some advantages like:

  • GFM compatibility (wiki+docs)
  • extended testing command
  • responsive assets
  • developer experience improvements writing docs

This is porting open-sauced#1103 to its proper repository

feature: update the logo

Type of feature

Select the type of feature request, the lowercase should also be the PR prefix.

  • ๐Ÿ• Feature
  • ๐Ÿ› Bug Fix
  • ๐Ÿ“ Documentation Update
  • ๐ŸŽจ Style
  • ๐Ÿง‘โ€๐Ÿ’ป Code Refactor
  • ๐Ÿ”ฅ Performance Improvements
  • โœ… Test
  • ๐Ÿค– Build
  • ๐Ÿ” CI
  • ๐Ÿ“ฆ Chore (Release)
  • โฉ Revert

Current behavior

The logo font is inter - https://github.com/open-sauced/assets/blob/main/Logos%20/wordmark-Black%20Text.png

image

Suggested solution

Replace this
Screen Shot 2022-10-05 at 2 28 09 PM

Code of Conduct

By submitting this issue, you agree to follow our Code of Conduct.

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

Contributing Docs

If you plan on contributing code please read - Contribution Guide

  • I agree to follow this project's Contribution Docs

Bug: contribution guide page showing 404 error

Describe the bug

contribution page is showing 404 error.
Link is broken

Steps to reproduce

Visit any of the repos and click the "contributing guide" link

Affected services

opensauced.pizza, admin.opensauced.pizza, docs.opensauced.pizza

Platforms

Desktop

Browsers

Firefox

Environment

Production

Additional context

No response

Code of Conduct

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

bug: dead contributing link in readme

Describe the bug

The Contributing guide link in the README is broken.

Right now it links to https://github.com/open-sauced/docs.opensauced.pizza/blob/main/CONTRIBUTING.md which gives a 404.

I believe it is supposed to link to either

Steps to reproduce

Click on the link called Contributing guide under ๐Ÿค Contributing in the README.

Affected services

docs.opensauced.pizza

Platforms

Desktop, Mobile, Tablet, TV, VR

Browsers

Chrome, Firefox, Safari, Edge, Opera

Environment

Production, Development, Testing

Additional context

No response

Code of Conduct

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

Feature: add maintainer category docs

Is your feature request related to a problem? Please describe.

Maintainer-level docs are becoming a requirement.

Describe the solution you'd like

Add maintainer docs category explaining:

  • how to create a new repo
  • how to use octoherd-script-sync-repo-settings
  • how to use octoherd-script-copy-labels
  • how to use @octoherd/script-sync-branch-protections
  • how to add missing features
  • how to enable @open-sauced/semantic-release-conventional-config for an npm library or a docker app
  • other information the triage team considers to set the bar for maintainer support

Describe alternatives you've considered

Let everyone fail and retry 3-5 years until they become zen masters

Additional context

Feature: chrome extension add post to highlight

Type of feature

๐Ÿ“ Documentation

Current behavior

We need to create documentation for the post to highlight features in the extension.

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: add "hot.opensauced.pizza" category

Type of feature

๐Ÿ“ Documentation

Current behavior

Currently there is no category for hot repo.

Suggested solution

Make a new category for the hot repo, and possibly make a new doc page in it called "Getting Started", which guides user through the installation and running the project (probably just clone the readme of the project, but without the extra steps that are not functioning like tests).

Additional context

Similar to the Chrome extension guide we need user docs in the "Introduction to OpenSauced" section.

  • Voting
  • Filtering
  • Searching

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: Rearrange some sections

          The content looks good, I am not everything is place in the correct sections for discoverability. 

Today the Contributing and Technical Guide overlap a lot, and the "Welcome page" now includes a highlight, but after considering, it should be separate.

New layout

Start Here

  • Introduction
  • Highlights
  • Insights
  • Collaborations (Soon)
  • FAQs

Community

  • ...that list here

Contributing Guide

  • combine the technical and contributing list

I can clean this up after this is merged unless you have time this weekend @CBID2. I am going to be waiting in an airport for awhile and have time.

Originally posted by @bdougie in #103 (comment)

Style: clarifications to "Introduction to Contributing"

Type of feature

๐ŸŽจ Style

Current behavior

  1. In the "Setup" section a first-time contributor might not know (or might appreciate a refresher) on how to fork and clone a repo.

  2. In the "Testing" section it's not stated whether this step applies to the docs, but I don't think it does. Running npm test in this repo gives npm ERR! Missing script: "test", and I don't see any tests in this repo.

  3. In the "Pull Requests" section

    1. The bolded line under the section heading reads "We actively welcome your pull requests, however linking your work to an existing issue is preferred," but item 10 in the instructions below says "Unsolicited code is welcomed, but an issue is required for announce your intentions. PR's without a linked issue will be marked invalid and closed." These are somewhat contradictory, with the first suggesting a linked issue is preferred and the second saying a linked issue is required.

    2. In item 1, some contributors might like a guide to creating branches.

    3. In item 3, how should a contributor decided whether the code they've written should be tested?

    4. In item 5, contributors might benefit from knowing where to store images they'd like to add if there's a particular directory for images, and how to refer to a file in the image directory within the directory in which they're making changes.

  4. In the "Issues" section, the sentence "... please assign yourself by commenting on the following word .take" is maybe slightly confusing.

  5. In the "Funding" section, the link to funding.yml is broken, and seems to possibly not be applicable currently anyway.

Suggested solution

  1. Add a link to the GitHub doc on forking and cloning a repo and clarification about changing the link in the codeblock to the contributor's own cloned repo link.

  2. Add clarification, either on how to fix this error, or that this step does not apply to changes made in the docs.opensauced.pizza repo.

    1. These two sentences should be brought into full agreement, affirming either the preference or requirement for a linked issue.
    2. Perhaps a link to branching would be helpful.
    3. Add clarification about when testing is needed.
    4. Add instructions about where to store images and how to refer to them from other directories.
  3. This could maybe be rephrased to something like "... please assign yourself by commenting on the issue with .take".

  4. Change or remove the sentence "If you have made any contributions to the projectd directly or indirectly, please consider adding your profile to the funding.yml."

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 more opensauced.pizza branding

Type of feature

Style

Current behavior

We only have one logo and no pizza

Desired solution

Add more sauce to the footer, the header and, potentially, the navigation bars.

Announcement bar with a default message would be nice.

Additional context

No response

Code of Conduct

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

Bug: grammatical error in the contributing docs

Describe the bug

I noticed an error in grammar while using the open-sourced contribution docs
This error can be found on the 10th item of the Pull Requests section of the Intro to Contributing guide

Steps to reproduce

Visit the Pull Requests section of the Intro to Contributing Guide. Read through the 10th item on the list.

Affected services

docs.opensauced.pizza

Platforms

No response

Browsers

Chrome

Environment

Production

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: Community Section

Type of feature

๐Ÿ• Feature

Current behavior

We could use a section for to announce our events and opportunities for contributors and maintainers.

Suggested solution

Section named "Community" with a list of links

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

Bug: download book link goes to 404

Describe the bug

The download book link in the footer takes you to a 404

image

Steps to reproduce

  1. Go to https://docs.opensauced.pizza
  2. Click Download book
  3. See 404

Browsers

Chrome

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

Bug: Logo does not respect darkmode

Describe the bug

Screen Shot 2022-10-18 at 2 56 04 PM

Steps to reproduce

To fix this, we needs to check for dark mode and swap out the image. You can either right click and download or click the download image button.

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

This is outline in the docs to do here: https://github.com/open-sauced/docs.opensauced.pizza/blob/main/docusaurus.config.js#L27

the line that should be updated to respect dark mode https://github.com/open-sauced/docs.opensauced.pizza/pull/55/files

Affected services

docs.opensauced.pizza

Platforms

No response

Browsers

No response

Environment

No response

Additional context

https://github.com/open-sauced/docs.opensauced.pizza/blob/main/docusaurus.config.js#L27

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: document v2 and v3 of @open-sauced/semantic-release-conventional-config

Type of feature

Documentation

Current behavior

@open-sauced/semantic-release-conventional-config has alphas and betas and it's mostly there

Desired solution

Version 3 is incoming with fully dockerized build and action, one option completely removing the requirement for node and versioned files except the workflow executing the release.

The documentation should reflect and fully explain the convergence between v2 and v3 updates :pizz

Additional context

blocked until open-sauced/semantic-release-conventional-config#21

Code of Conduct

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

Feature: Fetching data from the GitHub graphql API needs to be rewritten

Type of feature

๐Ÿ• Feature

Current behavior

This content is our of date and needs to be update for recommending https://api.opensauced.pizza

Suggested solution

Removing all GraphQL mentions ans point users to using the REST api.

https://api.opensauced.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: Update Favicon to Pizza

Type of feature

๐Ÿ• Feature

Current behavior

The favicon is not legible.

Screen Shot 2023-05-05 at 6 44 30 AM

Suggested solution

To solve this issue, you have to replace the current docs.opensauced.pizza (the one on the left) favicon with the hot.opensauced.pizza (the one on the right) favicon.

227435561-15c3b757-8b2a-49e5-a317-662152aff338

Additional context

Previous issue #65 was meant to fix this and it didn't

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 Instructions for setting up authentication to the documentation

Type of feature

๐Ÿ“ Documentation

Current behavior

This question came up during the Octernship assignment a lot, maybe adding an authentication section to the Contributing Guide will help future contributors.

Suggested solution

Add the section "Set up Authentication" to the Contributing Guide. This will have the steps that a user can follow to obtain an Auth token from hot.opensauced.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

docs: Explanation doc on what branches do and mean within OpenSauced

Type of feature

๐Ÿ“ Documentation

Current behavior

We use the [alpha, beta, main] pattern for all projects and some first contributors can get confused on this.

Suggested solution

Create a new doc explaining the difference between the branches and how they work with out automation.

Additional context

This should be written by a new contributor to capture the beginner context.

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: unable to copy repository labels from opensauced.pizza

Describe the bug

This worked for explore:

npx octoherd-script-copy-labels \
  --template "open-sauced/open-sauced" \
  -T $GH_TOKEN \
  -R "open-sauced/docs.opensauced.pizza" 

We don't have any labels

To Reproduce

Expected behavior

Screenshots

Desktop

  • OS:
  • Browser:
  • Version:

Smartphone

  • Device:
  • OS:
  • Browser:
  • Version:

Additional context

maybe @bdougie has some ideas on workarounds if the script doesn't work

Feature: make repository tooling more compact

Type of feature

Refactor

Current behavior

There are some unneeded files hanging around like .czrc and release.config.js, extraneous .gitattributes even.

Desired solution

Clean up some of these files, update dependencies to latest packages.

Additional context

No response

Code of Conduct

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

docs: Rename "Technical Guide" category to "app.opensauced.pizza"

Type of feature

๐Ÿ“ Documentation

Current behavior

Since the docs.opensauced is supposed to be the official documentation for all open-sauce repos, having a category with a very general name like "Technical Guide" is very confusing, especially that it focuses mostly on just app.opensauce, without even referencing it.
image

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: Usage gifs

Type of feature

๐Ÿ• Feature

Current behavior

There is no guide on how to use the product and we need the following features explained via gif.

I will work on this for the 100daysofOSS

Suggested solution

  • Highlights
  • Collaborations
  • Insight Pages

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: document default community files for our existing repositories

Is your feature request related to a problem? Please describe.

Since getting default community files over at open-sauced/.github we are not required to duplicate some of the boilerplate when creating new repositories.

Describe the solution you'd like

Simplify GitHub documentation for community files and give visual examples for how they are used within @open-sauced

Describe alternatives you've considered

Make everyone silently wonder why things are so cool and just ๐Ÿคท often.

Additional context

Feature: add missing contributing docs

Is your feature request related to a problem? Please describe.

Fast forwarding docs deployment we skipped at least one essential article like "how to add a new document in the docs endpoint".

Describe the solution you'd like

Potentially have a contributor who's inexperienced with docusaurus add this document portraying their experience and we improve upon it.

Describe alternatives you've considered

Link people to docusaurus and forcing them to become masters of all.

Additional context

docs: Add "api.opensauced.pizza" category

Type of feature

๐Ÿ“ Documentation

Current behavior

Right now there is no category for the API project.

Suggested solution

Make a new category for the api repo, and possibly make a new doc page in it called "Getting Started", which guides user through the installation and running the project (probably just clone the readme of the project, but without the extra steps that are not functioning like tests).

Adding the doc page so that the category would not be empty.

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: Found some Markdown errors

Describe the bug

I found some Markdown errors in the "Welcome to Community" file. This something I will work on.

Steps to reproduce

N/A

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

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.