Useful guidance, not noise.
Guides, practical reference sheets and lab notes to better understand Moodle, IOMAD, instructional design and the digital architectures supporting learning.
Three frequently asked questions.
These first resources provide a brief, structured answer. They may later develop into detailed guides, tutorials or courses.
Moodle, CRM or WordPress: who does what?
An architecture becomes clearer when each system has a primary responsibility.
- WordPress presents and converts
- The CRM manages relationships and offerings
- Moodle delivers and tracks learning
- Support handles requests
Read the key takeaway
Avoid asking Moodle to become your public website, CRM and transaction tool all at once. Connections are useful, but responsibilities must remain explicit.
Before adding a plugin
A plugin can meet a real need, but it also adds a maintenance responsibility.
- Check Moodle’s native tool
- Confirm compatibility
- Test outside production
- Plan for updates
Read the key takeaway
The best plugin is not the one with the most features. It is the one that meets the need with realistic maintenance, consistent permissions and integration that follows Moodle standards.
Why create a lab?
A lab lets you learn and validate an idea without using real data or putting production at risk.
- Fictional scenarios
- Repeatable tests
- Concrete demonstrations
- Documented decisions
Read the key takeaway
A lab is excellent for confirming pathways and business rules. However, it does not replace the security, load and governance checks required before deployment.
Follow what truly changes practice.
The aim is not to comment on every new development. A resource deserves publication when it helps explain a decision, avoid a mistake or use a tool better.
Moodle and IOMAD
Versions, native features, administration, plugins and sustainable practices.
Instructional design
Structure, engagement, assessment, accessibility and transfer of learning.
CRM, web and support
System roles, data exchanges and enrolment journeys.
Lab notes
Tests, limitations encountered, fixes and reusable lessons.
A short check often prevents a long detour.
A resource should remain useful after publication.
The content of this library will follow four simple principles.
Practical
Examples, decisions and actions rather than accumulated jargon.
Honest
Limitations, assumptions and project statuses are clearly stated.
Traceable
Important versions and dates will be specified when the topic evolves.
Respectful
No confidential information or client data is needed.
Explore further: the blog
The resource centre provides quick guidance. The blog develops ideas, documents experiments and shares deeper analysis.
It could become the next useful resource.
If a Moodle, IOMAD or instructional design question keeps coming up in your organization, it may deserve a clear, reusable reference sheet.