├── .eslintrc.json
├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── enhancement-request.md
│ ├── feature_request.md
│ └── pull_request.md
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── SECURITY.md
├── app
├── (public)
│ ├── privacy
│ │ └── page.tsx
│ └── terms
│ │ └── page.tsx
├── blogs
│ ├── [slug]
│ │ └── page.tsx
│ ├── layout.tsx
│ └── page.tsx
├── editor
│ ├── old
│ │ └── page.tsx
│ └── page.tsx
├── globals.css
├── layout.tsx
├── not-found.tsx
└── page.tsx
├── components.json
├── components
├── icons.tsx
├── layout
│ ├── Header.tsx
│ ├── LandingHeader.tsx
│ ├── LandingPage.tsx
│ ├── OldLandingPage.txt
│ └── background-gradient.tsx
├── sections
│ ├── CTASection.tsx
│ ├── FAQSection.tsx
│ ├── FeatureSection.tsx
│ └── PricingSection.tsx
├── shadow-manager.tsx
├── shared
│ ├── Editor.tsx
│ ├── Editor.v2.tsx
│ ├── Header.v2.tsx
│ ├── NotAvailable.tsx
│ ├── PeerlistSpotlight.tsx
│ ├── ShowcaseImage.tsx
│ ├── ValidatedInput.tsx
│ ├── buttons
│ │ └── ExportButton.tsx
│ ├── new.txt
│ ├── types.ts
│ └── utils.ts
├── tailwind-indicator.tsx
├── text-manager.tsx
├── theme-provider.tsx
├── theme-toggle.tsx
└── ui
│ ├── accordion.tsx
│ ├── alert.tsx
│ ├── avatar.tsx
│ ├── badge.tsx
│ ├── button.tsx
│ ├── card.tsx
│ ├── dialog.tsx
│ ├── dropdown-menu.tsx
│ ├── input.tsx
│ ├── label.tsx
│ ├── popover.tsx
│ ├── select.tsx
│ ├── sheet.tsx
│ ├── slider.tsx
│ ├── tabs.tsx
│ ├── textarea.tsx
│ ├── toggle-group.tsx
│ └── toggle.tsx
├── config
└── config.ts
├── content
├── hacktoberfest.mdx
└── introduction.mdx
├── lib
├── blog.ts
├── canvas.ts
├── constants.ts
├── extractColors.ts
├── fonts.ts
└── utils.ts
├── next.config.mjs
├── package-lock.json
├── package.json
├── postcss.config.mjs
├── public
├── apple-touch-icon.png
├── demo-hero.png
├── favicon.ico
├── feature-demo.png
├── icon-192-maskable.png
├── icon-192.png
├── icon-512-maskable.png
├── icon-512.png
├── mockly-demo.png
├── peerlist-dark.svg
├── peerlist-light.svg
├── peerlist.png
├── showcase-dark.png
├── showcase-light.png
├── showcase.png
└── users.png
├── pull_request_template.md
├── showcase
├── hacktoberfest.png
└── introduction.png
├── tailwind.config.ts
└── tsconfig.json
/.eslintrc.json:
--------------------------------------------------------------------------------
1 | {
2 | "extends": "next/core-web-vitals"
3 | }
4 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: "[Bug] Sample Title"
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ## Bug Report Template
11 |
12 | ### **Describe the bug**
13 | _A clear and concise description of what the bug is. Example: "The application crashes when..."_
14 |
15 | ### **To Reproduce**
16 | Steps to reproduce the behavior:
17 | 1. Go to '...'
18 | 2. Click on '...'
19 | 3. Scroll down to '...'
20 | 4. See error
21 |
22 | ### **Expected behavior**
23 | _A clear and concise description of what you expected to happen._
24 |
25 | ### **Screenshots**
26 | _If applicable, add screenshots to help explain your problem._
27 |
28 | ### **Environment (please complete the following information):**
29 | - **OS**: [e.g., Windows, macOS]
30 | - **Browser**: [e.g., Chrome, Safari]
31 | - **Version**: [e.g., 22]
32 | - **Other relevant environment details** (e.g., Node version, database version)
33 |
34 | ### **Additional context**
35 | _Add any other context about the problem here (e.g., error logs, stack traces)._
36 |
37 | ---
38 |
39 | ### **Optional Sections (if relevant):**
40 |
41 | - **Priority (Low / Medium / High)**
42 | - **Is this issue blocking your progress?**
43 | - **Can you submit a PR to fix this?**
44 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/enhancement-request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Enhancement Request
3 | about: Improve an existing feature for this project
4 | title: "[Enchancement] Sample Title"
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ## Enhancement Request Template
11 |
12 | ### **Is your enhancement request related to a problem? Please describe.**
13 | _A clear and concise description of the problem you're facing or the limitation in the existing feature. Example: "The current implementation does not allow..."_
14 |
15 | ### **Describe the enhancement you'd like**
16 | _A clear and concise description of what you would like to see improved. Example: "I would like the feature to..."_
17 |
18 | ### **Describe alternatives you've considered**
19 | _A clear and concise description of alternative approaches or workarounds. Example: "I tried solving this by..."_
20 |
21 | ### **Possible Implementation Details**
22 | _If applicable, describe how the enhancement could be implemented. Include code snippets, mockups, or diagrams if helpful._
23 |
24 | ### **Additional context**
25 | _Add any other context, screenshots, or references relevant to the enhancement here._
26 |
27 | ---
28 |
29 | ### **Optional Sections (if relevant):**
30 |
31 | - **Priority (Low / Medium / High)**
32 | - **Are you willing to submit a PR for this enhancement?**
33 | - **Does this enhancement require changes in documentation?**
34 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: "[Feature Request] Sample Title"
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ## Feature Request Template
11 |
12 | ### **Is your feature request related to a problem? Please describe.**
13 | _A clear and concise description of the problem you're facing. Example: "It is frustrating when I cannot..."_
14 |
15 | ### **Describe the solution you'd like**
16 | _A clear and concise description of what you want to happen. Example: "I would like to have..."_
17 |
18 | ### **Describe alternatives you've considered**
19 | _A clear and concise description of any alternative solutions or features you've considered. Example: "Another way to solve this might be..."_
20 |
21 | ### **Additional context**
22 | _Add any other context or screenshots about the feature request here._
23 |
24 | ---
25 |
26 | ### **Optional Sections (if relevant):**
27 |
28 | - **Priority (Low / Medium / High)**
29 | - **Are you willing to contribute to this feature?**
30 | - **Does this feature require any third-party libraries or changes in existing ones?**
31 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/pull_request.md:
--------------------------------------------------------------------------------
1 | ## Pull Request Template
2 |
3 | ### **Description**
4 | _A clear and concise description of what this pull request does. Please include the purpose and details of the changes being made._
5 |
6 | ### **Related Issue**
7 | _If this PR is related to an open issue, please provide a link to the issue here._
8 |
9 | Closes # (issue)
10 |
11 | ### **Changes Made**
12 | _List out the specific changes made in this pull request:_
13 | - _Changed X to Y..._
14 | - _Refactored Z..._
15 |
16 | ### **Type of Change**
17 | _Select the type of change made with this pull request:_
18 |
19 | - [ ] Bug fix (non-breaking change that fixes an issue)
20 | - [ ] New feature (non-breaking change that adds functionality)
21 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
22 | - [ ] Documentation update
23 |
24 | ### **Screenshots (if applicable)**
25 | _Add screenshots, if necessary, to illustrate changes made to the UI or visual elements._
26 |
27 | ### **How Has This Been Tested?**
28 | _Explain how the changes have been tested. Include testing framework details, if any, and how the results can be reproduced._
29 |
30 | - _Tested with unit tests_
31 | - _Manually tested on local environment_
32 |
33 | ### **Checklist**
34 | _Check off the following items before submitting the pull request:_
35 |
36 | - [ ] My code follows the style guidelines of this project
37 | - [ ] I have performed a self-review of my code
38 | - [ ] I have commented my code, particularly in hard-to-understand areas
39 | - [ ] I have made corresponding changes to the documentation
40 | - [ ] My changes generate no new warnings
41 | - [ ] I have added tests that prove my fix is effective or that my feature works
42 | - [ ] New and existing unit tests pass locally with my changes
43 | - [ ] Any dependent changes have been merged and published in downstream modules
44 |
45 | ### **Additional Context**
46 | _Provide any additional context or information that might be useful for the reviewers._
47 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 | /.pnp
6 | .pnp.js
7 | .yarn/install-state.gz
8 |
9 | # testing
10 | /coverage
11 |
12 | # next.js
13 | /.next/
14 | /out/
15 |
16 | # production
17 | /build
18 |
19 | # misc
20 | .DS_Store
21 | *.pem
22 |
23 | # debug
24 | npm-debug.log*
25 | yarn-debug.log*
26 | yarn-error.log*
27 |
28 | # local env files
29 | .env*.local
30 |
31 | # vercel
32 | .vercel
33 |
34 | # typescript
35 | *.tsbuildinfo
36 | next-env.d.ts
37 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | suryanshsingh.general@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to Mockly
2 |
3 | 🎉 **Welcome, Hacktoberfest Contributors!** 🎉
4 | We’re excited that you’re here to help make Mockly even better. Whether it’s fixing bugs, adding new features, or improving documentation, we’re thrilled to have you onboard.
5 |
6 | ## Getting Started
7 |
8 | 1. **Fork the Repo**: Click the "Fork" button on the top-right of the repository page.
9 | 2. **Clone the Fork**:
10 | ```
11 | git clone https://github.com/YOUR-USERNAME/mockly.git
12 | cd mockly
13 | ```
14 | 3. **Install Dependencies**:
15 | ```
16 | npm install
17 | ```
18 | 4. **Create a New Branch**:
19 | ```
20 | git checkout -b feature/your-feature-name
21 | ```
22 |
23 | ## How to Contribute
24 |
25 | - **Check Existing Issues**: We have a list of issues tagged for **Hacktoberfest** that you can start with. Feel free to pick one or suggest your own improvements.
26 | - **Create an Issue**: If you find a bug or have a feature request that isn’t listed, open a new issue and explain the problem or idea.
27 | - **Submit Pull Requests (PRs)**: Once you’ve made your changes, push your branch to your fork and submit a pull request to the `main` branch.
28 |
29 | ## Areas to Contribute
30 |
31 | Here are some ideas for contributions:
32 | - **Fix Bugs**: Check for issues like performance problems (e.g., canvas flickering).
33 | - **Add Features**: More export options, custom screen sizes, UI improvements, etc.
34 | - **Improve Documentation**: Help make our docs clearer and more beginner-friendly.
35 | - **Code Review**: Provide feedback on others’ PRs and help keep the project quality high.
36 |
37 | ## Hacktoberfest Guidelines
38 |
39 | To ensure your PRs count toward Hacktoberfest:
40 | - Your pull request must be **merged**, **approved**, or tagged with **hacktoberfest-accepted** by a maintainer.
41 | - Spammy or low-quality PRs will not be accepted (we’re all here to learn and improve together!).
42 |
43 | ## Code of Conduct
44 |
45 | Be respectful, kind, and encouraging. We’re here to support each other and grow as a community. Please read our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing.
46 |
47 | ## Thank You!
48 |
49 | Your contributions mean the world to us! Let’s build something great together. Happy Hacktoberfest! 💻🎃
50 |
51 | If you have any questions, feel free to open an issue or reach out directly. 😊
52 |
53 |
54 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2024 Suryansh Singh
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Mockly 🎨
2 | [](https://www.mockly.site)
3 | [](https://nextjs.org/)
4 | [](https://reactjs.org/)
5 | [](https://www.typescriptlang.org/)
6 | [](https://tailwindcss.com/)
7 | [](https://ui.shadcn.com/)
8 | [](https://opensource.org/licenses/MIT)
9 |
10 |
11 | 
12 |
13 |
14 | Mockly is an open-source tool that allows developers to create professional-looking screenshots and mockups with ease. With Mockly, you can pick, place, and zoom—done. It's designed for fast, stress-free mockups for developers who'd rather code than design.
15 |
16 |
17 |
18 | ## ✨ Features
19 |
20 | 1. **Instant Mockups**: Upload, tweak, done. It's like magic, but without the wand.
21 | 2. **Multi-device Preview**: Instantly see how your designs look on any screen size—because nobody has time for resizing.
22 | - **Example**: Select "Screen Size" dropdown menu to automatically generate views for mobile, tablet, and desktop versions.
23 | 3. **Zoom & Place**: Precisely position your screenshot, and zoom in or out like a pro—minus the struggle.
24 | - **Example**: Drag your cursor to specify the position and use the zoom slider in the "Design" tab as needed.
25 | 4. **Text & Style**: Add text, pick your style, and make it pop. Because plain screenshots are so last year.
26 | - **Example**: Enter your text under the "Text" tab. Adjust the font size, weight, color, and drag it with around to align it your mockup.
27 | 5. **No Login Required**: Start creating immediately without any sign-up process.
28 | 6. **No Watermarks**: Your designs, your brand—no unwanted additions.
29 | 7. **Free to Use**: Powerful features accessible to everyone at no cost.
30 |
31 | ## 🚀 Getting Started
32 |
33 | ### Prerequisites
34 |
35 | - **Node.js** (v14 or later): Check your current version by running `node -v`.
36 | - **npm or yarn**: If you're using npm or Yarn, you can run `npm -v` or `yarn -v`.
37 |
38 | ### Installation
39 |
40 | 1. Clone the repository:
41 | ```
42 | git clone https://github.com/suryanshsingh2001/mockly.git
43 | ```
44 |
45 | 2. Navigate to the project directory:
46 | ```
47 | cd mockly
48 | ```
49 |
50 | 3. Install dependencies:
51 | ```
52 | npm install
53 | # or
54 | yarn install
55 | ```
56 |
57 | 4. Start the development server:
58 | ```
59 | npm run dev
60 | # or
61 | yarn dev
62 | ```
63 |
64 | 5. Open [http://localhost:3000](http://localhost:3000) in your browser to see the application.
65 |
66 | ## 🖱️ Usage
67 |
68 | 1. Navigate to the editor page.
69 | 2. Upload your screenshot or choose from available templates.
70 | 3. Use the intuitive interface to adjust, zoom, and place your image.
71 | 4. Add text, choose fonts, and style as needed.
72 | 5. Preview your design on multiple device sizes.
73 | 6. Download your finished mockup.
74 |
75 | ## 🔮 Future Scope
76 |
77 | We have exciting plans for the future of Mockly, and we welcome contributions in these areas:
78 |
79 | 1. **Video Editor**: We're planning to expand Mockly's capabilities to include a video editor that follows the same philosophy as our image editor—quick, intuitive, and designed for developers who want to create professional-looking video content without the complexity of traditional video editing software.
80 |
81 | 2. **AI-Assisted Design**: Implementing AI to suggest design improvements and automate repetitive tasks.
82 |
83 | 3. **Template Marketplace**: A platform for users to share and download custom templates.
84 |
85 | 4. **Collaboration Features**: Real-time collaboration tools for team projects.
86 |
87 | 5. **Plugin System**: Allowing developers to extend Mockly's functionality with custom plugins.
88 |
89 | We encourage contributors to think creatively about these future directions and propose innovative solutions to help bring these ideas to life.
90 |
91 | ## 🎉 Hacktoberfest 2024
92 |
93 | We're excited to participate in Hacktoberfest 2024! Here's how you can contribute:
94 |
95 | ### 📜 Ground Rules
96 |
97 | 1. Contributions must be meaningful and add value to the project.
98 | 2. Follow our code style and best practices.
99 | 3. Be respectful and collaborative in discussions.
100 | 4. Test your changes thoroughly before submitting a PR.
101 |
102 | ### 🛠️ How to Contribute
103 |
104 | 1. Fork the repository to your GitHub account.
105 | 2. Create a new branch for your feature or bug fix:
106 | ```
107 | git checkout -b feature/your-feature-name
108 | ```
109 | or
110 | ```
111 | git checkout -b fix/your-bug-fix-name
112 | ```
113 | 3. Make your changes, ensuring they align with the issue template if addressing a specific issue.
114 | 4. Commit your changes with a clear and descriptive commit message.
115 | 5. Push your branch to your forked repository:
116 | ```
117 | git push origin feature/your-feature-name
118 | ```
119 | 6. Open a Pull Request (PR) to our `main` branch.
120 |
121 | ### 🔄 Pull Request Process
122 |
123 | 1. Ensure your PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
124 | 2. Include screenshots or GIFs in your PR if you've made UI changes.
125 | 3. Make sure your code is properly formatted and passes all tests.
126 | 4. Your PR will be reviewed by maintainers. Be open to feedback and make necessary changes.
127 | 5. Once approved, your PR will be merged into the main codebase.
128 |
129 | ### 📝 Issue Templates
130 |
131 | When creating a new issue or PR, please use our provided templates:
132 |
133 | - For bug reports: [Bug Report Template](.github/ISSUE_TEMPLATE/bug_report.md)
134 | - For feature requests: [Feature Request Template](.github/ISSUE_TEMPLATE/feature_request.md)
135 | - For pull requests: [Pull Request Template](.github/PULL_REQUEST_TEMPLATE.md)
136 |
137 | ### 🐛 Existing Issues and Contributions
138 |
139 | We encourage contributors to explore our [existing issues](https://github.com/suryanshsingh2001/mockly/issues) and contribute to them. Here are some ways you can help:
140 |
141 | 1. **Bug Fixes**: Look for issues labeled `bug` and help us squash them!
142 | 2. **Feature Implementation**: Issues labeled `enhancement` are great opportunities to add new features to Mockly.
143 | 3. **Documentation**: Help us improve our docs by addressing issues labeled `documentation`.
144 | 4. **UI/UX Improvements**: If you have design skills, look for issues labeled `ui` or `ux`.
145 | 5. **Performance Optimization**: Help make Mockly faster by tackling issues labeled `performance`.
146 |
147 | Don't see an issue that matches your interests? Feel free to [create a new issue](https://github.com/suryanshsingh2001/mockly/issues/new/choose) and discuss your ideas with the community!
148 |
149 | We look forward to your contributions and hope you enjoy participating in Hacktoberfest with Mockly!
150 |
151 | ## ❓ Frequently Asked Questions (FAQs)
152 |
153 |
154 | 1. What is Mockly?
155 | Mockly is an open-source tool designed to help developers create professional-looking screenshots and mockups quickly and easily. It’s perfect for developers who want to produce high-quality visuals without needing to dive into complex design tools.
156 |
157 |
158 |
159 | 2. Do I need to sign up to use Mockly?
160 | No, Mockly does not require any login or account creation. You can start using the tool right away without the need for any sign-up process.
161 |
162 |
163 |
164 | 3. Is Mockly free to use?
165 | Yes, Mockly is completely free to use, and there are no hidden fees or watermarks. You get access to all its powerful features without any cost.
166 |
167 |
168 |
169 | 4. Is my data secure when using Mockly?
170 | Yes, it is. Mockly does not store any of your images, text, or designs. All processing is done in real-time, and nothing is saved on our servers.
171 |
172 |
173 |
174 | 5. What formats does Mockly support for screenshots?
175 | You can upload images in common formats like PNG, JPEG, and SVG. These formats are widely supported and make it easy to incorporate your screenshots into the tool.
176 |
177 |
178 |
179 | 6. How can I customize background image?
180 | You can customize the background image by uploading your own image or selecting from the available templates. You can also adjust the position, zoom, and text to create a unique mockup.
181 |
182 |
183 |
184 | 7. Can I preview my designs on multiple devices?
185 | Yes! Mockly allows you to preview your designs on various screen sizes and devices. This feature ensures that your mockups will look great on any platform.
186 |
187 |
188 |
189 | 8. Does Mockly support multi-language text input?
190 | Yes, Mockly supports multi-language text input. Just enter your preferred language in the text field, and Mockly will render it accordingly.
191 |
192 |
193 |
194 | 9. Are there any system requirements for Mockly?
195 | To run Mockly locally, you'll need Node.js (v14 or later) installed on your machine. Mockly works best in modern web browsers like Chrome, Firefox, and Safari for its web version.
196 |
197 |
198 |
199 | 9. Can I collaborate with others on Mockly?
200 | As of now, Mockly doesn't have real-time collaboration features, but they are part of the future roadmap! Stay tuned for updates.
201 |
202 |
203 |
204 | 10. Does Mockly have a plugin system?
205 | Not yet, but we plan to introduce a plugin system in the future that will allow developers to extend the tool's functionality by creating and integrating custom plugins.
206 |
207 |
208 |
209 | 11. How do I contribute to the project?
210 | Mockly is open-source and welcomes contributions! You can check out our contribution guidelines and participate in Hacktoberfest or submit features, bug fixes, and more throughout the year.
211 |
212 |
213 |
214 | 12. Where can I report bugs or suggest features?
215 | You can report bugs or suggest features by creating an issue in the Mockly GitHub repository. Make sure to check if an issue already exists before creating a new one!
216 |
217 |
218 |
219 | 13. Can I use Mockly for commercial purposes?
220 | Yes, Mockly is licensed under the MIT License, which allows you to use it freely for both personal and commercial purposes.
221 |
222 |
223 |
224 | 14. Will Mockly support video editing?
225 | Yes, we are planning to add video editing capabilities in the future, so you can create stunning video content with the same ease as creating screenshots.
226 |
227 |
228 |
229 | 15. What if I need help with Mockly?
230 | For any questions or help, feel free to reach out through our GitHub Discussions or contact us via our project website or GitHub repository.
231 |
232 |
233 | ## 👥 Contributing
234 |
235 | We welcome contributions from the community! Please read our [Contribution Guidelines](CONTRIBUTING.md) for more details on our year-round contribution process.
236 |
237 |
238 |
239 |
240 |
241 |
242 | ## 🤝 Code of Conduct
243 |
244 | We are committed to fostering an inclusive and welcoming community. Please read our [Code of Conduct](CODE_OF_CONDUCT.md) before participating.
245 |
246 | ## 📄 License
247 |
248 | This project is licensed under the [MIT License](LICENSE).
249 |
250 | ## 📞 Contact
251 |
252 | - Project Maintainer: [Suryansh](https://www.linkedin.com/in/suryanshsingh2001/)
253 | - Project Website: [https://www.mockly.site](https://www.mockly.site)
254 |
255 | ## 🙏 Acknowledgments
256 |
257 | - Thanks to all contributors who have helped shape Mockly.
258 | - Built with [Next.js](https://nextjs.org/) and [shadcn/ui](https://ui.shadcn.com/).
259 | - Icons provided by [Lucide](https://lucide.dev/).
260 |
261 | ---
262 |
263 | Made with ❤️ by the Mockly community
264 |
--------------------------------------------------------------------------------
/SECURITY.md:
--------------------------------------------------------------------------------
1 | # Security Policy
2 |
3 | ## Supported Versions
4 |
5 | Use this section to tell people about which versions of your project are
6 | currently being supported with security updates.
7 |
8 | | Version | Supported |
9 | | ------- | ------------------ |
10 | | 5.1.x | :white_check_mark: |
11 | | 5.0.x | :x: |
12 | | 4.0.x | :white_check_mark: |
13 | | < 4.0 | :x: |
14 |
15 | ## Reporting a Vulnerability
16 |
17 | Use this section to tell people how to report a vulnerability.
18 |
19 | Tell them where to go, how often they can expect to get an update on a
20 | reported vulnerability, what to expect if the vulnerability is accepted or
21 | declined, etc.
22 |
--------------------------------------------------------------------------------
/app/(public)/privacy/page.tsx:
--------------------------------------------------------------------------------
1 | import { Button } from "@/components/ui/button"
2 | import Link from "next/link"
3 |
4 | export default function PrivacyPolicy() {
5 | return (
6 |
16 | We collect information you provide directly to us when you create an account, use our Service, or communicate with us. This may include:
17 |
18 |
19 |
Personal information such as your name and email address
20 |
Usage data and preferences
21 |
Content you create, upload, or share using our Service
22 |
23 |
24 |
2. How We Use Your Information
25 |
26 | We use the information we collect to:
27 |
28 |
29 |
Provide, maintain, and improve our Service
30 |
Process transactions and send related information
31 |
Send you technical notices, updates, security alerts, and support messages
32 |
Respond to your comments, questions, and requests
33 |
Develop new features and services
34 |
35 |
36 |
3. Information Sharing and Disclosure
37 |
38 | We do not share, sell, rent, or trade your personal information with third parties for their commercial purposes. We may share information as follows:
39 |
40 |
41 |
With vendors, consultants, and other service providers who need access to such information to carry out work on our behalf
42 |
In response to a request for information if we believe disclosure is in accordance with any applicable law, regulation, or legal process
43 |
If we believe your actions are inconsistent with our user agreements or policies, or to protect the rights, property, and safety of Mockly or others
44 |
45 |
46 |
4. Data Security
47 |
48 | We use reasonable measures to help protect information about you from loss, theft, misuse and unauthorized access, disclosure, alteration, and destruction. However, no internet or email transmission is ever fully secure or error-free.
49 |
50 |
51 |
5. Your Choices
52 |
53 | You may update, correct, or delete your account information at any time by logging into your online account. If you wish to delete or deactivate your account, please email us, but note that we may retain certain information as required by law or for legitimate business purposes.
54 |
55 |
56 |
6. Changes to this Policy
57 |
58 | We may change this privacy policy from time to time. If we make changes, we will notify you by revising the date at the top of the policy and, in some cases, we may provide you with additional notice (such as adding a statement to our homepage or sending you a notification).
59 |
60 |
61 |
7. Contact Us
62 |
63 | If you have any questions about this Privacy Policy, please contact us at: privacy@mockly.com
64 |
65 |
66 |
67 |
70 |
71 |
72 |
73 | )
74 | }
--------------------------------------------------------------------------------
/app/(public)/terms/page.tsx:
--------------------------------------------------------------------------------
1 | import { Button } from "@/components/ui/button"
2 | import Link from "next/link"
3 |
4 | export default function TermsOfService() {
5 | return (
6 |
16 | By accessing or using Mockly, you agree to be bound by these Terms of Service. If you disagree with any part of the terms, you may not use our Service.
17 |
18 |
19 |
2. Description of Service
20 |
21 | Mockly provides an online platform for creating and editing screenshots and mockups . We reserve the right to modify or discontinue, temporarily or permanently, the Service with or without notice.
22 |
23 |
24 |
3. User Accounts
25 |
26 | When you create an account with us, you must provide accurate and complete information. You are solely responsible for the activity that occurs on your account, and you must keep your account password secure.
27 |
28 |
29 |
4. Intellectual Property Rights
30 |
31 | The Service and its original content, features, and functionality are owned by Mockly and are protected by international copyright, trademark, patent, trade secret, and other intellectual property or proprietary rights laws.
32 |
33 |
34 |
5. User-Generated Content
35 |
36 | You retain your intellectual property rights for content you submit to Mockly. By submitting content, you grant us a worldwide, non-exclusive, royalty-free license to use, reproduce, adapt, publish, translate, and distribute your content.
37 |
38 |
39 |
6. Termination
40 |
41 | We may terminate or suspend access to our Service immediately, without prior notice or liability, for any reason whatsoever, including without limitation if you breach the Terms.
42 |
43 |
44 |
7. Limitation of Liability
45 |
46 | In no event shall Mockly, nor its directors, employees, partners, agents, suppliers, or affiliates, be liable for any indirect, incidental, special, consequential or punitive damages, including without limitation, loss of profits, data, use, goodwill, or other intangible losses, resulting from your access to or use of or inability to access or use the Service.
47 |
48 |
49 |
8. Changes to Terms
50 |
51 | We reserve the right, at our sole discretion, to modify or replace these Terms at any time. What constitutes a material change will be determined at our sole discretion. By continuing to access or use our Service after those revisions become effective, you agree to be bound by the revised terms.
52 |