Next step · What to do next

Add an admin area so I can edit content myself

What you may see

I do not want to ask a developer for every price or text change

Why this step

An admin area saves time but is the most attractive target; it must check who is asking on the server for every action.

Before you start

What do you want to edit (prices, texts, images, orders, opening hours)? Who will use it?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Add an admin area so I can edit content myself

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
An admin area saves time but is the most attractive target; it must check who is asking on the server for every action.

DO THESE STEPS, IN THIS ORDER
1. Propose the smallest admin: only the screens for the items on my list, with simple forms and clear labels in English and Arabic.
2. Protect every admin page, API route and action on the server by sign-in and role; use two-step sign-in for admins; add database rules to match.
3. Validate every input, keep a change log (who changed what and when), and make delete a soft delete with an undo where possible.
4. Make it work well on a phone, and write tests that call each admin address logged out and as a normal user.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Admins can do the listed tasks, everyone else is refused everywhere, and every change appears in the log.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not expose the admin at a public address without protection.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Propose the smallest admin: only the screens for the items on my list, with simple forms and clear labels in English and Arabic.
Protect every admin page, API route and action on the server by sign-in and role; use two-step sign-in for admins; add database rules to match.
Validate every input, keep a change log (who changed what and when), and make delete a soft delete with an undo where possible.
Make it work well on a phone, and write tests that call each admin address logged out and as a normal user.

Do not do this

Do not share one admin password.
Do not expose the admin at a public address without protection.

Try another entry