Side-panel notes: a better workflow for reading the web

Side-panel notes work well when you need to read a page and capture a thought without losing sight of the source. Keep a short note beside the webpage, save its link and write down why the information matters. Move longer writing into a full document when you have enough material to synthesize.

The panel is a working surface. It does not need to become your entire knowledge system.

Start with one question

Suppose you are comparing three tools for a project. Before opening ten tabs, write the decision you need to make:

Which option lets our team review drafts without buying an account for every external reviewer?

That question is much easier to research than “find the best tool.” It suggests what to look for, which source pages matter and when you have enough information.

Keep the question at the top of your note. When an interesting but irrelevant feature appears, you can recognize it without adding it to the comparison.

Keep the source and the note side by side

Chrome's side-panel API allows an extension to display its interface alongside the webpage. The specific tools and page access depend on the app using it.

Open your chosen note tool in that space. Make the panel wide enough to read comfortably, while leaving enough room for the source. If the webpage becomes difficult to use, switch to a separate window or a full document. Side-by-side is a convenience, not a rule to obey at every screen size.

Dashy V2 is developing supported notes and tools in its side panel as part of the release planned for October 2026. See the Dashy side-panel preview for scope; this article describes a general workflow you can use with a suitable note tool.

Use a note format that preserves the evidence

You can copy this small structure into an ordinary note:

Question: What am I trying to find out?

Source: Page title and link.

Observation: What does the page actually establish?

Meaning for me: Why does that matter for my decision?

Still unclear: What would I need to verify?

The split between observation and meaning is valuable. A product page might establish that guest reviewers are supported. Your interpretation might be that it could suit occasional client feedback. Whether those guests can approve a draft on your intended plan may still be unclear.

Without that distinction, “possibly useful” has a habit of becoming “confirmed” by the time you revisit the note.

Capture less than you think you need

You do not have to copy the whole page to preserve a useful finding. Save the link, the section and a short note about the specific point. If you need exact wording, mark it as a quotation so you do not mistake it for your own prose later.

For our reviewer example, useful notes might be:

• Where the product documents guest access.
• Which plan the relevant permission appears under.
• Whether the page distinguishes commenting from approving.
• Which question remains unanswered.

A long paragraph about the vendor's mission does not help make this decision. Keep your capture tied to the question.

Turn notes into a comparison after reading

Do the first pass as observations. Then build a small table across the options:

This is a blank decision method, not a comparison of real products. Replace each cell with evidence you collected. “Not established” is often more accurate than “No.”

If the table exposes a missing fact, go back for that fact. Avoid restarting the entire research process because one detail is unresolved.

Let AI help with synthesis, not source invention

Once you have a few clear notes, an assistant can help organize them. A bounded prompt is:

Using only these notes, compare the options against my original question. Preserve each source link. Separate confirmed facts from unanswered questions. Do not fill gaps from memory or invent a recommendation where the evidence is missing.

Review the result against your notes. That instruction helps describe the job, but it cannot guarantee the assistant will follow it perfectly.

Share only the material needed for the task. A side panel showing a webpage is not consent to upload the whole page. If a capture feature is available, inspect what it includes. Our AI privacy guide explains the different access layers.

Finish with a decision or a next step

At the end of a reading session, leave something usable: a recommendation with reasons, a question to ask the provider, or a task to verify the missing permission.

Store the final document where you will look for it. Keep a link from the dashboard if the project is ongoing. The scratch note can be cleared once its useful contents have a home.

For a student, that destination may be a course note. For a product team, it may be a project brief. For your own purchases, a short comparison may be enough. The student dashboard guide and minimalist layout guide show how to keep those destinations easy to reach.

You should be able to return tomorrow and answer two questions: what did I learn, and where did it come from? If the note does that, the workflow is working.