Plugins will be included with export, but there are no guarantee that plugin will work. However you will have access to plugin code, so you can modify and make it working if needed.
We won’t be forcing our plugin creators to make it export ready, as that would require additional work for them, however, we are modifying our own and most used plugins to work with exported code.
That’s as much as we can do. This will cover most basic websites, websites that using regular plugins like popup, accordions, slider etc, however you can’t expect 3rd party plugins built by other users specifically for something else to work on export out of the box, it’s not realistic.
Greetings, Everyone! I’ve been closely following the discussions regarding the Divhunt export code, and I’d like to provide some clarity on a particular matter. If the Divhunt team is committed to putting forth their best effort, it should be possible to export the front end and host it as a static website, thereby moving away from the Single Page Application (SPA) structure. However, I must admit, I’m struggling to see a compelling reason for this aside from creating a backup.
Divhunt already takes care of various crucial aspects, including hosting, content management, plugins, Canva integration, and real-time modifications. Therefore, the idea of exporting your site to host it elsewhere raises some questions. You’d need to manage hosting, handle tasks like installing new PHP versions, and more. Not to mention, Webflow charges for front-end exports.
I’m genuinely interested in understanding why there is a desire to export the website at this point. Could you please provide some insight to clarify this aspect?
My reason is, I use the same hosting company for all of my clients - they provide outstanding hosting - further, I usually add PHP for certain features and other server side features. I’m super comfortable with my host and would never consider leaving them, or start hosting clients in multiple places.
Moral of the story is, not all hosts are the same, or offer the same services/features. So when you find a good one, you stick with it (at least I do )
I love Divhunt for their builder - not their hosting - to be fair, I don’t know anything about their hosting - but my current host has everything I would ever want and more. So a builder is all I need.
I used to use Webflow, but I can’t stand the limitations on how many projects you can have based on how much you pay.
So to answer your question - most web dev’s already have their preferred hosting companies - if they don’t, then I’m sure they would be fine hosting with Divhunt.
Client uses a different platform. It can’t be used with Divhunt. And, they also have — unfortunately — Bootstrap 3.
So, how can I find a visual builder with a code editor that lets me design and use twig (or any other, really) in the code editor? Then lets me export the working static site, but becomes dynamic when uploaded with SFTP.
Bootstrap Studio doesn’t cut it, too strict, for example.
This is my use case. But, on the other hand, with the upcoming Google Sheets feature will give a lot more possibilities to work with data.
Currently, these 2 features are the ones that I’m super excited for. The rest of the Divhunt features can be used depending on the project.
Why wouldn’t you like the Divhunt hosting?
It’s multi-regional, global CDN + it can handle billions of monthly requests.
So you don’t need to worry if your website gets super popular, you don’t need to worry about data, backups and much more.
It can’t be slow as we use replications, partitions, pools and many more features, so even if you have for example 1,000,000 blog CMS items, it’s still fast
@dejan - it’s not that I wouldn’t like Divhunt hosting, I’m sure it’s very good - but I currently don’t have interest in having different hosting companies for my clients. Maybe at some point that will change, but again, I purchased Divhunt specifically for the builder.
Sorry for misunderstanding, I meant to be done for end of Sunday - Monday morning, as the only time I can truly focus is weekend, due to support, questions, bug fixes etc during the week.
@David - yeah, took a chance - it’s a simple site so it wouldn’t take long to whip up in a different builder, but I wanted to learn Divhunt, so no better way
We’ve just released an alpha version, tomorrow we will continue working on it and will release beta version, of code export application, so you can try it out, and let us know if you get into any issues.
Just keep in mind, everything that is depended on Divhunt’s backend to work, will not work on your local machine or on any other server. So, CMS, REST API, some plugins (known so far is Popup when used in combination with component), in future these are going to be memberships, eCommerce, etc.
Here’s how you can try it out:
Go to admin settings of your project
Open applications & install Wexport
Go to yourwebsite.divhunt.art/wexport
While you can export and host your site anywhere, here’s why you might want to stick with Divhunt as your hosting provider:
Any features linked to the Divhunt back-end system, like the CMS, REST API, and some plugins, won’t work elsewhere.
Our hosting is top-notch and fine-tuned for the best performance.
With Divhunt, your site is hosted around the world through CDN, making it fast no matter where your visitors are.
Your website pages load instantly on Divhunt as it uses Single Page Application (SPA) technology.
Wow! Holy Cow! This is fantastic for an alpha version! Here are my initial impressions:
Very clean code! WHOOP WHOOP!!! This was critical for me - as many builders I have used in the past have terrible exported code - so this is really important and I am SO happy after looking at the code.
Currently the exported code has a CSS and JS folder. I would like to see an “images” folder with all the images used in the site (instead of linking images from https://global.divhunt.com/…)
KEEP UP THE GREAT WORK! I will soon be changing my profile name to “Divhunt Lifer”
Awesome, working perfectly.
If I want to import the files back to Divhunt only, How to do that? Is that possible now?
So then I can share the files after exporting to client and he can import in his Divhunt account.
What whaaat! I agree with @ShorePatrol about getting the images exported as well, plus having an export button would be wonderful somewhere in the builder. Thanks.
I would think being able to “share” a project with another Divhunt user would be better for this need…Importing can get messy, especially if changes were made to the code before importing - if I were working for Divhunt, I wouldn’t support importing. Sharing a project however, might be something for their roadmap based on how many users would need this (I don’t think I would ever need it).
If not import, then may be a clonable feature, like Webflow or Framer.
I understand, by the export feature your needs will be fulfilled but for people like me who don’t have a requirement to host somewhere else, we need this feature. So then we can have a backup or we can sell templates (as Divhunt Theme) anywhere, just like WordPress.
It’s obvious if any changes are made before importing, it may break after import, just like WordPress themes. So people who will need to import they will keep that in mind.
Anyway, maybe you don’t need this feature, But It’s what I need, so I asked.
I hope I made it clear.
)