I did not understand the pricing. Is it for the CMS then? Is it possible to self host and connect other CMSes?
No it's another one of those startups looking to cash in on becoming open source. If your open source projects contains a "pricing" page prominently in the top bar, it goes against the open source ethos and you should be ashamed of marketing it as such.
Plasmic.app: Visual editing and content platform for building websites and apps
81–88 of 88 posts
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#82Excited to see this posted here! I think probably because we announced it going open source today. I think the GitHub page is probably a bit clearer than our website right now: https://github.com/plasmicapp/plasmic Basically, it's a visual page builder that plugs into your own Next.js/Remix/React/etc. codebase. Your marketing/content/design team can then build and publish pages without filing tickets on eng. This (co…
Congrats on going open source! Which components are open sourced specifically? Is there any chance it will be self-hosteable? I don't want to host it myself any time soon but I prefer giving my money to a company where that's an option.
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#83Just for fun during the ETHDenver hackathon, I shipped an LLM-powered NFT generator, with 0 lines of code in 3 hours, and won a cash prize. This tool completely changes the game for me and my team.
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#84Best of all, their customer support staff are top tier. Plasmic has a dedicated Slack channel where they respond to questions and solve problems almost immediately. They will literally respond within 5 minutes of a slack and start helping. It's white glove service that is rare.
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#85Excited to see this posted here! I think probably because we announced it going open source today. I think the GitHub page is probably a bit clearer than our website right now: https://github.com/plasmicapp/plasmic Basically, it's a visual page builder that plugs into your own Next.js/Remix/React/etc. codebase. Your marketing/content/design team can then build and publish pages without filing tickets on eng. This (co…
I think another thing interesting about Plasmic is that it is a bit ambitious in trying to combine some seemingly disparate genres: - Webflow, Wordpress and other page builders - Retool and other tool builders - Glide and no-code app builders - Contentful and other CMSes Today these are different tools to specialize in, but the line between, say, a website and an application is blurry (consider an ecommerce storefron…
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#86Earlier quoted context omitted.
Mozilla needs to step up its game or its browser is gonna disappear :(
Or maybe Chrome needs to stop implementing non standardized APIs and becoming the new IE
Curious, what API this page uses that's so valuable to discard another browser
Re: Plasmic.app: Visual editing and content platform for building websites and apps
#87Re: Plasmic.app: Visual editing and content platform for building websites and apps
#88Earlier quoted context omitted.
This is my main concern too. I don't understand why tools like this "pick a winner" with a specific framework instead of rendering to Web Components with a framework wrapper, or using something like Stencil[1] that can render to any framework. [1] https://stenciljs.com/
We wanted to support tight integration with people's existing codebase, so that it is easy to use your React components directly in Plasmic, or to read data from your React contexts provided from outside of Plasmic, or to have your code components communicate with each other via React contexts when they're used within Plasmic, etc. There's power in being in "one React tree" with your existing app. I imagine it's poss…
There are several lightweight wrapper libraries to "reactify" web components.
Going the other direction is not as easy. While it's possible, it involves loading all of react into another framework.