feelback-integrations VS custom-elements-everywhere

Hi, I'm building Feelback, would like an hand to build the svelte integration. I did already for plain JS and React on this SDKs repo.

Are you twilling about internal private docs or internal source but public facing? Because for the latter I’m building Feelback where custom feedback systems can get a grasp on the user perception of the docs as content. I wrote the Case study of Stripe docs where I share some examples.

Hi, just published the technical architecture of Feelback. The article discusses design principles, tradeoffs and tricks used to build the launch architecture of a SAAS.

Hi, I' building a little plugin to add 'Is this page useful?' upvote buttons (with optional feedback) to documentation websites.

Hi, I'm developing several client SDKs for a website plugin, which require some integration with the common UI frameworks like React, Vue, Nextjs, ...

Hi, I made a little plugin to easily add - Like button or Emoji reaction for blog posts - Is this page useful? upvote widgets for documentation pages - Send feedback form to receive advices/error reporting from users

I built a react package on the repository.

Hi would like some feedback on a plugin allowing to receive user feedbacks about your website content. It allows to easily add: - Likes to blog posts - 'Is this page useful?' with up/down votes on documentation pages - Emoji reactions to sections, parts or comments - Send feedback form for tips or error reporting, with custom data

Hi, I'm building client libraries for a website plugin which allows to receive user signals about your website content.

With React (it seems) finally moving to support everything needed (they are the last major framework lagging behind substantially), too, we might be moving to a world post-framework discussions, and real interoperability on a technical level. I think Jake Lazaroff motivates this beautifully with his articles “Web Components Eliminate JavaScript Framework Lock-in” and “The Web Component Success Story”.

Seems it doesn’t work in React, everything is sent as a string. There was a link in the article that shows how well web components work with various frameworks.

https://custom-elements-everywhere.com/

You can see how React fares for itself.

React supports Web Components, just some quirks to be aware of: https://custom-elements-everywhere.com/

You could wrap each component as a Web Component and then import them for each repo. Web Components are not native to frameworks, so the support for them could vary when passing props. Or you could wrap the render method of each framework as a function and then use the receiving frameworks life cycle method and inject it onto the page. If you use frameworks like Svelte or Lit that are "Web Component" based, then you'd need to see if the receiving framework supports Web Components inorder to import the seamlessly.

Check compatibility of React with web components: https://custom-elements-everywhere.com/ It's not directly because of jsx, but because of synthetic "let's make it up" approach of React.

I have been using this approach recently as well, working great thus far ! Some things to consider though: - I would recommend checking if the other frameworks you intend to use have good web components support (looking at you, react): https://custom-elements-everywhere.com/ - There are ways to do so without web components, but I wouldn't recommend them unless your framework has poor web components support.

VueJS actually fails some advanced tests for WebComponents: https://custom-elements-everywhere.com/

So, VueJS docs are actually incorrect when they say it scores 100%. The actual score is 90%.

I had reported this 8 months ago.

Since Web Components are supported natively by browsers, they can be used in any libraries and frameworks either directly or with configurations. https://custom-elements-everywhere.com/ is a great site to check custom elements support status by different libraries and frameworks.