Replies: 3 comments
-
tldr : i want the same html/css parser as the studio sdk version and im willing to pay for anyone that can help me with that. |
Beta Was this translation helpful? Give feedback.
-
on top of that I even tried the studio sdk but I do not like it from a privacy standpoint ,to me it seems that this project turned to be a saas. i dont want anyone to stalk my customers or myself. |
Beta Was this translation helpful? Give feedback.
-
I even try the same .html as I try on the studio sdk demo and end up with a wide range of errors when importing those html : Uncaught TypeError: this.model.classes.pluck is not a function |
Beta Was this translation helpful? Give feedback.
-
🔍 Assistance Needed: "Import Code" Functionality in Open-Source GrapesJS vs. Studio SDK
Hello GrapesJS Community,
I hope this message finds you well. I'm reaching out to seek assistance and gain a deeper understanding of the "Import Code" feature within GrapesJS, specifically comparing the open-source version with the Studio SDK version.
🛠️ Issue Description
I've been working on a complex project using the open-source GrapesJS editor. Recently, I attempted to utilize the
<import code>
feature to import various complete webpages into my project. However, I've encountered significant issues:Styling Discrepancies: When importing pages using the open-source GrapesJS, the styling often appears very off or broken. This issue is prevalent across multiple websites, including:
Studio SDK Success: In contrast, using the same import process within the GrapesJS Studio SDK (Studio SDK Demo), the styling and layout are preserved accurately, closely matching the original websites.
📄 Questions
How Does the "Import Code" Feature Work in Studio SDK?
Are There Any Plugins Available?
Differences Between Open-Source GrapesJS and Studio SDK:
💡 Why I Prefer the Open-Source Version
I've already invested significant time and effort into building a complex project using the standard open-source GrapesJS editor. Migrating to the Studio SDK would require substantial rework, so I'm keen on enhancing the import functionality within the open-source version to match the capabilities of the Studio SDK.
** 💰 Compensation Offer **
I’m willing to compensate anyone who can provide guidance, share relevant resources, or assist in implementing a solution to enhance the import functionality within the open-source GrapesJS. Your expertise and support would be invaluable in saving me a significant amount of development time. ($200 USD, crypto or paypal).
🔧 What I've Tried
To demonstrate the issue, I've created a CodeSandbox Example showcasing my current implementation. Here's a snippet of the code I've been working with:
Beta Was this translation helpful? Give feedback.
All reactions