All projects

Case study · SmartSchool Education Ltd

SmartSchool Corporate Website

Frontend Developer · 2026

The corporate website of SmartSchool Education, an Indian EdTech company: a V2 redesign with a new homepage, brand pages, an investor relations page and a newsroom of 60 stories.

Page Files
21
Newsroom Stories
60
Widths Checked
4

Project overview

Homepage

SmartSchool Education makes classroom hardware, AI teaching tools and K-12 digital content for schools, colleges and coaching institutes, sold through two brands, StudynLearn and SNL. This is the V2 redesign of its corporate website: a new homepage, a clearer menu, company pages, an investor relations page and a newsroom. The earlier site is still the one at smartschoolonline.in; V2 is being built and previewed on its own branch. I designed and built V2 as the frontend developer. The products and the company are not mine: the site presents them.

Project type
Corporate website redesign (V2)
Company
SmartSchool Education Ltd
My role
Frontend Developer: design and build of V2
Timeline
Aug to Oct 2026, ongoing
Status
V2 on a preview branch; live site is the earlier build
Live site
smartschoolonline.in

Tools Used

Technologies, platforms, and tools used to design, develop, and deliver this project.

  • PHP, a server-side language
  • HTML5, the markup language of web pages
  • CSS3, the styling language of web pages
  • JavaScript, the language of the web
  • Vercel, hosting and deployment

The challenge

A company that sells through two brands, StudynLearn and SNL, needs a corporate site that explains the whole company without looking like a product catalogue. The earlier site mixed pages inherited from StudynLearn, so the parent company was hard to see.

  • The business objective

    • Show SmartSchool Education as the company behind two brands.
    • Send institutional buyers to one clear action: Book a Demo.
    • Give investors, press and job seekers a proper place to look.
    • Keep the two brands, StudynLearn and SNL, visible without hiding the company above them.
  • The earlier site

    • It mixed in pages inherited from StudynLearn.
    • It risked reading like a product catalogue instead of a company.
    • The parent company was hard to see behind the two brand names.
    • Several facts conflicted between pages, such as the customer count and founding year.
  • The constraints

    • Plain PHP on Vercel, no framework and no database.
    • Content the company has not approved cannot be shown: figures, documents, names.
    • The header, phone drawer and footer must always agree, so all menus come from one data file.
    • Every page has to work at phone, tablet and desktop widths.
  • What I wanted to improve

    • Make the company, its brands and the demo action clear on the first screen.
    • Use one design across every page.
    • Build the menu around the company, not the product list.
    • Keep Brands, Clients, Company, Blogs and Investor Relations easy to reach.
Frontend Development Lifecycle · Step 1 of 5

From brief to technical choices

The brief became a few firm technical rules.

  • Keep it plain PHP

    No framework or database: each page is one PHP file with shared header and footer parts. It deploys as one serverless function behind clean web addresses.

  • Honest content

    Where the company has not approved a figure or document, the page shows that it is not published instead of a placeholder.

  • Page-level styles

    The dev team asked for each page to carry its own styles. A build script trims each page's CSS to only what it uses.

Frontend Development Lifecycle · Step 2 of 5

How it's built

  • 21

    Page files

  • 60

    Newsroom stories

  • 16

    Investor sections

  • 4

    Widths checked

  • One design system

    Colors, spacing and type are shared tokens. A single change to the tokens turned the whole site dark while the homepage hero stayed light.

  • One menu file

    The header, the phone drawer and the footer render from one data file, so adding a link is a one-line edit.

  • One routing function

    Every page goes through one gateway file, because the hosting plan limits how many functions a project may have.

Frontend Development Lifecycle · Step 3 of 5

Key features

  • Investor Relations

    Sixteen sections with a sticky section bar. Documents appear only if the file exists, with filters and search once there are some. Financial figures show only when approved.

  • Newsroom

    Listing with search, category and year filters and pagination, plus one template for every story. Each story keeps its old address so existing links still work.

  • Blogs

    The latest StudynLearn posts, fetched and cached for an hour.

  • Responsive homepage

    The desktop and phone layouts are composed separately: the hero text comes first on a phone, and the logo strip becomes a swipeable row.

  • Cookie choice and demo contact

    A consent banner with Accept and Decline, and a contact form that opens a ready-made WhatsApp message.

Frontend Development Lifecycle · Step 4 of 5

Testing and optimization

What was checked. All of it was done by hand or with a script on my machine.

  • Layouts at 390, 768, 1024 and 1440 pixels

    Checked for sideways scrolling, a working phone menu and missing images. The checks found a hidden overlay that was blocking clicks, which was fixed.

  • Accessibility scan

    An automated WCAG 2.2 A and AA scan (axe) came back clean at 1440 and 390 on the homepage, about, careers, clients, downloads and newsroom pages.

  • Keyboard and motion

    Visible focus rings, menus that close on Escape, scrolling areas reachable by keyboard, and a hero video that pauses when reduced motion is on.

Not measured: Lighthouse scores, Core Web Vitals, traffic or conversions. Fonts are stand-ins for the licensed brand fonts, which I do not have.

Frontend Development Lifecycle · Step 5 of 5

SEO

What the pages carry for search engines.

  • Per-page metadata

    Each page sets its own title, description, canonical link, Open Graph and structured data. The homepage describes the company and its two brands.

  • Newsroom sitemap

    A sitemap lists the newsroom and every story with its real update date.

Open items: the canonical domain is split between two sites on older pages, and there is no robots file or site-wide sitemap yet. These wait on a decision from the company.

See the Design Lifecycle: how the experience was structured, the visual direction and the final screens.

Results

What changed for visitors

  • The company, its two brands and the Book a Demo action are visible from the first screen.
  • Investors and journalists have their own pages instead of links to the old site.
  • A visitor sees one consistent look and menu on every page.

No analytics, speed or lead numbers exist for V2, so none are claimed. V2 is not live: smartschoolonline.in still serves the earlier build.

What I learned

  • What I learned

    • A single menu data file saves more time than any visual polish.
    • An honest empty state is better than a made-up number on an investor page.
    • Fix overflow at its source: hiding it on the page only masks the problem.
    • Large visual changes are safest through shared tokens, not page-by-page edits.

My part

  • What I built

    • The V2 design and frontend: homepage, menu and footer, investor relations, newsroom and the dark restyle.
    • The checks at four widths and the accessibility scan.
  • Provided by SmartSchool Education

    • The company, its brands, products, logos, photographs and news stories.
    • The earlier site and its content.
    • Decisions on facts such as customer counts and the legal name.

On everyscreen

The portfolio home page on an iPhone

iPhone

The portfolio home page on a tablet

Tablet

The portfolio home page on an Android phone

Android

You may also like

EGN ConnectX screenshot

The official website for India's big education leadership summit. People can register, book stalls and nominate for awards, and explore the venue in an interactive 3D floor plan. Over 20,000 visitors are expected.

StudynLearn screenshot

A smart classroom website: smart boards from 55 to 98 inches, AI teaching software and a national Olympiad. I built 21 pages on one design and cut the video and photo weight by about half.