Helpdesk
Network, email, portal or website fault — Contact the ICT Helpdesk

SLUK-DPF

Digital Platform Framework

The October 2025 standard for SLUK websites, portals and connected systems.

SLUK-DPF

The University digital standard

The SLUK Digital Platform Framework (also called SLUK-DPF) is the University’s guideline for its online ecosystem. It was developed by the Directorate of ICT in October 2025, reviewed with faculty and department structures in version 1.1, and recorded as finally reviewed and approved by University Management in version 1.2.

Download the PDF

Document record

S/NData elementValue
1TitleSLUK Digital Platform Framework
2Alternative titleSLUK-DPF
3Version in the metadata blockVersion 1.0; October 2025
4PublisherSule Lamido University Kafin Hausa, Directorate of ICT
5TypeFramework
6Enforcement categoryRecommended
7OwnerVice-Chancellor’s Office and the Directorate of ICT
8AudienceManagement, faculties, departments, divisions, students, staff, alumni and external partners
9CopyrightSule Lamido University Kafin Hausa
10FormatPDF
11SubjectDigital infrastructure and online presence

Change history

AuthorVersionReleaseChange
SLUK ICT Directorate1.0October 2025Draft framework developed
ICT Directorate1.1October 2025Faculty and department structures incorporated
SLUK Management1.2October 2025Final review and approval

File properties of the PDF list the author as Ahmad Abubakar, created with Microsoft PowerPoint 2010 on 10 October 2025. The slides themselves attribute the work to the Directorate and to University Management.

Preamble and authority

The University wrote the framework because digital infrastructure now sits inside academic excellence and institutional visibility. It sets the structure, standards and guidelines for the main website, for faculties, centres, schools, directorates, divisions, academic and non-academic departments and units, and for associated portals.

The aim is a single digital presence: easier to use, easier to find, stronger for ranking, and able to grow. The authority line states that Management of Sule Lamido University Kafin Hausa issued the framework, and that it is the official guideline to be adopted across the University.

Scope

  1. Websites of all faculties, schools, centres, directorates and divisions.
  2. The main SLUK website, as the University-wide gateway.
  3. Links to the existing student and staff portals.
  4. Websites of all academic and non-academic departments.
  5. Integration with academic and administrative systems, including the e-Library, the learning management system and payments.

The main University website, as specified, is expected to carry highlights and quick links; an About section (location, vision and mission, core values, leadership, news, strategic plan, calendar, SDGs, facts and figures, financial statement); academics; admissions; research and innovation; the library; TETFund interventions; centres and directorates, including this Directorate; student and staff portals; support services; enterprise and campus life; news and events; contact; and a footer for quick links, FAQ and policies.

The Directorate of ICT is named among Centres and Directorates, alongside Academic Planning, Physical Planning and Maintenance Services, and Procurement.

Definitions used in the framework

  • Website framework. The structured design that sets content hierarchy, navigation and standards across SLUK websites.
  • Faculty, directorate, school or centre website. A platform for that level’s information, programmes, research and administration.
  • Department website. A unit site for activities, academic programmes and research focus.
  • Student portal. A secure access point for student records, e-learning, fee payments and academic services.
  • Staff portal. A secure platform for staff services, human-resource records and academic resources.

Why a single framework was needed

The document describes the University’s online presence as limited, without functioning websites across faculties, centres, departments, schools, divisions and directorates. It lists five pressures: fragmentation of design, weak scalability, poor visibility of research and achievements, gaps when moving between the main site and units, and a maintenance burden on ICT from many different platforms.

The expected gains are a consistent look, navigation that joins the main site to faculties, departments, centres, divisions and schools, clearer routes to admissions and research, one place for news and events, and cheaper upkeep because the tools are shared.

Strategic impact is described under five headings: academic excellence, reputation and ranking, student and staff experience, operational efficiency, and future readiness.

What each kind of site must contain

Directorates and divisions

A directorate site publishes the head of office, services, downloads, history, objectives, vision, mission, structure, units, contact, management, staff, news, and events and training.

Faculties and schools

Dean’s message and profile, academic programmes, research, about, departments, publications, alumni, contact, faculty management, staff directory, news, and student resources such as handbooks, timetables, guidelines and course structures.

Academic departments

The same pattern at department level: Head of Department, programmes, research, publications, alumni, contact, management, staff, news and student resources.

Centres and research institutes

Director’s office, programmes where relevant, research themes, about, projects and publications, facilities, contact, management, staff, news, partnerships, and events and training.

Journals

The framework also specifies a journals platform: public journal home, user roles, manuscript submission, editorial workflow, peer review, issues, indexing and metadata export, search, notifications, metrics, payment of article charges, and system administration. That platform is a separate product. This Directorate is responsible for the technical environment, not for editing journals.

How a unit asks for a website →

Review and amendments

  • The framework is reviewed every two years by the Directorate with stakeholders.
  • Amendments may follow a change in institutional priorities, new technology, feedback, or national and global digital policy.
  • The Directorate drafts revisions. The ICT Development Committee reviews them. The Vice-Chancellor’s Office endorses them. University Management ratifies them where required.
  • Every change is written into the change-history log: author, version, date and description.
  • Updated versions are published on the main University website and circulated to faculties, departments and relevant units.

Monitoring uses four instruments named in the document: key performance indicators (usage, content updates, satisfaction), annual reviews by the Directorate, reports to the Vice-Chancellor’s Office and University Management, and feedback from surveys, analytics and focus groups.

Current ICT projects are listed on the projects page.