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
Write an article about how to structure your Go projects, mention the "recommended" way and your own opinions.
Guidelines
Content Preparation:
Document Format: Please use Google Docs for your blog post. Please make sure we have view permission to your document.
Include relevant images, gifs, or screenshots to enhance your blog's visual appeal.
Share personal experiences or insights where applicable to give your blog a unique touch.
Consider adding code samples, examples, or practical demonstrations to illustrate concepts.
We encourage you to use AI for research and reference purposes. However, please submit original, human-written content.
Plagiarism Check:
Ensure your content is original by checking it for plagiarism. You can use a plagiarism checker like QUILBOT and share a screenshot showing the plagiarism percentage (ideally 25% max).
Collaboration & Avoiding Duplicates:
Claiming an Issue: If you'd like to write about a specific blog post topic, comment on the issue with a brief outline of your planned table of contents. This helps prevent two contributors from working on similar content.
Title
How to structure your Go projects
Brief
Write an article about how to structure your Go projects, mention the "recommended" way and your own opinions.
Guidelines
Content Preparation:
Plagiarism Check:
Ensure your content is original by checking it for plagiarism. You can use a plagiarism checker like QUILBOT and share a screenshot showing the plagiarism percentage (ideally 25% max).
Collaboration & Avoiding Duplicates:
Claiming an Issue: If you'd like to write about a specific blog post topic, comment on the issue with a brief outline of your planned table of contents. This helps prevent two contributors from working on similar content.
Confirmation Checklist:
[ ] You accept our Code of Conduct.
[ ] My blog post is written in Google Docs and you have view permission.
[ ] I've included relevant visuals and examples to enhance understanding.
[ ] My content is original and AI-free. I've run a plagiarism check and can share the results.
[ ] I've commented on the issue with a table of contents outline (if applicable).
Once you've completed these steps, check the boxes and feel free to submit your blog post! We appreciate your contribution to the Treblle community.
The text was updated successfully, but these errors were encountered: