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.

Sign up for GitHub

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

Jump to bottom

Write a Technical Blog or Case Study #11

Open
KartikeyMish opened this issue Sep 20, 2023 · 3 comments
Open

Write a Technical Blog or Case Study #11

KartikeyMish opened this issue Sep 20, 2023 · 3 comments
Assignees
@abhishek-kumar-91
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers hacktoberfest

Comments

@KartikeyMish
Copy link
Owner

Write a Technical Blog or Case Study

Description: As part of our Hacktoberfest contributions, we're inviting contributors to write a technical blog post or a case study about RepoSavant. This blog or case study should cover various aspects of the project, its architecture, the technologies used, and how it benefits the GitHub community.

Content Ideas:

  • An overview of RepoSavant and its key features.
  • How RepoSavant leverages cutting-edge technologies like GPT and LangChain.
  • Real-world use cases and examples of RepoSavant's impact.
  • Insights into the development process and challenges faced.
  • Tips and tricks for using RepoSavant effectively.
  • How RepoSavant aligns with the GitHub theme and ecosystem.

Submission Guidelines:

  • Ensure the content is technical and informative.
  • Include relevant images, diagrams, and code snippets if applicable.
  • Keep the content engaging and suitable for a technical audience.
  • Proofread and edit for clarity and correctness.

Contribution Steps:

  1. Fork the RepoSavant repository to your GitHub account.
  2. Create a new branch for your blog or case study: git checkout -b feature/blog-or-case-study.
  3. Write and format your content following best practices.
  4. Include the content in the /blog directory of the repository.
  5. Submit your pull request (PR) with your contribution.
  6. Our team will review and merge the PR once it meets the guidelines.

Additional Information:

  • If you have any questions or need assistance, please feel free to ask in the discussion or comment section.
  • We encourage contributors to share their insights and experiences related to RepoSavant.

Let's document and showcase the technical aspects and impact of RepoSavant through this technical blog or case study. Your contribution will be valuable for the RepoSavant community and the broader developer community.
@KartikeyMish KartikeyMish added documentation Improvements or additions to documentation hacktoberfest labels Sep 20, 2023
@KartikeyMish KartikeyMish added the good first issue Good for newcomers label Oct 1, 2023
@abhishek-kumar-91
Copy link

I want to work on this issue, can you assign me?

@KartikeyMish
Copy link
Owner Author

Yes you can start working on it . After Reviewing your work I'll merge it.

After completing you can add the refering documentation to the readme file after forking it and then create the pull request.

Feel free to ask any questions to the project

@KartikeyMish
Copy link
Owner Author

Check it out @abhishek-kumar-91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abhishek-kumar-91 abhishek-kumar-91

Labels
documentation Improvements or additions to documentation good first issue Good for newcomers hacktoberfest
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KartikeyMish @abhishek-kumar-91