Skip to content

Fixed formatting and added search functionality in documentation #203

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

Closed
wants to merge 37 commits into from

Conversation

avinabneogy23
Copy link

This pull request addresses Issue #191 by improving the documentation formatting and introducing search functionality to enhance usability.

@avinabneogy23 avinabneogy23 marked this pull request as draft March 16, 2025 06:49
@avinabneogy23
Copy link
Author

@avinabneogy23 avinabneogy23 marked this pull request as ready for review March 16, 2025 06:54
To use this image for setting up a local image
@StarTrooper08
Copy link
Collaborator

Hi Avinab,
Thanks for opening PR.
Right now we have to hold this PR. And resume it later on.

If you are looking to participate in GSoC.
Can you please go through the r-gsoc wiki page. You can find pretest for this project.

https://github.com/rstats-gsoc/gsoc2025/wiki/table-of-proposed-coding-projects

Thank you.

@hturner
Copy link
Member

hturner commented Mar 18, 2025

Just to echo what @StarTrooper08 said - if this is for GSoC, you should post a solution for Hard Test 1 that has a screenshot with (some of) your improved documentation deployed locally and a link to this PR.

@avinabneogy23
Copy link
Author

avinabneogy23 commented Mar 20, 2025

Hi Heather and Atharva,

I opened this PR as a solution for the Hard test 1 and as you have mentioned, Heather I will be linking this to the solution along with the relevant screenshots.

Thanks for the guidance you guys !

@hturner
Copy link
Member

hturner commented Mar 21, 2025

@Avinab there are quite a few conflicts as I just merged a PR implementing the pre-commit markdown linter which did a lot of automated tidying (enforcing line length of 80 characters, ensuring code blocks are always fenced - e.g. with ```bash and ```). It would be great if you could resolve this conflicts so we can review your new changes.

@avinabneogy23
Copy link
Author

Hi @hturner ,
I apologize for the multiple commits. As I'm new to documentation contributions, I encountered several linter issues that required iterative fixes.
Thanks!

@hturner
Copy link
Member

hturner commented Mar 28, 2025

We are also new to the pre-commit linter. But you should be able to install it to run the linter locally so you can fix things before committing, see https://pre-commit.com.

@avinabneogy23
Copy link
Author

Hey Heather,
Thanks! I'll check out the pre-commit linter and get it running locally. Appreciate the suggestion and it will save me a lot of time !

@avinabneogy23
Copy link
Author

Hey Heather,
I am closing this PR, will be opening separate PR for search (#212 ), documentation additions and formatting.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants