iSkew Learning.

1. The problem

   A site written for the wrong reader.

   The old site spoke to students. The people who book programs are the training and placement heads on each campus, so the whole site was rewritten for them.

Who stays in controlPlain files on the client's own hosting: they own the site outright, with no platform to rent.

Hover a marked term to decode itTap a marked term to decode it

• Rebuilt for a new reader

  The old site was written for students. I rewrote the whole thing for training and placement heads, the administrators who decide whether iSkew runs on their campus. Every page points to one action: request a proposal.

• Plain files, one small backend

  Seven pages in plain HTML, CSS and JavaScript, with no framework and no build step. The three forms post to a short PHP script that emails the client over authenticated SMTP and quietly drops bots with a honeypot field. A deploy script pushes changes to their hosting over FTPS.

• Warm, not corporate

  A red, ember and onyx identity on warm paper, set in Inter Tight, Inter and JetBrains Mono. The client's own logo and real photos stay, with the logo redrawn as a clean SVG set and a brand guidelines page to go with it.

• Motion that respects the reader

  Scroll reveals and a count-up on the stats, both of which switch off on their own when a visitor asks for reduced motion.

• Seven pages, one job

  Home, Programmes, About, How it works, Track record, Request a proposal and Become a trainer, each pointing to a proposal request.

• A proposal sized to the batch

  The proposal form asks for the college, the person's role and the number of students, so the first reply can already be specific.

• Every programme in one place

  Six training programmes, the iSkewPrep and iSkewPro practice platforms, and three test series, laid out by stage of the placement journey.

• Proof up front

  A wall of partner-college logos, count-up stats and a season-by-season track record, for readers who check before they reply.

• Answers before the call

  A seven-question FAQ written for placement teams, on the How it works page.

• Motion that steps aside

  Scroll reveals and count-ups switch off for anyone who has reduced motion turned on.

1. 01 · A placement head

   Planning next season.

   They request a proposal with their college, role and batch size, and it lands straight in the client's inbox.

2. 02 · A college that only needs practice

   Test series, nothing else.

   They ask for test-series access straight from the Programmes page.

3. 03 · A freelance trainer

   Joining the bench.

   They apply through Become a trainer, a form of its own.

4. 04 · A careful buyer

   Checking before replying.

   They read the track record and the partner wall before getting back to iSkew.