Added app load related info in FAQ section

[RamVinayMandal]

💡 What is the current behavior?

No documentation exists for detecting when iX components are fully loaded or preventing Flash of Undefined Custom Elements (FOUCE).

GitHub Issue Number: #2271

JIRA Number: IX-3785

🆕 What is the new behavior?

Added two new FAQ entries in faq.md:

• "How can I detect when IX components are ready?" - Documents the componentOnReady() method with null-safe examples for single and multiple components
• "How can I prevent flash of undefined custom elements (FOUCE)?" - Documents using the hydrated class with CSS :not(.hydrated) selector to hide elements until initialized

Also fixed broken links in existing FAQ entries for Figma library and framework support.

[netlify]

👷 Deploy request for industrial-experience pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	3666bdd

[gemini-code-assist]

Summary of Changes

Hello @RamVinayMandal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the faq.md documentation by introducing comprehensive guides on managing iX component lifecycle events. It provides developers with clear methods to detect when components are fully loaded and practical strategies to prevent visual inconsistencies like Flash of Undefined Custom Elements (FOUCE). Additionally, it includes essential maintenance by fixing outdated internal links, ensuring the documentation remains accurate and helpful.

Highlights

• New FAQ Entries: Two new FAQ entries have been added to faq.md to address common questions about iX component loading and rendering.
• Component Readiness Documentation: Detailed guidance on using the componentOnReady() method is now available, including null-safe JavaScript examples for both single and multiple components.
• FOUCE Prevention Guide: Instructions and CSS examples for preventing Flash of Undefined Custom Elements (FOUCE) using the hydrated class and :not(.hydrated) selector have been added.
• Broken Link Fixes: Two broken internal links within existing FAQ entries related to Figma library access and framework support documentation have been corrected.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds valuable information to the FAQ section regarding component loading states and preventing FOUCE, which will be very helpful for developers. It also fixes some broken links. The new content is clear and the code examples are useful. I've made a few minor suggestions to align the text with the repository's style guide, specifically regarding apostrophe usage, and offered a small refinement to one of the JavaScript examples for better conciseness.

[RamVinayMandal]

Screenshots after adding changes: