Refactor LibraryContent: remove TaxonomySidebar, integrate into ElementBrowser

[jfrench9]

Summary

Refactors the LibraryContent component by removing the standalone TaxonomySidebar component and integrating taxonomy selection directly into the ElementBrowser. This simplifies the library view layout and consolidates taxonomy-related UI into a single component.

Changes

• Removed TaxonomySidebar import and usage from LibraryContent, eliminating a separate sidebar panel for taxonomy filtering.
• Passed taxonomyId and setTaxonomyId as props to ElementBrowser, moving taxonomy selection responsibility into the browser component itself.
• Simplified layout structure by reducing the number of wrapper elements and removing the two-panel (sidebar + browser) layout in favor of a single ElementBrowser component that handles taxonomy selection internally.
• Removed selectedTaxonomy state variable that was previously used to bridge communication between TaxonomySidebar and the rest of the component (replaced by direct taxonomyId/setTaxonomyId prop drilling into ElementBrowser).

Key UI/UX Improvements

• Streamlined library view: Users no longer see a separate sidebar for taxonomy filtering. Taxonomy selection is now contextually embedded within the ElementBrowser, reducing visual clutter and providing a more cohesive browsing experience.
• Simplified component hierarchy: Fewer nested layout containers result in a cleaner DOM structure and potentially improved rendering performance.

Breaking Changes

• ElementBrowser component contract has changed: It now expects taxonomyId and setTaxonomyId props. Any other consumers of ElementBrowser will need to be updated accordingly.
• TaxonomySidebar may now be unused — verify if it can be deprecated/removed from the codebase entirely.

Testing Notes

• Verify that taxonomy filtering still works correctly within the ElementBrowser component.
• Confirm that selecting a taxonomy correctly filters the displayed library elements.
• Test the library view at various viewport sizes to ensure the removal of the sidebar doesn't introduce layout regressions.
• Verify that navigation to/from the library page preserves expected state (taxonomy selection, scroll position, etc.).
• Check that no other pages/components depend on the previous ElementBrowser prop signature without the new taxonomy props.

Browser Compatibility Considerations

• No new browser APIs or CSS features introduced — this is primarily a structural refactor.
• Layout changes should be verified across Chrome, Firefox, Safari, and Edge to ensure consistent rendering after sidebar removal.
• Test on both desktop and mobile viewports since the layout simplification may affect responsive behavior differently than the previous two-panel design.

---

🤖 Generated with Claude Code

Branch Info:

• Source: chore/update-library-view
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com