Lesson 12 of 16 · 45 min suggested practice
Run a security and quality review before launch
Review actual access rules, file delivery, errors, mobile behavior, and the available security scans before inviting people.
Make a risk-based inventory
Start with the version you are launching. A public library with original worksheets and local favourites has different risks from an app with accounts, uploads, and paid API calls. List the data, actions, and services that actually exist rather than checking irrelevant boxes.
For the simple Resource Shelf, check file permissions, truthful resource descriptions, broken links, accessible controls, and storage errors. For the optional account version, add ownership rules, password recovery, administrative actions, and server authorization. Use synthetic data while verifying behavior.
Review the scan findings
Lovable's Quick scan runs during publishing and checks a defined set of issues, including database settings and dependencies. Deep scan examines application code for broader logic and access problems. Open the security view, review the results, and identify which findings affect your intended use.
Fix the cause of an issue and rerun the relevant check. Do not hide a warning simply to make a release screen look complete. A scanner's scope is limited, so retain the manual checks for your resource permissions, download behavior, and any account-specific rules.
Walk through the important paths
Test search, topic filtering, direct detail URLs, each real worksheet, saved-list persistence, an empty state, and an invalid resource ID. Use a narrow viewport and a keyboard. If accounts are enabled, repeat the two-account test and a signed-out request to a protected action.
Check failure behavior deliberately: unavailable storage, a missing file, invalid form input, and a failed API call if one exists. Visitors should receive an understandable message and a useful next step. They should not see secrets, private records, or an invented success confirmation.
Record a concrete release decision
Use a test matrix with test case, expected result, actual result, date, and status. Separate passed checks from assumptions and untested paths. Identify the owner of any remaining issue and whether it blocks the intended launch.
Before collecting sensitive data or enabling a critical workflow, obtain review appropriate to that use. For this teaching project, a bounded public release of sample resources is enough. Keep the release small, keep a recovery point, and make it easy for a visitor to report a broken resource.
Try this focused prompt.
Review the current Resource Shelf version for release. Inventory public files, browser storage, optional account data, editor permissions, and external calls that actually exist. Run the available security scans and explain actionable findings. Verify the core browse/search/detail/download/save journey, direct URLs, mobile, keyboard, and relevant failure states. If accounts are enabled, repeat the two-account authorization checks. Produce a pass/fail/unverified matrix and identify blockers without claiming a scan proves complete security.
Replace the sample context with your own approved facts. Review Lovable’s proposed changes before accepting them.
Evidence before the next step
Check your work.
- The checklist matches the features actually present.
- Important user journeys and permission boundaries have observed results.
- Unresolved issues and the release decision are explicit.
Your checkmark stays in this browser. It records your own progress, not a certification.
Official sources & further reading
Reviewed November 19, 2026. Plans, terminology and interfaces can change; follow the linked documentation if your workspace differs.