# Getting started Find your way around the workspace and take your first piece of content from draft to published page. GroCMS 0.1.0 · Start here · Everyone using the CMS · Reviewed 15 September 2026 ## Your website and your workspace GroCMS has two sides. Visitors see the published website at the site’s root address. Your team signs in at /login and works under /admin. View site in the workspace header and Your website in the sidebar open the public website. A saved draft in the workspace does not automatically change what visitors see. The Overview is a starting point for finding content and checking activity. Pages hold lasting information such as About and Contact. Posts hold articles and announcements. Media library holds uploaded assets. The Your site group controls reusable design. The Workspace group covers publishing, people, configuration and these guides. > **Use the correct installation** > > Sign in at the address provided for your own installation. Each installation has its own accounts and content. A localhost address works only on the machine running the application. The product website is grocms.com; it is separate from your installed website. Sources: Workspace navigation and screen routing (repository: `apps/cms/src/components/admin/shell.tsx`); Content editor controls (repository: `apps/cms/src/components/admin/resource-editor.tsx`); Initial workspace setup (repository: `apps/cms/scripts/setup.ts`). ## Start your first session 1. Open the address provided by your administrator and sign in with your own email and password. An invitation lets a new team member create their account; there is no open public registration. 2. Check your name and role at the bottom of the sidebar. Your role determines which records and actions are available. Open your name to manage your password, sessions and authenticator. 3. Visit Overview, then open Pages or Posts. Search for the item you need before creating another. Some workspaces contain demonstration content; a clean installation starts with draft configuration and no sample articles. 4. Open an entry and inspect its current status and title. Use the Content or Details tab for fields, and the Visual editor tab when the entry has a custom composition or is a design resource. Sources: Workspace navigation and screen routing (repository: `apps/cms/src/components/admin/shell.tsx`); Account invitation workflow (repository: `apps/cms/src/cms/auth/people.ts`); Content editor controls (repository: `apps/cms/src/components/admin/resource-editor.tsx`); Initial workspace setup (repository: `apps/cms/scripts/setup.ts`). ## Create and publish your first entry 1. Choose Pages or Posts and use the creation action. Give the item a clear title and a suitable slug, then add the body and any required fields. 2. Add media with useful alternative text, select relevant categories for posts, and check SEO & visibility. Public and Private are deliberate choices; publication and visibility are separate. 3. Save your changes and wait for saving to finish. Layout changes also participate in the editor’s save flow. Do not assume an unsaved field is included in a preview or publication. 4. Use Preview to inspect the saved draft. Check text, links and narrow-screen layout. Preview is private access to draft content, so treat its link as sensitive. 5. If you have publishing permission, publish the saved revision. A contributor submits their work for review instead. Approval by a reviewer and publication are separate actions. 6. Open View site and check the public URL. For an existing published entry, further saved changes remain drafts until you publish again. For example, changing a published About page’s telephone number saves a new working revision while visitors continue to see the previous number. Publishing that revision switches the public page. Revision history lets you inspect and restore older work; restoring it creates working content to review before publication. Sources: Content editor controls (repository: `apps/cms/src/components/admin/resource-editor.tsx`); Revision and publication service (repository: `apps/cms/src/cms/services/content.ts`). ## Choose the guide for your task Each guide stands on its own and names the screen, intended audience, procedure and limits. Search documentation by a feature or problem, such as homepage, password, schedule or backup. Group filters narrow the results. Each article has an On this page index, related guides and references to the implementation or official product documentation. Start with How the CMS works to understand drafts and publication. Read Pages and Posts for editing, then Homepage and Visual editor for design. Administrators should read People, Settings and Account & security. Installation and maintenance instructions are in Setup & operations and involve terminal access rather than ordinary editing controls. Print this guide prints the current article. The handbook combines all guides for printing or saving as PDF through your browser. Download Markdown provides a portable text copy. These guides describe the delivered application; they are maintained with the application’s source code and are not editable through the Pages screen. Some installations also enable a public handbook at /docs. It contains an explicitly reviewed set of product guides and has its own search and downloads. Public documentation does not sign you into the CMS or grant access to the workspace. Ordinary installations keep this public feature disabled, so a Page using /docs remains ordinary website content. Sources: Documentation routes and rendering (repository: `apps/cms/src/components/documentation/article.tsx`); Reviewed public guide selection and links (repository: `apps/cms/src/cms/documentation/public.ts`). ## References - Workspace navigation and screen routing — repository path: `apps/cms/src/components/admin/shell.tsx` - Content editor controls — repository path: `apps/cms/src/components/admin/resource-editor.tsx` - Revision and publication service — repository path: `apps/cms/src/cms/services/content.ts` - Account invitation workflow — repository path: `apps/cms/src/cms/auth/people.ts` - Initial workspace setup — repository path: `apps/cms/scripts/setup.ts` - Documentation routes and rendering — repository path: `apps/cms/src/components/documentation/article.tsx` - Reviewed public guide selection and links — repository path: `apps/cms/src/cms/documentation/public.ts` ## Related guides - [How the CMS works](https://grocms.com/docs/how-cms-works) - [Pages](https://grocms.com/docs/pages) - [Posts](https://grocms.com/docs/posts) - [Homepage](https://grocms.com/docs/homepage) - [Account & security](https://grocms.com/docs/account-and-security)