Tribuna Jirafa: redesign with a CMS for editing news.

01Problem and context

The media outlet published news and articles for the pharmaceutical industry. The client needed to add, edit and remove content without depending on the developer for every change.

02Diagnosis

There is no technical report or prior measurement in the archive. The documented decision is to redesign the website with a CMS framework.

03Technical solution

Redesign with a CMS framework. Content editing was the priority: adding, editing and removing news without touching code.

The documented brief was, in the words of the archive, “Website redesign using a CMS framework to make it easy for the user to add, modify and remove content”.

Rejected alternatives and risks: not documented in the archive. No list of tools, plugins or a specific platform is published because the archive does not name them.

04Evidence

The available evidence is the original URL and the archive screenshot. There are no traffic, performance or ranking metrics with source and date; none are published.

• View the original website ↗(opens in a new tab) → The original URL may have changed: its current state is not verified from the prototype.
• View the archive screenshot → 3:2 image in the header of this page, taken from the 2015–2018 archive.

Gallery · example

Crops of the archive screenshot to preview the component. They will be replaced with the case’s own screenshots.

05Results and limitations

Documented result: the client could add, edit and remove content.

Limitations: no traffic, SEO or performance improvement is attributed; no metrics are published; the current state of the URL is not verified from the prototype.

06Permission and confidentiality

Name, URL and screenshot already appear in the public 2015–2018 archive. No metrics or private data are published.

Authorization for this current publication: pending confirmation. The archive does not record who authorized the mention, so it is not attributed to any person.

07Services and applied technologies

The brief was resolved as a redesign with a CMS framework, on the vendor’s own code. These are the site pages where you can see how this type of brief is handled:

• Custom web development → Projects that start from scratch or that need to be rebuilt entirely.
• Support and maintenance → Updates, backups, security and support, with the scope in writing.
• Technologies and levels → What stack we work with and at what level: specialty, builders and project capacity.

Case technology

CMS. The archive does not name a specific CMS, so none is added by attribution, and no link is made to a technology sheet that does not document this case.