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

Toornament integration #389

Open
skamoen opened this issue Mar 15, 2017 · 0 comments
Open

Toornament integration #389

skamoen opened this issue Mar 15, 2017 · 0 comments

Comments

@skamoen
Copy link
Member

skamoen commented Mar 15, 2017

I've started working on a Java-based Toornament api client. I'd really like to do more with this platform, so let's discuss what the MVP is for Toornament integration. Based on the desired features, I can prioritize api client features.

The platform can be used standalone, so it's usable regardless of what we integrate into the api.

I think we need more then just the api client features, so we'll need some sort of wrapper model to add our own fields to the Toornament fields.

Toornament MVP

Let's look at this from a front-end perspective:

lancie-frontend

Regardless of where we show this information (That's front-end specific)

  • Show available tournaments (with a link to subscription)
  • ?? Register yourself/team for a tournament
  • Show the current bracket/standings

lancie-admin

  • Create tournaments
  • Edit tournaments
  • Hide/show tournaments
  • View participant details
  • ?? Check-in using bracelet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants