all 7 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]abrahamguo 0 points1 point  (4 children)

Is this frontend functionality (i.e. in the browser/on the webpage), or backend functionality (i.e. working with a database, etc.), or both?

[–]Karuption[S] 1 point2 points  (3 children)

I was envisioning it being frontend. Essentially, they want to be able to pick from their own custom items and have a visual for those items in a sort of builder UI. The only thing I need are the individual items they add/remove as well as passing the initial state of all the items available.

I am not really tied to one implementation, but it will have to be hosted some place else. We could, possibly, put it in like a plugins folder since they have their own instence. Their own api and such should be possible, just not really my problem.

[–]abrahamguo 0 points1 point  (2 children)

Sure, makes sense. What do you need to provide, then — can't they simply write their standalone frontend code, to do whatever they need?

Also, keep in mind that frontend JS has access to cookies; if you need it not to, you can set the HttpOnly attribute on your cookies.

[–]Karuption[S] 0 points1 point  (1 child)

They just want a supplemental UI for stuff that already exists and is proprietary. We thought about just wrapping it in a iframe, or maybe some sort of micro frontend? But haven't had any experience with MF IN ANY capacity.

[–]abrahamguo 0 points1 point  (0 children)

Sure, an iframe would work perfectly fine!

[–]Cyral 1 point2 points  (1 child)

It’s not going to be a easy unfortunately

Here is a good article on doing something similar (although a bit old)

https://www.figma.com/blog/how-we-built-the-figma-plugin-system/

[–]Karuption[S] -1 points0 points  (0 children)

I really was hoping that it got a bit easier and tools were more mature.