___victor

It really depends on how well you want the design to integrate with your codebase, which is where most of Plasmic power lies on, such as: leveraging your existing custom components as building blocks within the design tool; or adding heavier instrumentation to props and rendered contents on the code side.

It is possible to use Plasmic's render API (https://docs.plasmic.app/learn/render-api/) to fetch the rendered HTML and just render your designs using any framework, but that means it's a more limited experience.

Plasmic does have support to different data integrations, including databases: https://www.plasmic.app/integrations

> is it easy to use it for client-side-only stuff and leave the backend alone?

Yes - using Plasmic to manage landing pages design and content is our main use case!

We still need to improve the experience for open source contributions, but we are open to that! That being said, React is still our main priority at the moment.

I'm not familiar with Blazor, but you may also explore our render API (https://docs.plasmic.app/learn/render-api/). It allows fetching rendered HTML from Plasmic servers, then you would just render it in the DOM.

While Plasmic does offer the flexibility to export designs to other frameworks like Angular, Vue or even plain HTML, it is mainly targeting React. Some features, such as the ability to register custom components from the user's codebase, are React-specific.