Projects and Files

A Lediv project is the whole website in one place, with its pages, components, styles, scripts and files. You build it visually and can export it as standard web source code that keeps evolving with regular tools.

Start a project

A new project needs a Name and a Template. The name shows in the dashboard and in the workspace header, and you can change it later in Project settings. The template sets how much you start with.

• Blank starts from scratch, for full control from zero.
• Demo starts from a page built with reusable components that you replace or adapt.

Every project is stored in your account and syncs across your signed-in devices, on every plan. You can keep editing offline, and changes reconcile when the connection returns. A new project opens straight in the editor.

In the dashboard, the menu on each project card opens the project, visits its published site, opens its settings, exports it, or moves it to the trash. On a project shared with you as a guest, Leave project takes the place of settings and the trash. In the editor, Undo and Redo in the header recover from accidental changes.

Project structure

A typical project looks like this.

├── pages/
├── components/
├── public/
│   ├── images/
│   └── videos/
├── package.json
└── vite.config.js

• pages/ contains route files.
• components/ contains reusable blocks.
• public/ contains static files served by URL.
• package.json lists the project's external dependencies.
• vite.config.js sets up Vite for local development and builds.

A Blank project starts with pages/index.html, package.json and vite.config.js. Folders like components/ and public/ appear once you add files to them.

Organize project files

The Files panel edits and organizes everything in the project.

• Create files and folders from the panel actions or the context menu.
• Rename, copy, cut, paste and delete items in the tree.
• Drag and drop to reorder items or move them between folders.
• Open text files in the code view, and images or videos in a preview.

Upload media and use public paths

Upload from the panel actions, or drag files and folders from your computer into the tree. Image and video fields can also upload directly from their media picker.

Keep files the browser loads inside public/ and reference them with root paths in markup and styles.

<!-- HTML example: image from /public/images -->
<img src="/images/hero.jpg" alt="Hero" />

<!-- CSS example: same asset referenced with a root path -->
<style>
  .hero {
    background-image: url('/images/hero.jpg');
  }
</style>

Files outside public/ are still part of the project and editable, but the browser cannot load them by URL.

Download project source

Download project in the Files panel exports the project as a ZIP. The same button in the Publish panel (owner only) and Export in the project card menu do the same. Your browser builds the ZIP from its local copy of the project, so open the project and let it finish syncing first. Anything the browser has not loaded yet cannot go into the archive.

You can edit and export a project shared with you, but only its owner can publish it. A shared project follows its owner's plan, so if that plan ends you can no longer open or export it.

Next steps