+26
README.md
+26
README.md
···
7
7
Check out this tldraw document and the assorted sub-pages to get a feel for what the plan is. Feel free to reach out to business@goose.art if you want to contribute!
8
8
9
9
[skyshrooms tldraw](https://www.tldraw.com/f/wcc4EMn5BlB-4HFOkCEw2?d=v-518.-2136.2714.4696.IB-qEjCfElG4a4DaOVr9w)
10
+
11
+
## Approximate TODO list:
12
+
13
+
### Backend
14
+
- [ ] Create way to index Card , Deck events from the jetstream
15
+
- [ ] Set up signer API that can create new Signed Cards
16
+
- [ ] Create card claim API that issues Card Claims for drawing from a given deck
17
+
18
+
### Frontend
19
+
- [ ] Build out decks list screen, assume there will be more decks
20
+
- [ ] Make more small, reusable frontend components to ensure consistency
21
+
- [ ] Create leaderboard screen
22
+
- [ ] Clean up / maybe totally redo the entire battle UI, looks horrible
23
+
- [ ] Figure out how to make cards stick together, drag and drop tokens
24
+
25
+
### Game Design
26
+
- [ ] Come up with reasonable language for "actions" that can be taken on your turn
27
+
- [ ] Figure out exactly how we want the battlefield to look
28
+
- [ ] Sketch out a few playable cards to test gameplay mechanics
29
+
- [ ] Improve card template design to be more distinctive and beautiful
30
+
31
+
### Housekeeping
32
+
- [ ] Refactor frontend files to be more easily searchable
33
+
- [ ] Move away from importing json directly -> data loading
34
+
- [ ] Try to make some use of server.js stuff?
35
+
- [ ] Write up some lexicons, start dumping test records on atproto instead of storing locally