Content, SEO, translations, videos, and courses
New staging website. Use
https://beti.worldyogaalliance.org/admin/contentand its linked staging routes. Check the target public page after any save.
Open Content
Section titled “Open Content”Choose Content in the Admin workspace sidebar or open /admin/content. The tabs are Contact requests, Testimonials, Videos, and SEO and translations.
The content workspace has two different kinds of write: editorial content and visibility, and SEO/cache operations. Check the public route after saving because a record can be saved but unpublished, hidden, excluded from the sitemap, or waiting for cache invalidation.
Handle contact requests
Section titled “Handle contact requests”Contact requests is a read-only queue. Each detail shows the sender’s subject, name, email, and message. Select Reply by email to open the approved mail workflow. The admin screen does not send a broadcast and does not edit the original request.
Publish or hide testimonials
Section titled “Publish or hide testimonials”In Testimonials, cards show Published or Hidden. Select Hide or Publish (the exact action follows the current state), then reload the list and check the public page. The action changes public visibility; it does not rewrite the testimonial text or attribution.
Edit legacy video metadata
Section titled “Edit legacy video metadata”Open Videos to see Video library with Video, Visibility, Views, Created by, and Actions. Rows can show Active / Inactive and Public / Private.
- Select
Edit metadata. - Edit
Name,English name,Thai name,Simplified Chinese name,Duration,Creator user ID,Description,Stream URL,Stored video path, andStored cover pathas needed. - Set
PublicandActivedeliberately. - Select
Save video metadata.
The editor explicitly says that uploads, transcoding, and video creation remain outside this editor. Hide video / Publish video changes active/public state. Do not enter a private storage credential in a path field.
The editor saves metadata only. A successful metadata update does not upload a video or generate a cover.
Maintain internal courses
Section titled “Maintain internal courses”Open Content → Courses at /admin/content/courses. The page calls these Internal courses and explains that they are for members with a school or teacher profile.
Create or edit a course
Section titled “Create or edit a course”- Select
New courseorEditon an existing course. - Enter
Course title. - Check
Publish for membersonly when the lessons are ready. - Add a plain-text
Description. - Under
Lessons, enter eachLesson titleandYouTube URL or ID. - Use
Add lessonorRemove lesson Nto keep the ordered list correct. - Select
Create coursefor a new course orSave coursefor an existing course.
There must be 1–50 lessons. Every lesson needs a title and a valid YouTube URL or the 11-character video ID. Use a watch or share URL, not an arbitrary streaming address. Reopen the course and check lesson order after saving.
Select Delete only after confirming that all lessons will be removed. Course deletion is a business write and cannot be undone from this editor.
Edit page translations
Section titled “Edit page translations”Open SEO and translations or /admin/content?view=cms&site=platform. The selector is Select page and locale and contains:
Page— the registered CMS page (site / routeKey).Locale— currentlyen,th,zh, orhi.SEO target—Page,School,Teacher,Event, orPlatform event.Target ID / key.Load.
For a page target, the translation card is labelled Translation · {locale}. Edit Title, Excerpt, rich-text Body HTML, and Slug; then choose Published in {locale} and select Save translation. Title and Body HTML are required. To remove a locale entry, select Delete translation and confirm.
Use the page’s public locale route to check headings, links, formatting, and publication. Keep HTML intentional and do not paste secrets or untrusted scripts into the body.
Edit SEO metadata
Section titled “Edit SEO metadata”The SEO card is labelled SEO · {locale}. The editable fields are:
SEO titleFocus phraseMeta descriptionOpen Graph titleOpen Graph descriptionOpen Graph image URLTwitter titleTwitter descriptionTwitter image URL
Expand Technical SEO controls for Canonical URL, No index, No follow, Include in sitemap, and Structured data JSON. The SEO estimate displays a score out of 100 and checks. Select Save SEO, wait for the result, and inspect the corresponding public page and social metadata after the cache is updated.
Only set No index or No follow when the content owner has approved it. A staging hostname already sends an environment-level crawler exclusion; that does not automatically exclude a production page from search.
Purge the current environment cache
Section titled “Purge the current environment cache”The Cache controls card says Current environment only · no database or media deletion. The buttons are Purge page, Purge site, and (for a superuser) Purge all caches.
- Save the translation or SEO record first.
- Choose the smallest scope that contains the changed page.
- Confirm the prompt
Purge {scope} cache in this environment?. - Reload the public page and confirm the new content.
Cache invalidation is environment-scoped. A successful save followed by an invalidation error can show Saved, but cache invalidation failed. Please retry the purge. Retry the purge after checking the public page; do not duplicate the editorial write.
Edit interface translations
Section titled “Edit interface translations”Choose Content → Translations or /admin/content/translations. The page is titled Interface translations and offers language tabs English, ไทย, 中文, and हिन्दी.
- Choose the language.
- Use
Find interface textto locate a key. - Edit its translation and select
Save translation. - To return to the source text, select
Restore default.
Keep placeholders such as {count} and formatting tags unchanged. The editor validates message syntax and the key’s placeholders. A fallback English message can appear until a valid translation is saved; reload an open page to see a change.
Confirm publication
Section titled “Confirm publication”Reopen the saved record and view the public page. Check publication, visibility, sitemap settings, and cache separately. If a save reports that cache invalidation needs a retry, check the public page before saving the same content again; the editorial change may already be stored.