Understand the system.

A guide is the right place to begin when the problem crosses more than one layer of an app. A list, for example, is not only a visual component: it depends on the collection queried, the record available to the screen, the filters applied, and the action that carries a selected record forward. The guides make those dependencies visible before asking you to reproduce individual clicks.

Each resource states its verification level, last review date, sources, limitations, and testing checklist. Legacy walkthroughs are preserved for their useful concepts, while current claims are separated from older interface details. When a page says it was verified from public evidence, that means current documentation and dated community reports were checked; it does not claim an unseen end-to-end builder test.

If you are completely new, begin with the beginner’s guide and sketch the user’s job, collections, and screen flow. If your records are wrong or missing, move to the lists guide and prove the query before styling the row. Use the linked answers for narrow implementation problems, then return to the guide to test the whole path in context.

That final context check matters: a component can look correct in isolation while still receiving the wrong record or changing the wrong collection.

Looking for the retired course? Read the Adalocado Masterclass status and maintained replacements.