--- title: Editor slug: test-archbee/editor docTags: createdAt: 2024-10-04T09:01:13.000Z --- :::ExpandableHeading ## Download native app *** **How to download the native app of Archbee? ** Press on help help icon form bottom right corner to open the help menu, then click on the "Download the native app". The system will detect your device OS and will start downloading the app. *** ::: :::ExpandableHeading ## Spaces *** **How to delete a space?** To delete a space, open the space settings modal (by clicking on the gear icon), and in the "General" modal, click on the "Delete Space" button. A new modal will appear that warn you this will permanently delete the current space. Once you delete a space, there is no going back, even if you contact [support@archbee.com](mailto\:support@archbee.com). Please be certain. To confirm, you have to write the name of the space in the input field and then, press on "Delete space" button. The intput field is case sensitive. You have to write the exact name of your space (including upper case, lower case and symbols). The final "Delete Space" button is disabled until you write the exact space name. All this is to ensure that there is no human error and this action is 100% intended. *** ::: ::::::ExpandableHeading ## Version Links :::::WorkflowBlock ::::WorkflowBlockItem :::ExpandableHeading ### SwimLane Explanation **Archbee Space Versions: Best Practices & Workflow** This guide outlines the recommended workflow for managing sequential software releases (e.g., v25.4.x, v25.5.0) using Archbee Space Versions. It is designed to ensure stability across your production documentation while allowing for parallel development of future releases. **1. Core Concept: The "Main Space"** In a versioned documentation architecture, one specific space serves as the **Parent** or **Main Space**. This is typically your currently active production documentation (e.g., *Piedpiper 25.4.x*) and serves as the primary "source of truth" for your project structure. - **Main Space (The Hub):** This is the control center for your documentation set. It is the designated location where you must manage settings, configure access, and generates new version branches. Think of it as the "trunk" of the tree from which all other branches grow. - **Versions (The Branches):** These are independent snapshots branched directly from the Main Space. Once created, they function as distinct entities. They are typically used to archive past releases (e.g., v24.0) or to draft future documentation (e.g., v26.0) in isolation without risking changes to the live production site. **2. The Golden Rule of Versioning** **⚠️ CRITICAL:** Always create and manage versions specifically from the Main Space. To maintain a healthy version tree, you must strictly adhere to the parent-child relationship. When you need to create a new version (e.g., strictly creating the 25.6.0 draft while 25.4.x is live), you must return to the source: 1. Open the **Main Space** (*Piedpiper 25.4.x*). 2. Navigate to **Space Settings > Version Links**. 3. Create the new version entry here. **⛔ What NOT to do:** Never open a child version (e.g., the *Piedpiper 25.5.0* draft) to create a subsequent version. - **Why?** Space versions are designed to be siblings of each other, all children of the Main Space. - **The Risk:** Attempting to branch a "grandchild" version (creating a version *from* another version) disrupts the hierarchy. This often leads to broken navigation menus, orphaned spaces that do not appear in the dropdown, and fragmented search indexes. - **The Exception (Patch Versions):** You may branch from a child version *only* if you are creating a direct **patch** update (e.g., branching from *25.5.0* to create *25.5.1*). **Never** use a child version to create the next major or minor release (e.g., do not use *25.5.0* to create *25.6.0*). **3. Recommended Workflow for "Piedpiper"** **The Scenario** - **Live Production:** Piedpiper 25.4.x (Visible to customers) - **In Development:** Piedpiper 25.5.0 and 25.6.0 (Internal drafts) **Step-by-Step Guide** 1. **Set the Foundation:** Verify that *Piedpiper 25.4.x* is your designated Main Space. This ensures all future versions share a common origin point. 2. **Create Draft Versions:** - From within *Piedpiper 25.4.x*, go to the **Version Links** settings. - Create the version *Piedpiper 25.5.0*. - Create the version *Piedpiper 25.6.0*. - *Note: This copies the current state of 25.4.x into these new spaces as a starting point.* 3. **Control Visibility:** - **Piedpiper 25.4.x:** Keep this **Published** (Public). This ensures your customers always land on the stable documentation. - **Piedpiper 25.5.0 & 25.6.0:** Keep these private by not publishing them. This allows your internal technical writers and reviewers to access, edit, and audit the content, but effectively hides them from the public version dropdown and search results until you are ready for launch. 4. **Release Day:** - When *Piedpiper 25.5.0* is finalized and the software is released, you can publish it. - (Optional) Adjust the display order in **Space Settings > Version Links** of the Main Space. You might want the new version to appear at the top of the list, or set as the default view for new visitors. **4. Content Propagation & Maintenance** Once created, Space Versions act as completely separate copies (forks) of the content. They do not share a database for document content. - **No Automatic Sync:** If you fix a typo, update a code snippet, or rewrite a paragraph in the Main Space (*25.4.x*), that change does **not** automatically propagate to *25.5.0* or *25.6.0*. - **Manual Updates:** You must apply content fixes manually to every active version that requires the change. - **Why is this beneficial?** While this requires manual effort, it ensures stability. It prevents a change intended for the latest API (v26.0) from accidentally breaking the documentation for a legacy API (v24.0) that relies on older behavior. - **Exception (AI Translations):** AI Translations are designed to propagate changes across *languages* within a single version (e.g., English to Spanish within v25.4.x), but this mechanism does not cross the boundary between version branches. **5. Navigation and Links** **Linking is "Version-Aware"** Archbee's linking system is intelligent enough to respect the version context the user is currently viewing. - **Relative Navigation:** If a user is reading *Doc A* in **v25.5.0** and clicks a link to *Doc B*, they will automatically be taken to the **v25.5.0** copy of *Doc B*. They will not be bounced back to the Main Space. - **Context Switching:** Switching versions using the dropdown simply switches the context. If the user is on "Getting Started" in v25.4, and switches to v25.5, the system attempts to keep them on the "Getting Started" page of the new version. **Search** **Behavior** - **Scope:** The global search bar indexes content from all currently **Published** versions. - **User Control:** To prevent result clutter, readers can filter search results to see matches only from the version they are currently reading. This helps users avoid finding v25.6.0 features when they are trying to troubleshoot a v25.4.x installation. ::: :::: ::::: :::::: :::ExpandableHeading ## Tips & Tricks **How to create social media links?** Right now, Archbee doesn't have any feature related with social media links and a place dedicated for social media links. But there is a workaround to create them: 1. First, hit the plus icon to create a new file in the desired space; 2. Convert the document into a link (find [here](<./././DOCUMENTS/Convert to link.md>) more details) 3. Click on the new link item to open the link menu 4. Write your label (e.g. LinkedIn, ProductHunt, etc.) 5. Paste your social media URL in the second field 6. Hit Done to finish it. Optionally, you can check the option "open in new tab". Repeat the process as many times you need. Don't forget to publish the space after you finish to add your social links. This method allows you to create custom links to any external social platform you choose directly in your document tree level. You can also create them in the [Space Links](<./././HOSTED SPACES/Space Links.md>) tab from space settings to display them in the upper right corner of your documentation plaftform. :::