Open mimi-uxui-dev opened 2 years ago
feedback 2-22.06.03
1. wireframing feedback
full width
/full height
overlay, which you showed and is super awesome
username/workshops/workshop-title-XYZ
) is the same as in the search bar (which you noticed too) AND the searchbar has the "action button" (e.g. new
, etc...) to trigger actions, just like we could trigger actions by probably typing the command in the terminal ...which tells me, the search bar with the action button and the terminal command line are the same thing so we should merge them.
regarding styling and features for the next iteration:
2. issue structure feedback - maybe you can try to update it with my feedback below?
i love the new TWM issue. i fixed some things about linking to the figma files.
Also the "tags" or "flags" you are talking about ...there is only @input
and @output
and nothing else.
I think we should not use @result anymore ...every task is either textual or an issue link and can have textual sub tasks or sub issue and each of them can have @input
and/or @output
links and thats it. There is nothing else.
regarding the new TWM issue
now the previous issue should not be linked as an @input
, because issues itself should never be @input
or @output
, but instead we take specific resources/links/files/etc... that were @output
on the old issue and use them as @input
in the new issue and additionally use the from field in that input to link to the old issue where they were created.
check the todo list above - i updated the WF figma links to reflect that :slightly_smiling_face:
@input
s coming from the old TWM issue where they were created and added planned @output
s.another example formatted in markdown:
* [ ] some new task on the new TWM issue
* `@input` :package: [`WF 13: iteratin1`](https://figma.com/link/to/wireframe/...) from #101
* `@input` :package: [`WF 05: iteratin 04`](https://figma.com/link/to/wireframe/...) from #101
* [ ] do this
* [ ] do that
* [ ] do some more to produce the final output for the parent bullet point "some new task on the new TWM issue"
* `@output` :question: [WF 15: TWM specs in WF - Iteration 3-](https://figma.com/link/to/wireframe/...)
* [ ] next task
so you see, the above example has:
Ideally we remove the @input
link to the old issue completely and instead add all the @output
figma and other links as @input
to specific tasks in the new issue instead. Because those @input
links will have a from we will know that they came from the old TWM issue :slight_smile:
the new TWM issue can be put as a new task into the issue where the old TWM issue is currently linked, which is our main UI/UX/concept design
issue task:
:+1:
@Todo
@input
tiling window/folder manager (= "folder editor/tool") concept & design ISSUEFile/folder explorer
in a tile in the TWMTap + Hold
in mobile/layout is the equivalent forRight Click
in Web orTap
and the overlay will appear instead ofLeft Click
...
file explorer entry so users can click it to see the menushow more
action to notificationconfirm
,cancel
actions to notification cardopen in ..
option for the wireframe, the only thing will remain is theopen in browser tab
which will be added next to the search bar as an iconopen with ...
overlayicon + workshop title
at the bottom left@input
:package: WF 01: Design inspiration, Figma Link@input
:package: WF 02: Iteration 01, Figma Link@input
:package: WF 03: Iteration 02, Figma File@input
:package: WF 04: Iteration 03, Figma File@input
:package: WF 05: Iteration 04, Figma File@input
:package: WF 06: Iteration 05, Figma File@input
:package: WF 07: Iteration 06, Figma File@input
:package: WF 08: Iteration 07, Figma File@input
:package: WF 09: Overlay, Figma File@input
:package: WF 10: Tab button, Figma File@input
:package: WF 11: File explorer tool concept and design, Figma File@input
:package: WF 12: Tab button -Iteration 2-, Figma file@input
:package: WF 13: TWM specs in WF -Iteration 1-, Figma File@input
:package: WF 14: TWM specs in WF -Iteration 2-, Figma File@output
:question: WF15: TWM specs in WF - Iteration 3 - figma@input
:question: WF15: TWM specs in WF - Iteration 3 - figma@output
:question: WF16: TWM specs in WF - Iteration 4 - figma@output
:factory:twm editor slides
@output
:factory:twm editor linked markdown file per slide in "./slides/<slidename>.md"
@output
:factory:twm editor wireframes
@Info