#Update Docs for z-index & drop-shadow for better clarity

[RONAK-AI647]

Description

The Google Material Design elevation image is not relevant to our approach to drop-shadows, so it should be moved down to the "z-index" section where it is more relevant.

Issue addressed

#813

Addresses #*PR# #819

Before/after screenshots

Changelog

• Description: This PR addresses the reorganization of content related to Material Design elevation. The Google Material Design elevation image was previously located under the dropdown menu section, which was not relevant to its intended focus on layering and hierarchy. It has been moved to the z-index section for better alignment with layering concepts.
• Products impact: updated API
• Addresses: Update Docs for z-index & drop-shadow for better clarity #813
• Components: no
• Impacts a11y: no
• Guidance: Clearer guidance reduces the potential for confusion while referring to the drop-shadow docs.

Steps to test

(optional) Implementation notes

At a high level, how did you implement this?

Does this introduce any tech-debt items?

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical and brittle code paths are covered by unit tests
• The change is described in the changelog section above

Reviewer guidance

• Is the code clean and well-commented?
• Are there tests for this change?
• Are all UI components LTR and RTL compliant (if applicable)?
• Add other things to check for here

Comments

The google material design elevation image from dropdown menu is shifted to the z-index section as the image is more relevant there.

[nucleogenesis]

The documentation changes LGTM - I think that your linting issue might be directly related to the changelog issue -- however, to me your changelog section looks right so I'm wondering if maybe @MisRob might see something I'm missing there.

Thank you @RONAK-AI647 for your work on this!

[MisRob]

I'm not sure why the linter check is failing. Sometimes I need to run yarn lint-fix twice. Would you try that @RONAK-AI647 and committed the change? Also it'd be helpful if you could upload your terminal output.

[MisRob]

@RONAK-AI647 @nucleogenesis another issue is that this PR contains updated yarn.lock and package.json. That will need to be removed before we can merge. This could help @RONAK-AI647 https://stackoverflow.com/questions/38743912/remove-a-file-from-a-git-pull-request. "Files changed" tab shouldn't contain these two files at all as a result.

[RONAK-AI647]

@MisRob please take a look what my terminal output is:

[MisRob]

Thank you @RONAK-AI647, I don't understand why that's happening. I could see an update made by the linter

so I went ahead and pushed the change for you.

[RONAK-AI647]

Thank you @MisRob for the help , the local server is passing the linter check but it is not passing here in the cicd, i was struggling for it so much.

[MisRob]

You're welcome @RONAK-AI647, sorry for the trouble :)

[MisRob]

Anything else here @nucleogenesis or could we merge now?

[nucleogenesis]

Thanks again for this @RONAK-AI647 !