What it is
A system through which the owner changes texts, prices and products without a developer. WordPress is the best-known ready CMS; a custom admin panel is written separately and does exactly what is needed.
How we use it
For showcases we install WordPress with a custom theme; for stores with stock we write a FastAPI panel: prices and availability are edited in one table, orders arrive in Telegram.
Where an admin panel helps a business
- Prices and stock change every week, and waiting for a developer for each edit is expensive.
- A store owner wants to add products with photos from a phone and see orders.
- Texts, contacts and legal details on the site must change without the risk of breaking something.
- The service has to be run from a phone, on the go.
Types
- A ready CMS: WordPress. A familiar admin and editor. We choose it when the client values a familiar environment, and we write our own theme.
- A custom panel. It does exactly what the owner changes: products, prices, stock, orders. For a store with its own logic.
- Content in files. Texts live as markdown in git; an edit is a file change and a rebuild. Suits a site run by someone comfortable with git.
- A bot as the admin. Management right from Telegram: buttons in the chat and a cabinet inside Telegram.
How we use it
- ยซะัั
ะฐะฝะธะต ะะพะฒะพะปะถััยป: WordPress with a Site section, including a launch-readiness checklist, prices and stock in one table with a percentage change for all prices, texts with a live preview in desktop and phone views, and an "Original text" option on every field. Plus a built-in 11-section guide and a separate 29-page guide in Word.
- The shirt store: a custom panel on a separate subdomain with products, photos, "hit" and "new" labels, removal from the storefront, and orders with a one-tap call to the buyer.
- The packaging manufacturer's sites: a Site menu with more than 60 fields, where every save is remembered and can be undone with a "Restore as it was" button.
- UNLOCK: 72 labels and the card theme are edited from the bot and from a cabinet inside Telegram, with no code or deploys.
- The studio website: no database and no admin; content lives in git and a schema checks its structure.
We plan the admin panel from the start under Websites and online stores.
Common problems
- An edit breaks the layout. A preview before saving and a change history with an undo button help.
- What does an empty field mean? Our rule is "empty means do not use": an unfilled analytics counter ID does not load its script.
- The owner forgot how to do it. The guide must live inside the admin itself, not in an email from six months ago.
- Too many rights. Each person sees only their own: in UNLOCK a client sees only their own cards.
When you do not need it
If the site changes twice a year, an admin panel is extra code to maintain; it is faster to edit a file. And if the developer makes all edits as part of maintenance, a separate admin will not pay for itself.