Open roamye opened 1 month ago
@kamerynB - would a UAT example be to check more tools -> developer on the record page?
The current functionality is that the frontend retrieves the HAL link results on page load. Once the user opens the accordions, the API requests are made for each individual result. Is the intent that the frontend will make all of those individual result requests on page load as well? @roamye
cc: @clarkepeterf
@kamerynB -
I thought adding the HTML to the accordions would do allow for the information in the accordions to load upon the page load. If this is not correct, what is the intention behind adding the HTML to the accordions?
@kamerynB When the page loads, it gets all of the related list results, so we already have the information needed to link to each entity, it just won't have a nice link name.
When someone opens up the accordion, we do a useGetItemQuery()
to get the name of the entity for the link.
Before the accordions are opened, is it possible to include links that are hidden and are just named after the URI instead of the entity name? That way, google will be able to crawl the related lists.
Issue should be updated with the info from @clarkepeterf above
@clarkepeterf So I'm clear, the frontend would not be making the requests to each individual entity, it would just be populating a collapsed accordion with the URIs of those entities?
@kamerynB correct. It should populate the collapsed accordion with links to those uris so that google can crawl them.
@clarkepeterf Thank you. That makes sense.
Problem Description: Google Analytics crawlers only crawl links available when the page loads. Since accordion links appear upon selection, not on page load, crawlers ignore them.
Expected Behavior/Solution: The list of URIs contained in each accordion, respectively, will be exposed in the rendered HTML so the crawler can read them.
Requirements:
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
UAT/LUX Examples: N/A
Dependencies/Blocks: N/A
Related Github Issues: N/A
Related links: N/A
Wireframe/Mockup: Front end remains the same to users.