Confused by submissions system

Correct, we don’t provide ways to explicitly set those parts. We construct it all based on some of the data we have with the submission. It’s intended to be fairly basic, where the user simply submits a form, and BadgeOS handles the rest with non-public post types.

Edit: Administrators are able to see them in the admin area and approve/deny/manage.

so how are any of the submissions translated into fully realized content on the site? the approved / denied buttons do not appear to translate the submission into a standard post where tags/categories can be applied.

I guess what I’m most confused about is what the workflow is for the submissions, what do you see as the standard course of operations from when a user submits content to the end of the successful process?

The user fills in a form, located wherever you use the submission form shortcode, and it creates an internal post in the submission post type, which administrators can look at and review in the WP admin. For admins only, there is a list on the frontend that should be able to be used as well. Users themselves won’t see either location.

Once you approve/deny, the details for the submission/achievement get recorded to the appropriate user, and they’re marked as having earned the achievement or not, and are awarded appropriately. They’ll see the results of the submission via the achievement, just not the submission themselves.

For the benefit of others, I was initially confused by this, too. “Submission” does not mean “submitting content to be approved and then displayed on the site,” which in WordPress terms is what ‘submission’ usually means. E.g., BadgeOS isn’t letting someone submit a post for approval and publication.

In BadgeOS terms, it should probably be called “Evidence” or “Application,” as in, you are applying for an achievement and providing whatever evidence the achievement requires. An admin must manually review your application and approve it, which would then award you.