+
Skip to content

aletiq/frontend-take-home

Repository files navigation

Frontend Challenge - Document Table UI Fix

Overview

We have created an application to view a list and documents in a table and display details about the documents in a side sheet that overlays the main screen. This is still a prototype and we are already discovering issues with it. Your task is to help us fix one of these issues

Current Issue

The application has a layout problem where the "Open" button (OpenDocumentButton) in the document table gets hidden behind the DetailsSheet when it's opened. This creates a poor user experience as users cannot access the button when the details panel is visible.

Problem Details:

  1. OpenDocumentButton Position: The button is positioned with absolute right-1 top-0.5 classes within table cells
  2. DetailsSheet Width: Currently the only sheet DocumentDetailsSheet has a fixed width of w-[800px] but future sheets could have different width
  3. Z-index Issue: The sheet appears to overlay the button, making it inaccessible
  4. Responsive Behavior: The button should remain visible and clickable regardless of the sheet's width

Your Task

Fix the layout issue so that:

  • ✅ The OpenDocumentButton remains visible and accessible at all times
  • ✅ The button stays within its table cell boundaries
  • ✅ The solution works with variable DetailsSheet widths
  • ✅ The fix maintains the current design aesthetics
  • ✅ The solution is responsive and works on different screen sizes

Getting Started

  1. Install dependencies:

    pnpm install
  2. Start the development server:

    pnpm dev
  3. Open the application and test the issue:

    • Click any "Open" button in the table
    • Notice how the button becomes inaccessible when the details sheet opens
    • Try different approaches to fix the layout

Evaluation Criteria

Your solution will be evaluated on:

  1. Functionality: Does the button remain accessible when the sheet is open?
  2. Code Quality: Is the solution clean, maintainable, and follows React best practices?
  3. CSS/Styling: Does the fix maintain visual consistency and responsive behavior?
  4. Edge Cases: Does it handle different sheet widths and screen sizes?
  5. User Experience: Is the interaction smooth and intuitive?

Constraints

  • Do not modify the core functionality of opening/closing the details sheet
  • Maintain the existing table structure and data display
  • Keep the current button styling and behavior
  • Document your approach and reasoning in comments

Good luck! Take your time to understand the codebase structure before implementing your solution.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载