30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
|
|
|
|
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
|
|
* 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
|
|
* Compatibility with Loomio?
|
|
- Translate each module into Loomio practices, implicitly or explicitly (e.g., time for a proposal, threshold, voting options)
|
|
* Module system with database
|
|
- JavaScript pulling from GDocs?
|
|
- Use Jekyll yaml in _data/ to create modules
|
|
- Jekyll csv data pull? https://jekyllrb.com/docs/datafiles/ |