Added Gif in index.md

[Urjaswi-2655]

Added code for Gif addition in Line 80

[rohanKanojia]

Where is this gif hosted?

[rohanKanojia]

Okay, it seems to be here #33 . Why did you create a separate PR for this?

[Urjaswi-2655]

Mistakenly, I made separate PR's , Sorry will not repeat it again.

[manusa]

Please, add your changes to a single PR so we can track everything there.

If you check the IntelliJ version, even though it has lots of room for improvement, there is a full description of what the user should do. You included a screen recording that "shows" a few of the required steps to add the importorder file, but it's quite confusing (IMHO), and completely lacking accessibility (remember that there might be users who use a screen reader or other devices and are completely left over if you only include this kind of content).

[Urjaswi-2655]

@manusa Ok I will add all my PR.
I tried to make a GIF so that each step can be identified because in Eclipse we have to go through, different paths unlike IntelliJ
like Java -> Code Style -> Formatter and Java -> Code Style -> Organize Imports respectively. I tried to shift to dark mode but then text like Java, Code Style, etc was unreadable because of the black background and dark blue text color.
I have tried to address all the steps in the GIF.
What can be done to increase readability and accessibility?

[Urjaswi-2655]

@manusa I have to merge only PR #33 and #34 because I think my other PR #1401 is for a separate issue.
And please provide an option to increase the readability and accessibility of the above issue. I will try to solve it and then
merge the PR

[manusa]

@manusa I have to merge only PR #33 and #34 because I think my other PR #1401 is for a separate issue. And please provide an option to increase the readability and accessibility of the above issue. I will try to solve it and then merge the PR

Your #1401 PR is in a different repo and has nothing to do with this. In general, a PR should encapsulate a group of changes that provide a feature, fix a bug, and so on. The PR should be self-contained and merging it into a main/master branch should not break the branch. For example, in this case, merging this PR would break the page you just modified because the image resource doesn't exist.

Regarding docs, you can provide a separate screenshot of each configuration tab if you think they are relevant relevant