codeninjasgg/roblox-royale-camp
1
0
Fork 0
mirror of https://github.com/codeninjasgg/roblox-royale-camp.git synced 2024-11-24 08:17:52 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
A companion site for the Roblox Royale Camp!
25 commits 8 branches 0 tags 131 KiB
JavaScript 98.8%
SCSS 1.2%
Find a file
dependabot[bot] 7af5588e65
Bump marked from 1.1.1 to 4.0.10 
Bumps [marked](https://github.com/markedjs/marked) from 1.1.1 to 4.0.10.
- [Release notes](https://github.com/markedjs/marked/releases)
- [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json)
- [Commits](https://github.com/markedjs/marked/compare/v1.1.1...v4.0.10)

---
updated-dependencies:
- dependency-name: marked
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2022-01-15 02:45:31 +00:00
.github/workflows Initial commit 2020-08-02 11:11:08 -07:00
.vscode Initial commit 2020-08-02 11:11:08 -07:00
pages Update Hall of Fame.md 2020-09-04 16:34:46 -07:00
src Initial commit 2020-08-02 11:11:08 -07:00
static Update favicon.svg 2020-08-03 09:57:19 -07:00
.env.sample Initial commit 2020-08-02 11:11:08 -07:00
.gitignore Initial commit 2020-08-02 11:11:08 -07:00
LICENSE Initial commit 2020-08-02 11:11:08 -07:00
package-lock.json Bump marked from 1.1.1 to 4.0.10 2022-01-15 02:45:31 +00:00
package.json Bump marked from 1.1.1 to 4.0.10 2022-01-15 02:45:31 +00:00
README.md updated the readme 2020-08-03 11:26:33 -07:00

README.md

Roblox Royale Camp

A companion site for the Roblox Royale Camp

GitHub Workflow Status GitHub repo size

Visit the site!

Editing Documents 🖊

Edit Existing (Online) 📝

  1. Visit your live site.
  2. Navigate to the page that you wish to edit.
  3. Click the link at the top of the page to edit the document.
  4. Commit your changes.

Create New (Online) 💡

  1. Visit the pages directory on GitHub.
  2. Navigate: Add file > Create new file.
  3. Commit the new file.

Work on Desktop

  1. Open your repository in your favorite code editor.
  2. Edit the contents of the pages directory.
  3. Commit your changes.

Deployment 🚀

  1. Set your .env secrets in your GitHub repository: Settings > Secrets > New Secret.
  2. Now, every push will trigger a deployment!

Created with ☕ by Code Ninjas Garden Grove