You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QuickSnip is a welcoming and collaborative community for developers to organize, share, and discover code snippets. By participating in QuickSnip, you agree to uphold this code of conduct to maintain a friendly and inclusive environment.
4
+
5
+
### Short Version
6
+
7
+
- Be respectful to everyone in the community.
8
+
- Avoid harassment, trolling, or spamming.
9
+
- Ensure QuickSnip remains a safe and productive space for all.
10
+
- Report any inappropriate behavior to [me](mailto:technophilechannelyt@gmail.com), the owner of QuickSnip, or our [Discord team](https://discord.gg/UtJJcnsN).
11
+
- No unauthorized bots without prior permission.
12
+
13
+
---
14
+
15
+
### Long Version
16
+
17
+
#### Harassment-Free Environment
18
+
19
+
We are committed to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, national origin, or religion (or lack thereof). Examples of unacceptable behavior include:
20
+
21
+
-**Harassment:** Includes sexual language or imagery, deliberate intimidation, stalking, name-calling, unwelcome attention, libel, and malicious hacking or social engineering.
22
+
-**Trolling:** Posting inflammatory comments to provoke an emotional response or disrupt discussions.
23
+
-**Spamming:** Posting off-topic messages, promoting unrelated products, soliciting donations, advertising jobs or gigs, or flooding discussions with files or text.
24
+
25
+
#### Reporting Issues
26
+
27
+
If you experience or witness harassment, trolling, spamming, or any other inappropriate behavior, please report it to [me](mailto:technophilechannelyt@gmail.com), the owner of QuickSnip, or our QuickSnip [Discord team](https://discord.gg/UtJJcnsN). Include details like screenshots and URLs, if possible, to help us address the issue effectively.
28
+
29
+
I, or the QuickSnip team will review all reports and take appropriate actions, which may include warnings, temporary bans, or permanent removal from the community.
30
+
31
+
#### Respectful Use of Bots
32
+
33
+
No bots are allowed within the QuickSnip community without prior written permission from the QuickSnip team. Unauthorized bots will be removed.
34
+
35
+
#### Final Notes
36
+
37
+
This code of conduct is inspired by [FreeCodeCamp’s approach](https://www.freecodecamp.org/news/code-of-conduct), emphasizing clarity and friendliness. Let’s work together to make QuickSnip a supportive and productive space for all developers!
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+65-11Lines changed: 65 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,35 +11,89 @@ You can contribute in two main ways:
11
11
12
12
## Improving the code
13
13
14
-
If you have a feature request or want to fix a bug, feel free to:
14
+
### How to report bugs
15
15
16
-
-[Open an Issue](https://github.com/dostonnabotov/quicksnip/issues) to let us know what’s up.
17
-
-[Send a Pull Request](https://github.com/dostonnabotov/quicksnip/pulls) with your changes.
16
+
If you spot a bug in the codebase or issues with the documentation, please open up a [GitHub issue](https://github.com/dostonnabotov/quicksnip/issues) detailing the problem before creating a PR. Once confirmed with maintainers, you can then create a PR.
17
+
18
+
### How to propose new features
19
+
20
+
If you are interested in proposing new features, please open up a new [GitHub discussion](https://github.com/dostonnabotov/quicksnip/discussions) with details for the proposed feature.
21
+
22
+
Please do not create a PR for a new feature without first discussing it with the maintainers. If you create a PR for a new feature without discussing it first, then your PR will be closed.
23
+
24
+
---
25
+
26
+
## Snippets Guidelines
27
+
28
+
### Snippet Tags
29
+
30
+
- Tags must describe the snippet with simple word.
31
+
32
+
Here's an example:
33
+
34
+
```md
35
+
---
36
+
title: Convert Number to Currency
37
+
description: Converts a number to a currency format with a specific locale.
38
+
author: axorax
39
+
tags: number,currency
40
+
---
41
+
```
42
+
43
+
**Do not use generic keywords or the language itself as a tag `utility` or `javascript`!**
44
+
45
+
### Snippet Format
46
+
47
+
**All** snippets should follow the following structure:
48
+
49
+
- A `code` segment, containing a function with the actual snippet functionnality
50
+
- An `example` segement, containing one or more examples of use
51
+
52
+
Example in javascript:
53
+
```js
54
+
functionexample(x) {
55
+
return x *2;
56
+
}
57
+
58
+
// Usage:
59
+
example(5) // Returns: 10
60
+
```
61
+
62
+
If your function doesn't return anything just show how to use it. If the result of your function is too complicated to be expressed in a single comment, your snippet is probably too complex to begin with.
63
+
64
+
### Snippet boundaries
65
+
66
+
To ensure your snippet isn’t refused, consider these questions:
67
+
-**Does the standard library of my language provide an easy way of doing this ?**
68
+
-**Does that snippet have a real, and practical use case ?**
69
+
-**Could it be split into separate parts to be better understood ?**
70
+
71
+
If any answer is yes, then your snippet will most likely get rejected.
18
72
19
73
---
20
74
21
75
## Adding Snippets
22
76
23
77
### Adding a New Snippet
24
78
25
-
To add a new code snippet:
79
+
1.**Ensure your snippet match [guidelines](#snippets-guidelines)**
26
80
27
-
1.**Navigate to the relevant folder:**
81
+
2.**Navigate to the relevant folder:**
28
82
29
83
- Go to the `/snippets` folder in the root directory.
30
84
- Locate the folder for the programming language of your snippet, such as `javascript` or `python`.
31
85
32
-
2.**Choose the correct category:**
86
+
3.**Choose the correct category:**
33
87
34
88
- Within the language folder, find the relevant category folder for your snippet.
35
89
- If no suitable category exists, refer to [Adding a New Category](#adding-a-new-category).
36
90
37
-
3.**Create a markdown file:**
91
+
4.**Create a markdown file:**
38
92
39
93
- Create a new file with a `.md` extension.
40
94
- Name the file appropriately, keeping it descriptive and concise.
41
95
42
-
4.**Add your snippet:**
96
+
5.**Add your snippet:**
43
97
44
98
- Use the following format to structure your snippet:
Copy file name to clipboardExpand all lines: README.md
+14-7Lines changed: 14 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,10 +23,15 @@ Be sure to check out the [CONTRIBUTING.md](/CONTRIBUTING.md) file for detailed g
23
23
24
24
### Improving the code
25
25
26
-
Got a feature idea or bug fix? Here's how you can contribute:
26
+
-**Reporting bugs**
27
27
28
-
-[Open an issue](https://github.com/dostonnabotov/quicksnip/issues) to share your ideas or report a bug.
29
-
-[Send a pull request](https://github.com/dostonnabotov/quicksnip/pulls) with your changes.
28
+
- If you spot a bug in the codebase or issues with the documentation, please open up a [GitHub issue](https://github.com/dostonnabotov/quicksnip/issues) detailing the problem before creating a PR.
29
+
- Once confirmed with maintainers, you can then create a PR.
30
+
31
+
-**Proposing new features**
32
+
33
+
- If you are interested in proposing new features, please open up a new [GitHub discussion](https://github.com/dostonnabotov/quicksnip/discussions) with details for the proposed feature.
34
+
- Please do **not** create a PR for a new feature without first discussing it with the maintainers. If you create a PR for a new feature without discussing it first, then your PR will be closed.
30
35
31
36
### Adding a Snippet
32
37
@@ -99,11 +104,13 @@ For more details about adding new categories or programming languages, check out
99
104
100
105
To keep things smooth and consistent, please:
101
106
102
-
- Follow the formatting rules described above.
103
-
- Include all mandatory fields in the snippet.
104
-
- Test your snippet to ensure it works as expected.
107
+
-[x] Follow the style and contribution guidelines of this project.
108
+
-[x] Include all mandatory fields in the snippet.
109
+
-[x] Test your snippet to ensure it works as expected.
110
+
111
+
Following these guidelines helps us (and everyone else) review and merge your contributions faster.
105
112
106
-
Following these guidelines helps me (and everyone else) review and merge your contributions faster.
113
+
**If you fail to meet the guidelines, your PR will most likely get rejected.**
QuickSnip is an open-source tool designed for developers who want to organize, search, and share code snippets. It aims to streamline the coding process by providing a centralized platform for snippet management.
6
+
7
+
## Core Principles
8
+
9
+
-**Developer Focused**: Focus on features that truly improve developer productivity.
10
+
11
+
-**Open and Extensible**: Encourage community contributions and integrations.
12
+
13
+
-**Lightweight and Fast**: Keep performance high and avoid unnecessary complexity.
14
+
15
+
## Our Goals
16
+
17
+
- Seamless snippet management without turning into an overly complex tool
18
+
19
+
- Enable collaboration and sharing while respecting user privacy and customization needs.
20
+
21
+
We do **NOT** aim to be:
22
+
23
+
- a component library
24
+
- a documentation
25
+
26
+
## QuickSnip Roadmap
27
+
28
+
### v1.0 (Launching Soon)
29
+
30
+
-[x] A new snippets storage system for better maintainability and scalability
31
+
-[ ] Search functionality
32
+
-[ ] A support for frameworks and libraries
33
+
-[ ] An ability to share snippets with others
34
+
-[ ] A basic SEO (Search Engine Optimization)
35
+
36
+
### v2.0 (Planned Vision)
37
+
38
+
-[ ] An ability to have private snippets with personal account
39
+
-[ ] Improved search functionality with filters
40
+
-[ ] An improved SEO (Search Engine Optimization)
41
+
42
+
### Potential Future Ideas
43
+
44
+
-[ ] Plugins for IDEs like VS Code and JetBrains
45
+
-[ ] Enterprise-grade support for larger organizations
46
+
47
+
## Disclaimer on Future Plans
48
+
49
+
This roadmap outlines our current vision for QuickSnip and may evolve based on user feedback, community contributions, and shifting priorities. We welcome your input and encourage you to help shape QuickSnip’s future.
50
+
51
+
## Future Vision
52
+
53
+
QuickSnip aims to become the preferred platform for developers to store, retrieve, and collaborate on code snippets.
54
+
55
+
Explore our [GitHub Releases](https://github.com/dostonnabotov/quicksnip/releases) for updates and join us on this journey.
0 commit comments