MES · Sites .md · Standard Website Build Specification

1. Login + Google Sheets backend

Every new MES/Sites website is built with a login system connected to Google Sheets unless explicitly requested otherwise.

Before building the login/backend, ask for the Google Sheet link that must be used.

After the Sheet link is known, create the required Google Apps Script files, including:

• Code.gs

• any other required .gs files

• any required .html partials/components

• Index.html

The login/application must support:

• person registration

• person login

• per-user data

• customers / clients

• administrators

• full admin management

2. Google Site / canonical site link

Every website is linked to a Google Site or another canonical site URL.

Before building, ask:

Welke site/link wil je gebruiken voor exports, bovenaan en bij de credits?

Use this site URL:

• as the site mention at the top

• inside exports

• at the bottom in the credits

For Google Sites URLs, derive the short name from the final slug.

Examples:

• https://sites.google.com/view/gabeler → Gabeler

• https://sites.google.com/view/Budgetcoach → Budgetcoach

At the top of the site:

1. show the short site name

2. place the full Google Site link directly underneath it

3. Persons, clients and users

Every MES/Sites website includes tools for:

• registering persons

• person login

• customers / clients

• users

• admins

• configurable roles where useful

Every person gets an ongoing personal programme containing:

• profile

• current situation

• goals

• financial data where relevant

• debts / arrears where relevant

• tasks

• sessions

• sent-message history

• next-contact date

• own files and uploads

The standard ongoing workflow is:

situation / problem → advice → action → result → next step

This makes it possible to continue coaching, support or service on the next day without losing context.

4. Import / Export everywhere

Import and Export tools must work across the whole website.

They must appear:

• at the top of every page/view

• near the bottom of every page/view

• above the credits

Minimum supported formats:

• JSON

• TXT

Where useful, also support:

• CSV

• HTML

• DOC / DOCX

• PDF

• WhatsApp

• full-system backup JSON

Client/user exports should preserve enough data to continue on another day or another device.

Exports must include:

• canonical site name

• canonical site URL

• person/client identity where relevant

• programme/session data where relevant

• export date/time where useful

5. Files

Every person/client should be able to have their own files.

The system should allow uploads and downloads for relevant file types, including where useful:

• TXT

• JSON

• CSV

• PDF

• DOC / DOCX

• XLS / XLSX

• images

• other supporting files

Files should be linked to the correct person/client record.

6. Admin

Admin always has full management rights over:

• users

• clients

• registrations

• sessions

• messages

• tasks

• files

• imports

• exports

• settings

• programme data

Default admin:

• padelstijn@gmail.com

Also allow configurable additional admin Gmail accounts, including:

• stijn.gabeler@gmail.com

• other Gmail accounts from Stichting GODOGOOD

Admin email addresses must be configurable.

7. ACO · Always Credits On

ACO is the default for every new site unless explicitly requested otherwise.

Credits are always visible.

Standard credits:

Stichting GODOGOOD.eu

GODOGOOD.eu links to:

https://sites.google.com/view/godogood-eu/

Stijn Gabeler.eu

Use the text:

Stijn Gabeler.eu

Gabeler.eu

Gabeler.eu links to:

https://sites.google.com/view/gabeler

Also include the canonical project/site name and link in the credits.

Credits appear below the bottom Import / Export section.

8. Standard top area

Every new site should begin with a reusable top area containing:

• short site name

• full canonical site link directly underneath

• registration

• login

• client/user navigation

• Import

• Export

• admin access when applicable

For MES-style sites, preserve the established navigation concept where relevant:

• Teksten

• Registratie

• Import JSON

• Exports

• Credits

• ChatGPT

Additional application-specific tabs may be added.

9. Standard bottom area

Every page/view should end with:

1. Import tools

2. Export tools

3. canonical site link

4. ACO credits

10. Google Apps Script build flow

For a new MES/Sites application, use this order:

1. Ask for the canonical Google Site or website link.

2. Derive the short site name.

3. Ask for the Google Sheet link.

4. Define Sheets/tabs and data structure.

5. Create Code.gs.

6. Create any additional .gs backend files needed.

7. Create Index.html.

8. Create additional HTML views/components where needed.

9. Add registration and login.

10. Add person/client profiles.

11. Add ongoing programmes.

12. Add sessions, tasks, messages and files.

13. Add admin functionality.

14. Add top and bottom Import / Export tools.

15. Add canonical site link throughout exports and interface.

16. Add ACO credits.

17. Prepare the files for Google Apps Script deployment / Google Sites embedding.

11. Default client programme

Where the website supports people, coaching, support, training or administration, each person should have:

Profile

• name

• email

• phone

• municipality/location where appropriate

• role

• status

• tags

• registration date

Situation

• current issue

• background

• urgency

• important notes

Goals

• main goals

• short-term goals

• long-term goals

Financial section where relevant

• income

• fixed costs

• essential costs

• debts

• arrears

• creditors

• repayment agreements

• benefits / allowances / support checks

Tasks

• action

• owner

• due date

• status

• notes

Sessions

• date/time

• coach/support person

• plan

• notes

• result

• next step

Messages

• date/time

• channel

• message content

• sent status

• follow-up status

Next contact

• date

• time where relevant

• channel

• reason

Files

• filename

• type

• upload date

• note

• linked person/client

12. Personalisation and automation direction

Every MES/Sites system should be designed so it can later support:

• personalised messages

• reminders

• follow-up suggestions

• next-action generation

• recurring coaching/support workflows

• client-specific advice

• session continuity

• automated preparation for the next contact

• dashboard overview of all clients/users

The human coach/admin remains in control of the final advice and actions.