What you will finish
Publish a public schedule for one Alexandria amateur team, showing the next fixture, venue, confirmation state, update date and a contact route when arrangements change.
1. Gather these details
- Obtain the organiser’s permission to publish the team name and fixtures, and permission for logos and photographs. Do not assume group membership authorises publishing individual images.
- Prepare three genuine fixtures for launch or explicitly fictional records for testing. Each needs a date, meeting time, playing time, venue and checked published address.
- Identify one person responsible for confirming changes with the venue and other team. A stable website link cannot replace someone checking the actual arrangements.
- Agree clear pending, confirmed, postponed and cancelled states. Specify the channel participants should use for urgent changes on the day itself.
2. Define how the project works
1. Get fixture details from the responsible organiser
Do not copy an old chat message without reconfirming it. Give each fixture a reference, the permitted team names and a full date rather than next Thursday alone. Use the venue name and checked address link. If booking or agreement with the other team is incomplete, show pending confirmation. A green colour or prominent share button must not imply certainty while the arrangement itself is still only a proposal.
2. Separate meeting time from playing time
Use distinct fields for arrival and the start of play, clearly labelled in Egyptian local time. Add short entry instructions confirmed by the venue, without inventing charges or rules. Put the next fixture first and order the rest by date. If supporters may use the page, explain whether attendance is actually permitted and who can confirm it. Reading a public fixture schedule should not require an account or personal details.
3. Make changes visible rather than silently rewriting dates
When a fixture moves, show postponed with an update time and the replacement date only once confirmed. If no replacement exists, say that clearly. For cancellation, keep a visible notice long enough for someone relying on an older screenshot to understand the change. The page owner publishes after verification, then shares the updated link through the agreed channel. Publication alone does not establish that every participant has read the message.
4. Publish only the necessary public information
Team name, fixture details and a consented contact route are enough for this page. Player telephone lists, individual attendance and reasons for absence belong elsewhere. A private attendance tool or multi-editor results system would need a different scope. Test on a small phone and ask someone outside the group to find the meeting time, venue and confirmation state. If those are difficult to locate, shorten the introduction and improve the information order.
3. Work through an example
| Fixture | Time and state | What readers should see |
|---|---|---|
| Example Team versus Team B | 22 October; meet 6 pm, start 6:30 pm; confirmed | Two distinct times and a venue to verify |
| Example Team versus Team C | 25 October; pending confirmation | Clearly not ready-to-attend confirmation |
| Example Team versus Team D | 28 October; postponed | Replacement date not yet confirmed |
| Last review | 18 October 2026; illustrative | A visible review date beside the schedule |
The sample meeting and playing times differ by thirty minutes. Replace every fictional entry with arrangements the organiser has authorised for publication.
4. Set up your account and start the build
- Use your account or register.Visit www.gammal.tech/join. New account activation takes 1–10 days. Use a National ID from a country whose citizenship you hold; the official account guide explains the limited exceptions for Egyptian citizens. Submit identity documents only through the official registration process.
- Activate the WhatsApp subscription.After approval, open my.gammal.tech and add EGP 200 to your wallet, or use sufficient existing funds. Activate the monthly WhatsApp subscription in your account and check that it is active. Funding the wallet alone does not activate it. This subscription covers light personal use; website creation is charged separately.
- Open the building conversation.Message +201033998844 and send the following command by itself, including the required square brackets. Wait for confirmation of build mode:
[mode: build][mode: web]is an alternative for the same mode; you only need one command. - Send the request in the next section.Replace its placeholders and ask for exactly one page using an available name of at least three characters. Before execution, request an itemised quote separating the one-time build fee, EGP 100 for the first month of standard hosting and any additional usage. Ask how changes beyond the agreed scope are charged.
- Check the total and approve the build.Once you understand the quote, return to your account and add any missing funds. Return to WhatsApp and confirm the scope and price. Some simple sites take minutes; requirements and revisions affect timing. Open the resulting address and run this guide’s acceptance checks.
- Record the renewal date.MeNooN hosting renews manually: select the duration and confirm payment before expiry. Leaving funds in your wallet does not renew it automatically. Send
[exit], including brackets, when you finish the building conversation.
Budget: quoted build fee + EGP 100 hosting + EGP 200 for one WhatsApp month if it is not already active, plus agreed usage. Twelve months of standard hosting cost EGP 1,200; adding one WhatsApp month makes EGP 1,400 before build and usage fees. Keeping WhatsApp active for further months costs separately.
Service steps and prices reviewed on 18 October 2026. Check the amount shown in your account before paying. WhatsApp steps · Hosting and renewal
5. Adapt and send this request
Replace every bracketed placeholder with your real details. Copy this request after the assistant confirms build mode. Do not publish the illustrative figures as your own.
Build ONE PAGE on MeNooN for [team name], an amateur team in Alexandria, in [language]. I am authorised to publish the supplied fixtures and logo. Do not fetch famous-team news, invent results, venues or bookings. Each fixture needs full date, opposing team, meeting time, playing time in Egypt, venue, checked address link and pending/confirmed/postponed/cancelled status. Put the next fixture first and show the last update. For postponement, retain a notice about the original arrangement and show a new date only after I confirm it. Do not present proposed changes as final. Visitors need no login or data collection. Include my personal WhatsApp [permitted public number] for questions and identify [channel] for urgent changes. Do not publish player contact lists or attendance, and do not add pitch booking or live scores. Make states understandable in text as well as colour, with readable dates on phones. Before starting, quote the one-time build fee separately from the first month of standard 100 EGP hosting for an available name of at least three characters, plus additional costs. Wait for approval.
6. Test the result before relying on it
- Enter a 6 pm meeting and 6:30 pm playing time.Expected result: Both appear distinctly with a thirty-minute gap, a full date and Egyptian local time.
- Postpone the next fixture without a replacement date.Expected result: The page clearly shows postponement and an unconfirmed replacement, not a confirmed upcoming fixture.
- Open venue and WhatsApp links on a phone.Expected result: They reach the approved address and consented contact; a prepared message is not sent automatically.
- Ask an unfamiliar reader to identify the next fixture.Expected result: They find the date, meeting time, venue, state and a route for asking about missing information.
7. Use the project during its first week
Start with the next two weeks. Ask the organiser to check every entry against the actual venue and opposing-team arrangements, then add the link to the team group description with permission. At the first change, update the page and send a message identifying the change and linking to the revised schedule. Ask two readers whether the status is clear. After the fixture, add verified answers to repeated practical questions. Measure fewer contradictory messages or visits to an old date rather than promising popularity or attendance growth.
An announcement you can adapt
The [team name] Alexandria schedule now has one link: [website link]. Find the meeting time, playing time, venue and confirmation state. Check the latest update before travelling, and use [agreed channel] for urgent changes. Pending fixtures are labelled clearly.
Questions about this project
Can I add match results later?
You can publish a result confirmed by the organiser, but this version focuses on arrangements. Live scoring and updates by several people require additional design.
Should cancelled fixtures disappear immediately?
Keep a cancellation notice temporarily so readers of an older schedule understand the change. Archive it later without leaving an apparently active date.
Does the website confirm a pitch reservation?
No. The booking authority confirms the reservation; your page reports its status. Publish confirmed only when the real arrangement is complete.