⚙Understanding Aurora Hive Live technically

The editor recognises the place in the text that has been released for editing, makes it clickable and sends the change to the server. There it is saved and the page concerned is delivered afresh.

What that means:

• It is not a second version. There is exactly one text, and that is what gets changed.
• It takes effect immediately. No draft, no publishing.
• It only affects the section changed, not the whole page.

What does not happen: the visitor does not notice anything. The editor only appears when someone is signed in; for everyone else it is an ordinary website.

And what this means for loading time: nothing. The editor is only loaded for people who are signed in.

In the same content store from which the page is built — not in a separate repository.

That is the important point for everyone who runs Aurora Hive Sites and Live together: whatever someone changes with Aurora Hive Live is then also changed in Aurora Hive Sites. There is no synchronisation that could go wrong, because there is only one source.

What follows from this:

• Anyone working in Aurora Hive Sites sees the changes made via Aurora Hive Live. Even in the middle of a rebuild.
• The change history records both — who changed what and when.
• A conflict arises if both edit the same section at the same time. Coordinate with each other.

And the same applies to one-pagers created outside Aurora Hive Sites: the text is in one place.

For pages from Aurora Hive Sites and for one-pagers it is a setting — you switch it on, and that is all.

For a page you have built yourself, two things are needed:

1. Include the editor, usually with one line in the page head.
2. Mark the editable places, so that the editor knows what it may touch.

The second point is the real work — and the decision you make with care: whatever is released can be changed; whatever is not, cannot.

What you should always do afterwards: sign in yourself and make a change. An account that does not work at the first attempt will not be tried a second time.

Because the release is attached to the section. If a section is replaced, the old release is gone.

This happens with:

• New sections in place of old ones.
• A changed theme, if blocks are swapped in the process.
• Rebuilt pages.

What to do after every larger rebuild:

1. Check for yourself with the Aurora Hive Live account what is clickable.
2. Set any missing releases.
3. Let the customer know if something has moved.

The case that otherwise occurs: after three months the customer wants to change an opening time, cannot find the pencil in the usual place, and calls. That defeats the purpose.

Two causes are likely, and both are quickly checked:

1. The browser is showing an old version. Hard reload — Ctrl + Shift + R. That explains most cases.
2. The inclusion is missing. On a page you built yourself, a rebuild may have removed the line that loads the editor.

What you check:

• Sign in in a private window. If it works there, it was the cache.
• Try on another page of the same site. If it works there, only one page is affected.

For pages from Aurora Hive Sites, the inclusion is part of the delivery — it cannot get lost there. If the pencil is still missing, it is the account or the cache.

The editor is loaded only for signed-in users. A visitor does not get it, and there is nothing they could click.

What makes up the limitation:

• Only released places can be changed. Even a hijacked account can only change texts.
• No access to structure, design, settings or other websites.
• The change history records who changed what.

The realistic damage from a misused account: an unpleasant text that you reverse in five minutes. Annoying, but no data leak and no takeover of the website.

What you should still do: one account per person, switch it off when someone leaves, do not reuse passwords.

No — an account belongs to one website. Anyone who looks after two needs two.

Why: the separation prevents someone from accidentally changing something on the wrong site, and it ensures that a switched-off account really only affects that one site.

For agencies that look after many customer sites, this means: keep a list of which account belongs to which site. That belongs in the password manager, not in a spreadsheet on the shared drive.

And when a working relationship ends: switch off all accounts for that customer, not just the one you remember.

Because they do not consist of a text that can be replaced:

• Navigation. It arises from the pages and their settings, not from a text field.
• Legal notice and privacy notice. They are generated from stored master data.
• Automatically filled areas — event lists, post overviews, project grids. Their content comes from the respective records.
• Design. Colours, fonts and spacing are not content.

What this means when explaining it to customers: it is not paternalism but a limit inherent in the thing. A menu item cannot be changed as text because it is not text.

Where one of these places has to be changed, the way leads through the administration — and rightly so, because such changes affect the whole site.

The new image is added to the website’s media library and the reference on the section is changed. The old image remains — it is just no longer displayed.

What follows from this:

• Swapping back is possible, as long as the old image is still there.
• The media library grows. For someone who swaps images often, a look once a year is worthwhile.
• Resizing happens automatically. A large phone photo is adapted for delivery.

What does not happen automatically: cropping. A portrait image stays portrait and is cropped by the block. If the crop matters, it has to be cropped beforehand.

And the alt text: if it is not changed along with the swap, it describes the old image. Point this out.

Each language version is content in its own right — changing the German version does not change the English one.

This is the most common confusion with multilingual sites: someone corrects a typo and is surprised that it is still there in the other language.

What you should do:

• Mention it when introducing people that there are several versions.
• Show the language switcher — you change the version you are currently in.
• For important changes, check both versions.

And for translations: anyone who does not master the second language should not change it. A typo in a language you do not speak easily turns into an error of meaning.

Usually one of four things:

1. The session has expired. Sign in again and try again. That is the most common case.
2. The connection has dropped. On a phone when out and about, or on weak Wi-Fi.
3. A character the text cannot cope with — usually pasted from Word.
4. The section has been changed in the meantime, by someone else or in the administration.

What you should do before trying again: copy the text. A second failed attempt can cost you the input.

And if it happens reproducibly in the same place: report it — stating which page, which section and what you pasted in.

Just as with a multi-page website — except that there is only one page.

What makes the difference in practice:

• Everything is close together. An unfortunate text is noticed immediately.
• The boundaries matter more. Go through more carefully what is released.
• There is no subpage to which changes could be moved.

The typical use: a one-pager built for an individual person — interim managers, consultants, the self-employed. There, the text is the product, and the person wants to be able to maintain it themselves.

What you should mention at handover: that a change is public immediately, and that the one-pager is often the only source from which a customer forms an impression.