<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Extension Kit</title>
    <description>The latest articles on DEV Community by Extension Kit (@web_automationlover_cc88).</description>
    <link>https://dev.to/web_automationlover_cc88</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4015008%2Ff9c6e39b-161a-46a9-a4a7-f09eaa4f7813.png</url>
      <title>DEV Community: Extension Kit</title>
      <link>https://dev.to/web_automationlover_cc88</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/web_automationlover_cc88"/>
    <language>en</language>
    <item>
      <title>Source-linked radiology study exports with a Chrome extension</title>
      <dc:creator>Extension Kit</dc:creator>
      <pubDate>Sun, 05 Jul 2026 03:55:28 +0000</pubDate>
      <link>https://dev.to/web_automationlover_cc88/source-linked-radiology-study-exports-with-a-chrome-extension-2a9e</link>
      <guid>https://dev.to/web_automationlover_cc88/source-linked-radiology-study-exports-with-a-chrome-extension-2a9e</guid>
      <description>&lt;p&gt;Radiology review notes are easier to trust when each exported study asset keeps a clear path back to the original source. RadNote is a Chrome extension workflow for turning selected Radiopaedia articles and cases into reviewable Anki, PDF, and case conference materials while preserving source links and attribution.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RadNote website: &lt;a href="https://www.radnoteapp.com/" rel="noopener noreferrer"&gt;https://www.radnoteapp.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Chrome Web Store listing: &lt;a href="https://chromewebstore.google.com/detail/radnote-%E2%80%94-radiopaedia-to/albabcfkhabighccjjlcnegpkcimkggh" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/radnote-%E2%80%94-radiopaedia-to/albabcfkhabighccjjlcnegpkcimkggh&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Workflow notes: &lt;a href="https://webautomationlover.github.io/radnote/workflow.html" rel="noopener noreferrer"&gt;https://webautomationlover.github.io/radnote/workflow.html&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Source attribution notes: &lt;a href="https://webautomationlover.github.io/radnote/source-attribution.html" rel="noopener noreferrer"&gt;https://webautomationlover.github.io/radnote/source-attribution.html&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A source-first review workflow
&lt;/h2&gt;

&lt;p&gt;A useful export workflow starts with a narrow learning goal. For example, a resident might turn one topic into a small Anki set, then keep a PDF sheet for longer review before a case conference.&lt;/p&gt;

&lt;p&gt;The important habit is not just exporting notes. It is keeping the source URL visible so the learner can return to the article or case when details need checking.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Keep one concept per Anki card where possible.&lt;/li&gt;
&lt;li&gt;Use PDF sheets for longer explanations or grouped teaching points.&lt;/li&gt;
&lt;li&gt;Keep source attribution visible in cards, handouts, and slide outlines.&lt;/li&gt;
&lt;li&gt;Review the source material before using exported notes for teaching.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;More RadNote support links are collected here: &lt;a href="https://webautomationlover.github.io/radnote/" rel="noopener noreferrer"&gt;https://webautomationlover.github.io/radnote/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;RadNote is independent and is not an official Radiopaedia product. It is intended as a study workflow aid, not a replacement for source review.&lt;/p&gt;

</description>
      <category>tutorial</category>
    </item>
    <item>
      <title>Building source-traceable study exports in a Chrome extension</title>
      <dc:creator>Extension Kit</dc:creator>
      <pubDate>Sun, 05 Jul 2026 02:31:14 +0000</pubDate>
      <link>https://dev.to/web_automationlover_cc88/building-source-traceable-study-exports-in-a-chrome-extension-3h3</link>
      <guid>https://dev.to/web_automationlover_cc88/building-source-traceable-study-exports-in-a-chrome-extension-3h3</guid>
      <description>&lt;p&gt;When a browser extension turns a source page into study material, the hardest part is not just export format. The harder product problem is preserving context.&lt;/p&gt;

&lt;p&gt;RadNote is a Chrome extension for radiology learners who want to turn selected source material into reviewable assets while keeping source links and attribution visible.&lt;/p&gt;

&lt;p&gt;Official links:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Website: &lt;a href="https://www.radnoteapp.com/" rel="noopener noreferrer"&gt;https://www.radnoteapp.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Chrome Web Store: &lt;a href="https://chromewebstore.google.com/detail/radnote-%E2%80%94-radiopaedia-to/albabcfkhabighccjjlcnegpkcimkggh" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/radnote-%E2%80%94-radiopaedia-to/albabcfkhabighccjjlcnegpkcimkggh&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why source traceability matters
&lt;/h2&gt;

&lt;p&gt;A study card without its source can be hard to audit later. In medical imaging education, the original case framing, modality, finding description, and attribution can all matter. A useful export should make it easy to return to the source page when a learner wants to verify context.&lt;/p&gt;

&lt;h2&gt;
  
  
  The RadNote workflow
&lt;/h2&gt;

&lt;p&gt;A typical RadNote session is deliberately small:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the source page being reviewed.&lt;/li&gt;
&lt;li&gt;Select the teaching points worth revisiting.&lt;/li&gt;
&lt;li&gt;Export Anki-ready notes, PDF study sheets, or case conference slides.&lt;/li&gt;
&lt;li&gt;Keep the source URL and attribution attached to the output.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Design boundary
&lt;/h2&gt;

&lt;p&gt;RadNote is an independent study workflow tool. It is not an official Radiopaedia product. It is designed for selected, reviewed study material rather than automatic bulk collection.&lt;/p&gt;

&lt;p&gt;That boundary matters. It keeps the product closer to a review workflow: capture less, keep context, and make the exported material easier to check later.&lt;/p&gt;

</description>
      <category>chrome</category>
    </item>
    <item>
      <title>Preparing Google Maps Leads for CRM Import with LeadsMap</title>
      <dc:creator>Extension Kit</dc:creator>
      <pubDate>Sat, 04 Jul 2026 16:28:33 +0000</pubDate>
      <link>https://dev.to/web_automationlover_cc88/preparing-google-maps-leads-for-crm-import-with-leadsmap-2hkh</link>
      <guid>https://dev.to/web_automationlover_cc88/preparing-google-maps-leads-for-crm-import-with-leadsmap-2hkh</guid>
      <description>&lt;p&gt;A local lead list is more useful when the records are clean before they reach a CRM. This note covers a simple review flow for teams that collect visible Google Maps business results with &lt;a href="https://www.leadsmap.io/" rel="noopener noreferrer"&gt;LeadsMap&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start with a focused search
&lt;/h2&gt;

&lt;p&gt;Use one city and one business niche at a time. A focused search makes it easier to spot duplicate listings, mixed categories, and records that should not enter the same CRM segment.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Keep CRM fields separate
&lt;/h2&gt;

&lt;p&gt;Before import, keep the business name, website domain, phone number, address, category, rating, review count, and Google Maps link in separate columns. The original map link is useful when a teammate needs to verify the record later.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Clean duplicates before outreach
&lt;/h2&gt;

&lt;p&gt;Group records by website domain and business name. If two listings share the same domain, decide whether they represent one account, multiple locations, or a duplicate.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Preserve source context
&lt;/h2&gt;

&lt;p&gt;Keep city, search term, and category notes with each export. This context helps downstream teams understand why the lead was collected.&lt;/p&gt;

&lt;p&gt;You can install the browser extension from the &lt;a href="https://www.leadsmap.io/how-to-install" rel="noopener noreferrer"&gt;LeadsMap install guide&lt;/a&gt;. I also keep a public checklist for &lt;a href="https://webautomationlover.github.io/leadsmap/crm-import.html" rel="noopener noreferrer"&gt;CRM import prep&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>sales</category>
    </item>
    <item>
      <title>How to turn Google Maps searches into a local business lead list</title>
      <dc:creator>Extension Kit</dc:creator>
      <pubDate>Sat, 04 Jul 2026 14:11:33 +0000</pubDate>
      <link>https://dev.to/web_automationlover_cc88/how-to-turn-google-maps-searches-into-a-local-business-lead-list-5fbi</link>
      <guid>https://dev.to/web_automationlover_cc88/how-to-turn-google-maps-searches-into-a-local-business-lead-list-5fbi</guid>
      <description>&lt;p&gt;When you are doing local outreach, the hardest part is usually not writing the first email or making the first call. It is getting a clean starting list of businesses that match a specific location and niche.&lt;/p&gt;

&lt;p&gt;A practical workflow is to start with a narrow Google Maps search, capture the business fields you actually need, and export everything into a spreadsheet before any outreach happens.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple workflow
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Pick one focused search query, such as &lt;code&gt;dentists in Austin&lt;/code&gt;, &lt;code&gt;coffee shops in Brooklyn&lt;/code&gt;, or &lt;code&gt;roofing companies in Denver&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Open the results in Google Maps and review whether the query is returning the type of businesses you want.&lt;/li&gt;
&lt;li&gt;Capture the core fields: business name, phone, website, address, rating, category, and review count.&lt;/li&gt;
&lt;li&gt;Export the list to CSV so you can deduplicate, filter, tag, and prioritize in a spreadsheet or CRM.&lt;/li&gt;
&lt;li&gt;Before contacting anyone, check the business website and make sure your outreach is relevant and compliant with local rules.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For small lists, doing this manually is fine. For repeated searches, a browser workflow saves a lot of copy-paste time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where LeadsMap fits
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.leadsmap.io/" rel="noopener noreferrer"&gt;LeadsMap&lt;/a&gt; is a Chrome extension built around this workflow. It helps extract business leads from Google Maps searches and export them to CSV. The extension is designed for sales teams, recruiters, agencies, and local prospectors who need structured lists from location-based searches.&lt;/p&gt;

&lt;p&gt;A few useful details:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It works from Google Maps search result pages.&lt;/li&gt;
&lt;li&gt;It can capture fields like name, phone, website, address, rating, category, and more.&lt;/li&gt;
&lt;li&gt;CSV export is available without creating an account.&lt;/li&gt;
&lt;li&gt;The install flow is documented here: &lt;a href="https://www.leadsmap.io/how-to-install" rel="noopener noreferrer"&gt;LeadsMap install guide&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keep the list useful
&lt;/h2&gt;

&lt;p&gt;A bigger list is not always a better list. I usually get better results from smaller, cleaner batches:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;one city at a time;&lt;/li&gt;
&lt;li&gt;one business category at a time;&lt;/li&gt;
&lt;li&gt;remove duplicates before outreach;&lt;/li&gt;
&lt;li&gt;tag leads by intent or fit;&lt;/li&gt;
&lt;li&gt;verify the website before sending anything;&lt;/li&gt;
&lt;li&gt;avoid sending irrelevant bulk messages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point matters. Lead generation tools should help organize public business information, not replace judgment. The best outreach still starts with a clear reason the business might care.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final thought
&lt;/h2&gt;

&lt;p&gt;If your local lead workflow starts with Google Maps and ends in a spreadsheet, a repeatable export process can make the rest of the work easier. Keep the search narrow, keep the CSV clean, and treat the data as a starting point for thoughtful research rather than a shortcut around it.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>tutorial</category>
      <category>javascript</category>
      <category>marketing</category>
    </item>
    <item>
      <title>Installing a Chrome extension from a ZIP: a small safety checklist</title>
      <dc:creator>Extension Kit</dc:creator>
      <pubDate>Sat, 04 Jul 2026 12:08:26 +0000</pubDate>
      <link>https://dev.to/web_automationlover_cc88/installing-a-chrome-extension-from-a-zip-a-small-safety-checklist-3glo</link>
      <guid>https://dev.to/web_automationlover_cc88/installing-a-chrome-extension-from-a-zip-a-small-safety-checklist-3glo</guid>
      <description>&lt;p&gt;I keep a short checklist for any browser extension that is installed from a ZIP file instead of a store listing.&lt;/p&gt;

&lt;p&gt;This is especially useful for small tools, private beta builds, or documentation-first projects where the official install page is the source of truth.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start from the official project page
&lt;/h2&gt;

&lt;p&gt;Do not download a ZIP from a random mirror. Use the project’s own site, docs, or support repository.&lt;/p&gt;

&lt;p&gt;For this workflow, I keep the public install notes here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.hotfansdownload.com/blog/onlyfans_download" rel="noopener noreferrer"&gt;HotFansDownload installation guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.hotfansdownload.com/" rel="noopener noreferrer"&gt;HotFansDownload official site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.massloader.com/" rel="noopener noreferrer"&gt;MassLoader product site&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Unzip locally and inspect the folder
&lt;/h2&gt;

&lt;p&gt;A Chrome ZIP install should usually become a normal extension folder. Before loading it, check that the folder contains expected extension files such as a manifest and readable source assets.&lt;/p&gt;

&lt;p&gt;If the archive expands into a strange nested folder, executable installer, or unrelated files, stop and re-check the source.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Use Chrome's Load unpacked flow
&lt;/h2&gt;

&lt;p&gt;The standard local installation path is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Chrome Extensions.&lt;/li&gt;
&lt;li&gt;Enable Developer mode.&lt;/li&gt;
&lt;li&gt;Choose Load unpacked.&lt;/li&gt;
&lt;li&gt;Select the unzipped extension folder.&lt;/li&gt;
&lt;li&gt;Keep the original ZIP and install page bookmarked for updates.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  4. Keep permissions boring
&lt;/h2&gt;

&lt;p&gt;Read the extension permission screen. The more sensitive the workflow, the more boring the permissions should feel.&lt;/p&gt;

&lt;p&gt;A practical rule: if you cannot explain why a permission is needed, do not continue until you understand it.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Respect access, terms, and ownership
&lt;/h2&gt;

&lt;p&gt;A browser extension does not change what you are allowed to access or use. Use tools only with content and accounts you are permitted to access, and keep local backup workflows aligned with platform terms and applicable laws.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Update from the same source
&lt;/h2&gt;

&lt;p&gt;When a ZIP-based extension updates, return to the official guide instead of searching for a copy. This avoids stale builds and third-party mirrors.&lt;/p&gt;

&lt;p&gt;The same principle applies to product-focused documentation, support, and pricing pages; for MassLoader, the canonical starting point is the &lt;a href="https://www.massloader.com/" rel="noopener noreferrer"&gt;MassLoader website&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A small checklist like this is not glamorous, but it removes most of the avoidable mistakes around manual extension installs.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>tutorial</category>
      <category>productivity</category>
      <category>security</category>
    </item>
  </channel>
</rss>
