TYPO3
Make a TYPO3 website static, without touching TYPO3.
Your editors keep working in the TYPO3 backend. The public gets a copy of the finished pages as files — no extension to install, nothing to configure on the server, and no access to either.
A copy that works, not just its HTML
Writing a site out as static HTML keeps what is in each page and the files it names. What a page asks for once it is open — the data a script fetches, a file another file loads, a redirect from an old address — is not among them, and that is where exported sites quietly stop working.
We keep every answer your site gave while its pages were opened, and give the same answer again: the same content, the same kind of file, the same redirect. That is why the copy behaves like your site instead of only looking like it — and why you can check it yourself, side by side, before you decide anything.
An installation that is years into its life
Many TYPO3 sites run for a decade: set up by an agency, extended over the years, and by now on a version whose regular support has ended. Moving to a current version is a project of its own, because extensions have to be replaced and templates adjusted.
A static copy does not do that project for you, but it takes the pressure off it. While the public reads files, the version behind them is no longer what a visitor reaches.
Nothing is installed
Static output in TYPO3 usually means an extension that writes pages out on the server TYPO3 runs on — installed, configured, and kept compatible with every TYPO3 version after it.
We read the pages from outside, the way a visitor does. The TYPO3 version does not matter, and nothing in the installation changes.
Forms, search and logins
After the first copy of the whole site you get a list of everything that needs something running behind it, with the page it is on.
- A contact form — from the form framework or an extension such as powermail — is received by us when a visitor sends it, mailed to you and listed on your site's page. It looks exactly as it does now.
- The search box answers from the text of the copy's pages. It is a search over the words on them, not TYPO3's own search, and the list says so.
- A login for visitors cannot be a file. It is listed for you, not taken over.
When an editor publishes
The copy catches up when you publish it. Each publish is listed with the pages that were added, changed or removed — so whoever looks after the site can see what changed, and when.
Questions people ask
- Does anything change in our TYPO3 installation?
- No. Nothing is installed and nobody needs access to the backend or the server.
- Does it work with an older TYPO3 version?
- Yes. We read the pages it publishes, so the version behind them is not something the copy depends on.
- Does our agency have to be involved?
- Not to try it: the trial copy needs only the address. Pointing your domain at the copy is a change at your DNS provider, which whoever manages your domain can make.
See it on your own site
About twenty seconds, and nothing to sign up for. You will have your site and the copy open next to each other before you decide anything.