Implement initial Next.js frontend with filtering, mobile nav, and model details for Model Leaderboard #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Created various manifest files for app, build, fallback, prerender, and routes. - Added server-side files including error handling and middleware manifests. - Introduced static chunks and CSS files for styling. - Established frontend structure with components, pages, and hooks. - Included configuration files for Next.js and Tailwind CSS. - Added media assets and data files for application functionality.
- Added a new FilterDropdown component for enhanced filtering functionality. - Updated import paths in page.tsx and MobileControls.tsx to reflect the new component structure.
- Introduced pretrain datasets filter in the ModelTable and MobileControls components. - Updated state management to handle selected pretrain datasets. - Enhanced filtering logic to include pretrain datasets in the results. - Updated imports to include DatabaseIcon for the new filter option.
- Introduced a new `_events.json` file to log CLI session events, including version and duration details. - Updated the `trace` file with additional performance metrics for build processes. - Removed obsolete type definitions related to cache life and layout/page structures to streamline the codebase. - Disabled the custom `distDir` setting in `next.config.js` for development purposes.
- Deleted several outdated JSON and manifest files related to build and server configurations. - Introduced new HTML files for 404 error pages and added favicon and touch icon images. - Added new static chunks and CSS files for improved styling and functionality. - Updated the Next.js configuration to reflect the changes in the project structure.
- Removed the custom `distDir` setting in `next.config.js` to streamline the build process. - Added a new script in `package.json` to build and copy output files to the documentation directory.
- Modified .gitignore to ensure the 'lib/' directory is ignored. - Fixed formatting in next.config.js for consistency. - Added new utility functions in utils.ts for class name merging. - Created an index.ts file to export utilities from the lib directory.
Disable jekyll
- Introduced new static files and updated existing HTML templates to reflect the new base path for the model leaderboard fork. - Added a new CSS file for styling and updated JavaScript chunks for improved functionality. - Updated the 404 and index pages to use the new asset paths. - Added a new FAQ page with collapsible components. - Updated methodology page to align with the new structure.
- Removed console log statements from the column toggle handler for cleaner code. - Updated filter dropdown titles from "Pretrain on" to "Pretrained on" for consistency across components.
- Commented out basePath and assetPrefix in next.config.js for flexibility. - Added focus styles in globals.css to improve keyboard navigation experience. - Updated FilterDropdown component to use a ref for the trigger and prevent default mouse events. - Simplified header navigation by mapping links and added active state styling for better user feedback.
- Updated column widths for better layout consistency. - Introduced a TableSkeleton component to display a loading state while data is being fetched. - Added loading state handling in the Home component to improve user experience during data retrieval.
- Replaced DatasetFilter with BenchmarkFilter in the Home component for improved functionality. - Introduced a new BenchmarkFilter component with desktop and mobile versions for dataset selection. - Updated MobileControls to use the new BenchmarkFilter component.
… 100ms for improved responsiveness.
…ality - Replaced old CSS files with updated versions for better visual consistency. - Updated HTML files to reference new CSS and JavaScript assets. - Introduced new static chunks and removed obsolete ones to optimize loading performance. - Enhanced the layout and structure of various pages, including 404 and FAQ sections.
- Changed the FAQ section heading from a div to an h2 for better semantic structure. - Added an aria-label to the header link for improved accessibility.
…mance - Updated HTML files for 404, index, FAQ, and methodology pages to reference new asset identifiers for better consistency. - Removed obsolete static files to optimize loading performance. - Enhanced the layout and structure of various pages, ensuring better semantic HTML usage.
- Introduced a new favicon.ico file for better branding. - Updated layout.tsx to reference the favicon and other icons with relative paths for consistency and improved asset management.
- Updated HTML files for 404, index, FAQ, and methodology pages to reference new asset identifiers. - Introduced a new favicon.ico file for better branding. - Enhanced layout structure for improved semantic HTML usage and asset management.
… deployment - Changed section title from "Adding shadcn/ui Components" to "Building for Production" for better clarity. - Added instructions for building documentation for GitHub Pages, including the creation of static files and a .nojekyll file. - Updated the description of the regular production build process to specify its use for various deployment methods.
… height for improved UI consistency - Modified focus styles in globals.css to apply outline only to focused elements, enhancing accessibility. - Updated SearchInput component to include a height class for better alignment and visual consistency.
…ormance - Updated HTML files for 404, index, FAQ, and methodology pages to reference new asset identifiers. - Introduced new static files for improved structure and performance, including a new build manifest and SSG manifest. - Removed obsolete static files to optimize loading performance and enhance overall user experience.
…bility and consistency - Updated prose styles in globals.css to enhance text readability with new line heights and custom link styling. - Modified various components (Home, Methodology, BenchmarkFilter, ColumnToggle, FilterDropdown, ParameterFilter) to utilize the updated prose classes for better visual consistency. - Adjusted button classes to improve text visibility across components.
- Introduced a new DropdownFilterSlider component for enhanced parameter filtering in the Home and MobileControls components. - Replaced the existing ParameterFilter with DropdownFilterSlider to improve user experience and maintain consistency across the UI. - Integrated useRangeFilter hook to manage parameter range state and filtering logic. - Updated relevant components to utilize the new filtering mechanism, ensuring a more responsive and intuitive interface.
…anced filtering options - Introduced DropdownFilterCheckbox and DropdownFilterRadio components to improve filtering capabilities in Home and MobileControls. - Replaced existing FilterDropdown instances with the new components for better user experience and consistency. - Updated SearchInput component for improved styling and responsiveness. - Enhanced mobile controls to utilize the new filtering components, ensuring a more intuitive interface.
- Created a new formatters.ts file to centralize formatting functions for parameter counts and percentages. - Updated Home and MobileControls components to utilize the new formatters for improved code clarity and maintainability. - Replaced inline formatting logic with calls to the formatters module, enhancing consistency across the application.
- Introduced a new `useUniqueValues` hook to streamline the extraction of unique values from data arrays. - Replaced manual unique value extraction in the Home component with calls to the new hook for licenses, architectures, and pretrain datasets. - Improved code clarity and maintainability by reducing redundancy in the Home component.
- Removed the BenchmarkFilter, LicenseFilter, and ParameterFilter components to streamline the codebase. - Updated the ModelTableRow component to utilize centralized formatting functions for better consistency. - Enhanced the page component by importing additional icons for improved UI elements. - Replaced inline formatting logic with calls to the new formatters module, ensuring a more cohesive approach across the application.
…e component - Introduced `useSetFilter` hook to manage set-based filters for licenses, architectures, and pretrain datasets. - Refactored Home component to utilize the new hook, simplifying filter management and improving code clarity. - Removed redundant filter handler functions, enhancing maintainability and reducing complexity in the filtering logic.
- Introduced the `useColumnManager` hook to centralize column visibility management, enhancing the Home component's structure. - Refactored column visibility handling, including toggling, showing, hiding, and resetting columns to defaults. - Updated the Home component to utilize the new column management system, improving code clarity and maintainability. - Removed redundant column handling logic, streamlining the overall component design.
- Replaced inline TableSkeleton implementation with a new SkeletonTable component for improved code organization and reusability. - Removed unnecessary comments and unused code related to parameter range state initialization. - Updated loading state logic in the Home component to utilize the new SkeletonTable, enhancing the user experience during data loading.
…ement and organization - Restructured the Home component to enhance clarity by grouping related imports and organizing state management sections. - Updated MobileControls to utilize the new `useSetFilter` and `useColumnManager` hooks, consolidating filter and column management logic. - Simplified filter handling by passing filter objects directly to MobileControls, reducing prop drilling and improving maintainability. - Enhanced the filtering logic in Home to streamline the application of filters and sorting, ensuring a more efficient data handling process.
- Updated mobile versions of ColumnToggle, DropdownFilterCheckbox, DropdownFilterRadio, and DropdownFilterSlider components to improve spacing and organization. - Added titles to mobile filter sections for better clarity and user experience. - Refactored layout to ensure consistent styling and spacing across mobile controls, enhancing overall usability.
- Updated button variants in ColumnToggle, DropdownFilterCheckbox, DropdownFilterRadio, DropdownFilterSlider, and MobileControls components from 'outline' to 'transparent' for a unified appearance. - Enhanced the button styles in the button.tsx file to include hover effects and border properties, improving the overall user interface consistency.
- Adjusted gap spacing in the RootLayout component for better alignment on smaller screens. - Modified padding in the Home, FAQ, and Methodology sections to enhance layout consistency across different screen sizes.
- Replaced outdated CSS files with new styles to enhance visual consistency across the application. - Updated HTML files in various sections (404, FAQ, Methodology) to reference the new CSS, ensuring a unified look and feel. - Removed deprecated CSS files to streamline the codebase and improve loading times. - Introduced new JavaScript files for better build management and optimized performance.
…siveness - Adjusted the size of the RoboflowLogo component for better visual alignment. - Modified CSS in the container-base class to enhance layout consistency across different screen sizes.
…ling - Adjusted the orb-container CSS to ensure it occupies the full viewport height and width, enhancing responsiveness. - Modified the background opacity of TableRow in the Home component for better visual contrast and clarity.
…ance - Updated HTML files in the 404, FAQ, and Methodology sections to reference new CSS styles, ensuring a consistent look and feel across the application. - Replaced outdated CSS files with new styles to enhance visual consistency and streamline the codebase. - Removed deprecated CSS files and JavaScript files to optimize loading times and improve overall performance.
…d styling - Changed the position of the orb-container from absolute to fixed for better viewport management. - Updated class names in ModelTableRow for enhanced styling consistency and visual clarity, including adjustments to background opacity and hover effects.
…ance - Updated HTML files in the 404, FAQ, and Methodology sections to reference new CSS styles, ensuring a consistent look and feel across the application. - Replaced outdated CSS files with new styles to enhance visual consistency and streamline the codebase. - Removed deprecated CSS files and JavaScript files to optimize loading times and improve overall performance. - Enhanced ModelTableRow and button components with updated hover effects for better user interaction.
- Changed heading sizes from text-4xl to text-3xl sm:text-4xl in Home, FAQ, and Methodology pages for a more uniform appearance. - Ensured visual consistency in typography across the application.
…ance - Updated HTML files in the 404, FAQ, and Methodology sections to reference new CSS styles, ensuring a consistent look and feel across the application. - Replaced outdated CSS files with new styles to enhance visual consistency and streamline the codebase. - Introduced new JavaScript files for better build management and optimized performance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Please include a summary of the change and which issue is fixed or implemented. Please also include relevant motivation and context (e.g. links, docs, tickets etc.).
List any dependencies that are required for this change.
Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
YOUR_ANSWER
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs