Role

Product Design

Client

YDUQS (Education)

Multibrand Blog

Redesign of multi-brand blogs and planning for migration to a new CMS

Main Project Image
Main Project Image
Main Project Image

Yduqs is a company that owns several higher education brands. A few years ago, a major project was undertaken to create a multi-brand platform for the websites of these institutions under a single Content Management System (CMS).

The project was successful, which opened the door for a similar initiative — this time focused on integrating the blogs of these institutions.

In this new project, I led all stages and coordinated with multiple teams to make it happen.

All posts from the current blogs need to be migrated to the new version. With that in mind, the new structure must be capable of accommodating all content, including text, images, multimedia, and other relevant information.

Large Project Gallery Image #4
Large Project Gallery Image #4
Large Project Gallery Image #4

Premises

Premises

01

01

01

Security

Security

Security

The blogs were hosted on WordPress, which resulted in a lack of security and several attempted breaches over the years.

02

02

02

Consistency

Consistency

Consistency

Each blog was developed by a different team, which meant that while the institutional portals were similar, the blogs were inconsistent and often outdated.

03

03

03

Usage

Usage

Usage

The current CMS was developed based on the specific needs of each brand; however, the blogs did not benefit from the new user experience introduced in the previous project.

04

04

04

Multibrand Support

Multibrand Support

Multibrand Support

The new layout should be adaptable across different brands, while preserving the unique look and feel of each individual brand.

Steps of the process

Blog Lifecycle

Project Documentation: A document was created in collaboration with the business team, outlining all project expectations, including goals, requirements, functionalities, and scope.

Benchmarking: The analysis included a review of current blogs, competitors, and blogs from other industries, with the aim of identifying features to be incorporated into the new blog.

MVP Scope: It was decided to launch the blog as an MVP. I coordinated with the business, design, development, and SEO teams to define the functionalities that would be included in the first iteration. To prioritize these, I used the MoSCoW method.

Refinement: With the previous steps completed, it was time to refine the product. The blog was divided into different page types, each further subdivided into sections, which were designed and reviewed with the design team during a series of design critiques. Once everything was finalized and approved by the involved teams, it was handed over to development.

Result

Launching the MVP

The new layout was built using components from the company’s internal design system, which wasn’t possible in the previous project.


I also created a few specific team components to address specific needs and improve overall consistency.

Blog Home

Before

After

Post Page

Before

After

Takeaways

Takeaways

Cross-team collaboration

The involvement of all teams from the beginning was crucial to the development of the project. In larger companies, it's often challenging to align all the necessary parties early on, which can lead to issues during development and result in rework.

Past, present and future

All stages of the blog’s lifecycle had to be taken into consideration. Content migration was a major focus during feature development, ensuring a smooth transition from the existing platform. Planning also accounted for future stages—beyond the MVP, the second and third releases were already outlined.