Skip to content

Commit 7a79112

Browse files
authored
Merge pull request #12 from trivedi-khushi/update-details
Updates for Website content
2 parents 81213a3 + f998efa commit 7a79112

File tree

2 files changed

+79
-81
lines changed

2 files changed

+79
-81
lines changed

README.md

Lines changed: 46 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Writers Program
99
</b>
1010
</h1 >
1111

12-
At Keploy, we're always looking for new ways for our community to get involved in what we do. And so this time, we introduce a new writer's program to pay writers from the community to write technical content for software developers. Through this program, authors can now either **earn or get swags worth up to 100$** for publishing content on our blog.
12+
At Keploy, we're always looking for new ways for our community to get involved in what we do. Keploy Writer's program is focused to acknowledge the creativity, skills, and talent of various writers in the technical ecosystem, and pay them for writing developer-centric content. Through this program, authors can now either **earn or get swags worth up to $100** for publishing content with Keploy🧡
1313

1414
<p style='font-size: 20px;'> We seek a broad range of technical content from experienced writers to produce content for software developers that provides rich detail about using popular tools. We’re looking for content that targets beginner to intermediate software developers. </p>
1515

@@ -38,41 +38,63 @@ We are seeking individuals who meet the following eligibility criteria:
3838

3939
## The Process
4040

41-
1. **Submit your idea:** Submit your idea via our application form with an outline of your content and a previous writing example demonstrating your technical knowledge and writing capabilities. We will only publish unique, first-run content where our blog is the first platform for it to be published. The Keyword for the blog should have a volume of at least more than_400.
42-
2. **Refine:** Our editorial team reviews all submissions once every 3 months to identify topics we want to publish. We will reach out to you to provide feedback on the idea and make any structural change requests.
43-
3. **Write your content:** Once we’ve approved your topic, it’s time to write the content. We'll provide additional guidelines and expectations to help you get started.
44-
4. **Revise:** Submit your initial draft to our editors, and we’ll collaborate with you to copy edit, design a hero image, and prepare the article for publication. You should expect 1-2 rounds of revisions over the next 1-2 weeks.
45-
5. **Publish:** Once revisions are complete, we’ll send your compensation, publish the article, and promote it across all of our channels.
46-
6. **Let's do it again:** There’s no limit to the number of articles you can publish through this program. We love to build long-term relationships with our community and would love for you to be a repeat author on our blog. Start at step 1 again and keep going!
41+
1. **Register Yourself:** Fill out [this form](https://forms.gle/ZP72SpWdNyjg4gbu8) and register to the writers program. We'll be earger to have you along.
42+
2. **Onboarding Starts:** Get onboard with us, learn about Keploy's ecosystem, connect with the team & mentors.
43+
3. **Research your Idea** You'll start by choosing and researching about your write-up. Get access to mentorship & resources by the team.
44+
4. **Craft your Work:** Start crafting your ideas into words. This part includes you working on the approved ideas and topics.
45+
5. **Revision & Submissions:** This includes copy editing, hero image design, and revision of your article. Yes, we got to help you revise it before submitting.
46+
6. **Publication** Once the content meets all the guidlines, you're all set to publish your content with Keploy, earn and redeem your benefits.
4747

4848
## Technical Writing Guidelines
4949

5050
### Conditions
5151

52-
As stated in our publishing policy, we only accept new articles. I’m afraid we cannot republish existing work. We are not accepting agency work, promotional material, or sponsored posts of any kind.
52+
1. As stated in the publishing policy, we only accept 100% fresh write-ups(of any kind). We strictly do not encourage republishing any existing work or even a portion of it. Keploy doesn't accept agency work, promotional material, or sponsored posts of any kind.
53+
2. Submitted entries must have a volume of more than 500 words, & chosen keywords (will be shared after topic submission).
54+
3. Adhere strictly to the plagiarism policy.
55+
4. Understand and comply with the Terms and Conditions of the Keploy Community Writing Program.
5356

54-
### Writing Instructions
57+
### Rewards
5558

56-
1. **Be Certain**: Make sure you are confident in your topic and presenting factual information. If you are not sure, please reach out to us and we can help you refine your idea.
57-
2. **Cut the fluff**: Don't use unnecessary words or contextless words. Make sure all the words in a sentence have a contextual relevance and meaning.
58-
3. **Use numeric values**: Use specific numeric values. Instead of writing there are many reasons or some reasons for X, write there are 5(or any specific numbers) main reasons for X.
59-
4. **Optimize subordinate text first sentence**: Optimizing subordinate text means optimizing the first sentence after a heading. When search engines process a content they don't check the entire content. If the subordinate text is not responsive enough search engines can skip the whole content. That's why give the answer early and make it clear as much as possible with the correct format. <br>
60-
<u>Example: </u><br>
61-
Heading: How to do X <br>
62-
Wrong Subordinate Text: X is... <br>
63-
Correct Subordinate Text: To do X... <br>
59+
Our compensation amounts are measures in USD (valid for 1 published submission of minimum word count of 500 words)
6460

65-
5. **Match the Anchor text with the Targeted Web page's title**: If you want to use "X" as your anchor text ensure "X" is used in the Title tag of the targeted web page and the source page's Heading. It will provide the best possible responsiveness if you're able to match them providing contextual relevance.
61+
- $10 for 350 views on article.
62+
- $20 for 500 views on article.
63+
- $50 for 1000 views on article.
64+
- $100 for 2000 views on article.
6665

66+
(Compensations might be subject to any updates. Changes will be informed to all onboarded candidates on priority and updates will be made suitably in the guide.)
6767

68-
### Rewards
6968

70-
We pay $ for an article which translates into a choice of:
69+
## Terms and Conditions
70+
71+
Keploy Community Writing Program Standard Terms & Conditions (“Writing Program Terms”):
72+
73+
- Submissions do not establish an employment relationship; you are an independent contractor.
74+
- You grant Keploy a perpetual, non-revocable license for your submitted content.
75+
- All content is licensed under Creative Commons Attribution-Noncommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0).
76+
- You must comply with all applicable laws, including copyright laws, and Keploy's Terms of Service.
77+
- Keploy is not liable for any damages related to this agreement.
78+
- You warrant that your content does not infringe on third-party intellectual property rights.
79+
80+
81+
## Plagiarism Policy
82+
Keploy blog requires original content. Any copied or reproduced work will result in immediate cessation of collaboration, potentially without notice. This includes:
83+
84+
Rewording existing posts as your own.
85+
Copying and pasting external documentation without proper attribution.
86+
Modifying someone else's code without significant original contributions.
87+
Using copyrighted images without permission.
88+
If unsure about plagiarism concerns, consult with the Keploy content team before submission.
89+
90+
91+
## Screenshots
92+
Screenshots can enhance your article by visually representing instructions. Ensure all content in the images is your original work and does not include copyrighted material. For clarity:
93+
94+
- Increase font size for readability.
95+
- Crop to focus on relevant elements.
96+
- Remove unnecessary details.
7197

72-
- 25$ for 500 views
73-
- 50$ for 1000 views
74-
- 100$ for 2000 views
75-
Payment is made after your article has been published. We also run regular events that offer bonuses for writing about specific topics.
7698

7799
## FAQs
78100

@@ -89,33 +111,3 @@ Our editorial staff will reach out to let you know if we want to publish your co
89111
### How do you evaluate content ideas?
90112

91113
Our team reviews every submission, and we look for technical content that comprehensively covers software development topics with clear explanations. Explain as much detail as possible and leave no concepts out.
92-
93-
## Terms and Conditions
94-
95-
Keploy Community Writing Program Standard Terms & Conditions (“Writing Program Terms”):
96-
97-
1. Your submission of content to Keploy does not in any way establish any sort of employment relationship between you and Keploy. Your relationship with Keploy is that of an independent contractor, not an employee.
98-
2. You agree to grant Keploy a perpetual, non-revocable, license to the content you submit to Keploy.
99-
3. All content submitted to Keploy under this program shall be licensed under the Creative Commons Attribution-Noncommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) license.
100-
4. You agree to comply with all applicable laws and regulations, including copyright laws.
101-
5. You agree to comply with the terms and conditions of the Keploy Terms of Service.
102-
6. In no event shall Keploy be liable concerning any subject matter relating to this agreement under any contract, negligence, strict liability, or other legal or equitable theory for special, incidental, consequential, or direct damages.
103-
7. Keploy makes no representation or warranty of any kind. You represent and warrant that your content will not infringe upon or misappropriate the intellectual property rights of any third party.
104-
105-
## Plagiarism Policy
106-
107-
The Keploy blog produces original, first-run content that has never been published previously in any form, digital or physical. All code, copy, images, and other content should be the result of the author's original thought, work, research, and self-expression. At our discretion, Keploy will cease all work — possibly without notice — with any author that reproduces, copies, or claims someone else's work as their own. This policy extends to content that has been published or is in the process of being published, by the author elsewhere without prior permission from Keploy. This policy includes borrowing content, wording, code, documentation, or organizational structure from any other person or organization's prior work.
108-
Some examples of plagiarism include:
109-
110-
1. Rewording existing blog posts to pass the content as your own.
111-
2. Copy and paste external documentation without directly referencing the documentation source.
112-
3. Modifying someone else's code to change variable and/or function names, comments, or other elements.
113-
4. Using images from another source, even if you make modifications to that image.
114-
5. Failing to attribute content or datasets published under permissive licenses like the Creative Commons License.
115-
If you're unsure about a question or concern related to plagiarism, please consult with the Keploy content team before submission.
116-
117-
## Screenshots
118-
119-
Screenshots can be a great way to show visual representations of the instructions in your article. You might want to include screenshots of terminal output, tool configurations, or other items related to your content. If you have screenshots in your content, ensure that all content that appears in the image is your unique work and doesn’t include copyrighted images or other content from other sources.
120-
121-
To get the best screenshot, increase the font size of the text displayed in the image to something easily readable from a distance, crop screenshots to focus on elements relevant to the text, and remove unnecessary details when possible.

0 commit comments

Comments
 (0)