Update Project roadmap
This commit is contained in:
@ -1,9 +1,24 @@
|
||||
|
||||
|
||||
UX:
|
||||
- if I want to learn more about a module and click the information link, it navigates the current page I'm on and loses all my progress - you probably want to either save the state as you go or make it so modules pop up a new window
|
||||
|
||||
|
||||
|
||||
* Move all this to issues?
|
||||
* Landing page
|
||||
- Better explanation of what this is. What's a rule? What is needed to begin?
|
||||
- It's very white and black, some additional accent color would be nice.
|
||||
* Modules
|
||||
- If you click on a module, it eliminates progress. Need to make all module links open in a new window, in the short term.
|
||||
- Seem too academic
|
||||
- Some are empty
|
||||
* Simpler questions
|
||||
- The rights
|
||||
* Javascript output button
|
||||
- Could it output to IPFS or some other persisitent storage medium?
|
||||
* Rules (ready-to-deploy presets)
|
||||
- Brand preset rules as CommunityRule rules with tools to create badges out of them
|
||||
* Less textual, more visual header for Rule pages
|
||||
* Further modularity
|
||||
- Aim for a logic of [progressive disclosure](https://en.wikipedia.org/wiki/Progressive_disclosure), making templates really simple but facilitating more complex iteration
|
||||
- In _modules, develop pseudocode primitives and complex modules with inputs, outputs, and actions
|
||||
|
Reference in New Issue
Block a user