Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redo Sprig gallery/gameplay experience #1937

Open
4 tasks
recursiveforte opened this issue Jul 10, 2024 · 2 comments
Open
4 tasks

Redo Sprig gallery/gameplay experience #1937

recursiveforte opened this issue Jul 10, 2024 · 2 comments
Assignees
Labels
feature request New Feature or Request

Comments

@recursiveforte
Copy link
Member

recursiveforte commented Jul 10, 2024

I propose we separate the editor from the experience of playing a game. When opening a game, we should only show the game and its description/author/metadata - there should be a button to open the editor interface, which includes the code and help panes. This helps turn Sprig into more of a "game platform" instead of a platform purely focused on creating games, drawing people in who would not otherwise play games in the gallery.

The former interface - focused on gameplay - should show the game as the largest element and have the following functions:

  • a share button
  • a button to open the code editor
  • a button to upload the game to the console
  • a description (determined by the text in the first comment block, after the metadata).
  • information on the submitted date, author, # of views, and an upvote function

Tasks

  1. feature request
    recursiveforte
  2. feature request
    recursiveforte
  3. feature request high priority
    EerierGosling
  4. feature request
    recursiveforte
@recursiveforte recursiveforte added the feature request New Feature or Request label Jul 10, 2024
@grymmy
Copy link
Contributor

grymmy commented Jul 10, 2024

I approve these generally but please create individual feature requests per bullet item and add any required product info to each for their impl

@grymmy
Copy link
Contributor

grymmy commented Jul 24, 2024

I am closing this issue as the actual work behind it is logged as separate issues.

@grymmy grymmy closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2024
@recursiveforte recursiveforte reopened this Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New Feature or Request
Projects
None yet
Development

No branches or pull requests

2 participants