> For the complete documentation index, see [llms.txt](https://docs-example.gitbook.io/forge-website/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-example.gitbook.io/forge-website/modify-the-website/things-you-need-to-remember-to-do.md).

# Things you need to remember to do

1\. How to Save You need to save your file manually for the changes to work.

* Windows: Press `Ctrl + S`
* Mac: Press `Cmd + S`

*(Pro Tip: VS Code also has an Auto Save feature. You can turn it on by going to `File > Auto Save` in the top menu.)*

2\. How to Fix Mistakes (The Timeline) If you break something or delete code by accident, don't panic! VS Code keeps a history of your local saves.

1. Right-click the file name in the file explorer (left sidebar).
2. Select "Open Timeline".
3. A list will appear at the bottom of the screen showing every time you saved. You can click these to find your old code and copy-paste it back.

***

3\. Write a "Commit Message" When you send your changes to GitHub (Commit), you will be asked to write a message.

* Do: Write exactly what you changed (e.g., *"Changed header color to blue"*).

4\. Wait for the Update After you commit, the live website doesn't change instantly.

* It usually takes 2–3 minutes for the system to process and update the live link.
* Grab a coffee and refresh the page in a few minutes!