Hosting with 20% off when you buy through the link

The admin panel

The panel Velk builds from your site.json: what each area holds, drafts and publishing, deleting and ordering lists, users and roles, its language and its address.

The admin panel is where the site is run day to day: posts written, texts changed, images uploaded, leads read. Nobody designs it. Velk builds it from theme/site.json: each page, content type, form and options group declared there becomes a screen, and each field becomes an input with the label you gave it. Change the file and the panel changes.

It answers at /admin on the site's address (on your computer, http://localhost:8080/admin), with the email and password created at the install.

What's in the side menu

AreaWhat it holds
DashboardHow many entries each content type has, with shortcuts to the pages and categories.
StructurePages (the ones in site.json, plus the ones the client creates when the theme offers page templates) and Media, the library of images and files.
ContentOne entry per content type (blog, cases, services), with its count and, underneath, its categories and tags.
FormsEach form with its number of leads: submissions, recipients, spam and export.
StoreOrders, when the store is on.
OptionsThe site-wide groups the theme declares, such as contact details, footer and menu.
SettingsUsers and Scripts (tracking codes), plus Members, Plans & Subscriptions and Languages, with the translation of the theme's fixed texts, when the site uses them.

Drafts and publishing

Entries of a content type are Draft or Published. On a new entry, Create publishes it and Save draft keeps it off the site; after that, the status field decides. A visitor who opens a draft's address gets “not found”, while you, signed in, see the page: a preview before publishing. Pages have no draft: what you save is live.

Lists open newest first, with a search by title or address and a filter by status. The editor of each page, and of each entry with its own address, ends with an SEO & sharing section (see SEO and the sitemap).

Deleting and ordering

  • Bulk delete. On content and category lists, the trash icon turns on a selection mode: tick the rows, or select all, and delete them at once after a confirmation. Nothing goes to a bin you can restore from: deleted is gone.
  • An order you choose. Content comes newest first and categories alphabetically. For a team, a FAQ or a product grid, ask for manual order: since v3.7.5 a drag handle appears on that list and the site follows the order you drag. Lists show 50 rows per page, and a row moves within its page.
  • Inside the editor. Repeated rows (a list of services) and page blocks are reordered by dragging, and the Scripts screen orders scripts the same way within each position.

Ask the AI

Our team page should follow the order we choose, not the publish date. Turn on manual ordering for the Team content type and check that the site follows the panel's order.

The AI sets manual_order in site.json. The first time the list opens, the order on screen is kept, and the client drags from there.

On a phone

Since v3.8.0 the panel works on a phone: the menu opens from a button in a top bar, the fields of a row stack one under the other, and wide tables scroll sideways inside their own box. Since v3.9.0 the text editor's toolbar is a single row that scrolls sideways, and it stays at the top of the screen while you scroll a long text.

Users and roles

Admin users are the people who sign in to the panel. They are not the site's members: visitors who register in a members area have their own login on the site and never reach the panel, and both admins and editors can manage them.

  • Administrator: full access, including managing users.
  • Editor: the same access, except managing other users; an editor sees only their own account.

Each account can turn on two-factor sign-in: besides the password, a 6-digit code sent to the account's email. Check that the address receives messages first; an administrator can turn it off if someone loses access. The sign-in screen also has a “Forgot your password?” link that emails a reset link valid for 60 minutes. Both depend on the site's email sending.

Ask the AI

Create an admin user for Marina Lopes, marina@lopesarchitecture.example. Generate a strong temporary password and show it to me once; she'll change it in her account.

The AI runs bin/velk user:create, which always creates an Administrator. To make her an Editor, change the role in Settings › Users.

The panel's language and address

The panel speaks English, Portuguese and Spanish. ADMIN_LOCALE, in .env, sets the default (English on a new install; pt and es switch it), and each user can pick their own language in their account. Since v3.9.1 the built-in SEO fields and the Plans & Subscriptions screen follow the panel's language too.

ADMIN_PREFIX moves the panel from /admin to an address you choose. Your computer and the server each have their own .env: make the change on each one you use.

Ask the AI

The client's team speaks Portuguese. Set the panel to Portuguese for everyone and move it from /admin to /manage. Then tell me the new sign-in address.

The AI changes ADMIN_LOCALE and ADMIN_PREFIX in .env. Tell the editors: old bookmarks stop working.

Can the client break the site from the panel?

The panel fills the fields you declared; the structure and the look stay in the theme, out of its reach. What the client can do is delete content, with no bin to restore from, so keep backups.

I forgot my password and the site doesn't send email.

Ask the AI to create another administrator with bin/velk user:create. Sign in with it and set a new password on your own account in Users.