Update your website
How the school asks JPRAXC for content changes after launch, and what to include so the change is made right the first time.
After launch, content changes are part of the ongoing care in JPRAXC's Website Designing & Hosting service, along with backups, security updates and technical support. The school sends the change; JPRAXC makes it on the live site and tells you when it is done. Schools on Web+ERP Cloud can also publish notices to the website themselves from the ERP (see Web+ERP Cloud).
Before you start#
- Agree inside the school who approves website changes. Usually it is the project owner named when the site was ordered.
- Have the final, approved wording and pictures ready. Half-finished text leads to a second round.
Steps#
- Write down the change:
- the page, by its address or its name in the menu
- what should change, and the exact new text
- any new pictures or documents, attached as files (photographs the school has the right to use)
- the date the change should appear, if it matters (for example, admission dates)
- the name of the person who approved it
- Send it to JPRAXC support. Write to support@jpraxc.com, or, if the school uses the School ERP, open Contact JPRAXC in the ERP and use the support e-mail, phone or WhatsApp shown there.
- Keep the ticket number or reply you receive, and use it for any follow-up about the same change.
- When JPRAXC confirms the change, open the page on a phone and on a computer and check it.
- If something is not right, reply on the same thread with what still needs fixing.
Good to know#
- Send one request per change, or one clear list, rather than many small messages. It is easier to track.
- Never send passwords or bank details in a change request. JPRAXC does not need them to update your content.
- Larger work, such as new sections, new forms or a full redesign, may fall outside the agreed scope. JPRAXC tells you before starting if it needs a separate quote from Sales.
- For a problem rather than a change (the site is down, a form does not arrive, a security warning), say so in the subject so it is handled as a support issue.
