{"id":15182,"date":"2026-09-23T14:57:18","date_gmt":"2026-09-23T11:57:18","guid":{"rendered":"https:\/\/creativethemes.com\/blocksy\/?p=15182"},"modified":"2026-09-23T14:59:41","modified_gmt":"2026-09-23T11:59:41","slug":"tainacan-plugin-case-study","status":"publish","type":"post","link":"https:\/\/creativethemes.com\/blocksy\/blog\/tainacan-plugin-case-study\/","title":{"rendered":"How Tainacan Built Digital Archives for Major Brazilian Cultural Institutes With Blocksy Theme"},"content":{"rendered":"\n

Shrinking developer team (8 to 2), growing feature requests, political instability, and funding cuts \u2013 these are some of the biggest challenges Mateus Machado Luna<\/a> and his team were facing while growing Tainacan<\/a> \u2013 their powerful digital archive management plugin.<\/p>\n\n\n\n

On top of all that, they were maintaining a full-fledged in-house theme called Tainacan Interface<\/a> that let Tainacan users customize the plugin\u2019s archive and single item templates.<\/p>\n\n\n\n

\n
\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n\n
\n
\n

\u201cI had to offer support to users, keep evolving the plugin, and still maintain the official theme. I only then realized how complicated it was to keep a good WordPress theme.<\/strong>

The amount of things you have to consider to tackle the multiple usage scenarios is no joke. From multiple layouts to SEO, A11Y, performance\u2026 I already had too much on my plate from the plugin side.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n<\/div>\n<\/div>\n\n\n\n

To refocus on plugin development, Mateus and his team began looking for a powerful external theme<\/strong> that isn’t just SEO-friendly, accessible, and fast, but also supports advanced customizations and integrates deeply with a custom post type-driven (CPT) plugin like Tainacan.<\/p>\n\n\n\n

\n\n\n\n

Finding a WordPress Theme With Advanced Customization & Deep Custom Post Types (CPT) Integration Capabilities<\/h2>\n\n\n\n

After trying several popular themes, Tainacan settled on the Blocksy Theme<\/a> because it\u2019s built on the foundations of<\/strong> WordPress Blocks<\/strong><\/a> \u2013 modular building units that allow very advanced customizations to posts, pages, and custom post types like archives as well as single item pages.<\/p>\n\n\n\n

Mateus recalls that the Gutenberg Editor had already launched, and blocks were becoming the foundational framework. The shift to full site editing would be slow, so they knew they had to rely on a block-based theme instead.<\/p>\n\n\n\n

\n

\u201cI wanted something that was clearly getting in shape for the Block Editor world. A theme that would not \u2018fight it,\u2019 while still offering its own way into the existing features of WordPress.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n\n\n\n

That\u2019s what Mateus and his team found in Blocksy \u2013 a theme built around blocks instead of treating them as an afterthought.<\/p>\n\n\n\n

\n

\u201cBlocksy’s version of the Customizer shines. It understands how the WordPress UI needs work, and it improves it hugely, without making the theme alien to Gutenberg Editor features such as the block-editor panel and<\/em> Blocksy\u2019s own blocks<\/em><\/a>. Blocksy’s vision of the Customizer has kept WordPress theming rock solid for a variety of projects we’ve been working on.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n\n\n\n

Blocksy\u2019s Customizer also came with built-in support for custom post types<\/a>, and since Tainacan archives are CPTs, this meant deep compatibility out of the box.<\/p>\n\n\n\n

Blocksy\u2019s Customizer supports layout modifications of custom post types.<\/figcaption><\/figure>\n\n\n\n

Mateus could use Blocksy\u2019s filters (hooks) to add new features and capabilities to allow customization of Tainacan\u2019s archive and single item pages.<\/p>\n\n\n\n

\n

\u201cThat was the turning point, because I realized they had prepared their code to be extended by others, which is part of the best practices of the WordPress philosophy. This made me realize it was worth spending time there.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n\n\n\n

Citing an example, Mateus says Tainacan lists categories and their values, and if a user wants the display to look more like a traditional WordPress post listing, he could just customize Blocksy\u2019s existing archive templates to achieve that design.<\/p>\n\n\n\n

Other reasons that sealed the deal between Tainacan and Blocksy were the theme\u2019s extreme attention to performance<\/a>, serious care with accessibility<\/a>, support for popular page builders (like Elementor), and theme developers really listening to users.<\/p>\n\n\n\n

\n\n\n\n

Building CPT-Driven Archive & Single Item Pages With Blocksy For Multiple Cultural Institutions<\/h2>\n\n\n\n

With the Blocksy Theme handling front-end customizations, Mateus and the Tainacan team went on to build CPT-driven, visually distinct, on-brand websites for several Brazilian cultural institutes (from museums to artist archives) without having to create custom themes for each<\/strong>.<\/p>\n\n\n\n

\n

\u201cI think the best way to see how Blocksy was part of the stack is by comparing the design in each project. The fact that<\/em> they look so different from one another is kinda our proof of success; it is why we wanted to make Tainacan in WordPress, so cultural institutions could express content the way it fits for them.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n\n\n\n

Museu Paulista<\/h3>\n\n\n\n

Mateus and his team created archive and single item pages for Museu Paulista<\/a> \u2013 one of Brazil’s most important museums. The museum already had a public-facing website at Museu do Ipiranga<\/a>. Tainacan had to replicate its layout to create pages<\/strong> for Paulista.<\/p>\n\n\n\n

Using Blocksy\u2019s custom CPT<\/a> options, Tainacan created a curated content-style landing page for the Indigenous Peoples of Brazil<\/a> and archive-style pages for the Iconographic Documents<\/a> and the Sticker Album of the 1932 Revolution<\/a>. Each archive page has advanced search, filters, dropdowns, and next\/previous navigation.<\/p>\n\n\n\n

\"iconographic\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
The archive page on Museu Paulista’s site, with Tainacan’s search, filters, and sorting styled to match the museum’s own layout.<\/figcaption><\/figure>\n\n\n\n

Ziraldo<\/h3>\n\n\n\n

The Tainacan team was commissioned to build archive pages for Ziraldo<\/a> \u2013 one of Brazil’s most relevant cartoonists, painters, and comic creators. They had to adhere to the client\u2019s proposed visual identity<\/strong>.<\/p>\n\n\n\n

The team achieved the desired result by using Tainacan and Blocksy hooks and feature extensions to create the Ziraldo Collection<\/a>. The pages have Tainacan\u2019s signature advanced search and filter options.<\/p>\n\n\n\n

They also built another archive page called Highlights<\/a>, displaying individual items.<\/p>\n\n\n\n

\"ziraldo\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
The archive page on Ziraldo, where Tainacan’s filters and search sit inside the institute’s own black-and-white visual identity.<\/figcaption><\/figure>\n\n\n\n

SESI Lab<\/h3>\n\n\n\n

Tainacan took on the challenge of building a digital archive for SESI Lab<\/a> \u2013 a museum dedicated to arts, science, and technology in Brazil. They have a vibrant website with interactive, colorful content, and the digital archive had to reflect that spirit<\/strong>. The pages Tainacan had to build required multiple shifting visual identities,<\/strong> including color palettes, layout style, typography, and narrative.<\/p>\n\n\n\n

Tainacan leaned on Blocksy for the visual aspects, and on Greenshift animation and page builder blocks to build the digital archive<\/a> and shifting pages like Biocanomia Amazonica<\/a> and The Future of Professions<\/a>.<\/p>\n\n\n\n

\"sesi\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
One of SESI Lab’s several archive sections \u2013 each built with its own distinct color palette and visual style.<\/figcaption><\/figure>\n\n\n\n

Other prominent clients Tainacan built full archive and single item pages with Blocksy include Museu Boulieu (a traditional museum website), Revista Zupi (an art magazine archive), Visite Museus (a Ministry of Culture platform where museums promote their events), and Bem Brasileiro (a digital repository for Brazil\u2019s historic and artistic heritage).<\/p>\n\n\n\n

\n\n\n\n

Building a Dedicated Integration Plugin (Tainacan Support for Blocksy) For Reusable, Site-Wide Customizations<\/h2>\n\n\n\n

Since Blocksy is built to be extended, Mateus and the Tainacan team used its hooks and filters to create an add-on plugin<\/strong> called Tainacan Support for Blocksy (TSB)<\/a>, giving Tainacan users advanced layout control<\/strong>.<\/p>\n\n\n\n

The plugin grew out of a recurring problem \u2013 the team had to keep rebuilding the same custom features in the Blocksy Child Theme for each client website. With TSB, the repeated work became a one-time custom setup that users could turn on and tweak.<\/p>\n\n\n\n

Before TSB, Tainacan users could access a few search components like filters, advanced search, and different viewing modes on full archive pages.<\/p>\n\n\n\n

After installing TSB, Tainacan users gained access to a whole lot of new settings like color palettes, header customization, search control display customization, and filter behavior.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
With TSB enabled, the WordPress Customizer offers customization options for every Tainacan archive page.<\/figcaption><\/figure>\n\n\n\n

Before TSB, Tainacan users could only add custom structured metadata (using a custom form) to single item pages.<\/p>\n\n\n\n

After installing TSB, Tainacan users gained granular control over how items are displayed on the page. Users could make changes to title appearance, add banner or feature images, set content wide, narrow, or with a sidebar, add next\/previous navigation, related items, comment sections, etc.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
With TSB enabled, the WordPress Customizer offers customization options for every Tainacan single item page.<\/figcaption><\/figure>\n\n\n\n

On top of all this, TSB lets users configure customizations for different screen sizes (desktop, tablet, mobile) on the same page.<\/p>\n\n\n\n

\n

\u201cI’ve had mostly positive feedback about the sites where I used this stack (Tainacan + TSB). When combined with a good visual identity, the theme really \u2018brings life\u2019 to digital archives that could before look a bit tedious or too technical.\u201d \u2013 Mateus Luna<\/em><\/p>\n<\/blockquote>\n\n\n\n

\n\n\n\n

Leaning on a Powerful Theme Like Blocksy Helps Boost Delivery & Reduces Updating Risks<\/h2>\n\n\n\n

Tainacan\u2019s answer to common CPT-plugin problems (teams stretched thin, in-house theme building and maintenance eating into plugin development) was to lean on a powerful, dependable theme like Blocksy, freeing up time to focus on core plugin development<\/strong>.<\/p>\n\n\n\n

Mateus points to two tangible benefits since adopting Blocksy in their tech stack: accelerated delivery speed and peace of mind!<\/p>\n\n\n\n

\u201cCertainly, the speed of delivery once<\/mark> I learned all the ways of customizing things. In terms of maintenance, I’ve never had any strong worries about upgrading<\/mark> the plugin and theme version, except with some migration needed from version 1.x to 2.x, but that was well communicated by the developers.\u201d<\/em><\/p>\u2013 Mateus Luna<\/em><\/cite><\/blockquote><\/figure>\n\n\n\n

\n
Give Blocksy a Try \u2192<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Shrinking developer team (8 to 2), growing feature requests, political instability, and funding cuts \u2013 these are some of the biggest challenges Mateus Machado Luna and his team were facing while growing Tainacan \u2013 their powerful digital archive management plugin. On top of all that, they were maintaining a full-fledged in-house theme called Tainacan Interface […]<\/p>\n","protected":false},"author":63,"featured_media":15212,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[30],"tags":[],"class_list":["post-15182","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-resources"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":8}},"acf":[],"_links":{"self":[{"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/posts\/15182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/users\/63"}],"replies":[{"embeddable":true,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/comments?post=15182"}],"version-history":[{"count":15,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/posts\/15182\/revisions"}],"predecessor-version":[{"id":15218,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/posts\/15182\/revisions\/15218"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/media\/15212"}],"wp:attachment":[{"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/media?parent=15182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/categories?post=15182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/creativethemes.com\/blocksy\/wp-json\/wp\/v2\/tags?post=15182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}