Skip to content

[Feature] Implement datatables in Cases Page #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 task
Tracked by #329
Queen-codes opened this issue Feb 26, 2025 · 0 comments
Open
1 task
Tracked by #329

[Feature] Implement datatables in Cases Page #277

Queen-codes opened this issue Feb 26, 2025 · 0 comments
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@Queen-codes
Copy link
Contributor

Problem

vocab-refresh: The current case page of the CC Legal Database uses a table component made for the legacy vocabulary. This affects consistency across Creative Commons websites and limits the table's functionality. DataTables was successfully implemented in CC Open Source's vocab-refresh branch providing improved interactivity and usability.

Description

Replacing the existing table with a DataTables implementation will ensure consistency with Vocabulary and enhance usability.

Additional context

Implementation

  • I would be interested in implementing this feature.
@Queen-codes Queen-codes added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Feb 26, 2025
@cc-open-source-bot cc-open-source-bot moved this to Triage in TimidRobot Feb 26, 2025
@Queen-codes Queen-codes mentioned this issue Jan 27, 2025
Open
70 tasks
@TimidRobot TimidRobot added 🏁 status: ready for work Ready for work 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 31, 2025
@TimidRobot TimidRobot moved this from Triage to Backlog in TimidRobot Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
TimidRobot
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TimidRobot @Queen-codes