Overview

Add a blog customization option that lets a user disable submissions.

Background

Right now, when activating Submit.as, all blogs on an account or team automatically get a Submit.as page. Giving users the option to disable submissions will help keep the UI clean, and reduce mental overhead for users.

Users

Creating the issue now, after activating Submit.as for a 5-year user interested in trying it out for a project (i.e. Submit.as isn't their primary reason for using the platform).

Implementation

Add an extra flag or collection attribute that indicates whether a collection should have a Submit.as page.

If so, keep current behavior on Write.as and Submit.as. If not, on Write.as hide the Prompts and Submissions blog items; on Submit.as return a 404 on the collection page.

Design

Idea 1: Add an option, only visible with Submit.as activated, that lets users disable submissions.

Idea 2: Add an always-visible option that lets users enable submissions. If they have Submit.as, simply enable submissions; if not, allow them to purchase the upgrade (ideally through a modal window).