Closed Mehrabbruno closed 1 year ago
13min
24min
@output
📦 Presentation slides for github issues top level comments for tasks v0.0.2
13min
5min
1h51min
@output
📦 Presentation Slides for creating new issues and markdown
35min
@output
📦 github issues top level comments for tasks [4/6] v0.0.2
24min
@output
📦 Presentation slides for [Connecting Figma With GitHub] v0.0.2
20min
@output
📦 Connecting Figma With GitHub [3/6] v0.0.2
20min
@output
📦 creating new issues and markdown v0.0.1
creating new issues and markdown v0.0.1
This should hopefully cover up all the stuffs regarding markdown and separate that with the previous top comment of github
videofeedback 2022.11.25
Introduction to Figma Version control and Task Management [1/6] v0.0.1
:+1: perfect
github issues top level comments for tasks [4/6] v0.0.2
:+1: perfect
Worklog comment structure [6/6] v0.0.1
:+1: perfect
Version Control on Figma [2/6] v0.0.1
**NEW PROBLEM - after some feedback from other people :-)
see https://youtu.be/zhudzjCAeVM?t=161
please edit the old popovers
wireframes. They are not supposed to contain versioned content. In the content area of that version it shows all the individual component names with their individual versions, but that made no sense to people, because the popover component was a component that included all these designs inside itself without independent design parts with versioned names ...and was later marked as deprecated by us when we split those into individual successor components with their own page/name/version.
Multiple people were confused by it when i shared the video with them and they all asked how come that the popover component version has design content that has individual version names but is not listed in dependencies/dependents ...and i think the issue is that in the old popover component those designs were not yet independent components before we split them.
...
Could you fix that?
We need Version Control on Figma [2/6] v0.0.2
Connecting Figma With GitHub [3/6] v0.0.2
oh no :-) haha, almost perfect
The link in figma to the project management software should link to the worklog comment (in which the output document was introduced), because the whole issue with all comments as such has potential lots of output links and many figma components would share the same issue link, so we should link instead directly to the github worklog comment.
Could you fix that part when you copy the github issue link instead of the worklog comment link?
Question: Instead of re-recording the video, could you just record the part where you copy the comment link and use that on figma and then cut the video to insert that? That should be less work - but if re-recording is quicker, thats fine too.
additionaly - also to mention: The "publish" button needs to be pressed only once, while the github issue link is meant to be added to every component version, but a user does not need to click publish every time they make a new component - maybe that's worth mentioning.
Create new issues and markdown text v0.0.1
you mention more information about the input/output would be shared in another video, but that video doesnt seem to exist
the example.com
link in both the link to the button component and the comment is a bit confusing. I think it would be good for people to see how to get a github worklog comment link and the button component repo could be a link to a figma page to make the example more realistic and meaningful
Otherwise: :+1: great video :-)
@inputs, @output, next and their status [5/6] v0.0.2
In the video Create new issues and markdown text v0.0.1
you mention this video,
which will share more information about the input/output status, but this video
doesn't seem to exist yet, so below i will share all feedback that i previously shared regarding the next version of this video :-)
The new version of this input/output/next/from/status video should mention:
@output
:package: document links have a from comment
link and why.
And:
next
and from
fields correctly:planned:
and what other status exists and when they are used:
@output
from
:crystal_ball:Of course to mention the rules:
output
used in the same issue needs no next.output
needs a from comment
,
which can be mentioned, but he details of the "from comment" will be explained in the next video (just shortly showing such a comment is ok)...
Could you fix that?
We need @inputs, @output, next and their status [5/6] v0.0.2
a new playlist version
:-)We need a new playlist that puts it all together :-)
addition: No work should ever be done when there is no task/issue to make a worklog comment. So if there is ever a situation where it seems work needs to be done before worklogs can be made, that is a strong signal to check back and discuss matters first
2023.05.17
29min
14min
@output
📦 Presentation slides for [Connecting Figma With GitHub] v0.0.3
39min
16min
@output
📦 Connecting Figma With GitHub [3/6] v0.0.3
feedback 2023.05.20
great. yeah, al fine. let's finish all the tasks and link the final results, so the top level comment where we started to make this playlist for figma version control and task management can be closed.
It would be great, if you could link all issues properly and mark remaining tasks as done and create the final playlist, use all
as @input for that task and final worklog and then immediately mark them all as final output but with the
to mark list all the inputs also as final output including the playlist :-)
21.05.2023
39min
2min
@output
📦 Task Management and version Control v0.0.321.05.2023
13min
35min
@output
📦 Task Management and Version Control v0.0.4
@todo
124
@input
📦Presentation slides for github issues top level comments for tasks v0.0.1
from #124@output
📦Presentation slides for github issues top level comments for tasks v0.0.2
fromcomment
@output
📦Presentation Slides for creating new issues and markdown
fromcomment
@input
📦github issues top level comments for tasks [4/6] v0.0.1
from #124@output
📦github issues top level comments for tasks [4/6] v0.0.2
fromcomment
@input
📦Presentation slides for [Connecting Figma With GitHub] v0.0.1
from #124@output
📦Presentation slides for [Connecting Figma With GitHub] v0.0.2
fromcomment
@input
📦Connecting Figma With GitHub [3/6] v0.0.1
from #124@output
📦Connecting Figma With GitHub [3/6] v0.0.2
fromcomment
@input
📦Presentation slides for [Connecting Figma With GitHub] v0.0.2
@output
📦Presentation slides for [Connecting Figma With GitHub] v0.0.3
fromcomment
@input
📦Connecting Figma With GitHub [3/6] v0.0.1
from #124@output
📦Connecting Figma With GitHub [3/6] v0.0.3
fromcomment
@input
📦Presentation Slides for creating new issues and markdown
@output
📦creating new issues and markdown v0.0.1
fromcomment
@input
📦github issues top level comments for tasks [4/6] v0.0.2
@input
📦Connecting Figma With GitHub [3/6] v0.0.2
@input
📦Creating new issues and markdown v0.0.1
@output
📦 Task Management and version control playlist_v0.0.3 from comment@input
📦 Task Management & Version Control playlist_v0.0.1 from #124@input
📦 Task Management & Version Control playlist v0.0.2 from #124@input
📦 Task Management and version control playlist_v0.0.3@output
🏁 Task Management and Version Control v0.0.4 from comment