ForgeCrowdBookWe don't sell the fish – we give you the rod.

Six Months Later

Half a year has passed. The site has been running quietly, you have changed a text or two on Codeberg, and now you need something bigger: a new page, a new price list, a holiday notice. You have forgotten how any of it works. That is normal, and this chapter is for that day.

Goal

By the end of this chapter you will know:

  • what you still have and where it is,
  • how to get the AI back up to speed on your site,
  • what to do when the site is down.

What you still have

Nothing went away while you were not looking:

What Where
Your texts and pages Codeberg, your content repository
Settings, theme, modules your server, in the site folder (often /opt/... or /var/www/...)
ForgeCMS itself your server, running as a service
The AI your server: claude

Your server has kept itself running. There is no admin area that needed updates in the meantime and no plugins that might have broken.

Keep one note somewhere safe, from the first day on: the server's IP address, the root password (in a password manager), the Codeberg address of your content repository, and the folder of your site on the server. Claude told you that folder at the end of chapter 4.

Small changes: Codeberg

For texts, prices, opening hours, a new picture: go to Codeberg, open the file, pencil, change, commit (chapter 5). No server, no AI. If you do not remember which file holds a text, use the search box of the repository, or open the page on your site and look for a word from it.

Bigger changes: the AI

Log in and start Claude Code:

ssh root@203.0.113.10
claude

Claude Code does not remember your last conversation. Give it a moment to read your site first. This request works every time:

This is my ForgeCMS website on this server. I have not touched it for months
and I do not remember how it works. Please:

1. Find the site folder and read AI.md of ForgeCMS.
2. Explain in plain words which files hold the menu, the home page and the texts.
3. Then make this change: ...
4. Tell me in simple words what you changed, and push content changes to Codeberg.

Replace the dots with what you want. Claude reads the files, explains them in two minutes, and you are back where you left off.

Typical changes, and where they live

You want … Usually in
a new text, new wording a .md file on Codeberg
a new page in the menu a new .sml file and a line in site.sml on Codeberg
a holiday notice on the home page index.sml on Codeberg (or ask the AI)
new colours or a logo theme.sml on the server
a contact form, a blog, a shop app.sml on the server: a module (Part III)
a new language app.sml and a language folder (chapter 6)

When in doubt, describe the result to the AI. It knows this table too.

Keeping ForgeCMS up to date

ForgeCMS gets new features and fixes. Once in a while, maybe every few months, ask:

Please update ForgeCMS to the latest version from Codeberg, rebuild it,
restart the service, and check that my site still works.

The same goes for the server's own updates, which matter more for security:

Please install the operating system updates and restart if needed.

When the site is down

It rarely happens, but it does: the server was restarted by the provider, a certificate could not be renewed, a disk ran full. Do not guess. Log in, start Claude Code, and say:

My website does not load. Please check ForgeCMS, Caddy and the server,
find out what is wrong, fix it, and tell me what it was.

If you cannot log in at all, look at your provider's panel: is the server running? Most panels have a button to restart it, and a "console" that works even when SSH does not.

Pitfalls

  • Lost the root password: most providers let you set a new one in the panel. Do it, then store it properly.
  • Changes on the server and on Codeberg at the same time: if you edit a file on Codeberg while the AI changes the same file on the server, git notices and the AI will ask you which version to keep. Let it merge; nothing is lost.
  • "It worked yesterday": look at the history on Codeberg (chapter 5). The last change is usually the cause, and one request undoes it.

What you learned

  • Texts are on Codeberg, settings on the server, and both keep their history.
  • Small changes: Codeberg in the browser. Bigger ones: claude on the server, with a request that first lets it read your site.
  • Update ForgeCMS and the server every few months by asking.
  • When the site is down, let the AI look; when you cannot log in, use the provider's panel.

This is the end of Part II. You have a website of your own, you know where everything is, and you can change it. Part III adds the things that usually come as plugins: a blog, a contact form, a newsletter, events, a shop, payments and courses.