feat(web): Add and link privacy and tnc page

[kriptonian1]

User description

Description

Give a summary of the change that you have made

Fixes #[ISSUENO]

Dependencies

Mention any dependencies/packages used

Future Improvements

Mention any improvements to be done in future related to any file/feature

Mentions

Mention and tag the people

Screenshots of relevant screens

Add screenshots of relevant screens

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings
• My changes are breaking another fix/feature of the project
• I have added test cases to show that my feature works
• I have added relevant screenshots in my PR
• There are no UI/UX issues

Documentation Update

• This PR requires an update to the documentation at docs.keyshade.xyz
• I have made the necessary updates to the documentation, or no documentation changes are required.

---

PR Type

enhancement

---

Description

• Added custom MDX components for styled HTML tags in MDX files.
• Updated footer links to point to newly added legal pages (Terms and Conditions, Privacy Policy).
• Created a layout component for MDX pages to standardize page structure.
• Introduced new MDX content for Terms and Conditions and Privacy Policy.
• Configured MDX support in the Next.js configuration to handle MDX files.
• Added necessary MDX dependencies in package.json.

---

Changes walkthrough 📝

	Relevant files
Enhancement	mdx-components.tsx Add Custom MDX Components with Styled HTML Tags                    apps/web/src/mdx-components.tsx Added custom MDX components for various HTML tags with specific styles. +29/-0    index.tsx Update Footer Links to New Legal Pages                                      apps/web/src/components/shared/footer/index.tsx Modified footer links to point to the new terms and conditions and privacy policy pages. +10/-4    layout.tsx Create Layout Component for MDX Pages                                        apps/web/src/app/(main)/(mdx)/layout.tsx Created a new layout component for MDX pages. +12/-0
Bug fix	index.tsx Syntax Correction in CardProps Interface                                  apps/web/src/components/shared/card/index.tsx Minor syntax correction in CardProps interface. +1/-1
Documentation	page.mdx Add Terms and Conditions MDX Content                                          apps/web/src/app/(main)/(mdx)/terms_and_condition/page.mdx Added a new MDX file for terms and conditions with detailed legal information. +299/-0  page.mdx Add Privacy Policy MDX Content                                                      apps/web/src/app/(main)/(mdx)/privacy/page.mdx Added a new MDX file for privacy policy with detailed information on data handling. +113/-0
Configuration changes	next.config.mjs Configure MDX Support in Next.js                                                  apps/web/next.config.mjs Configured MDX support in Next.js configuration. Added page extensions for MDX and TypeScript files. +12/-2
Dependencies	package.json Add MDX Dependencies in package.json                                          apps/web/package.json Added dependencies for MDX support. +4/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-free]

PR Description updated to latest commit (a8d3b93)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codiumai-pr-agent-free]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	3, because the PR involves multiple files and significant changes including the addition of new components, MDX content, and configuration changes. The complexity is moderate with the introduction of new dependencies and potential implications on existing functionalities.
🧪 Relevant tests	No
⚡ Possible issues	Possible Bug: The use of EncryptText in the footer links without a corresponding import or definition in the provided diff could lead to runtime errors if not defined elsewhere.
	Styling Consistency: The styling applied to MDX components uses hard-coded values which might not be consistent with the rest of the application's theme management.
🔒 Security concerns	No

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Category	Suggestion	Score
Performance	Improve rendering performance by using React.memo Consider using React.memo for the component definitions within useMDXComponents to avoid unnecessary re-renders. This is particularly beneficial for components that are expected to receive the same props in typical use cases, improving performance. apps/web/src/mdx-components.tsx [6-8] -h1: ({ children }) => ( +h1: React.memo(({ children }) => ( <h1 className="text-brandBlue my-8 text-2xl md:text-3xl">{children}</h1> -), +)), Suggestion importance[1-10]: 7 Why: Using React.memo for static components can prevent unnecessary re-renders, enhancing performance. The suggestion correctly identifies a performance improvement opportunity in the new code.	7
Maintainability	Reduce redundancy and ease future modifications by using a constant for repeated className strings Extract the repeated className string into a constant to avoid redundancy and facilitate easier future modifications. apps/web/src/components/shared/footer/index.tsx [95-101] -className="text-white/60 transition-colors hover:text-white" +const linkClassName = "text-white/60 transition-colors hover:text-white"; +className={linkClassName} Suggestion importance[1-10]: 6 Why: Extracting repeated className strings into a constant is a good practice for maintainability and ease of future changes. The suggestion is relevant and correctly applied to the new code.	6
Enhancement	Improve layout adaptability by using a more responsive unit for margins Use a more responsive unit than vw for top margin to improve the layout's adaptability across different screen sizes. apps/web/src/app/(main)/(mdx)/layout.tsx [9] -<div className="mt-[10vw] px-8 md:w-[60vw]">{children}</div> +<div className="mt-10 px-8 md:w-[60vw]">{children}</div> Suggestion importance[1-10]: 5 Why: The suggestion to use a more responsive unit than 'vw' for margins is valid for improving adaptability. However, the impact on the overall layout might not be significant, hence the moderate score.	5

[rajdip-b]

🎉 This PR is included in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀