Projects & Asset Library

While not “modules” in the sense of performing AI tasks, Projects and Library are essential sections of Lunix Studio for managing your work and outputs. We touched on Projects in Getting Started; here we’ll explain them along with the Asset Library in more detail.

• Projects (Recap): The Projects section (accessible via the left sidebar) is where all your analysis projects are listed. Each project can be thought of as a container for a website you are working on or researching. Within a project, you might run multiple analyses (maybe on different pages of a site), generate several components, build pages, etc. Projects help keep these related items together.

  • In the Projects view, you’ll see a list of project names. You can probably rename or delete projects from here (for example, via a context menu or an edit button on each project entry).

  • Clicking a project typically opens the project’s dashboard or main page, which might show an overview (like last analysis date, number of components or assets generated, etc.). It might also filter your library to only show assets associated with that project.

  • Projects are useful if you juggle multiple clients or websites; they ensure you don’t mix up assets or analysis results between them. For instance, a project “My Personal Blog” and another “Client A Website” would keep their data separate.

  • If you started Lunix Studio by jumping straight into an Analyzer or Code Generator without explicitly creating a project, the platform might have created a default project for you (sometimes called “Untitled” or “Default Project”). It’s a good idea to rename it to something meaningful or explicitly create one to organize things.

• Asset Library: The Library is where all generated and uploaded assets are stored and organized. Think of it as your resource manager – it keeps track of code components, images, and possibly other files you have created or imported.

  • When you click Library in the sidebar, the main pane will show a search bar and filters (so you can quickly find assets by name or tag). There are usually tabs or categories within the library. From the screenshot, we see at least two:

    • Components: This tab lists Generated Components (code snippets/components created via the Code Generator). Each entry might have a name (auto-generated or one you gave it), maybe a brief description, and options to preview, edit, or export the code. Initially, if you haven’t generated any code yet, it will say you have 0 components.

    • Assets: This tab likely contains Images and other media assets. These would include images you generated in Image Lab, images you uploaded for editing or use in the builder, and possibly any other media (videos, icons, etc. if supported). Each asset might be represented by a thumbnail. You can probably click an image asset to view it or download it. You might also be able to tag assets or put them in folders for organization (depending on the interface features).

  • Using the Library: From the library, you can quickly grab assets to use in your project. For example, when in the Website Builder and you need to add an image, the image selection might open your Library for you to pick from existing assets. Similarly, if you want to insert a custom code component, you might choose from your library of components.

  • Exporting Assets: There is an “Export to ZIP” option in the library. This likely allows you to download all or selected assets in a zip file – useful for backing up your work or transferring it. For instance, after generating a bunch of components and images, you might export them and then integrate them into a separate project or share with a teammate.

  • Importing into Library: While not explicitly shown, many asset libraries allow uploading your own assets. For example, you might upload a company logo image so you can use it in the builder, or import a piece of code. If you have an “Upload” or “Import” button in the Library, you can add external files here for use in Lunix Studio.

  • Managing Assets: Over time, your library could grow large. Use the search and tagging features to find things. You can create consistent naming conventions for your components (e.g., “hero-section-dark” vs “hero-section-light” if you generate variations) to keep them identifiable. If the library supports folders or tagging, group related assets (maybe by project or type).

  • Library and Projects: It’s possible that the library shows all assets by default, but when you are viewing a specific project it might filter to that project’s assets. Be mindful of whether an asset is global or project-specific. The wording “all your generated components and images” suggests it’s a global repository, which is convenient for reusing assets across projects. For example, an icon set you generated could be used in multiple projects via the library.

In summary, Projects help structure your overall work by project/case, and the Asset Library is your go-to place for any piece of code or image you’ve created or need to reuse. Proper use of these will keep your workflow organized, especially as you conduct multiple analyses or build multiple sites with Lunix Studio.