For Developers
Keep the browser side of building in order.
Documentation, a local preview, an issue and a few useful references. Keep the project context close while you inspect the page and work through the next change.
Check the narrow layout, then attach a capture to the issue.
Illustrated example
From inspection to review
Keep the implementation loop close
Let your editor own the source code. Use the browser to inspect the result, keep references handy and document what you see.
Inspect and try visual changes on the page
Use InTab's developer tools to inspect elements and experiment with page styling. Bring the changes you want to keep back into your project, then verify them in the actual implementation.
See the visual developer toolsA browser-side edit is an experiment. Keep your repository as the source of truth and test the final change across the states your UI supports.
Park one project before opening another
Save the preview, docs, issue and reference tabs as a project session. Restore them when you return to the task without keeping every project's resources open at once.
Save a development tab sessionSplit sessions by task when the project grows: account UI, API integration or release checks. Local development pages still need their server running.
Make UI feedback visible
Capture the page and annotate the area that needs attention. Add the image to a bug report or review alongside reproduction steps and the viewport where the issue appears.
Capture browser UI issuesInclude expected and actual behavior in the issue. A screenshot explains appearance, but it cannot reproduce keyboard or interaction failures on its own.
Keep the next change in view
Save the tabs for the task you are working on and return to the same browser context when you resume.
Features and usage limits vary by plan. Compare plans and limits