Prosolve Software website (www.prosolve.co.uk)

Plain HTML, CSS and a little JavaScript, plus one small PHP file for the enquiry form. No build tools, frameworks, Node.js, database or .NET runtime are needed. It's built the same way as the RevUp Blaze website (..\RevUpWebsite), so the same habits apply.

RevUp Blaze has its own site. This site deliberately doesn't duplicate it; instead it signposts it:

• a strip at the top of every page ("Looking for RevUp Blaze? Visit www.revup.co.uk")
• a RevUp Blaze button in the main navigation on every page
• a large "Looking for RevUp Blaze?" panel directly under the home page hero
• redirects: prosolve.co.uk/revup, and the old /features and /coming-soon pages, go to revup.co.uk.

Folders

Folder	What it is	Uploaded?
Assets\	Your original images. Never modified.	No
site\	The website source. Edit files here.	Via deploy\
deploy\	Generated copy of site\, i.e. exactly what goes in Hostinger's public_html. Never edit it directly; it is replaced each build.	Yes
tools\	make-images.ps1 (web-sized images from Assets\) and build-deploy.ps1 (builds deploy\).	No
server-config\	prosolve-smtp.example.php, an optional template for a Prosolve mailbox password file (see "Enquiry form").	No

Pages

Page	Contents
index.html	Hero, RevUp signpost, what we do, systems we've built, clients, why Prosolve, our story
services.html	Bespoke development, consultancy, how we work, modernisation, OpenInsight and Revelation, support and hosting
work.html	The systems we've built, sectors and clients
about.html	History, the "one business since 1984" note, timeline, 1999 logo, football sponsorship, company details
contact.html	Enquiry form (new project / OpenInsight / support / other), email addresses, registered office
privacy.html, 404.html	Privacy notice; "page not found"

Preview locally

Double-click site\index.html. Everything works from the file system except sending the enquiry form, which needs PHP on the web host; the contact page says so when previewed locally.

Common edits

• Text: edit the relevant site\*.html file. The RevUp strip, header, navigation and footer are repeated in each page, so change all of them when editing those parts.
• Styles/colours: site\assets\css\site.css. Brand colours are at the top (:root). The green comes from the logo; RevUp's navy, plum and red are used only for the RevUp signposts.
• Images: put a new original in Assets\, add a line to tools\make-images.ps1, then run powershell -ExecutionPolicy Bypass -File tools\make-images.ps1. The script also draws the favicon (green tile with an italic "P") and the social-sharing image. Assets\revup-blaze-logo.png is the same file the RevUp Blaze website uses; if that logo changes, copy the new one into Assets\ too.
• Logo on dark backgrounds: there is no reversed version, because the "VE" of PROSOLVE is a white knockout on the swoosh and disappears on dark colours. The footer shows the normal logo on a white tile.
• Font: Manrope (SIL Open Font License), self-hosted in site\assets\fonts\. Nothing loads from Google.
• Phone number: 01234 838965 on all pages (search for 441234838965 to change it).

Enquiry form

site\contact-handler.php works exactly like the RevUp site's: it validates the form, checks for spam (hidden honeypot field, submission-time check, maximum of 3 links, and 5 enquiries per hour per visitor) and emails the enquiry by authenticated SMTP using PHPMailer 7.1.1 (site\includes\PHPMailer\, LGPL licence included). PHP mail() is deliberately not used.

Settings are in site\includes\config.php (a folder the web server refuses to serve). Enquiries go to info@prosolve.co.uk, with subjects starting [prosolve.co.uk], and pressing Reply replies to the enquirer.

Which mailbox sends them. The handler uses the first SMTP settings file it finds, and always sends from that file's mailbox, so the email passes SPF/DKIM/DMARC for that mailbox's domain:

1. domains/prosolve.co.uk/private/prosolve-smtp.php: an optional, dedicated Prosolve mailbox.
2. domains/revup.co.uk/private/revup-smtp.php: the file you already created for the RevUp site. If both websites are in the same Hostinger account, this is found automatically and enquiries arrive from noreply@revup.co.uk with the name "Prosolve Software website". No setup is needed.
3. public_html/includes/smtp-config.php: a fallback if PHP can't read outside public_html.

Recommended: leave it on option 2. prosolve.co.uk's email is Microsoft 365, with its MX records at Namesco, so don't create a Hostinger mailbox for prosolve.co.uk (Hostinger would expect to handle that domain's email). Sending through Microsoft 365 by SMTP is possible but not recommended: Microsoft is phasing out password-based SMTP sign-in. server-config\prosolve-smtp.example.php is kept only in case that ever changes.

If no file is found or SMTP fails, the visitor sees "your message could not be sent" with the email address, and the reason is written to the PHP error log. The log never contains the password.

Deploying to Hostinger

Email is unaffected. prosolve.co.uk's email is Microsoft 365 and its DNS (including MX records) is at Namesco, so moving the website doesn't touch it. At Namesco, only ever change the website records (@ and www); leave the MX, autodiscover, SPF (TXT) and other Microsoft 365 records alone.

1. Build: powershell -ExecutionPolicy Bypass -File tools\build-deploy.ps1 -Zip This creates deploy\ and deploy.zip.
2. Keep a record of the old site. Website Builder sites can't be exported, so take screenshots of any page you might want to refer back to. (Its text and contact details were already used to write this site.)
3. Replace the Website Builder site with a custom one. In hPanel, prosolve.co.uk is currently a Website Builder site. Hostinger normally lets a domain have only one website, so either:
   • ask Hostinger support (live chat) to switch prosolve.co.uk from Website Builder to a custom/empty website on your Business plan (the simplest route); or
   • delete the Website Builder site for prosolve.co.uk, then Add website → empty/custom website for prosolve.co.uk. Expect the site to be offline for a few minutes in between.
4. Upload: hPanel → File Manager → prosolve.co.uk's public_html → delete any leftover builder files → upload deploy.zip (it does not extract on upload) → right-click it → Extract → enter . in the folder box (meaning public_html itself) → tick Overwrite → Extract → delete deploy.zip from the server. Check that .htaccess is present (enable "show hidden files"). FTP alternative: upload the contents of deploy\ into public_html.
5. Domain records: if hPanel shows a different IP address for the new site than the DNS currently uses, update only @ (A record, plus AAAA if given) and www (CNAME to prosolve.co.uk) at Namesco. Leave all Microsoft 365 email records alone.
6. HTTPS: hPanel → Security → SSL → make sure the certificate covers both prosolve.co.uk and www.prosolve.co.uk. .htaccess then redirects everything to https://www.prosolve.co.uk. When both work, uncomment the Strict-Transport-Security line in site\.htaccess and redeploy.
7. Enquiry form: nothing to do if the RevUp site's revup-smtp.php is on the same account (see above). Send a test enquiry and check it arrives.

Launch checklist

• Every page loads at https://www.prosolve.co.uk/…. http://prosolve.co.uk and http://www.prosolve.co.uk redirect to it.
• Old addresses redirect: /other-services → Services, /company → About, /support → Contact, /privacy-policy → Privacy, /features and /coming-soon → revup.co.uk. /revup → revup.co.uk.
• Send a real enquiry of each type. Confirm they arrive at info@prosolve.co.uk, not in junk, and Reply goes to the enquirer. In one, view the message source: Authentication-Results should show spf=pass, dkim=pass and dmarc=pass.
• The success message appears. Then submit 6 times quickly and confirm the 6th is politely refused.
• https://www.prosolve.co.uk/includes/config.php returns 403 Forbidden.
• A made-up URL shows the "That's one problem we can't solve" 404 page.
• Check on a phone: menu, RevUp strip, contact form.
• Submit https://www.prosolve.co.uk/sitemap.xml in Google Search Console (optional).

Structured data (JSON-LD)

Each page except the privacy and 404 pages has a JSON-LD block at the end of <head> (Organization, WebSite and WebPage on the home page; AboutPage, ContactPage and WebPage elsewhere). Don't edit the blocks by hand: edit toolsadd-jsonld.js and run node toolsadd-jsonld.js site. The Organization @id (https://www.prosolve.co.uk/#organization) is shared with www.revup.co.uk, so keep the company details (address, company number, VAT number) the same on both sites. Check with https://validator.schema.org/.

Rollback

Before uploading a new version, download a zip of the current public_html from File Manager (or keep the previous deploy.zip). To roll back, delete the site files and extract the previous zip. Keep these zips outside public_html.

Content notes (please review before launch)

Content comes from the previous prosolve.co.uk site, your notes, and Companies House. Please check:

• Client names (home and work pages) are listed as "clients past and present", with a "no endorsement implied" note; none is singled out as current. The home page shows 15 boxes, five across. "BAE" may have been British Aerospace at the time.
• The Times: described only as "featured in an article in The Times". Add the year if you know it.
• System descriptions (courier booking, taxi, fire and rescue, healthcare monitoring, stock control, parts maintenance, payroll and personnel, high-value insurance tracking) are deliberately general, and the work page says so. Add detail (e.g. "for a London courier firm") wherever you're happy to.
• Councils: the around-70-councils work was installation and configuration of a third-party OpenInsight product in Citrix environments, and is described that way (home and work pages). It's not claimed as Prosolve software.
• Company history (about page): Companies House shows Prosolve Software Limited (04777164) incorporated 27 May 2003 (named Quinn Mills Associates Ltd until 6 Feb 2004), matching the 2003 date used.
• Services offered for OpenInsight and Revelation (maintenance, consultancy, Citrix delivery, integration with .NET, planning migration) are written as things you offer. Remove any you'd rather not take on.
• Hosting: "secure UK data centres in Birmingham and Maidenhead", from the old company page.
• "100% UK-based team and data centres" (home page stats) relies on all hosting being in the UK.
• "Classic car enthusiasts" (about page) matches the wording on the RevUp site.
• Email addresses shown: info@ (general), support@, accounts@. webmaster@ from the old site isn't shown.