PortuguêsGitHub

Changelog

Everything that went into Rubrica.

What changed in each version of Rubrica (core, themes and the create-rubrica CLI). Details for each one are in the release notes. To update a v2 project, see Updating Rubrica; to leave v1, Migrating from v1.

2.3.0

LatestRelease notes

The case body is now made of blocks, with brand and media blocks and the option to dress a case in the client's look. Everything is optional: a case in the old format keeps showing up. Theme contract 1.4.

New

  • Case in blocks: the project body uses the same blocks as pages (blocks on the project), without hero, contato and cases, starting at h2. In the panel, a block editor and a case preview right in the project.
  • Brand and media blocks: before and after (with a sliding comparison), color palette, typography, brand variations and images (grid, mosaic or carousel, with GIF for short animations). YouTube and Vimeo video gains chapters.
  • A case in the client's look: the client's colors (light and dark) and title font only inside the case (brand on the project). The minimum contrast is checked on save (4.5:1 for text, 3:1 for the accent) and the font is downloaded at build time.
  • Blocks: contexts (page, case or both) and the color field.
  • Themes: the case template receives blocks and brand, and the 14 themes get the case-in-blocks template and CSS.
  • MCP: the block_* tools accept project (a case body), blocks_catalog filters by context and the project's brand is validated before saving.
  • create-rubrica: the v1 converter carries cases over as blocks and update lists the data migration.

If you are updating

  • Data migration: projects-sections-to-blocks converts content and sections into texto blocks. update runs it on development; on production, after publishing the backend: npx convex run --prod rubrica/collections:migrateSectionsToBlocks (idempotent).
  • Third-party and ejected themes: sections and content are deprecated. The case template must show blocks. See Creating a theme.

2.2.0

Release notes

The proposal, the acceptance page and the contract PDF are back to everything v1 had, with a new look in the theme's colors. Nothing changes for proposals that already set their own payment options and cancellation policy.

New

  • Proposal: an introduction letter at the top (UI text proposal.intro, editable under Texts), a lead text and badge for the investment, a footer with the site name and a new card layout with icons, a timeline and the investment highlighted.
  • v1 defaults: with no payment options, the proposal and the contract show the default ones, calculated from the final price (PIX with 10% off, 50/50, credit card in 3 interest-free installments and in 12). With no cancellation policy, the default one applies, with jurisdiction in the city of the site's address. Both are UI texts (proposal.pay.* and proposal.rescissionDefault).
  • Acceptance: the contract is shown open, with the reading notice and the confirmations; the acceptance clause gets a heading. The signature is required again, with the option to use the typed name for people who can't draw.
  • Contract PDF: the provider's header, a title band, a signature box with line and caption, technical evidence (hash, IP, browser, version, reference and UTC time), a legal footer and A4 pages.

Fixes

  • Every proposal has a contract: without a custom template, or with the templates plugin off, the default template applies.
  • Cancellation policy in the admin: no longer required (empty uses the default) and accepts long texts (previously 800 characters).
  • migrar: carries the v1 proposal introduction.

2.1.0

Release notes

The padrao and cyberpunk themes now match the v1 layout page by page, and the migrar converter carries what was missing from the v1 data. Everything new is optional: projects that don't use the new fields see no change. Theme contract 1.3.

New

  • Contact: the wizard takes topics with their own steps (choice, text, contact details) and opens in the theme's contact window, on any page. The admin shows each request's answers by name.
  • Blog: a carousel of featured posts, search by title, summary and tags, an RSS button and v1-style cards (showFeatured and showSearch on the posts block).
  • Post: back to the blog, tags, subtitle, an author card and the related case study.
  • Portfolio and case study: a category filter and cards with tags, a highlight number and a button; case numbers with icons (metrics on projects), screenshots in a carousel with an enlarged view, and the closing invitation with the next case study.
  • About, testimonials and 404: the personal text, a day-to-day mosaic (span on the photos), the FAQ in one card, testimonials grouped by category with a link to their page, and the terminal 404.
  • Shell: a more compact desktop sidebar and a close button on the mobile drawer.

Fixes

  • Post dates in the site's time zone: a post published at night in Brazil no longer shows the next day's date. Reading time rounds up, as in v1.
  • Projects linked with link: (e.g. create --local): the icons on case study pages no longer break React in the dev server.

2.0.0

Release notes

v2: Rubrica stops being a template copied into your project and becomes a core in a package, with themes and two site lines (personal and company). Updating becomes bumping a package version.

Coming from 1.x: it is not an update, it is a migration. Run npx create-rubrica@latest migrar in a project on 1.13.1, with a clean git state: it creates the rubrica-v2 branch, swaps the code, converts the data and lists what you customized. Nothing is written to Convex: the import goes into a new development database, and production only with your "ok". Guide: Migrating from v1. v1 keeps receiving bug and security fixes for 6 months on the v1 branch, which also holds its documentation.

Security

Three v1 flaws are fixed in v2. v1 does not get a fix for them: if you have a v1 site with proposals, the fix is to migrate to v2.

  • A password-protected proposal no longer leaks its content through the API. In v1, whoever called the proposal's public query received the content without typing the password: only the page hid it. Now, without a valid session, the API returns only the state ("locked"), without the content.
  • The wrong-password limit now really blocks. A wrong attempt threw an error, which undid the attempt count, so the limit was never reached. Now the attempt is recorded and, past the limit, the proposal answers TOO_MANY_ATTEMPTS.
  • A single default contract template. v1 had two default templates (one in code and one in the database), and a proposal could use one different from what the panel showed. In v2 there is just one, the database one (marked as default); the text shipped in code only serves to create it when none exists yet.

What changed in the architecture

  • Core in a package. @rubrica/core brings the site (Astro), the panel (React), the backend (Convex) and the MCP. Your project keeps only configuration, own blocks and ejected components. The project's convex/ becomes one-line files that re-export the core's backend.
  • Static site in Astro. No more makeshift prerendering and SPA: pages come out as HTML, with almost no JavaScript (only the interactive parts become islands). Images and fonts go through Astro's own handling, fonts are served by the site itself, and the body and heading fonts are preloaded.
  • Pages made of blocks. Each page is a list of typed blocks, with a live preview in the panel. The catalog has 21 blocks (15 common, 1 personal and 5 company), and the catalog is generated from the code in Blocks. Four are new: video (YouTube or Vimeo; a light thumbnail, with the player loading only after the click), embed (a calendar, form, map or player, only from allowed providers; the generated CSP already includes them), timeline and plan comparison. You can create new pages in the panel. The block contract is at 1.2: a block definition can carry validate (rules across fields), sample (an example for the showcase), enhances (an island that improves the block) and guidance (usage guidance).
  • Two site lines. pessoal (personal, the portfolio as always) and empresa (company: about us, services, pricing, team, cases, contact). The company line adds the plans collection, the team and the company data (which build the Organization/LocalBusiness structured data). The scope is explicit: the company line is for those who sell a service and get quote requests, and it is not a store (no product catalog, cart or stock). The company page recipes use the timeline and the plan comparison. See Company site.
  • 14 themes, 15 color schemes. The 13 v1 layouts become themes (same names), plus padrao. Each theme is a @rubrica/theme-<name> package. Any scheme works in any theme, and each theme or site can have an optional texture over the page (grain, paper or scanlines). All pass the same test battery (testar-tema: axe, single h1, complete <head>, JavaScript limit, Lighthouse).
  • Several languages. The language list is configurable and the main one is your choice (no URL prefix). Content without a translation simply doesn't exist in that language: no empty pages or internal 404s.
  • Agency and client roles. root is the agency, admin the site owner, and there is a new comercial role (proposals, contracts, checkouts, contacts and plans).
  • Users. The root resets someone's password in the panel, with no email: a temporary password comes out, shown only once, the person's sessions are dropped and changing it is mandatory on the next sign-in. Users can also be suspended and reactivated (the role is kept). The backend enforces the change of the temporary password: until it is changed, neither the panel, nor the MCP, nor the API work for that account.
  • Proposals, acceptance and payment. Turned-on plugins generate public pages: the proposal (with a password, the contract, acceptance with an optional signature, and PDF), the acceptance, the checkout (PIX, bank slip or card, through Asaas) and the payment completed page. Each route becomes a static page per language, and the project generates the rewrites for Vercel, Netlify and Cloudflare Pages.
  • WhatsApp and announcement bar. In the site settings, an optional floating WhatsApp button and an announcement bar with start and end dates (evaluated at build). The whatsapp: address works in any button or link, and the number goes into the JSON-LD as contactPoint. migrar brings the number v1 had. See Content and panel.
  • Contacts and privacy. Requests go to the panel and, if you turn them on, to Telegram, email (Resend) and a signed (HMAC) webhook, with automatic retry. Forms record consent, the privacy policy is generated, and a person's data can be exported or deleted.
  • Agents. The local MCP server (rubrica mcp) replaces the rubrica skill's Python script: the agent edits pages, blocks and collections with a panel user's login, with a preview before writing. The writing skills (rubrica-voz, rubrica-case, rubrica-blog, rubrica-curriculo, rubrica-apresentacao, rubrica-pilar) use the MCP to write. The MCP has proposal tools, uses the project's real catalog (own blocks included, read through the backend), validates the installed theme's variants, serves the theme's recipes (page_recipes) and the usage guidance of each block.
  • Development. pnpm dev reflects what you save in the panel without restarting. Forms work outside Vercel and on your computer: the API address comes from Convex (PUBLIC_RUBRICA_API is optional). The panel's live preview works on the published site.
  • Documentation. The block catalog is generated from the code, and there are guides to create a block and create a theme, plus plugins (in 2.0 there is no public API for third-party plugins), environment variables and the company site.
  • Neutral hosting. Vercel stays the official host (publicar automates only it), but the project generates vercel.json, public/_redirects and public/_headers from the same configuration, and the Publish button accepts any host's deploy hook.
  • New CLI. Commands create, setup, config, publicar, senha, update, ejetar, verificar, testar-tema, mcp, migrar and telemetria. See CLI commands.

Breaking changes from v1

  • The project is no longer a copy of the template. There is no app src/, templates/, cli/ or scripts/ in the project. update stops merging files (and generating .rubrica-new): it bumps packages and regenerates convex/.
  • Code customizations do not migrate on their own. migrar lists them, and each becomes configuration (panel tokens), an own block (src/blocks/) or an ejected component (ejetar).
  • The app is no longer a Vite SPA. Pages and routes belong to Astro; the panel lives at /admin (before, /login and /admin/* in the SPA).
  • The playground plugin is gone. The i18n plugin ("AI translation") became translation: languages belong to the core, and the plugin only fills in translations.
  • Section texts became block fields (titles, subtitles and buttons); only interface texts stay in "Texts".
  • The ptBR/enUS translations become a per-language map. In migrar, the main language is pt-BR and the /en URLs stay the same.
  • Requirements: Node 22.23.4 or newer (before, 20).
  • The rubrica skill's Python script is gone: use the MCP.
  • Environment variables. The new names are in docs/v2/variaveis.md (in Portuguese); v1's (TELEGRAM_ADMIN_CHAT_ID, VERCEL_DEPLOY_HOOK_URL, VITE_UMAMI_*) are still accepted.

Known pending items

They are in docs/v2/pendencias.md (in Portuguese). The main ones:

  • Panel: images in text bodies, a live preview of posts and cases, translating a whole item at once and opening the AI résumé PDF.
  • For 2.0.x: update still does not regenerate vercel.json and public/_headers (header and rewrite fixes, and the embed providers, only reach new projects); the rewrites were not tested on real hosting; and there is no cookie notice before an embed loads.

1.13.1

Release notes

The first visit shows up without waiting for animations.

Coming from 1.13.0:

  • Update with npx create-rubrica@latest update. No new CLI version needed, nothing to push to Convex.

Speed

  • Content visible right away: entrance animations kept the title and content invisible until the JavaScript loaded. Now the prerendered page arrives in its final state, and animations still run when navigating between pages. On a real site, the home went from 86 to 100 in Lighthouse (mobile), with LCP dropping from 4.1 s to 1.2 s; a post went from 84 to 95.

1.13.0

Release notes

A page audit: SEO fixed, faster first visits and accessibility across the 14 layouts.

Coming from 1.12:

  • Update with npx create-rubrica@latest update. No new CLI version needed, nothing to push to Convex.
  • Customized vercel.json? Bring over from .rubrica-new the new rewrites (only app routes go to app.html), trailingSlash: false and the /fonts/ cache. Without the new rewrites, addresses that don't exist keep answering 200.
  • Customized the sidebar? Compare with .rubrica-new: the mobile menu button and the language switch got names for screen readers, and some text got more contrast.
  • Customized index.html? Remove maximum-scale=1 from the viewport: it blocked zooming.

SEO

  • Addresses that don't exist answer 404. Before, they answered 200 with an empty page Google could index.
  • robots.txt: generated in the build, with the sitemap address and the panel blocked. Before, the address returned the site's page.
  • No duplicate addresses: /blog/ redirects to /blog.
  • A title on every page: the brutalist, swiss, bento, magazine, zine, blueprint and chat layouts had no title, description or canonical on their own pages. Now every fixed page gets a default the page can override.

Speed

  • The first visit keeps the build's HTML. The page content (the whole post, cover included) was thrown away and rendered again right after loading. Now the page code arrives first and nothing is redone.
  • Images sized for the screen: phones download an 800px version instead of the 1600px one; images carry width and height so the page doesn't jump as they load, and the main one gets priority.
  • Fonts served by the site itself: the page no longer waits for Google Fonts to show up.
  • Main JavaScript 19% smaller: animations, the contact and testimonial wizards, the terminal and the CV generator load only when used.
  • Panel and proposal texts are no longer in public pages.

Accessibility

  • Zoom allowed on phones.
  • Names for screen readers: the mobile menu button, the language switch and the bento layout's GitHub and LinkedIn links.
  • Contrast: more readable text in the default sidebar and home, and in post tags.

Fixes

  • A post containing $& or $' (code, for example) could come out corrupted in the build.
  • An image whose id ended in digits only could be swapped for the smaller version.

1.12.0

Release notes

The project list gets much lighter: pages that show projects no longer carry every case study's full text.

Coming from 1.11:

  • Update with npx create-rubrica@latest update. No new CLI version needed, nothing to push to Convex.
  • Publish again (npx create-rubrica publicar or the panel's Publicar button) so the build generates the new project files.

Site

  • Slim project list: the home, portfolio, case study pages and posts carried in their HTML the full text of every case study, each project's long description and the data of each library image. Now the list only carries what it shows (case study metrics and image addresses), and each full project lives in its own file, read by the case study page. On a real site, the list went from 153 KB to 33 KB, the home from 241 KB to 138 KB, and a case study page from 233 KB to 123 KB.
  • Portfolio modal: the long description is fetched when the modal opens. Until it arrives, the short description shows.
  • Cyberpunk layout: the sidebar's "Download CV" button also fetches the resume only on click.

1.11.0

Release notes

Content images come out of the build optimized and cached, and pages get much lighter.

Coming from 1.10:

  • Update with npx create-rubrica@latest update and run pnpm install (or npm install): the build uses sharp, which is new. No new CLI version needed, nothing to push to Convex.
  • Customized vercel.json? Bring over from .rubrica-new the /media/(.*) block, which serves images with one-year caching.
  • The first publish after updating downloads and optimizes every image, so it takes a bit longer. Later ones only download new images.

Site

  • Images optimized in the build: covers, case study and post images and avatars are downloaded from Convex, resized to at most 1600px, converted to WebP and served by the site itself with one-year caching. Before, every visitor downloaded the original file from the storage, with no CDN caching. On a real site, images went from 26 MB to 7.3 MB, and a post cover from 841 KB to 116 KB.
  • Link previews in JPG: og:image uses a 1200px JPG version that every network accepts.
  • Faster builds: images are cached between publishes and only new ones are downloaded. Videos and PDFs stay on the storage.
  • Lighter pages: the blog list no longer carries every post's text (on a real site, /blog went from 1.3 MB to 233 KB), and the "Download CV" button only fetches the resume on click instead of loading it on every page.

Fixes

  • The resume PDF opens in a tab created right on click, so the browser doesn't block it as a popup.

1.10.0

Release notes

Public pages come out of the build ready, with an English version under /en, and blog posts get SEO fields.

Coming from 1.9:

  • Update with npx create-rubrica@latest update. No new CLI version needed.
  • The backend changed (convex/): push it to the local Convex with npx convex dev --once and, on the live site, with npx create-rubrica publicar. The new post fields are optional: existing posts stay the same.
  • Customized vercel.json? Bring over from .rubrica-new the rewrite change from /index.html to /app.html. Without it, the panel and login open with the home page's HTML and fail.
  • Customized the build script in package.json? It now ends with npm run build:site, which generates the pages.
  • The language now comes from the address: English lives under /en/.... The choice saved in the browser no longer switches the language on its own; visitors whose browser is in the other language see a prompt to switch.
  • The settings in /admin/site-config (colors, site title and description) now apply to the published site. Before, the live site used the ones in rubrica.config.ts. Check the panel before publishing.
  • Texts edited in /admin/textos show up on the site after publishing, like the rest of the content.

Site

  • Pages ready in the build: home, About, Resume, Portfolio, each case study, Blog, each post and Testimonials come out as HTML with each page's content, title, description and image. That's what Google and link previews (WhatsApp, LinkedIn) read. In the browser, the site still navigates without reloading the page. Panel, login, proposals and checkout work as before.
  • English under /en: every page exists in both languages, with the right canonical, hreflang and <html lang>, and the sitemap lists both versions.
  • Post SEO: each post has its own title, description, image and structured data (JSON-LD). Before, every post came out with the site's title.
  • One <h1> per page: the name in the sidebar (default and cyberpunk) is no longer every page's <h1>; the brutalist home, About and Testimonials got their own.

Blog

  • SEO and sharing on posts: title and description for Google, a share image and a preview of the search result, in /admin/blog. All optional: left blank, the site uses the title, subtitle and cover. English is translated on save.
  • Stable slug: the post address is suggested from the title only on creation and then only changes if you edit it; changing a published post's slug shows a warning, since it breaks links.

Skills

  • rubrica: post-criar, post-editar and aplicar-plano accept the post SEO fields.
  • rubrica-blog: the SEO step writes the Google description, and the plan carries the fields to the post.

Fixes

  • Editing a published post's title changed its address.
  • Two posts could end up with the same address when editing the slug.
  • The published site ignored the colors and SEO saved in /admin/site-config.

1.9.0

Release notes

CLI 1.6.0: anonymous telemetry from the commands, to learn what people use the most.

Coming from 1.8:

  • To get the new CLI, use npx create-rubrica@latest. Existing projects can update with npx create-rubrica@latest update: only documentation changed in the template, nothing to push to Convex.
  • Don't want to send anything? npx create-rubrica telemetria desligar in the project folder, or RUBRICA_TELEMETRIA=0.

CLI

  • Anonymous telemetry: when create, setup, publicar, update and config finish successfully, the CLI sends the choices made (layout, scheme, color mode, texture, fonts, plugin bundle, integrations turned on, versions). No name, email, site address, content, keys or IP. The project gets a random id in rubrica.json, and the CLI tells you the first time.
  • telemetria command: npx create-rubrica telemetria shows whether it's on; ligar and desligar store the choice in the project. --sem-telemetria turns it off for one run (on create, the project starts with it off). DO_NOT_TRACK=1 also works, and in CI the CLI never sends anything.
  • Sending takes at most 2 seconds and never breaks the command.

Documentation

  • New page CLI telemetry: what is sent, what isn't and how to turn it off.

1.8.1

Release notes

Fix: new texts from an update showed up as raw keys on the site.

Coming from 1.8:

  • Update with npx create-rubrica@latest update. No new CLI version is needed and nothing to push to Convex.

Fixes

  • After updating Rubrica, texts added in the new version (such as the testimonial translation notice and the "Show original" button from 1.8.0) showed up as portfolio.showOriginal instead of the text. The site now uses the default text while the key isn't in the database. Texts you edited in the admin still take precedence.

1.8.0

Release notes

Case metric cards and the case testimonial now have an English version.

Coming from 1.7:

  • Update with npx create-rubrica@latest update. No new CLI version is needed.
  • The backend changed (convex/): push it to your computer's Convex with npx convex dev --once and, for the live site, with npx create-rubrica publicar. The new fields are optional: existing cases stay the same.
  • Cases you already saved stay in Portuguese on /en/ until you open each project at /admin/projects and save it again. The translation happens then.

Cases

  • Metrics in English: when you save the project, the label and value of each card are translated. Numbers ("365", "7 GB → 400 MB") stay the same; text ("Entrada + saída") is translated. The card metric on the home and portfolio pages is translated too.
  • Testimonial with its original language: pick the language the person wrote the testimonial in (Portuguese or English). In the other language, the site shows the translation with a "Machine translation of the original" notice and a button to see the original.
  • The prompt for importing a case as JSON asks for the translated metrics and testimonial.

Skills

  • The rubrica and rubrica-case skills know how to translate the metrics and set the testimonial's original language.

1.7.0

Release notes

Proposals with per-item prices, discounts and gifts. The skills now open an issue when Rubrica can't do what was asked, and projects get instructions for AI agents.

Coming from 1.6:

  • Update with npx create-rubrica@latest update. No new CLI version is needed.
  • The backend changed (convex/): push it to your computer's Convex with npx convex dev --once and, for the live site, with npx create-rubrica publicar. The new fields are optional: existing proposals stay the same.
  • For the discount to show up in contracts from templates you already saved, add {{discount}} to the template at /admin/contracts.

Proposals

  • Per-item price: each scope item can have a price, shown next to it in the proposal and in the contract.
  • Discount: optional original value (before the discount). The proposal shows the original value struck through, the discount in R$ and %, and the final value. The admin suggests the original value from the sum of the items and warns when the sum doesn't add up.
  • Gift: mark a priced item as a gift. In the proposal it shows the "Brinde" badge, the price struck through and R$ 0,00.
  • The project value is still the final value, used in the contract and the payment options. The contract mentions the discount and the gifts, and contract templates get the {{original_value}} and {{discount}} variables.

Skills and agents

  • Opening issues: when someone asks for something Rubrica doesn't support, or something breaks, the skills decide whether it's a bug or a feature request, look for a similar issue and, once the person says ok, open it on Rubrica's GitHub (with gh or a prefilled link), without private data.
  • The rubrica skill knows how to handle proposal prices, discounts and gifts.
  • AGENTS.md and CLAUDE.md at the project root: they teach agents such as Claude Code, Codex and Cursor how to update Rubrica (including the .rubrica-new files), what they can run in the CLI and what stays with you. See "With an AI agent" in CLI commands.

1.6.0

Release notes

The Rubrica site gets an English version, a changelog page and the documentation, with three new guides: getting started, CLI commands and publishing.

Coming from 1.5:

  • Update with npx create-rubrica@latest update to get the rubrica-voz skill that understands the interview in English. No new CLI version is needed, and nothing has to be pushed to Convex.

Rubrica site

  • In English, at userubrica.vercel.app/en, with a language switch at the top. Builder, "Create yours", layouts and schemes, all translated. The page notes that the CLI and the admin panel are in Portuguese.
  • Changelog at /en/changelog (and /novidades): this changelog on the site itself, with a version index.
  • Documentation at /en/docs (and /docs): the template guide, the 13 layouts, the color schemes, creating a layout and updating become site pages, with navigation and an index. Links on the site no longer send you to GitHub.

New guides

  • Getting started: from zero to the site running on your computer, and what to fill in on each panel screen.
  • CLI commands: every question, option and file of create, and the other commands.
  • Publishing the site: the first publish, the panel's Publish button, another computer, custom domain and common problems.
  • The README and the CLI README are shorter and point to these guides.

Voice interview in English

  • At /en/voice, with dictation in English and answers saved apart from the Portuguese ones. The rubrica-voz skill recognizes the English interview and observes the voice in the language of the answers.

1.5.0

Release notes

The admin panel's Publish button (Publicar) now works without GitHub, the AI agent can work on the published site, and publicar is safe to run on another computer.

Coming from 1.4:

  • Update with npx create-rubrica@latest update and run npx create-rubrica@latest publicar. It records the published site's address in rubrica.json and offers to turn on the panel's Publish button (you create a Vercel token and paste it in the terminal, only once).
  • Commit rubrica.json with the project: setup and publicar use it to recognize, on another computer, that the site is already live.

Panel Publish button

  • No GitHub needed. Vercel only creates Deploy Hooks for projects linked to GitHub, and publicar deploys from the terminal. Now the panel uses a Vercel token to redeploy the latest production deployment: the build runs again and fetches the updated content. If you have a Deploy Hook, the panel keeps using the hook.
  • publicar opens Vercel's tokens page, explains what to fill in, takes the token without showing it on screen, checks that it can access the project and saves it to the production database.
  • The panel shows why publishing failed (button not configured, expired token). Before, it said "Deploy started successfully!" ("Deploy iniciado com sucesso!") even on errors.

AI agent on the published site

  • The rubrica skill gains --producao (or RUBRICA_AMBIENTE=producao) to work on the live site. The default is still the site on your computer.
  • In a project that is already published, login asks whether you want to sign in to the published site or the one on your computer. status shows both addresses.

publicar and setup on another computer

  • publicar saves the published database and site addresses under producao in rubrica.json (1.4 projects get this when they publish again).
  • Without the .vercel folder (fresh clone, another computer), publicar notices the site is already published, links the folder to the same Vercel project and just publishes. Before, it redid the first-time flow: it generated new login keys (everyone was signed out of the panel) and rewrote the panel data.
  • If the computer is linked to a different Convex project, publicar stops before writing anything, so it doesn't swap the live site's database for an empty one. setup, in a clone of a published site, links to an existing Convex project instead of creating a new one.
  • When you publish again, Telegram and OpenRouter set up on your computer after the first time are sent to production (only the ones missing there).

create

  • Git starts on the main branch, with a first commit of the generated project. Before, the branch name depended on the computer (usually master) and the branch only existed after the person's first commit.

1.4.1

Release notes

Layouts adjusted for wide screens (1920px monitors and up). Nothing changes on screens up to 1600px.

Coming from 1.4:

  • Update with npx create-rubrica@latest update. No new CLI version is needed, and nothing needs to be pushed to Convex. If the site is already published, publish again after updating.

Wide screens

  • Jardim Digital: content sat against the sidebar, with a huge empty space on the right. Now the column is centered.
  • Bento: the grid only stopped at the screen edge, and the cards got huge. Now it stops at 1600px and is centered.
  • Suíço: menu and content stop together at 1600px and, beyond that, get side borders in the layout's line style, like a centered sheet.

1.4.0

Release notes

npx create-rubrica publicar puts the site live on Vercel without copying anything by hand, and the template now works when published from a CLI project.

Coming from 1.3:

  • Update with npx create-rubrica@latest update. It brings the domain/ folder (without it npm run build fails), public/color-mode.js and the fixed build:i18n.

Publishing

  • npx create-rubrica publicar: signs in to Vercel (login in the browser), creates the project, prepares the Convex production database (key, backend, login keys, Telegram and OpenRouter integrations, profession), creates the published site's admin and initial data, saves the variables on Vercel and publishes. Running it again just publishes.
  • setup ends by explaining how to put the site live.

Fixes for the published site

  • Projects created by the CLI failed on npm run build: the domain/ folder, used by the RSS generator, was left out of the release package.
  • The Vercel build wiped the site's translations when the translation plugin was off (the menu showed navigation.home). Now the texts from the database are merged over the repository's translations.
  • The light/dark mode script was blocked by the published site's security policy (CSP). It moved to public/color-mode.js.

1.3.0

Release notes

Skills for the AI agent to write the site's content with a method and in the owner's voice, plus the voice interview on the site. Nothing changes on the site or the panel for people on 1.2.

Coming from 1.2:

  • Update with npx create-rubrica@latest update. It brings the .agents/skills/rubrica-* folders (and the shortcuts in .claude/skills/) and the .rubrica/ line in .gitignore. Nothing needs to be pushed to Convex.
  • The first time you ask the agent for a site text (introduction, case, resume, post), it will send you to the voice interview at https://userubrica.vercel.app/voz. It takes about 20 minutes.

Content skills

  • Six new skills for the AI agent to write the site's content with a method and in the owner's voice: rubrica-voz, rubrica-apresentacao, rubrica-case, rubrica-curriculo, rubrica-blog and rubrica-pilar. The introduction, case and resume techniques come from research with sources (included with each skill in references/pesquisa.md).
  • Voice comes first. Without a voice profile, the skills send the person to the voice interview on the site (/voz, hidden from search engines): 21 questions, answered by speaking (browser dictation) or typing, with a button that copies everything as Markdown for the agent. rubrica-voz measures the style with a script, builds the profile with verbatim excerpts, runs a blind calibration with the person and proposes the personal side of the About page.
  • The strategist skills don't save anything: they deliver a plan in .rubrica/planos/, reviewed by rubrica-pilar, which the rubrica skill applies.
  • New aplicar-plano command in the rubrica skill's script: validates the plan before saving (structure, files, text keys, duplicate slug, contrast, missing English, functions that don't exist), shows the before → after (--verificar), refuses plans made for a different Convex and resumes where it stopped if something fails (--retomar).

1.2.0

Release notes

A CLI designed for non-technical people: fewer questions, nothing asked twice, straight from the site to the terminal, and changing the panel password from the terminal. Nothing breaks for people on 1.1.

Coming from 1.1:

  • Update with npx create-rubrica@latest update. It brings the function used by npx create-rubrica senha. If the site is already published, publish again after updating.
  • The panel password now follows the same rules everywhere: 12 or more characters, with uppercase, lowercase and a number. Old passwords still work; the rule applies to future changes.

Straight from the site to the terminal

  • The site's Create yours section (Crie o seu), below the builder, builds a command with --receita. It carries the chosen look, the plugins, the identity, the profession and the specialties. Nothing leaves the browser.
  • With the recipe, the CLI shows a summary, confirms and only asks for what is missing. The project is created on Convex without Convex's questions, and the terminal asks for only the panel password. Telegram and Vercel are left for a later setup.
  • Readable options for those who prefer them: --layout, --esquema, --modo, --textura, --fonte, --mono, --plugins, --alternancia.

Fewer questions in create

  • It starts by asking Quick (Rápido) or Custom (Personalizado). In quick mode, colors, texture and fonts come from the layout, and the language is Portuguese.
  • Plugins come in ready-made bundles (Completo, Para vender serviços, Só o portfólio — complete, for selling services, portfolio only), with the one-by-one list as an option. Names and descriptions in plain language, also in config.
  • Site address without typing https://: meusite.com/ becomes https://meusite.com. An @ handle and an X profile link are also accepted. If you don't have a domain, you can keep the suggested <projeto>.vercel.app.
  • Git and dependency install with no questions: with pnpm if create came from pnpm create, with npm otherwise.
  • Offers to set up the panel right away: connects Convex and runs setup in the same flow, with no second terminal.

setup, config and password

  • setup connects Convex on its own when .env.local is missing, doesn't ask again for the site address and pre-fills the admin email. Telegram and Vercel sit behind a yes/no, and the questions no longer show environment variable names.
  • The profession entered in setup now appears below the name on the site. Before, it was saved by a function that required login and failed silently.
  • Running setup again no longer asks for the password when the panel already has an admin.
  • npx create-rubrica senha: changes the panel password from the terminal, on the published site or the one on your computer, and unlocks a login blocked by wrong attempts.
  • config → Identity (Identidade) opens the questions with the saved values, instead of asking for everything again.
  • CLI maintenance guide (in Portuguese): what to change in the CLI when a new layout, color scheme, font or plugin comes in, and the recipe rules.

1.1.0

Release notes

8 new layouts, 15 color schemes with light and dark modes, visitor mode toggle, textures, and admin colors split by mode. Nothing breaks for people on 1.0.

Coming from 1.0:

  • Update with npx create-rubrica@latest update and then run npx create-rubrica@latest config → Appearance (Aparência) to choose the scheme, mode, toggle and texture. Before update, config warns that the new layouts and light/dark mode don't exist in the project yet.
  • Colors changed earlier in the admin keep applying to both modes until the appearance is saved again.

8 new layouts

  • Desktop Retrô, Índice, Monografia, Zine, Blueprint, Jardim Digital, Conversa and Pôster Cinético, each with the 5 pages (Home, Resume, Portfolio, About, Blog), working on mobile and in both modes. See the templates guide (in Portuguese).

Color schemes, light/dark mode and texture

  • 15 color schemes, each with light and dark modes and 11 color roles: the 4 original presets (now also in the other mode), Neon (the original look) and 10 new ones (Riso, Cianotipia, Tropicália, Azulejo, Sumi, Fósforo, Crepúsculo, Concreto, Sorbet, Alto Contraste). The 5 original layouts still use only the usual 4 colors; the new ones use the full scheme.
  • Light, dark or automatic mode (follows the visitor's system), with an option to show a button so visitors can switch. All 13 layouts have the button.
  • Optional textures: film grain, paper and scanlines.
  • create-rubrica and create-rubrica config → Appearance ask for scheme, mode, toggle and texture, with each layout's recommended option marked.
  • Shared pages (post, case study, testimonials, proposals, checkout, 404 and the forms) now work in light mode. The admin panel is always dark.
  • Admin colors per mode: in Site & Appearance (Site & Aparência), each mode has its own 4 colors. The fields start with the scheme's colors, only what you change is saved, and "Use the scheme colors" ("Usar as cores do esquema") undoes the customization. Before, saving the appearance (even just changing the font) locked the 4 colors on top of the scheme.
  • The Google Fonts link now also loads the mono font, which wasn't loaded before.

1.0.0

Release notes

First stable version. From here on, within 1.x, updating doesn't break your customizations or your data: new database fields are always optional, and changes that need a migration only come in a new major version, with a guide.

Coming from 0.x:

  • Update with npx create-rubrica@latest update. Projects created with the CLI up to v0.3.18 pass their starting version with --from (see Atualizando o seu Rubrica, in Portuguese); fork projects use git merge v1.0.0.
  • Payments are now real: set ASAAS_API_KEY and register the Asaas webhook (README → "Configurando os pagamentos"). The Stripe integration was removed.
  • The Umami script now uses VITE_UMAMI_SCRIPT_URL and VITE_UMAMI_WEBSITE_ID (the old variables are still accepted).

Update without losing customizations

  • create-rubrica update was rewritten. Before, it extracted the new version over the project (losing any hand-edited file) and reset the identity in rubrica.config.ts. Now it merges Rubrica's changes with yours, file by file; when both changed the same part, your file stays intact and the new version goes to <arquivo>.rubrica-new. New options: --dry-run, --from, --to, --yes.
  • create now saves the version actually downloaded in rubrica.json (before, it always saved 0.1.0). Older projects pass their starting version with --from or by answering update's question.

Real payments (Asaas)

  • Checkout now creates real charges on Asaas: PIX (QR code and copy-and-paste code), boleto (bank slip with line code and PDF) and card in up to 12 installments, through Asaas's secure page. The site never receives card data.
  • Serious fix: card payments were marked as confirmed without any charge. Now a checkout only becomes paid when the Asaas webhook confirms it.
  • The installment price with interest is calculated on the server; before, it came from the browser and could be tampered with.
  • Switching payment method cancels the previous charge (before, two open charges were left), including every installment of an installment plan. Expired or deleted links cancel the PIX/card charge.
  • A boleto that was already generated can't be switched to another method: it may have been paid and still be clearing.
  • Protection against double payment and abuse: a lock against two simultaneous clicks, a limit of charges per link, and an expired PIX QR code that can be regenerated.
  • Asaas refunds and chargebacks mark the checkout as refunded and send a Telegram alert; payment of a charge other than the current one, on a deleted link or for a lower amount also triggers an alert.
  • Payment error messages reach the customer in production (before, they became "Server Error").
  • Checkout with a minimum of R$ 5, at most 2 decimal places and a valid due date; installments under R$ 5 aren't offered; the payment method restricted on the checkout is respected.
  • Payments admin working: Asaas customers, charges and invoices, with audit log. Checkout links generated with cryptographic randomness.
  • The checkout page no longer breaks on open (it tried to format the CPF and phone number that the server hides on purpose). /payment-success shows "confirming" ("confirmando") until the payment is confirmed.
  • New Convex variables: ASAAS_API_KEY (sandbox or production, detected from the key) and, optionally, ASAAS_ENV. setup asks for the key, generates ASAAS_WEBHOOK_TOKEN and shows how to register the webhook.
  • Removed: the Stripe integration, which never worked (unused stubs in the interface), the /webhooks/stripe webhook and the STRIPE_WEBHOOK_SECRET variable.

Layouts on mobile

  • Swiss, Magazine, Brutalist and Bento fixed on phone screens: grids that didn't stack (content overflowing the screen), giant titles cut off, name broken in the middle in the Magazine header, excessive margins, squeezed testimonials and mosaics, the Brutalist blog table. Checked at 390, 768 and 1280px in all 5 layouts.
  • New src/components/MobileLayoutStyles.tsx: on mobile, grids built with inline styles become a single column; exceptions by attribute (data-m-cols="2", data-m-keep, data-m-hide, data-m-scroll, data-m-bleed).
  • Cyberpunk: the top of the pages is no longer hidden behind the fixed mobile header.
  • Swiss and Bento: post, case study and testimonials get side margins (before, they touched the edge).
  • Post dates formatted in Bento and Brutalist (they showed as 2026-01-15T00:00:00.000Z).
  • Sample posts (seed and demo data) in HTML, the way the editor saves them; before, they showed raw # and **. Sample case slug fixed to lumen-saude.

Security and cleanup

  • Login: explicit limit of 5 wrong passwords per account per hour.
  • Umami: the script is only added to the site when VITE_UMAMI_SCRIPT_URL and VITE_UMAMI_WEBSITE_ID are set (before, it loaded a URL with the literal placeholder); Umami Cloud allowed in the CSP. VITE_ANALYTICS_ENDPOINT/VITE_ANALYTICS_WEBSITE_ID are still accepted.
  • .env.example rewritten with the variables the code actually reads.
  • Removed leftovers from an old setup: vite-plugin-manus-runtime, ManusDialog, Map.tsx (unused Google Maps), @shared/@assets aliases and monorepo paths in the scripts.

Fixes

  • npx create-rubrica <nome> and pnpm create rubrica <nome> create the project again (before, they only showed the list of commands).
  • config, identity: no longer resets SEO, RSS and the share image, updates the meta tags in index.html and saves the identity in rubrica.json.
  • config, appearance: changing palette or font no longer deletes the meta tags in index.html.
  • config, layout: works in projects created by the CLI (downloads the layouts for the project's version) and includes the Magazine layout.
  • Vercel build: the build:i18n script, called by vercel.json, had gone missing from package.json. Removed the daily cron for /api/cron-deploy, a route that doesn't exist.
  • The release includes scripts/ and vercel.json again: without them, pnpm build failed in projects created by the CLI.
  • The dashboard's "New proposal" ("Nova proposta") and "New project" ("Novo projeto") shortcuts open the creation form again.
  • Texts on the login, testimonials, home, blog and about pages come from the translations (i18n) again instead of being hardcoded.

Quality

  • CI on GitHub Actions: types, tests and build for the template and the CLI on every PR.
  • Template and CLI tests and typecheck passing (there were 21 + 8 failing tests and 9 + 4 type errors).

0.3.18

Release notes

  • Conversion-focused portfolio structure in every layout: metrics, featured cases, working principles, case sections (role, before, decisions, lessons learned), category filters, testimonials by category, grouped skills, CV download at the top of the resume, and Umami events on CTAs. All new fields are optional.

0.3.17

Release notes

  • Security: siteConfig:setBatch now requires the root or admin role.
  • Seeds no longer erase customized texts and home page.
  • Publishing after editing texts or configuration works again.
  • The site name and contact entered in the CLI are now saved to Convex.
  • New rubrica skill for AI agents (Claude Code, Codex, OpenCode).
  • 4-color system in every layout, including light palettes; templates and colors guides.

0.3.16

Release notes

  • The sidebar no longer covers part of the content on desktop.

0.3.15

Release notes

  • Installs without the i18n plugin no longer show keys (home.title) instead of texts.

0.3.14

Release notes

  • The home page no longer breaks when the technology list comes in an unexpected format.

0.3.13

Release notes

  • Sidebar without a nested <a> (hydration error).

0.3.12

Release notes

  • setup applies the seeds again (the command failed silently and the tables stayed empty).

0.3.11

Release notes

  • The Magazine layout no longer repeats the Masthead three times.

0.3.10

Release notes

  • Broken import in the Brutalist Navbar; pages and components that were missing from the template.

0.3.9

Release notes

  • Masthead import fixed in the Magazine layout.

0.3.8

Release notes

  • Theme CSS variable conflict fixed.

0.3.7

Release notes

  • ASCII art of the name, and --bg/--text colors from Convex now applied.

0.3.6

Release notes

  • The generated vite.config no longer references isDev.

0.3.5

Release notes

  • Brutalist fixes (colors, navigation, identity in the CLI, ASCII art) and a clean console.

0.3.4

Release notes

  • 4-color CSS contract (--bg, --text, --primary, --accent) and 2 fonts in every template.

0.3.0

Release notes

  • Full pages (Home, Resume, Portfolio, About, Blog) for Brutalist, Swiss, Magazine and Bento.

0.2.0 – 0.2.4

  • setup command: JWT keys, SITE_URL, per-plugin variables, root user and seeds. Fixes to saving JWT_PRIVATE_KEY.