Skip to main content
Maheswar Barrenkala

Maheswar Barrenkala

Start a Conversation

05 / UX engineering to implementation

ITU Student Portal & Digital Experience Redesign

A research-led university digital-experience redesign combining information architecture, responsive frontend and CMS implementation, accessibility, and student-support workflows.

Explore verified task pathsView current ITU Student Hub
Current ITU contextStudent Hub · captured August 2026
Current ITU Student Hub showing the page title, enrollment guidance, and tools for Class Schedule, My ITU, EMS, and Catalog.
Current destinationUniversity Registrar · mobile
Current ITU University Registrar page on a narrow viewport, showing the ITU header, page title, and registrar mission.
Verified public pathStudent HubUniversity Registrar
Current ITU organization context · captured August 2026. These present-day screens are not presented as proof of Maheswar's historical implementation.Current site context
50%increase in engagementUser-confirmed ITU outcome; contributed to through the portal work
40%reduction in administrative workloadUser-confirmed ITU outcome; contributed to through the portal work

ITU-specific outcomes. Measurement period, baseline, and methodology are not publicly documented.

Real current-site evidence

Public context reveals the information landscape.

The live Student Hub, Academics, and Registrar views show how public destinations are grouped today. I use them to explain the institutional context, then separate that context from my confirmed historical UX and implementation contribution.

Current organization context / captured August 2026

Inspect the present-day information landscape.

Three selected current-site views make the institution's public information structure inspectable. They are context, not historical authorship evidence.

Current organization contextCurrent ITU Student Hub
Current ITU Student Hub showing the page title, enrollment guidance, and tools for Class Schedule, My ITU, EMS, and Catalog.
Student Hub → task and tool grouping

The current hub groups direct destinations such as Class Schedule, My ITU, EMS, and Catalog around recognizable student tasks.

Current ITU Student Hub selected. Current organization context captured August 2026.

Verified current labels used in the explanation

  • Academic planningAcademic Advising · Class Schedule · Catalog
  • RecordsUniversity Registrar · Forms
  • International supportISO · OPT
  • Institutional informationAcademics · Admissions & Finance

Open verified public context

View current ITU site Current ITU Student Hub Open Academics Open Admissions

One source boundary applies to this entire set: the links and screenshots establish current organization context, not authorship of every current ITU element.

Responsive experience walkthrough

Find the next step by task, not department.

This Signal Ledger interface arranges verified current ITU labels into inspectable task paths. It is not a historical ITU screen, collects no data, and calls no external API.

Signal Ledger / verified ITU pathsResponsive experience walkthrough
Verified current labels

Plan my studies

Connect a planning need to the current advising and course-information destinations.

  1. 01Student Hub
  2. 02Academic Advising
  3. 03Class Schedule
  4. 04Catalog

Plan my studies path selected. 4 steps shown.

As IT Designer & Developer and Student Body President, I connected student discovery to information architecture, responsive frontend and CMS changes, accessibility, coordination, and maintenance. UX decisions continued into implementation across Academic, Admissions, Student Body and Student Services, and IT functions.

Research became implementable requirements

Interviews, surveys, usability review, personas, journey mapping, and student/stakeholder input exposed fragmented information and administrative handoffs. Requirements: group related content, clarify navigation, prioritize small screens, and route inquiries clearly. No participant count or study methodology is published.

ITU / research to requirements
Research-to-requirements flow based on confirmed methods; no sample size or participant quotation is claimed.System flowAlt-text intent: Interviews, surveys, usability review, personas, and journey mapping inform requirements for content grouping, navigation clarity, responsive priority, and inquiry routing.

Information architecture organized around student intent

I mapped academic information, admissions, student services, international-student information, and IT support into task paths that respected institutional ownership without making students decode it before finding help.

ITU / information architecture
Information-architecture comparison based on confirmed research and project work.System flowAlt-text intent: A documented department-led problem state is reorganized through a tasks-before-departments information architecture into student-facing pathways.

UX decisions continued into the frontend

My contribution continued through Figma, HTML, CSS, JavaScript, responsive layouts, navigation changes, CMS content, and refinement. Navigation hierarchy shaped responsive behavior; content groups became reusable page structure; accessibility priorities informed semantics, focus, readability, and reflow.

ITU / UX to implementation
Implementation map based on the confirmed frontend, accessibility, CMS, and maintenance work.System flowAlt-text intent: Navigation hierarchy, content grouping, accessibility priorities, and content operations map to responsive frontend, semantic behavior, CMS updates, and maintained product outcomes.

Across desktop, tablet, and mobile, the primary task and destination moved ahead of secondary context instead of compressing the desktop layout. The interactive explanation above makes that decision inspectable with verified current ITU labels, without presenting it as historical ITU UI.

ITU / responsive information priority
Responsive information flow using verified current ITU labels; not a historical interface reproduction.System flowAlt-text intent: Verified ITU destinations move from parallel wide-screen context into a task-first narrow-screen reading order.

Accessibility and content operations were product constraints

Semantic structure, keyboard access, visible focus, readable hierarchy, and reflow were implementation priorities, not a certification claim. CMS work and maintenance kept institutional content usable.

Outcomes stayed tied to ITU

The work contributed to a 50% engagement increase and 40% reduction in administrative workload in the ITU context. These outcomes remain separate from reconstructed UI; their period, baseline, and methodology are not publicly documented.

ITU / contextual outcomes
Registry-backed ITU outcomes shown with contribution context; no measurement method or period is inferred.System flowAlt-text intent: ITU outcomes show a 50 percent increase in engagement and a 40 percent reduction in administrative workload, each described as a contributed result in institutional context.

Ownership, coordination, and tradeoffs

I owned research synthesis, information architecture, frontend and CMS implementation, accessibility-informed refinement, and maintenance. Student leadership supplied context while I coordinated with institutional teams; engineering remained the center of the work.

Evidence and next validation

The current ITU website provides organization context rather than attribution for historical screens or components. Dated captures remain labeled as current context; programmatic explanations use verified labels or neutral structural language rather than invented university data.

The next evidence step is a reviewed historical-artifact set mapped to the IA and frontend changes, plus a confirmed measurement period for the outcomes.