Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A course provider needs lessons, enrolment and a visible progress record.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Restoring an old database can erase new enrolments or progress.
Before a source copy or backup restore starts, the authorized operator must restrict the target and quarantine outbound mail, payment, fulfillment and other provider effects at the receiving environment. Restored WordPress settings can overwrite plugin suppression; reapply sandbox credentials and verify isolation before tests.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A course provider needs lessons, enrolment and a visible progress record. A learner resumes a lesson and the recorded completion persists after a test change.
Choose the approach
Choose an LMS plugin against progress, grading and student export requirements. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Tutor LMS is a documented example to evaluate, with its own course-builder, enrolment and licensing rules.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Tutor LMS official documentation and course administration
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Specify lessons and progress
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Specify lessons and progress.
- Action
- Define a course map with modules, lesson completion, enrollment source and instructor permissions. Write one learner test for starting, leaving and resuming a lesson.
- Expected result
- The team can evaluate LMS choices against a concrete learning path.
- Verify
- An instructor approves the sample course and expected progress event.
- If it fails
- If certificate or grading needs are unstated, mark them before plugin selection.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Select LMS and provision WordPress
- Where
- xCloud Add site and site overview
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Select LMS and provision WordPress.
- Action
- Select an LMS plugin from its vendor documentation, checking license, PHP/WordPress compatibility, enrollment and export behavior. Deploy WordPress on a compatible xCloud stack.
- Expected result
- The hosting and application choices can support the sample course.
- Verify
- Confirm WordPress site identity and match each required LMS function to documentation.
- If it fails
- If a function depends on an unowned extension, resolve procurement before advertising it.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Tutor LMS official documentation and course administration
Step 3 of 5
Build a sample course and enrollment
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Build a sample course and enrollment.
- Action
- Build a sample course and configure instructor and learner accounts in the LMS. Connect payment or enrollment source only through the selected vendor's documented integration.
- Expected result
- A test learner can enter the intended first lesson.
- Verify
- Inspect both enrollment state and lesson visibility as the learner and instructor.
- If it fails
- If payment succeeds without access, stop sales and repair the enrollment handoff.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration
Step 4 of 5
Test learner progress persistence
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test learner progress persistence.
- Action
- Complete a lesson, sign out and return with the same learner account. Compare progress shown to learner and instructor, then test an ineligible account.
- Expected result
- Completion persists and access is correctly restricted.
- Verify
- Record course, account and completion time in the application, not only a successful public page load.
- If it fails
- If progress disappears, investigate database/session handling before promotion.
Sources: WordPress roles and capabilities · Tutor LMS official documentation and course administration
Step 5 of 5
Rehearse recovery of learner data
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Rehearse recovery of learner data.
- Action
- Confirm that backup scope includes course content, users and progress. Rehearse a safe restore and assign staff to failed enrollments and selected updates.
- Expected result
- A future recovery can preserve learner state.
- Verify
- Compare backup timestamp with later completions and identify replay or reconciliation owners.
- If it fails
- Do not restore an older database over active learners without that decision.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A learner resumes a lesson and the recorded completion persists after a test change. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. Restoring an old database can erase new enrolments or progress. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
- Create a WordPress site mcp · write
Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site.
Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS.
Operation identifiers and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Build a sample course and configure instructor and learner accounts in the LMS. Connect payment or enrollment source only through the selected vendor's documented integration.
- The business owner compares the controlled sample with this observable result: Completion persists and access is correctly restricted.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): A learner resumes a lesson and the recorded completion persists after a test change. Test learner progress persistence
- recovery (covered): Restoring an old database can erase new enrolments or progress. Rehearse recovery of learner data
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Tutor LMS official documentation and course administration
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud