So you’d like to be a contributor to Topcoder Thrive, huh? I can’t say it’s a surprise as our members are amongst the brightest in their fields and have a lot of knowledge to share with others. We are very excited about your interest and hope to publish your article or video very soon.
Your article can be used as a source of learning a particular topic. If you find that your submission is more based on opinion, perhaps you may want to attempt to submit to the Topcoder Blog. Thrive = Education!
Your article has a minimum of 500 words in length
The article passes the Plagiarism Check from Grammarly. It is free for use, so please use it!
Check the issues list for issues tagged [WIP] which will mean someone else is already working on the topic that you want to write about
Take a tour around Thrive and the Topcoder Blog in the category that you are planning on writing about to make sure the topic hasn’t already been covered.
In your document include the following information:
Title of your article
Your First and Last Name / Handle
Choose between: Design, Development, Data Science, Competitive Programming, QA, Topcoder
Is your article about a specific technology, application, tool, or theory? Write down that specific item here.
Use comma-separated words/phrases that further explains your article. For example, the primary theme of your article may be about Java (which would be your subcategory) but you also talk about “Binary Trees” and have some “Python” code written in there. For this tags section you would then write:
Binary Trees, Python
About how long will it take an average reader to read your article?
If you’d like a more accurate result there is a Google Extension called Reading Time that can help you estimate.
Paste a link to the image you would like used for this article. Make sure that the image is not copyrighted and that the dimensions of the image are 445 pixels wide and 355 pixels tall. If you need to crop your image you could use https://www.photopea.com/ to make it correct size.
Here is where you provide the content of your article. If there are images you wish to use in your content, remember to paste the link to the image as we are not able to download the image if you paste that in your document. If you are at all familiar with Markdown, please use that format to create your content.
To keep a high-quality level of articles in Thrive we have defined special prerequisites an article should meet before it gets accepted for review. Please, read the dedicated article and make sure your submission meets those requirements. Submissions that fail to pass initial screening according to the described requirements will be not accepted for review.
Additionally to the listed requirement above applied screening will check your submissions meets the following criteria:
Your article has min 500 words length
The article passes Plagiarism Check from Grammarly https://www.grammarly.com/plagiarism-checker. It is free for use, so please use it!
Check the issues list for issues tagged [WIP] which will mean someone else is already working on the topic you want to write about
Check Thrive and the Topcoder Blog to make sure your topic has not been written about already.
When you are sure that your article passes the prerequisites go to https://gitlab.com/topcoder-thrive/article-submit/-/issues and click the “New issue” button in the top right.
Fill the issue form by following this template:
Please note that we need you to type the title, track and your TC handle. Do not forget to attach or link to the article itself.
At this point, you are done submitting! Your article will now be reviewed and feedback will be provided soon. Please monitor your notifications for next steps.
Your submission will be reviewed by a track evangelist and copilot. From here there are 3 paths possible:
Passed Review - The evangelist or copilot will set this label when the article has been accepted for publishing. Payments will be processed by the project copilot immediately upon the publishing of the article and the ticket will enter the tcx_FixAccepted state and then finally the tcx_Paid state when it is closed.
Review Feedback - The evangelist or copilot will make a comment on the ticket about how to improve the article. Writers will have 12hrs to handle/update the request by the copilot. When ready - notify the reviewer by mentioning them (@) in the ticket. For example: “@xyz ready for review”.
Rejected Review - Don’t get demotivated! Look at this as an opportunity to improve your skills and submit again!
We need to maintain clear rules and objectively apply them. Members that violate the repo rules will be removed and will lose access to the project!
Please, click on the link and login with your TC account when prompted.
We need to link your GitLab to TCX to be able to process your payment:
A: The articles will go through several levels of moderations from community veterans. You will then receive a notification if they are approved or if they may need any final fixes
A: As soon as your article is published you will receive the payment. The publish dates will be according to the number of articles we receive. We hope to moderate and then publish all the articles in the next few weeks. Note, the processing of articles could take more time, up to 4 weeks. We do our best to read all articles and respond as soon as possible! Check here for the payment policies and instructions.
A: For sure, yes! All we are looking for is your expertise in your field. The article will go through a formal editing process before being published. Feel free to use tools like Grammarly.