01 / Functional scope
Education Website
Best for
Public presence and programme discovery
Typical functions
Website, programme pages, contact and enquiry pathways, and scoped applications.
Explore Education WebsiteDigital Campus / The connected foundation
Bring together your public website, learner experience, LMS, assessments, certificates, staff workflows, support and reporting around one digital foundation.
The right connections, configured to your agreed scope. Not every enterprise capability is included in every implementation.
Starting from R49,900
Final scope depends on institution size, required functionality, integrations, content readiness and implementation requirements.01 / Explore the architecture
Select a layer to see its role in the institution. These are capability areas, not a promise that every feature is included automatically.
System layer / agreed scope
Help prospective learners understand your institution and take the next step.
An agreed enquiry or application process leads into onboarding, not an automatic promise of admission.
System layer / agreed scope
Give each learner a clear place to access learning and find help.
Course activity informs staff review and administration. Completion follows institutional rules.
System layer / agreed scope
Give lecturers the tools and context to guide learning.
Roles connect teaching, feedback and support without granting every staff member administrator access.
System layer / agreed scope
Coordinate access, records and institutional oversight.
Agreed permissions and data structures support consistent records across institutional workflows.
System layer / agreed scope
Provide the technical and operational base underneath the experience.
Deployment, access and maintenance responsibilities are scoped explicitly, including any recurring costs.
Future concept / separately scoped
Prepare organised information for future, governed assistance.
Conceptual future layer. Requires approved sources, access controls, separate scoping and human oversight.
Shared foundation: identity, permissions, data and documentation. Future intelligence builds on these controls, not around them.
02 / One platform. Different experiences.
Switch between learner, lecturer and administrator workflows. These interface concepts explain implementation capabilities, not a live production platform.
Learner experience
One starting point for enrolled courses, learning activities, progress and support.
Digital Campus / Learner
Sample records. No live accounts or backend actions.
Capability demonstrations, not a guarantee that every feature is included in the starting package. Production workflows, permissions and integrations are configured to the agreed scope.
03 / The institution journey
Follow a learner through the institution and see which part of the Digital Campus handles each step. Support is available throughout, not only after completion.
Step 1 / 10
Institution website and programme pages explain what you offer.
04 / The implementation boundary
The starting package covers a core website and LMS foundation, onboarding, staff training and launch support. Explore possible implementation areas below; detailed inclusions depend on institutional requirements and the agreed scope.
Can include, configured according to agreed scope:
Can include, configured according to agreed scope:
Can include, configured according to agreed scope:
Can include, configured according to agreed scope:
Can include, configured according to agreed scope:
Beyond the starting scope
These requirements may need an additional quotation, specialist input or third-party costs. They are not automatically included in the starting package.
05 / Built with your team
Explore the implementation stages. Sequence, responsibilities and timing are agreed after discovery; this is not a fixed-duration promise.
Step 1 / 9
Review programmes, people, current systems and operational needs.
06 / Choose the right scope
Each is a valid starting point. The difference is the functional scope your institution needs, not a ranking of better and worse services.
01 / Functional scope
Public presence and programme discovery
Website, programme pages, contact and enquiry pathways, and scoped applications.
Explore Education Website02 / Functional scope
Structured learning delivery
Courses, lessons, assessments, progress and configured certificates.
Explore LMS Implementation03 / Functional scope
Connecting public experience, learning and institutional workflows
Website, applications, learner portal, LMS, assessments, certificates, staff workflows, support and reporting, with a foundation for future AI readiness.
Explore Digital Campus07 / Digital Campus Lab
The Tan-Pixels Future Skills Academy makes the learner experience tangible without presenting fictional records as real outcomes.
Tan-Pixels Future Skills Academy
Explore the types of learner experiences, course structures, support workflows and interfaces we can design. This is a fictional demonstration, not a registered or accredited institution, and no records represent real learners.
Reused from the existing demo learner portal. Progress and records are illustrative; no production backend is implied.
08 / Responsible intelligence
AI is most useful after institutional information, processes and permissions are organised. A well-structured campus can support carefully governed assistance in future.
Intended architecture / future concepts
These are concepts, not a claim that every AI feature is deployed. Integrations, governance and operating controls require separate discovery and agreement.
Answer approved platform and course questions, guide navigation and explain approved processes.
Draft announcements, summarise common support issues and locate institutional information.
Search documentation, assist with reporting narratives and support structured workflow tasks.
Prepare course-support drafts, assessment drafts, question banks and summaries for human review.
09 / Reporting & visibility
A scoped reporting architecture can connect activity to informed staff review. Explore example categories and their possible sources, without invented statistics.
No live learner data, calculated metrics or performance claims. Available reports depend on the platform, data quality, permissions and agreed scope.
10 / Built to grow
Expand in response to real institutional needs, staff capacity and reliable data. You do not need to buy every capability immediately; integration and intelligence are separately scoped future possibilities.
Website + LMS + learner access
Lecturer/admin workflows + support + reporting
External tools + data flows + institutional systems
Search + automation + AI-assisted workflows
11 / The commercial starting point
The price reflects a connected foundation. Discovery turns your requirements into an explicit scope, rather than an open-ended feature list.
Digital Campus Package
Starting from R49,900
The starting package brings together the core public website and learning platform, onboarding, staff training and launch support. It is not an unlimited custom-software engagement.
Discuss your implementationDetailed deliverables, quantities, responsibilities and recurring costs are confirmed in the agreed scope before implementation.
12 / Is this right for us?
A consultation should clarify what to implement now, what can wait, and who will operate the platform after launch.
You may only need a professional website or a standalone LMS first. If your organisation is not yet ready to maintain digital learning operations, start by clarifying staff capacity, ownership and content readiness.
Your institution. Your next step.
We can help you define what your institution needs now, what can wait, and how the system can grow over time.