Add more to the TODO
This commit is contained in:
parent
e1935b7935
commit
6ba7b13e3e
43
TODO.md
43
TODO.md
|
@ -56,6 +56,48 @@ impl ViewState {
|
|||
This pattern allows for each Object to be stored at most once during a route, and it also avoids
|
||||
cloning when multiple submissions were posted by the same profile, for example.
|
||||
|
||||
## Toolkit
|
||||
Currently, the Submission Boxes shown on the home page and profile page are defined by
|
||||
hyaenidae-server. This is potentially a future issue for Themeing, because the colors are not set by
|
||||
the toolkit.
|
||||
|
||||
Tasks:
|
||||
- Create a grid/hover-overlay component in the toolkit and use it to implement the submission boxes
|
||||
|
||||
## Pagination
|
||||
Right now, the only things that paginate are Submissions. This could potentially cause issues on the
|
||||
Notifications page, or the Admin page.
|
||||
|
||||
Tasks:
|
||||
- Enable pagination for Known Servers, Federated Servers, Federation Requests,
|
||||
- Enable pagination for Reports
|
||||
- (potentially) Enable pagination for comments on submissions
|
||||
- this one is less clear because comments are tree-structures
|
||||
|
||||
## Submissions
|
||||
Right now, following doesn't do much of anything from a user perspective. A follower can view
|
||||
followers-only posts on the author's Profile, or on the Home Page, and following a remote profile
|
||||
enables that profile to federate new submissions to the local server.
|
||||
|
||||
Followers-Only submissions also exist on the back-end, but it is not yet exposed in the UI.
|
||||
Originally, this was blocked on adding a select component to the toolkit, but that blocker has gone
|
||||
away.
|
||||
|
||||
Tasks:
|
||||
- Create a Submission View in which submission from followed profiles can be viewed in publish
|
||||
order
|
||||
- Expose Submission Privacy Settings on the Submission Update page for unpublished submissions. It
|
||||
does not make sense to allow changing submission privacy after a submission has been published.
|
||||
|
||||
## Registration
|
||||
There is currently no way to disable or limit registration to Hyaenidae
|
||||
|
||||
Tasks:
|
||||
- Add an option in the Admin settings to disable registration
|
||||
- Create a concept of Invite Links which can be used N (user specified) times to register accounts
|
||||
when registration is disabled
|
||||
- Add an option in the Admin settings to generate invite links
|
||||
|
||||
## Tags
|
||||
Tags are useful for searching Hyaenidae for content. There should be a tag system that makes it
|
||||
simple to search for submissions.
|
||||
|
@ -73,6 +115,7 @@ Tasks:
|
|||
ensure the object is not accessible locally
|
||||
- Enable forwarding reports to origin server. There is already code written to perform this
|
||||
forwarding, but it is not exposed in the UI.
|
||||
- Enable viewing of closed reports
|
||||
|
||||
## Reacts
|
||||
Reacts are similar to "likes" on other platforms, but do not get added to a collection for a given
|
||||
|
|
Loading…
Reference in a new issue