> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rtfm.guide/llms.txt
> Use this file to discover all available pages before exploring further.

# Editing Guides

> Learn how to update and manage your published guides

## Accessing Your Guides

### View All Your Guides

1. Go to [My Guides](/my-guides)
2. See all guides you've created
3. Filter by status:
   * **Published**: Live and visible
   * **Draft**: Saved but not published
   * **Archived**: Hidden from public view (coming soon)

### Find a Specific Guide

* Use your dashboard
* Check your profile page
* Search for it in the main search

## Edit a Published Guide

<Steps>
  <Step title="Navigate to My Guides">
    Go to [My Guides](/my-guides) from your dashboard
  </Step>

  <Step title="Find Your Guide">
    Locate the guide you want to edit
  </Step>

  <Step title="Click Edit">
    Click the **Edit** button on the guide card
  </Step>

  <Step title="Make Changes">
    Update the content using the Markdown editor
  </Step>

  <Step title="Preview">
    Review your changes in the live preview
  </Step>

  <Step title="Save">
    Click **Update** to publish changes immediately
  </Step>
</Steps>

## What You Can Edit

### Content

* Title
* Body content (Markdown)
* Code examples
* Images and links

### Settings

* Visibility (Public, Unlisted, Private)
* Status (Published, Draft)
* Categories (coming soon)
* Tags (coming soon)

### What You Cannot Edit

* URL slug (set from original title)
* Creation date
* Author
* View count and reactions

## Managing Drafts

### Save as Draft

When editing a published guide:

1. Make your changes
2. Change status to **Draft**
3. Click **Update**
4. The guide becomes unpublished

<Info>
  **Draft mode** is useful when making major revisions. The guide won't appear in searches until you republish it.
</Info>

### Work on Drafts

* Access drafts from [My Guides](/my-guides)
* Edit anytime without affecting public content
* Preview before publishing
* Delete drafts you no longer need

## Version History (Coming Soon)

Future features include:

* View edit history
* Compare versions
* Revert to previous versions
* Track who made changes

## Best Practices

<AccordionGroup>
  <Accordion title="When to Edit">
    Edit guides when:

    * Fixing typos or errors
    * Updating for new library versions
    * Adding clarifications from comments
    * Improving code examples
  </Accordion>

  <Accordion title="Major Changes">
    For significant rewrites:

    * Consider creating a new guide
    * Or save as draft while revising
    * Add a note about what changed
    * Notify users who commented
  </Accordion>

  <Accordion title="Communicate Changes">
    * Add "Updated: \[date]" at the top
    * Mention version changes
    * Explain deprecations
    * Thank users who reported issues
  </Accordion>
</AccordionGroup>

## Deleting Guides

### Soft Delete (Recommended)

1. Edit your guide
2. Change visibility to **Unlisted**
3. Or save as **Draft**

This hides the guide from public view but preserves it.

### Permanent Delete

To permanently delete:

1. Go to [My Guides](/my-guides)
2. Find the guide
3. Click **Delete**
4. Confirm the deletion

### What Gets Deleted

* The guide content
* All reactions
* All comments
* View statistics
* Saved bookmarks (from users' saved lists)

## Handling Feedback

### Responding to Comments

* Address questions in the comments
* Fix issues users report
* Thank users for corrections
* Update the guide based on feedback

### Dealing with Outdated Info

When your guide becomes outdated:

1. **Option 1**: Update it
   * Add version info
   * Update code examples
   * Test everything again

2. **Option 2**: Archive it
   * Add "Outdated" note at top
   * Link to newer resources
   * Consider unpublishing

3. **Option 3**: Create new guide
   * Write a fresh version
   * Link from old to new
   * Keep old one for reference

## Analytics (Coming Soon)

Track your guide's performance:

* View count over time
* Reaction breakdown
* Save count
* Comment activity
* Traffic sources

## Need Help?

* Check [Creating Guides](/guides/creating-guides) for content tips
* Review [Community Guidelines](/community/community-guidelines)
* Report issues with the editor as bugs
