Skip to main content
Learning station / open routes

Find the signal
in software.

Wedomari is an English-language IT course station built around real handoffs: from a question, to a working model, to a clear explanation of what happens next.

01—04
Working pathways
Small
Practice groups
Clear
Starting points
SYSTEM
ORIENTATION
A desk with laptops and turquoise lighting at dusk
Route statusSwitchyard active
37° / 12′ / 08″
learn by routing
ROUTE WEATHERGood conditions for a first move.
VISIBILITYHighStart with a tangible task.
TRAFFICSteadyOne focused session at a time.
Turquoise cable, keyboard and tags on a light desk
01 / route planner

Choose a track,
not a label.

A first route is simply a useful next direction. Select the kind of problem that holds your attention and we will surface the course language, first exercise and a sensible companion platform.

Turquoise cable connecting a keyboard
ROUTE 01 / BUILD SYSTEMS

Make a small tool do one reliable thing.

Start with HTML, CSS and JavaScript as a connected system. Practice reading a brief, naming what belongs where and testing one change at a time.

FIRST EXERCISEA one-page status tool
TRANSFER TOPlatform A
Open the platform
02 / entry platforms

Enter where the work
feels legible.

Each platform is a welcoming first station, not a fixed destination. They share a common practice: observe, make a move, test the route, then record what changed.

Person working beneath a large board
PLATFORM A

Code
Foundations

For people who want to understand how web pages and simple scripts are assembled.

Explore
Group reviewing work around a table
PLATFORM B

Data
Questions

For people who prefer spotting patterns, checking assumptions and explaining a finding.

Explore
Person holding a laptop beside a network cabinet
PLATFORM C

Service
Operations

For people drawn to reliable handoffs, diagnostics and calm communication.

Explore
03 / platform labs

Practice in
connected yards.

Short laboratories make the handoffs visible. One challenge leads into the next with a different tool, a different role or a clearer explanation.

01
Learner arranging planning cards on a wall
ALIGNMENT LAB

Map a small product decision.

Translate a request into a compact plan, a question list and a testable next step.

02
Group working around laptops with cables
CONNECTION LAB

Follow an input through a system.

Trace how a form, a stored value and a response meet one another.

03
Hands arranging colored markers on a desk near a keyboard
INTERFACE LAB

Make a choice easier to see.

Use hierarchy, labels and states to make an interface feel less mysterious.

04 / transfer cards

Pick a card.
See the handoff.

Routes become more useful when you can name the transfer. Choose a card to reveal a concrete way one learning mode supports another.

Coiled black cable and small geometric components
TRANSFER 01 / OBSERVE

Start with what is already happening.

Before changing a screen or a script, learn to describe its current behavior. That observation becomes a useful note for design, data and operations work alike.

CURRENT HANDOFFQuestion → evidence → next move
05 / signal desk

Errors are route notes.

We treat a snag as information to work with. The desk below helps learners turn a vague “it broke” moment into a specific observation and a safe next action.

Ask about a route
Signal desk / error route table
SignalRead it asFirst move
Blank screenA connection is missing.Check the browser console.
Unexpected valueAn assumption needs a test.Print the input and compare.
Stuck requestA handoff is unclear.Write the smallest reproduction.
Busy interfaceThe route needs hierarchy.Remove one competing action.
06 / project departures

Board the work
while it is moving.

PROJECTPLATFORMDEP.ROUTE
Small status pageA / Code FoundationsReady for a layout check
Pattern noteB / Data QuestionsGathering observations
Service mapC / Service OperationsTracing a handoff
Interaction stateA / Code FoundationsTesting a useful change
A keyboard and red control connected by a turquoise cable
07 / handoff station

Keep a record
someone else can use.

Technical learning becomes more durable when it can travel. At the handoff station, learners turn a working file into a short note: what it does, what was changed, what to check next and what remains uncertain.

  • Write the purpose before the detail.
  • Include one repeatable check.
  • Leave the next person a decision point.
08 / learning timetable

A rhythm for
practical progress.

OPEN SIGNALOrientation and route choice
All platforms
LAB ABuild a clear page structure
Code Foundations
LAB BTurn a question into a data note
Data Questions
TRANSFER WINDOWCheck, explain and hand over
All platforms
LAB CTrace a service request
Service Operations
09 / route questions

Before you arrive.

Four practical answers for people deciding where to begin.

No. The entry platforms are designed to make the first technical concepts observable before they become abstract. You may arrive with curiosity, work experience, school experience or none of these. What matters most is being willing to try a small task, describe what happened and ask a precise follow-up question.

10 / departure form

Send a first signal.

Tell us what you want to understand or make. This browser-only form does not transmit personal data; it simply confirms that your route note is ready to copy into your own message.

WEDOMARI / CONTACT DESK
English course enquiries