Design
The first version of the wuruwuru website was a one-pager with a checkered background. Most of the links opened external sites, and the most exciting thing about it was a moving cursor.
Our first exploration was a highly visual site similar to Instagram stories, displaying images and short intros for all our projects. While this was an interesting approach it hindered our ability to give due credit to contributors and didn't provide a clear browsing experience.
We scrapped the initial design as it didn't align with our objectives, and went with a more conventional and distinctly clear version. The simpler design had three main pages:
- a projects page to showcase all our projects,
- a people page to highlight the creators we collaborate with, and
- an about page to explain what the studio’s mission.
On the "People" page, our aim was to present concise bios of the creatives, outline the projects they were involved in, and provide contact information. To accomplish this, we needed to implement a dynamic Content Management System (CMS), so we brought in Tomi and Nifemi for the website development.
Development
They utilized a framework called Astro to build the website due to its lightning-fast delivery capabilities. Within the Astro setup, dynamic content is delivered through JSON files embedded in the codebase. Additionally, they employed GitHub for version control and used Netlify for hosting services.
Content
As they built the site, Ope and I curated the content. He handled copywriting, while I distributed a form to collaborators to gather information for the 'People' page. Anticipating that not everyone would respond promptly, I looked all over the internet to gather any available information about them so we could keep moving.
After configuring the local development servers, I took over the task of updating the website's information. I individually contacted the creatives to review their profiles, and made necessary corrections. Subsequently, I applied the updates to the live site by initiating pull requests on GitHub.
Analytics
The previous website didn’t have any analytics software installed, so we had no idea how many people visited the site. To address this, we opted for a different approach in the new version, incorporating Plausible to track website traffic.