Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to structure your Go projects #17

Open
JustSteveKing opened this issue Feb 9, 2024 · 4 comments
Open

How to structure your Go projects #17

JustSteveKing opened this issue Feb 9, 2024 · 4 comments
Labels
Blog Article A blog article is required

Comments

@JustSteveKing
Copy link
Contributor

JustSteveKing commented Feb 9, 2024

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:

  • 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.

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.

@JustSteveKing JustSteveKing added the Blog Article A blog article is required label Feb 9, 2024
@Mohiit70
Copy link

Mohiit70 commented Apr 7, 2024

I'd like to take this.

@sarthaksarthak9
Copy link

@JustSteveKing do we here need to share a google docs or open a pull request ?

@JustSteveKing
Copy link
Contributor Author

Please open a PR @sarthaksarthak9

@Rahulkhinchi03
Copy link
Contributor

@Mohiit70 You can also work on this issue.

@sarthaksarthak9 @Mohiit70 It will be better if you can explain your content in pointts here so there is content clash between you both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blog Article A blog article is required
Projects
None yet
Development

No branches or pull requests

4 participants