This will require some design before we can begin this ticket.

This will require some design before we can begin this ticket. Mainly the icons needed for the property menu. Maybe this also changes the font sizing and spacing too

Here is an example of how GitHub is handling edits. Could be useful inspiration.

the UX/UI for toggling the collapse feature needs to be designed before implementation.

This will require some design before we can begin this ticket. Mainly the color schemes and the icons needed for the property menu.

can it be done?
what would be a good format?
are there other formats that would be helpful?
what new UX/UI will we need?

This ticket is design blocked by #17

Engineering asked if we could link to a version of a file.

A user left the following comment about not being able to add links.

I think this user's feedback is more specifically referring to links inside the body of the changelog text itself. I believe there is a limitation here in terms of what is available from the widget API in terms of formatting. To my knowledge they only offer single or multiline input text fields and those fields don't have the option for Rich Text or Markdown etc.

Is there a way around with an additional library or something?

We need to update the Figma Community page and the GitHub repo with new copy and graphics.

GitHub Repo

• update the image at the top to match the image used on the community page (Ryan to provide a new image)
• assess if any updates are needed to the Overview section
• update the Features section
  • 7 changelog types (Coming Soon) -> 7 log types (New!)
  • 9 link types (Coming Soon) -> 11 link types (New!)
• update any copyright dates such as on the license page?
• add/remove any links or required references for new icon usage

Figma Community Page (Ryan can make the edits, need to prep the content)

• update the image at the top to the latest community header image
• open to copy suggestions in the Features section.
  • I feel like instead of a list, we can use h3 headers and supporting text for the specific feature, such as how to add a link, etc
  • 7 changelog types (Coming Soon) -> 7 log types (New!)
  • 9 link types (Coming Soon) -> 11 link types (New!)
• feedback section content updates
  • any additional branding-related updates from Kat
  • add/remove any links or required references for new icon usage
• a reminder to update Formidable Figma org content

What is the best way to implement this feature without adding other logos to the codebase?

More context in this thread.

@cpresler

"Nice! It would be awesome if changes added to FigLog would trigger a new version in Figma's version history. Even better if it could automatically sync up with non-autosave version tags :)"

this comment was left on the Figma community page by Pascal Adriaansen. Pretty useful idea I think.

we need to investigate if we can do this, I think we might be able to.
what happens when a log is updated, can we keep them in sync?

This comment was left by Andrew Moore on our Figma community page...

"Excellent widget, we love it for our design library change log. I would like to recommend adding the ability to lock the widget so that accidental changes can not be made to the specific frame."

This can easily be done. A few things to note.

• this could be a feature for the widget owner only, contributors would then either be able to edit or not
• not sure if this is the right way to go, what if the widget owner is no longer around then the widget could be locked
• I think having the feature be available to anyone, so at least that person had to, on purpose, make changes is okay
• maybe reach out to Andrew and see if he wouldn't mind if we asked some questions about his use case to make sure we are hitting the mark?

what does a user see right after clicking the "new" button?

date is automatically captured
edited or not is automatically generated

how does a user select or change the type of log (depreciated vs breaking)?
how does a user delete a log?
can/should the user be able to change the date of a log?
should there be a setting for not allowing edits?

https://keepachangelog.com/en/1.1.0/

We have additional image slots on our community page, we could use one for this?

https://help.figma.com/hc/en-us/articles/360042293394-Publish-plugins-to-the-Figma-Community
https://github.com/stefanwittwer/FigType

"We're loving it, although there was a point where the fidget completely froze and I had to restart it, might want to look into that."

The above comment was left on the Figma community page. I think it would be good to get an engineer to have a look at the code and see if there are any performance tweaks to be made. Otherwise, we can keep an eye on this. I've never had the widget freeze personally, even with having multiple on one page.

We need a way to reproduce to fix.

https://lucide.dev/

Not sure if this will be possible. This will require some design before we can begin this ticket.

The Idea
The basic idea behind this feature is for the owner of the widget, the user who added the widget to the file, to have admin-level rights to edit and remove all changelogs and content. Whereas collaborators on the widget will only have access to edit and remove their own changelogs.

Some experimentation has been done already for this. Basically, because of how Figma widgets work ("you touched it last") this might need to be redesigned. It seems we are hitting a ceiling in terms of how multi-player editing works with widgets but maybe there is a creative way around it.

The Blocker
Currently, the widget displays in the state the last collaborator to the widget left it. So in the previous attempt to implement this if user A adds a changelog, then clicks away. User B will see the widget in that very same editable state even though they should not be able to edit. Once User B interacts with the widget, the widget will rerender the state based on User B's credentials. When user A comes back they won't be able to initially edit their previous logs but will be able to edit user B's logs, because they will be seeing the widget as User B left it. This is what I mean by "you touched it last display". Essentially all users see the same view instead of each user seeing a dynamic view based on their difference in state.

More information on how Figma widgets run.

https://github.com/stefanwittwer/FigType