Project Visibility & Public Remixing

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Project Visibility & Public Remixing working in a real project rather than a sandbox.

   Set up Project Visibility & Public Remixing in this project — workspace-default visibility with opt-in public remixing. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Safer defaults

   The record lists this as one of the jobs Project Visibility & Public Remixing is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Project Visibility & Public Remixing for safer defaults. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Project Visibility & Public Remixing is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Project Visibility & Public Remixing before I publish. Check workspace-only by default and per-project access controls, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Templates and showcases

   A second job the record lists for Project Visibility & Public Remixing, useful once the first path works.

   Extend this project so Project Visibility & Public Remixing also covers templates and showcases. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Project Visibility & Public Remixing?

  Project Visibility & Public Remixing is Lovable's Publishing feature: Workspace-default visibility with opt-in public remixing. Public project visibility was removed; all projects default to workspace visibility with access controlled via project access settings.

• Is Project Visibility & Public Remixing GA or in beta?

  Project Visibility & Public Remixing is generally available (GA) on Lovable.

• What Lovable plan includes Project Visibility & Public Remixing?

  Project Visibility & Public Remixing is available on all Lovable plans.

• When did Project Visibility & Public Remixing launch?

  Project Visibility & Public Remixing launched on Apr 24, 2026.

• Granular Publishing AccessSame category, also GA · Apr 2026
• CDN / Reverse Proxy DomainsSame category, also GA · Apr 2026
• Branded app URLsSame category, also GA · May 2026