About Ben-Gurion University
Ben-Gurion University of the Negev, a public research university in Israel.
Ben-Gurion University already ran its public website on C# and Umbraco, hosted on AWS. Students and staff, however, still had to visit many separate systems to check a timetable, a grade or a tuition balance.
The university wanted a closed portal behind a login where each person sees only what applies to them. OSKI built it as a sister project to the public site.
What had to be solved
Personal content had to come from many sources, and editors had to stay in control of who sees what.
- Show content by role and attributes such as faculty, department and user type, across 8 criteria in total.
- Let editors restrict any single item to specific groups.
- Bring schedules, grades, payments, messages, events and Moodle into one place from separate student and faculty systems.
- Run alongside the public website without a second CMS or a second infrastructure to maintain.
How the team built it
The portal reuses the public site's C# and Umbraco backend and its AWS setup: Fargate, RDS, S3 and a load balancer. It runs on its own domain and root page, while editors work in the same back-office.
Each content item can be limited to user groups defined by 8 criteria. Editors choose the audience directly, and staff members can take on a student role to see the portal the way a student does.
The Angular single-page app pulls in day, week and month schedules, grades, course payments and assignments. Moodle opens through single sign-on. In total the portal talks to more than ten APIs.
An Angular app embedded in the Umbraco back-office lets editors open a page as a chosen user before publishing, so targeting mistakes are caught early.
What changed
Students and staff now start from one personal portal instead of a list of separate systems.
- Each user sees content matched to their role and attributes.
- The portal runs on infrastructure it shares with the public site.
- Custom back-office components give editors flexible control over content and audiences.
- Editors can check any page as a specific user before it goes live.
Inside the product
