THE EKG MARKETING WORKSHOP
Open Web Lab.
Look inside the websites and tools behind the work.
Learn how they’re built, what you control and how to make them your own.
FEATURED LAB / 001
You see the website.
Let’s open it up.
Our own WordPress stack, explained through the parts that do the work: the shared theme, the site’s identity and four focused plugins.
Look inside the buildSOURCE INSPECTION · WORDPRESS
FOLLOW YOUR CURIOSITY
Three ways into the workshop.
What do you actually own?
Make an inventory of the access, files and records you would need to move.
Read the guide ↗
The work has a history.
See where files, recorded changes and review fit into a development workflow.
Explore the tool ↗service-tool storage?From the six-record teaching dataset
Start with the visitor’s question.
Filter six teaching records and inspect the data that connects the answers.
Try the example ↗EXAMPLE SITE / LAB 005
Laser TeamWork: learning with sources.
Our first public AI test project brings together models, reference knowledge and explanations people can inspect. Explore the documented pilot and take the knowledge pack into your own experiments.
A PRACTICAL FIRST STEP
Could you move your website tomorrow?
You don’t need to know every answer. The ownership check helps you find the questions worth asking.
FROM THE READING BENCH
Better questions. Clearer decisions.
Open Source vs SaaS: The Question Isn’t Which Is Better
Separate permission to use software from the responsibility to operate it, then choose the combination your team can sustain.
WordPress Plugins vs Custom Code
Compare the whole obligation: behavior, updates, data, editing and the person who will maintain it.
AI-Assisted WordPress Development Without AI Dependency
Keep requirements, source and tests outside the chat so another person—or another tool—can continue the work.
How Git Changes the Way We Build WordPress
A change history makes code review possible. You still have to account for the database, uploaded files and deployment target.
LEARN BY MAKING
Build something
you can explain.
Fourteen practical modules. One small project. Finish with source files, a test record and an explanation another person can follow.
Explore the learning path ↗- 01—04Understand the webRequests · domains · HTML · content
- 05—10Make the pieces workWordPress · Git · models · features · AI
- 11—14Test it. Explain it. Share it.Accessibility · release · documentation
Built from EKG’s work. Open for your questions.
About the Lab Suggest a correction Principles AI policy