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
A feature like on ArtStation when you create a new portfolio item, but for creating a mod page on the Forge. Ability to set the mod to public or hidden. This way we can work on the mod page before making it public. Maybe should make it only available before setting it to public so people don't abuse the function to all of a sudden hide their mods or by accident.
I believe this is already a thing with how we are going to handle publishing mods.
Basically, you will need to set if a mod is published or not and will be able to set a publish after date as well, if you want to plan a public release time.
If a mod isn't published it will only be accessible by the author and site moderators.
I believe this will apply to specific mod versions as well.
@refringe can correct me if I got any of that wrong.
We have a field for a published date set-up and working in the back end, but as of right now there's no UI that's exposed for mod creation, so the details surrounding exactly how that field will be used from a front-end perspective are still in the air. We'll keep this issue around so we can circle back when there is more to talk about.
On the front-end creation form there's probably going to be a toggle for if the mod is published or not, and another field for a published datetime. Unpublished mods have the published_at column set to null, published mods have published_at column set to a specific datetime (or now(), if no date is specified).
A feature like on ArtStation when you create a new portfolio item, but for creating a mod page on the Forge. Ability to set the mod to public or hidden. This way we can work on the mod page before making it public. Maybe should make it only available before setting it to public so people don't abuse the function to all of a sudden hide their mods or by accident.
Originally written by MoxoPixel
The text was updated successfully, but these errors were encountered: