Skip to content
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.

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

[Feature] add ability to manage past board members listing page, similar to team-index context. #80

Open
1 task done
possumbilities opened this issue Dec 9, 2024 · 0 comments
Assignees
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: awaiting triage Has not been triaged & therefore, not ready for work

Comments

@possumbilities
Copy link
Contributor

possumbilities commented Dec 9, 2024

Problem

The board listing page originally was a table edited through the TablePress plugin. This is not ideal, and it did not migrate fully into the new site. To resolve this, post migration, a table was inserted into the page manually, and is currently edited manually in the same fashion.

Some form of GUI based editing would be more user-friendly.

Description

If we follow a similar functionality route to the team-index context we might be able to accommodate this more easily. However, there are other dimensions of data that are present on that page that are not captured within a Person content type post.

Once the presentational UX is resolved here, this can migrate to an adjoining Issue within vocabulary-theme to work out the backend implementation details and modelling.

Alternatives

Rebuild the table within Tablepress, improving the manageability, but not making it match other routes of "person listing" management.

Implementation

  • I would be interested in implementing this feature.
@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Dec 9, 2024
@possumbilities possumbilities self-assigned this Dec 9, 2024
@possumbilities possumbilities added the 🕹 aspect: interface Concerns end-users' experience with the software label Dec 9, 2024
@possumbilities possumbilities moved this to Backlog in possumbilities Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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: awaiting triage Has not been triaged & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

1 participant