Yes. The 255-page WXR should not mean 255 individually designed WPBakery/VC pages. The clean architecture is to separate the site into designed institutional pages, dynamic archive/filter pages, LMS-generated application screens, and course/program records.

The custom LMS already defines courses as the og_course custom post type, along with lessons, quizzes, assignments, certificates, and live classes, so those should not be duplicated as ordinary WordPress pages.

Build-type key

Type	Meaning
VC	Build as a polished WPBakery/Visual Composer page
AUTO	Generated dynamically from taxonomy, CPT, query, archive, or shortcode
COURSE	Create as og_course, not a normal Page
PROGRAM	Better as a program record/CPT with reusable template
LMS	Generated by the OneGodian University LMS
ACCOUNT	Login/account/application functionality
SIMPLE	Standard Gutenberg/VC-light informational or legal page

1. Seven main pages — all need premium VC designs

These are your main institutional landing pages and should be among the strongest pages on the site.

Page	Build
Academics	VC
Courses	VC + dynamic course catalog
Programs	VC + dynamic program catalog
Schools	VC + dynamic school directory
Student Experience	VC
University	VC
Resources	VC

I would also build Home as a major VC page.

So the first 8 flagship VC pages are:

1. Home
2. Academics
3. Courses
4. Programs
5. Schools
6. Student Experience
7. University
8. Resources

---

2. Academics

VC pages

These need explanatory content, diagrams, cards, pathways, CTAs, or substantial educational information:

• Academic Overview
• How Learning Works
• Academic Calendar
• Learning Model
• Course Levels
• Credit and Study Hours
• Foundational Pathway
• Professional Pathway
• Builder Pathway
• Leadership Pathway
• Technology Pathway
• Advanced Studies
• Certificate Overview
• Academic Integrity
• Student Conduct
• Choose a Learning Path
• Recommended First Courses
• Course Prerequisites
• Program Roadmaps
• Continuing Education
• Contact Academic Support

AUTO pages

These are primarily filters or catalog views rather than standalone editorial pages:

• Beginner
• Intermediate
• Practitioner
• Advanced
• Architect
• Master-Level Study

They should query courses by difficulty / level.

Similarly:

• Foundation Certificates
• Professional Certificates
• Advanced Certificates
• Specialized Certificates

should query the certificate/program database.

SIMPLE policy pages

These can use one standard policy template:

• Course Requirements
• Assessment Standards
• Completion Requirements
• Grading Standards

LMS

• Certificate Verification

Use:

at:

/certificate-verify/

---

3. Courses

This is where the biggest architectural correction should happen.

The individual named courses should not be individually rebuilt as normal WP pages.

They belong in:

og_course

The LMS specification already defines og_course as the canonical course content type.

Main catalog

• Courses → VC + AUTO
• All Courses → AUTO
• New Courses → AUTO
• Featured Courses → AUTO
• Popular Courses → AUTO
• Free Courses → AUTO
• Paid Courses → AUTO

These should all use one course-card engine with different queries.

Example

/courses/

could contain:

Hero
Search
Categories
Featured Courses
Newest Courses
Free Courses
Professional Certificates
Learning Levels
Course Grid
CTA

Then the actual catalog is:

---

4. These are COURSE records, not VC pages

OneGodian Foundations

• Introduction to OneGodian™
• The OneGodian Identity™
• The OneGodian Journey™
• OneGodianology™ Foundations
• Mortal Duties™
• OneGodianism™ Today

OneGodianosophy™

• Introduction to Onegodianosophy™
• OneGodian Epistemology™
• OneGodian Logic™
• OneGodian Metaphysics™
• OneGodian Ethics™
• OneGodian Aesthetics™

The Onegodianosophy sequence already has a coherent academic structure, including Epistemology, Logic, Metaphysics, Ethics, Aesthetics, and Political Philosophy.

Systems and Intelligence

• Introduction to O-H-I™
• Evolution of O-H-I™
• Introduction to OMOS™
• Belief Mapper™ Foundations
• The OneGodian Algorithm™
• OneGodian Build Process™

Technology and Enterprise

• OneGodian Technology Ecosystem
• Platform Architecture
• Digital Business Systems
• Entrepreneurship Fundamentals
• OneGodianonomics™
• Digital Products and Commerce

Leadership and Community

• Principles of Leadership
• Community Leadership
• Governance Fundamentals
• Community Development
• Strategic Leadership
• Institution Building

Result

Those 30 entries should become courses.

Each receives a reusable LMS course template such as:

/course/{slug}/

Not 30 hand-designed VC pages.

The course-development standard already gives these records a repeatable structure of course overview, objectives, modules, lessons, quizzes, assignments, final assessments, and certificates.

---

5. Programs

I would introduce:

og_program

or a similar first-party program content type.

That means the Programs page itself gets VC, but the actual programs should mostly be template-generated.

AUTO catalog pages

• All Programs
• Certificate Programs
• Professional Programs
• Specialization Tracks
• Program Comparison

PROGRAM records

Foundation Programs

• OneGodian Foundations
• OneGodianology™ Foundations
• OneGodian Identity Studies
• OneGodianism™ Studies
• Mortal Duties™ Studies
• OneGodianese™ Foundations

Philosophy Programs

• Onegodianosophy™ Certificate
• Epistemology Track
• Logic Track
• Metaphysics Track
• Ethics Track
• Political Philosophy Track

Systems Programs

• O-H-I™ Practitioner
• OMOS™ Foundations
• OneGodian Algorithm Specialist
• OneGodian Time™ Studies
• Belief Mapper™ Practitioner
• Systems Architecture

Professional Programs

• Digital Entrepreneurship
• Business Systems
• Technology and Platforms
• Leadership Development
• Community Development
• Creative Media

Future programs

Treat these differently:

• Associate Pathways
• Bachelor-Level Pathways
• Graduate-Level Studies
• Research Programs
• Capstone Programs
• Institutional Partnerships

I would build these as VC informational pages for now, because they describe future or developing pathways rather than active enrollment records.

---

6. Schools

The main:

Schools

page should be a premium VC directory.

Then I recommend each actual School have its own VC landing page with auto-generated course/program grids.

OneGodian Studies

• OneGodianology™
• Onegodianosophy™
• OneGodianism™
• OneGodianese™

Intelligence and Systems

• School of O-H-I™
• School of OMOS™
• OneGodian Algorithm™
• Belief Mapper™
• Consciousness Studies

Business and Economics

• Business and Entrepreneurship
• OneGodianonomics™
• Digital Commerce
• Founder Development
• Financial Literacy
• Enterprise Systems

Technology

• Technology and Digital Systems
• Web Development
• Platform Architecture
• Automation Systems
• Digital Infrastructure
• Responsible Technology

Leadership and Community

• Leadership Studies
• Governance Studies
• Public Administration
• Community Development
• Institution Building
• Conflict Resolution

Culture and Future Studies

• Creative Arts and Media
• Language and Culture
• Human Development
• OneGodian Time™
• Future Studies
• Research and Innovation

For these, the ideal pattern is:

VC School Landing Page + dynamic course grid + dynamic programs + certificates + faculty + featured resources.

So a School is a real public page, but its course cards are automatically populated.

---

7. Student Experience

This entire area should be split sharply between public VC pages and LMS application screens.

VC

• Student Experience
• Student Orientation
• Learning Community
• Discussion Groups
• Study Groups
• Student Events
• Community Guidelines
• Student Support
• Technical Support
• Academic Support
• Enrollment Support
• Billing Support
• Accessibility Support
• Certificate Support

LMS

Do not hand-design separate VC content pages for:

• Student Dashboard
• My Courses
• Continue Learning
• My Progress
• My Assignments
• My Quiz Results
• My Certificates
• Certificate Requirements
• Download Certificates
• Share Credentials
• Verify a Certificate
• Live Classes
• Upcoming Sessions
• Class Replays

These belong inside the application.

The dashboard specification already calls for enrolled courses, continue learning, progress bars, upcoming live classes, certificates, quiz scores, and student settings.

Dashboard

/dashboard/

[og_student_dashboard]

---

8. Live-learning pages

These should be generated from:

og_live_class

rather than manually creating pages for every event.

LMS/AUTO

• Live Classes
• Upcoming Sessions
• Class Replays
• Instructor Events
• Workshops
• Academic Webinars

Use:

/live-classes/

with:

[og_live_classes]

Individual sessions become generated records.

---

9. Account and Access

These should not be normal VC content pages.

ACCOUNT

• Log In
• Register
• Account Settings
• Profile
• Password Support
• Sign Out

The public-facing login/register shell can have OneGodian branding, but authentication should be application-generated.

Canonical routes from the LMS architecture include /login and /register.

---

10. University

This area contains many pages that genuinely deserve VC treatment.

Major VC pages

• About the University
• Mission and Purpose
• Educational Philosophy
• University History
• Founder and Originator
• University Development
• University Leadership
• Academic Administration
• Departments
• Faculty and Instructors
• Advisory Structure
• Admissions Overview
• How to Enroll
• Entry Requirements
• Transfer and Prior Learning
• Pricing
• Course Pricing
• University Membership
• Payment Options
• Scholarships and Support
• University News
• Partnerships
• Careers
• Press and Media
• Contact the University

AUTO / system

• Registration → account system
• Announcements → posts/query
• University News → post archive

SIMPLE policies

Use one reusable institutional-policy template for:

• Billing Policies
• Academic Policies
• Student Policies
• Instructor Policies
• Course Standards
• Certificate Standards
• Academic Integrity

These need content, but they do not each need elaborate custom VC artwork.

---

11. Resources

The primary Resources page gets full VC treatment.

Then divide everything else.

VC / editorial hubs

• Learning Center
• Student Guides
• Study Resources
• Getting Started
• Student Handbook
• Instructor Handbook
• LMS User Guide
• Certificate Guide
• Technical Documentation
• OneGodian Lexicon
• Source Documents
• University Publications
• Media Center

AUTO archives

• Course Catalog
• Program Catalog
• Articles
• Research Papers
• White Papers
• University News
• Course Announcements
• Events
• Videos
• Podcasts

These should populate from their content types rather than require manual updating.

TOOLS / application

• Belief Mapper™
• OneGodian Time™ Converter
• Certificate Verification
• Learning Path Finder
• Course Search
• Student Help Tools

Each should eventually be an actual interactive tool or shortcode application.

---

12. Legal

These need actual content but do not need custom VC builds.

Use the same legal-page template for:

• Terms of Use
• Privacy Policy
• Refund Policy
• Accessibility

I would add eventually:

• Academic Disclaimer
• Certificate Disclaimer
• Cookie Policy
• Intellectual Property
• Acceptable Use
• Student Terms

---

13. Header utility pages

Link	Type
Search	AUTO
Live Classes	LMS
Certificate Verification	LMS
Pricing	VC
Log In	ACCOUNT
Register	ACCOUNT
Student Dashboard	LMS

---

14. Footer links

You should not build duplicates.

The footer simply points to the canonical pages already created.

For example:

About the University

in the footer uses the exact same page as:

University → About → About the University.

Same rule for:

• Schools
• Admissions
• University News
• Programs
• Academic Calendar
• Academic Policies
• Student Dashboard
• My Certificates
• Live Classes
• Privacy Policy
• Terms of Use

One canonical page per concept.

---

15. Content types I recommend adding to the LMS

The university will become much easier to manage if we stop treating everything as page.

You already have the LMS content model for courses and related educational records. I would extend it to:

Content	WordPress Type
Institutional page	page
Course	og_course
Lesson	og_lesson
Quiz	og_quiz
Assignment	og_assignment
Certificate Template	og_certificate_template
Live Class	og_live_class
Program	og_program
School	og_school or taxonomy
Instructor	og_instructor taxonomy/profile
Research Publication	og_research
University Event	og_event
Resource	og_resource
Announcement	WordPress post or og_announcement

---

Recommended final breakdown

The practical build strategy for the 255 imported pages should therefore be roughly:

Build method	Role
~55–75 VC pages	High-value institutional/editorial/marketing pages
30+ COURSE records	Current named courses in og_course
20–30 PROGRAM records	Certificates, tracks and programs
20+ SCHOOL/discipline landing pages	VC shell + auto content
25–40 AUTO pages	Archives, filters, catalogs, taxonomies
15–25 LMS/application screens	Dashboard, progress, certificates, live classes
6–10 ACCOUNT pages/actions	Login, registration, profile, security
15–25 SIMPLE pages	Policies, support, documentation, legal

The WXR you already have is therefore best treated as the URL and information-architecture scaffold, not as instructions to manually design all 255 pages.

The most important rule going forward

VC builds the experience.
The LMS generates the learning application.
CPTs hold the structured records.
Archives automatically organize those records.

That will keep the University maintainable when the catalog expands from dozens of courses to hundreds. The University course catalog is already designed around modular schools, courses, certificates and specialization pathways, which fits this architecture well.