Design categories before filter buttons
A filter cannot repair categories that overlap or mean different things to different editors.
Start with the items, not the animation. List every portfolio item and the decisions a visitor might make. A category is useful when it changes that decision and when editors can apply it consistently.
Test each proposed category against three questions. Can an editor explain the boundary in one sentence? Can two editors classify the same item the same way? Will a visitor understand the term without internal company knowledge?
Avoid mixing dimensions in one control. “Branding,” “2026,” and “Featured” describe type, date, and editorial priority. They can all be useful, but one row of equal buttons hides the difference. Separate filters or use a primary category with secondary metadata.
Keep the unfiltered view useful. Filters reduce a set; they should not be required to discover that the set exists. A visitor who arrives through a search result or with scripts disabled still needs titles, descriptions, and working item links.