Publish
A project can go live directly from the editor, or be exported as standard web source code and deployed anywhere. Both paths stay open on every plan, so nothing you build is locked in.
Publish on Lediv
- Click the Publish icon in the header.
- Choose the address your site will live at.
- Click Publish site.
The site is served from that address within seconds. Publishing again updates the site in place. The new version only goes live once it is completely uploaded, so visitors never see a half-updated site.
Only the project owner can publish: people you invite keep editing the project with you, and on a team project publishing belongs to the team owner.
Every file in public/ keeps exactly the address you wrote for as long as the site
is published, so a link you share or a fetch() in your own JavaScript keeps working
after every republish. Visitors get the new version the moment you publish it, with nothing to
configure and nothing to purge.
The Publish panel
Republish pushes your current work live. Next to the address sit three buttons,
each naming itself when you hover it. The pencil changes the
lediv.site address, the crossed-out eye hides the site from search
engines, and the bin unpublishes it. On Pro the panel also lists the last 10
deploys, any of which you can put back live with Restore this deploy. Below it,
Download project exports the whole project as a ZIP.
An address you release is free immediately, and anyone can take it. Nothing is forwarded, and we cannot get it back for you.
Moving a project to the trash takes its site offline, on your custom domains as well, and
reserves its lediv.site address meanwhile, so restoring the project brings the site
back at the same address. Holding that address is what keeps the site counting towards the three
a Free plan may publish, and nothing frees it on a timer: unpublish the site before trashing the
project, or empty the trash, and the slot comes back. Two things do not come back: the earlier
deploys are removed, so after restoring there is nothing left to roll back to, and a preview
link you had shared is turned off for good. Emptying the trash is different, because it releases
that address for anyone to take and disconnects your domains. Neither can be undone.
Sharing a preview before you publish
Create a preview, under Preview link in the Publish panel, builds the project and puts it at its own address, so you can show work to a client or a teammate without publishing it. It works on a project that was never published, and on a published site it leaves the live version exactly as it was. The link lasts seven days, and the panel counts down what is left. Update preview refreshes it with your latest work; beside it, two buttons that name themselves when you hover them copy the link and delete the preview.
Updating it keeps the same address, so a link you already sent stays alive and shows the new version, and the seven days start again when the new build settles, so a preview you keep updating stays reachable. A preview is always kept out of search engines, and it goes offline with the project: moving the project to the trash turns it off.
A preview that runs out is gone for good. When the seven days pass the pages stop being served, and the next preview you share gets a new address, so the old link stays dead for everyone who kept it. Deleting the preview does the same thing sooner.
Anyone with the link can open it. The address is long and unguessable, and search engines are told to skip it, but it is not a password. A preview on a project you never published also takes one of the sites your plan allows for as long as it lasts; deleting the preview gives that back straight away.
Keeping a site out of search engines
Some sites are not meant to be found, like a client review, a staging copy or an invitation page
you send by hand. The crossed-out eye turns that on and off at any time, and
you can tick Keep this site out of search engines before you publish for the
first time, so it goes live with the instruction already on. While the setting is on, every
address the site answers on carries the instruction, a domain of your own included. With it off,
the site is offered for indexing, except on the lediv.site address of a site that
has a custom domain, which always carries the instruction so your own domain is the one that
gets indexed.
This hides the site from search engines, it does not make it private. The site is still served to anybody who has the address, and honoring the instruction is up to each search engine. It is not a password.
Domains and redirects
On Pro a published site can also answer at a custom domain. It takes one DNS record, and the panel walks you through it. See Custom Domains for the record, the apex, several domains on one site, and what to do when one stops working.
Sites on a lediv.site address share one domain, so a cookie set there is visible to
every other published site. Keep state in localStorage or prefix cookies with
__Host-. A domain of your own shares nothing with other sites, so none of this
applies there.
A file named _redirects at the root of the project sends visitors from old paths on
your site to new ones. Applying it when you publish needs Pro, and it travels with the project
when you export it on any plan, so hosts that read the same file honor it. See
Redirects for the format.
What each plan includes
- Free: up to 3 published sites, each showing only its latest deploy.
- Pro: unlimited sites, custom domains, redirects, and the last 10 deploys of each site kept so you can roll any of them back live in one click.
If your plan lapses, sites you already published stay online, publishing goes back to the 3 sites of the Free plan, and the people you invited lose access to your projects, exporting them included, until you take up Pro again. Connected domains keep serving for 30 days, which Custom Domains covers in full.
The deploy history goes within a day, leaving only the version that is live, so go Pro again
straight away to keep it. If you had rolled back, the newer deploys you rolled away from go too.
Your _redirects rules last until your next publish.
A mount script that uses import stops a publish, because publishing does not bundle
imports. Exporting the project and deploying the built output stays open, with the guides below.
Export and deploy anywhere
- Click the Publish icon in the header.
- Click Download project to export a ZIP file.
- Upload or import that project in the hosting provider.
Provider setup is short in most cases. Use the pages below for practical steps by platform.
These guides are simple examples with popular providers. The project exported from Lediv is a standard static website, so it can also be published on many other hosting platforms.
For local execution, custom scripts, or deeper control over build/deploy steps, continue to Local Development.