Skip to content

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
piscesCat authored Jan 4, 2024
0 parents commit 3a9e166
Show file tree
Hide file tree
Showing 494 changed files with 60,907 additions and 0 deletions.
2 changes: 2 additions & 0 deletions .dockerignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
node_modules/
dist/
6 changes: 6 additions & 0 deletions .github/FUNDING.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# These are supported funding model platforms

open_collective: mazer
github: zuramai
ko_fi: saugi
custom: https://trakteer.id/saugi/tip
30 changes: 30 additions & 0 deletions .github/workflows/demo.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
name: Deploy demo to docs

# Will run on 2.0.0-rc.1 branch
on:
push:
branches: [ "main" ]
workflow_dispatch:

jobs:
build:
runs-on: ubuntu-latest

steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- name: Run install and build
run: yarn install
- run: yarn build
- run: yarn rtl

- name: Deploy 🚀
uses: JamesIves/[email protected]
with:
branch: docs # The branch the action should deploy to.
folder: ./dist # The folder the action should deploy.
target-folder: demo # Deploy to `demo` folder in `docs` branch
commit-message: "update: demo"


50 changes: 50 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
name: Release

on:
workflow_dispatch:
inputs:
version:
required: true
type: string
description: Release version number (semver)
prerelease:
required: false
default: false
type: boolean
description: Is it pre-release version?

# on:
# workflow_dispatch:
# inputs:
# version:
# required: true
# type: string
# description: Release version number (semver)
# prerelease:
# required: false
# default: false
# type: boolean
# description: Is it pre-release version?

jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3

- name: Install and Build 🔧
run: |
npm install
npm run production
rm dist/.gitignore
npm run zip
- name: Release
uses: softprops/action-gh-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
prerelease: ${{ github.event.inputs.prerelease }}
tag_name: ${{ github.event.inputs.version }}
files: |
dist.zip
23 changes: 23 additions & 0 deletions .github/workflows/stale.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
name: "Stale issue handler"
on:
workflow_dispatch:
schedule:
- cron: "0 0 * * *"

jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@main
id: stale
with:
stale-issue-label: "stale"
stale-issue-message: 'This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label.'
days-before-stale: 14
days-before-close: 14
operations-per-run: 1000
days-before-pr-stale: -1
days-before-pr-close: -1
exempt-issue-labels: 'type: bug, type: docs, type: feature, type: improvement, type: question' # All 'type: ' labels
- name: Print outputs
run: echo ${{ join(steps.stale.outputs.*, ',') }}
14 changes: 14 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
/vscode
.DS_Store
/node_modules

# ignore code scanning from package-lock
package-lock.json

dist.zip
.yarn/*
!.yarn/releases
!.yarn/plugins
.pnp.*
dist/*
template.zip
76 changes: 76 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at . All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
## Contributing

- Fork it (https://github.com/zuramai/mazer/fork).
- Create your feature branch (`git checkout -b my-new-feature`).
- Commit your changes (`git commit -am 'Add some feature'`).
- Push to the branch (`git push origin my-new-feature`).
- Create a new Pull Request.

## Note

Make sure to not commit generated files from your dist folder.
All changes need to be made in the source files located in the `src` folder.
- Change the `scss` files to adapt styles.
- Change the nunjucks based `html` files or the content defining `json` files to adapt layout and content.
- Change the `js` files to adapt the application code.

Always run a build and test the results before committing.
15 changes: 15 additions & 0 deletions CONTRIBUTING_ID.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
## Contributing

1. Lakukan *fork* pada (https://github.com/zuramai/mazer/fork).
2. Buat *Branch* fitur pada repositori anda. cth : (`git checkout -b my-new-feature`).
3. *Commit* perubahan yang anda lakukan. cth : (`git commit -am 'Add some feature'`).
4. *Push* ke repositorimu. cth : (`git push origin my-new-feature`).
5. Buat *Pull Request* pada repo **Mazer** (Pada poin pertama).

## Note
- Folder `./src` adalah *Working Directory* dari proyek ini.
- Proyek ini menggunakan `.scss`. silahkan lakukan perubahan pada file tersebut untuk melakukan perubahan *style* pada proyek ini.
- Edit file `html` berbasis *nunjuks* atau konten yang berbasis file `json` untuk merubah *Layout* dan Konten.
- Edit file `js` untuk melakukan perubahan skripting.

Selalu cek pekerjaan anda dengan melakukan tes dan *Build* pada perintah *Package Manager*
11 changes: 11 additions & 0 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
FROM node:16 AS frontend

WORKDIR /frontend
COPY package*.json /frontend/
RUN npm install

COPY . /frontend
RUN npm run dev

FROM nginx:latest
COPY --from=frontend /frontend/dist/ /usr/share/nginx/html
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2021-current Ahmad Saugi

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Loading

0 comments on commit 3a9e166

Please sign in to comment.