├── .env.example ├── .eslintrc.json ├── .github ├── CODEOWNERS ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── HACKING.md ├── ISSUE_TEMPLATE │ ├── BUG.yml │ ├── FEATURE_REQUEST.yml │ └── config.yml ├── PULL_REQUEST_TEMPLATE │ └── PULL_REQUEST_TEMPLATE.md └── img │ └── github-banner.svg ├── .gitignore ├── .prettierignore ├── .prettierrc.json ├── LICENSE ├── README.md ├── lib └── prisma.ts ├── next-env.d.ts ├── next.config.js ├── package-lock.json ├── package.json ├── pages ├── _app.tsx ├── _document.tsx ├── api │ ├── auth │ │ └── [...nextauth].ts │ └── hello.ts └── index.tsx ├── postcss.config.js ├── prisma └── schema.prisma ├── public ├── favicon.ico └── vercel.svg ├── styles └── globals.css ├── tailwind.config.js └── tsconfig.json /.env.example: -------------------------------------------------------------------------------- 1 | # Environment variables declared in this file are automatically made available to Prisma. 2 | # See the documentation for more detail: https://pris.ly/d/prisma-schema#using-environment-variables 3 | 4 | # Prisma supports the native connection string format for PostgreSQL, MySQL and SQLite. 5 | # See the documentation for all the connection string options: https://pris.ly/d/connection-strings 6 | 7 | # Database URL 8 | DATABASE_URL= 9 | 10 | # Required for email auth – setup instructions here: https://next-auth.js.org/providers/email#configuration 11 | EMAIL_SERVER=smtp://:@: 12 | EMAIL_FROM=noreply@example.com 13 | 14 | # Generate a random secret here: https://generate-secret.vercel.app/32 15 | NEXTAUTH_SECRET= 16 | -------------------------------------------------------------------------------- /.eslintrc.json: -------------------------------------------------------------------------------- 1 | { 2 | "extends": ["next/core-web-vitals", "prettier"] 3 | } 4 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # Learn how to add code owners here: 2 | # https://help.github.com/en/articles/about-code-owners 3 | 4 | # These owners will be the default owners for everything in the repo. 5 | # Order is important; the last matching pattern takes the most precedence. 6 | 7 | * @mfts 8 | /.github/ @mfts -------------------------------------------------------------------------------- /.github/CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | 2 | # Contributor Covenant Code of Conduct 3 | 4 | ## Our Pledge 5 | 6 | We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. 7 | 8 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. 9 | 10 | ## Our Standards 11 | 12 | Examples of behavior that contributes to a positive environment for our community include: 13 | 14 | * Demonstrating empathy and kindness toward other people 15 | * Being respectful of differing opinions, viewpoints, and experiences 16 | * Giving and gracefully accepting constructive feedback 17 | * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 18 | * Focusing on what is best not just for us as individuals, but for the overall community 19 | 20 | Examples of unacceptable behavior include: 21 | 22 | * The use of sexualized language or imagery, and sexual attention or advances of any kind 23 | * Trolling, insulting or derogatory comments, and personal or political attacks 24 | * Public or private harassment 25 | * Publishing others' private information, such as a physical or email address, without their explicit permission 26 | * Other conduct which could reasonably be considered inappropriate in a professional setting 27 | 28 | ## Enforcement Responsibilities 29 | 30 | Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 31 | 32 | Community leaders 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, and will communicate reasons for moderation decisions when appropriate. 33 | 34 | ## Scope 35 | 36 | This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. 37 | 38 | ## Enforcement 39 | 40 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at marc@papermark.io. All complaints will be reviewed and investigated promptly and fairly. 41 | 42 | All community leaders are obligated to respect the privacy and security of the reporter of any incident. 43 | 44 | ## Enforcement Guidelines 45 | 46 | Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: 47 | 48 | ### 1. Correction 49 | 50 | **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. 51 | 52 | **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. 53 | 54 | ### 2. Warning 55 | 56 | **Community Impact**: A violation through a single incident or series of actions. 57 | 58 | **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. 59 | 60 | ### 3. Temporary Ban 61 | 62 | **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. 63 | 64 | **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. 65 | 66 | ### 4. Permanent Ban 67 | 68 | **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. 69 | 70 | **Consequence**: A permanent ban from any sort of public interaction within the community. 71 | 72 | ## Attribution 73 | 74 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 75 | 76 | Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. 77 | 78 | For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. 79 | 80 | [homepage]: https://www.contributor-covenant.org 81 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html 82 | [Mozilla CoC]: https://github.com/mozilla/diversity 83 | [FAQ]: https://www.contributor-covenant.org/faq 84 | [translations]: https://www.contributor-covenant.org/translations 85 | -------------------------------------------------------------------------------- /.github/CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Papermark 2 | 3 | Thank you for your interest in becoming a contributor to Papermark. We welcome all contributions, no matter how large or small. Please take a moment to review this document in order to make effective contributions. 4 | 5 | - [Have a Question?](#question) 6 | - [Issues and Bugs](#issue) 7 | - [Feature Requests](#feature) 8 | - [Contributing](#contribute) 9 | - [Submission Guidelines](#guidelines) 10 | - [Release Process](#release) 11 | 12 | ## Have a Question? 13 | 14 | Have a question about Papermark? Ask questions or feel free to talk about anything Papermark related in our [GitHub Discussions forum](https://github.com/mfts/papermark/discussions). 15 | 16 | ## Discover a Bug? 17 | 18 | Something not working as expected? Let's see if we can work together to get it resolved. If you believe you have discovered a bug, please open an issue on the GitHub repository and select the "Bug Report" template. 19 | 20 | [Open an issue](https://github.com/mfts/papermark/issues/new/choose) 21 | 22 | ## Missing Feature? 23 | 24 | Would you like to see a new feature added to Papermark? Let's discuss it! All features for Papermark should begin as an Issue on the GitHub repository. Select the "Feature Request" issue template and engage with the community to come to a collective solution to the feature request. 25 | 26 | [Create a Feature Request](https://github.com/mfts/papermark/issues/new/choose) 27 | 28 | ## Contributing 29 | 30 | Want to contribute to Papermark? Great! We welcome all contributions no matter how large or small. Please begin by taking a look at the open issues and get involved in the conversation. We would be happy to assign you to an issue and help you get started. 31 | 32 | Get started by reading the [HACKING.md](./HACKING.md) document, and come back here when you're ready to submit. 33 | 34 | ### Submission Guidelines 35 | 36 | #### Commit Conventions 37 | 38 | This project strictly adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for creating human readable commit messages with appropriate automation capabilities, such as changelog generation. 39 | 40 | ##### Commit Message Format 41 | 42 | Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject: 43 | 44 | ```text 45 | (optional ): 46 | 47 | 48 | 49 |