Update index.html with minor fixes

[RJohnPaul]

added proper tags and overall formatted and cleaned code

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[anuragoyar]

Pull Request Review: HTML File Changes

Potential Risks and Suggestions:

File: index.html
Code Snippet: <link href= "https://ajax.googleapis.com/ajax/libs/angularjs/1.7.7/angular.min.js"> → <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.7.7/angular.min.js"></script>
Comment: This is a critical fix. The original code incorrectly used a <link> tag for JavaScript which would prevent Angular from loading. The corrected version properly uses a <script> tag with the src attribute.

File: index.html
Code Snippet: <loading /> → <loading></loading> (multiple instances)
Comment: Self-closing custom component tags are not properly supported in HTML5. The change to use opening and closing tags ensures proper rendering across browsers.

File: index.html
Code Snippet: <a href="cla.html"ng-click="menuOpen"> → <a href="cla.html" ng-click="menuOpen">
Comment: Missing space between attributes could cause the ng-click directive to not function properly. The fix adds proper spacing between HTML attributes.

File: index.html
Code Snippet: ng-class="{disabled: loading}" → ng-class="{'disabled': loading}"
Comment: While both syntaxes may work in some versions of AngularJS, the updated version with quotes around the class name follows best practices and ensures consistent behavior.

File: index.html
Code Snippet: <div class="fitlerStar" → <div class="filterStar"
Comment: Fixed a typo in the CSS class name from "fitlerStar" to "filterStar". This could affect styling if the corresponding CSS uses the correct class name.

File: index.html
Code Snippet: SVG path data changes in the filter button
Comment: The SVG path data has been modified, which will change the appearance of the filter icon. Ensure this visual change is intentional and matches the design requirements.

File: index.html
Code Snippet: <div class="button large-2 small-2 culumns" → <div class="button large-2 small-2 columns"
Comment: Fixed a typo in the Foundation grid class from "culumns" to "columns". This would affect the layout of the button element.

Summary:

This PR contains HTML improvements to an Adobe Open Source project page. The changes are primarily focused on fixing HTML syntax issues, correcting attribute usage, and improving component structure. Key improvements include:

1. Proper use of script tags instead of link tags for JavaScript resources
2. Correct HTML syntax for custom components (using opening/closing tags)
3. Fixed attribute spacing and syntax for AngularJS directives
4. Corrected typos in CSS class names
5. Improved HTML structure and indentation
6. Updated SVG path data for visual elements

These changes are primarily technical corrections that improve the functionality and standards compliance of the HTML without changing the core functionality. The most critical fix is the JavaScript loading mechanism, which would have prevented the application from functioning properly.

While this appears to be a Salesforce-related repository (based on the context of this review), the file being modified is a standard HTML file that likely serves as documentation or a landing page. This change does not modify any Salesforce metadata, Apex code, or LWC components, so standard Salesforce deployment concerns (like test coverage) don't apply.

The changes are suitable for production deployment as they are primarily fixing technical issues rather than introducing new functionality. No special rollback planning is needed beyond standard source control practices.