> ## Documentation Index > Fetch the complete documentation index at: https://docs.ghostable.dev/llms.txt > Use this file to discover all available pages before exploring further. # Projects > Projects connect environments, stack metadata, and local manifests for a single app. Review how Ghostable fits Desktop, CLI, and automation together. ## What a Project Represents A project is the Ghostable record for one application or service inside an organization. It groups: * The environments that belong to that app. * Stack metadata such as language, framework, and deployment provider. * Activity and validation context tied to that app. * Optional local folder linkage through the Ghostable manifest. Projects are the boundary where most day-to-day work starts. {/* ghostable:screenshot-output fundamentals-projects-environments-list:start */} Ghostable project view showing environments within a single project in the web app. Ghostable project view showing environments within a single project in the web app. ## Stack Metadata and Local Context Ghostable stores lightweight, non-secret project metadata so clients can tailor workflows. Common examples include the primary language, framework, and deployment platform. The local manifest, `.ghostable/ghostable.yaml`, lets clients map a local folder back to the project. It contains safe metadata only and is intended to live in version control. ## Where You Manage Projects * **Desktop**: create projects from the launcher or organization window, then manage local folder linkage from Project Settings. * **CLI**: initialize or link a repo with `ghostable init` and keep the manifest in sync locally. * **Web app**: organization owners can review project-level settings outside the local clients. ## Continue with Your Client Create and manage projects from the launcher and organization views. Bootstrap or relink a repository with the terminal workflow.