I joined WorldLink Publishing Consortium as Chief Technology Officer in my first semester at the University of Lagos. What started as a project with my course advisor evolved into building a full academic publishing platform — from brand design to backend architecture. Here's how it happened.
WorldLink Publishing Consortium is an open-access academic publishing platform formed by a consortium of professors across several Nigerian universities. The platform hosts four peer-reviewed journals spanning Life Sciences & Environment, Physical & Engineering Sciences, Information Technology, and Humanity & Management Sciences.
When I joined, the consortium had a vision but no technical implementation. They needed a platform that could handle journal listings, archives, editorial board management, e-books, and a complete author submission flow. They needed someone who could translate academic publishing requirements into a functional digital platform.
The Beginning — From Course Advisor to CTO
The opportunity came through my course advisor at UNILAG, who also serves on the consortium's editorial leadership. We had been discussing my technical work — Tutorial Haven, LagSciPrep, and various hackathon projects — when he mentioned that WorldLink needed technical leadership.
The consortium had been operating with manual processes — email submissions, manual review tracking, PDF distribution. They needed a system that could automate these workflows while maintaining the academic rigor and peer review standards that researchers expect.
"Academic publishing doesn't need to be manual to be rigorous. Technology can enhance quality, not compromise it."
I started working on the platform in my first semester, balancing it with coursework and other projects. What began as a technical contribution evolved through several rounds of design, testing, and review — eventually leading to a formal CTO appointment and a seat on the editorial board.
What I Built — From Brand to Backend
My contributions spanned the full technical stack and beyond. This wasn't just implementing a spec — it was helping define what the platform should be.
-
🎨
Brand Identity Design — I designed the logo and color theme for the entire platform. The visual identity needed to communicate academic credibility while remaining modern and accessible. We went with a professional blue palette with clean typography.
-
🌐
Full Website Build — Built the complete platform from scratch: journal listings with search and filtering, archives organized by volume and issue, editorial board management system, e-books section, and the complete author submission flow with status tracking.
-
🗄️
Supabase Backend Architecture — Chose Supabase for content storage because of its real-time capabilities and PostgreSQL foundation. The database handles articles, journal covers, instructional documents, author profiles, and submission metadata with proper relational structure.
-
🔄
Iterative Testing Cycles — Worked directly with the editorial team through multiple rounds of testing and feedback. Each iteration refined the user experience based on actual academic workflows — from initial submission to peer review to final publication.
-
📝
Author Submission Flow — Built a comprehensive submission system that guides authors through the process: manuscript upload, metadata entry, author information, abstract submission, and file formatting checks with real-time validation.
-
👥
Editorial Board Management — Created a system for managing editorial board members across all four journals, with role-based access for editors, reviewers, and administrators.
The Technical Stack
For the backend, I used Django with Supabase as the database layer. Django's robust authentication and admin system provided a solid foundation, while Supabase gave us real-time capabilities and easy file storage for articles and journal covers.
The frontend is built with React for a responsive, modern user experience. We focused on making complex academic workflows feel simple — researchers shouldn't need technical expertise to submit their work.
One of the key technical challenges was handling PDF storage and delivery. Articles are published in PDF format only, and we needed a system that could handle uploads, storage, and efficient delivery without performance issues. Supabase's storage solution handled this elegantly.
"The best technical architecture is invisible. Users should focus on their research, not the platform."
What I Learned
A simple "submit article" flow actually involves multiple stakeholders: authors, editors, reviewers, and publishers. Each has different needs and access levels. Building a system that accommodates all these roles while maintaining security required careful planning and role-based access design.
Researchers trust established brands. A poorly designed platform signals low quality, regardless of the actual content. Investing in professional brand identity — logo, color scheme, typography — was essential for establishing credibility with authors and readers.
We went through several rounds of testing with actual editorial board members. What seemed intuitive to me as a developer wasn't always intuitive to academics who had been using manual processes for years. Their feedback was invaluable in shaping the final user experience.
Being appointed CTO meant taking ownership of the platform's technical future. It wasn't just about building the initial version — it was about planning for scalability, security, and long-term maintenance. The role carries real responsibility for the platform's success.
What's Next for WorldLink
WorldLink Publishing Consortium is now live at worldlinkpub.com, with all four journals actively publishing monthly issues. The platform is handling real submissions from researchers across Nigeria and beyond.
We're planning several enhancements: improved search functionality across all journals, citation tracking for published articles, and integration with academic indexing services. We're also exploring features like author dashboards and automated plagiarism checking.
"Open access publishing isn't just about removing paywalls — it's about removing barriers to knowledge dissemination entirely."
For me personally, this role has been invaluable experience working at the intersection of technology and academia. It's taught me how to translate complex domain requirements into functional software, how to work with diverse stakeholders, and how to take technical leadership responsibility.
If you're a researcher looking to publish or an institution interested in partnering with WorldLink, visit the platform. We're building for a future where African research has global visibility — and technology is making that possible.
Explore WorldLink Publishing Consortium
Visit the platform to browse journals, access research, or submit your work.
Visit WorldLink View All Projects