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

[Feat]: Improve Documentation with READMEs for Individual Scripts #2985

Open
2 of 3 tasks
juj-star opened this issue Aug 15, 2023 · 1 comment
Open
2 of 3 tasks

[Feat]: Improve Documentation with READMEs for Individual Scripts #2985

juj-star opened this issue Aug 15, 2023 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@juj-star
Copy link
Contributor

Is your feature request related to a problem? Please describe.

There are several scripts in the repository that lack a dedicated README, making it harder for new users to understand their purpose and usage. Without these detailed READMEs, it can be challenging for both users and potential contributors to grasp the full functionality and potential of these scripts. For instance, I've noticed that the AI Calculator, along with two other scripts, don't have individualized documentation.

Describe the solution you'd like.

I propose creating dedicated READMEs for the following three scripts as a starting point:

AI Calculator
Air pollution Prediction
Automated scraper

These READMEs should provide:

A brief description of the script.
Pre-requisites or dependencies.
Step-by-step usage instructions.
Sample input/output or demonstrations.
Any other relevant information that a new user or contributor might need.

By creating these READMEs, we set a standard and precedent for other scripts in the repository, potentially encouraging other contributors to do the same for the remaining scripts.

Describe alternatives you've considered.

Inline Comments: While adding detailed inline comments within the script can provide some clarity, it doesn't offer the structured and comprehensive guide that a README can provide.

Centralized Documentation: Another approach could be to have a single, centralized documentation that covers all scripts. However, this could become overwhelming and might not be as user-friendly as individual READMEs.

Show us the magic with screenshots

image

image

image

Record

  • I agree to follow this project's Code of Conduct
  • I'm a GSSoC'23 contributor
  • I want to work on this issue
@github-actions
Copy link

To reduce notifications, issues are locked. Your issue will be unlocked when we add the label gssoc23. If you're participating in GSSoC'23, please add the gssoc23 label to your issue.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 15, 2023
@avinashkranjan avinashkranjan added the documentation Improvements or additions to documentation label Aug 15, 2023
@github-actions github-actions bot added the hacktoberfest Issues open for hacktoberfest label Oct 10, 2023
@github-actions github-actions bot removed the hacktoberfest Issues open for hacktoberfest label Nov 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants