You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some editors (namely myself) may have advance knowledge of comic metadata, due to subscribing on Patreon. These editors should be able to add the next day's comic into the database ahead of time.
Some considerations I've thought of:
Enable the editor to manually add the next day's comic to the database with a UI element
Comics created in the database by an editor (rather than the script) should be in a hidden state, only viewable to those with editor keys
The script that currently adds each day's comic should check if the comic exists in the database, and if it does, it should simply unhide the existing comic metadata, rather than creating a new row
Editors with keys should have the ability to publish/unpublish comics (aka show or hide them from regular viewers), perhaps limit to the most recent 5 comics for standard editor keys?
Editors with keys should have a client-side switch to show or hide unreleased comic info (aka spoiler a spoiler toggle)
There are probably some other considerations that would need to be thought through, but I don't exactly have a solid understanding of how the backend system works here. Happy to discuss here or via DM any of these ideas.
The text was updated successfully, but these errors were encountered:
Editors with keys should have the ability to publish/unpublish comics (aka show or hide them from regular viewers), perhaps limit to the most recent 5 comics for standard editor keys?
It's unclear to me what this is about. Why should editors have the power to override the publish state of comics at all? Either they've been published (i.e. the script that detects new comics has run), and the data should be visible to regular users or they haven't been published, and their data shouldn't be visible to regular users.
My thought was that an editor should be able to force-publish the comic, in the event that they happen to catch the comic going live between runs of the script. And unpublishing would be in case someone were to accidentally publish a comic by mistake (say, for example, while editing tomorrow's comic using information from Patreon).
Perhaps an alternate solution would be a way to fire off an event that runs the script to check if the comic is published or not, but I would imagine that would be even more complicated.
Some editors (namely myself) may have advance knowledge of comic metadata, due to subscribing on Patreon. These editors should be able to add the next day's comic into the database ahead of time.
Some considerations I've thought of:
There are probably some other considerations that would need to be thought through, but I don't exactly have a solid understanding of how the backend system works here. Happy to discuss here or via DM any of these ideas.
The text was updated successfully, but these errors were encountered: