Hysen Labs
Open-source project
ricocc/ricoui-portfolio avatar
ricocc

ricoui-portfolio

Designer Portfolio & Blog Template

100 stars37 forksAstroLicense varies
01
DEEP OPEN-SOURCE ANALYSIS

Rico Portfolio, an Astro template for designers

A designer portfolio and blog template built on Astro, with a retro blue theme, dark and light modes, MDX posts, and a stack that includes Tailwind, AOS, and Matter.js.

02
DEEP OPEN-SOURCE ANALYSIS

What ships in the template

Rico Portfolio is a modern, high-performance designer portfolio website template built with Astro. The README lists a retro blue theme with a dark and light mode toggle, a fully responsive layout, animations built on AOS plus custom effects, an MDX blog system, portfolio pages, built in SEO and social media tags, and performance work like image optimization, code splitting, and lazy loading. It is positioned as a complete portfolio and blog setup rather than a bare starter.

03
DEEP OPEN-SOURCE ANALYSIS

The technology behind it

The stack is spelled out: Astro 5.15.4 as the framework, Tailwind CSS 4.1.14 for styling, AOS for animations, Matter.js as the physics engine, MDX for content, and TypeScript for type checking. Figma assets for programming stickers, bento cards, and social cards are listed as well. A recent update section says the project upgraded to Astro 5.15.4, is fully compliant with Astro v5.15 standards, moved content collections to the new Content Layer API, dropped legacy APIs, and optimized build and runtime performance.

04
DEEP OPEN-SOURCE ANALYSIS

Adding blog posts the modern way

Posts live as MDX files in the src/content/post directory. The project uses the Astro v5 Content Layer API with a glob loader for content collections, which the README says keeps compatibility with Astro v6. It calls out the modern choices explicitly: entry.id instead of the deprecated entry.slug, render(entry) instead of the deprecated render() method, import.meta.env instead of process.env, import.meta.glob() instead of Astro.glob(), and string typed getStaticPaths() params.

05
DEEP OPEN-SOURCE ANALYSIS

Configuration notes

There is one environment variable to worry about: PUBLIC SITE URL. If it is not set, the template falls back to a default placeholder domain, and while that will not cause errors, the README recommends setting the correct domain after deployment so the sitemap, RSS feed, and SEO meta tags work properly.

06
DEEP OPEN-SOURCE ANALYSIS

Author and credits

The README closes with the author, Rico, a web and UI designer who writes on ricoui.com and keeps contact details, an email, and social handles listed. Acknowledgments cover Astro, Tailwind CSS, and the developers who contributed. There is even a support note encouraging small contributions, framed as a way to keep the author going.

07
DEEP OPEN-SOURCE ANALYSIS

Editorial conclusion

The template is actively maintained: it recently moved to Astro 5.15.4 with legacy APIs dropped in favor of the new Content Layer API. Figma assets and contact details round out a README that also introduces the person behind it.

08
DEEP OPEN-SOURCE ANALYSIS

Official sources

09
Community notes

Community notes