Ravelry Pattern Queue Organizer

WHAT IT DOES

This script scans Ravelry pattern queue pages for pattern entries—title, designer, yarn weight, craft type, added date, and notes—and displays a floating organizer panel allowing you to sort, filter, and group patterns by various criteria (craft, yarn weight, added date, priority). It extracts pattern data from the queue list on the page, shows a summary of queue statistics (total patterns, by craft, by yarn weight), and provides controls to organize your queue. You can add custom tags to patterns, mark patterns as "up next" or "in progress," set priority levels (high, normal, low), and export the queue as CSV. All queue organization data—tags, priorities, and statuses—is stored per user locally for reuse across visits.

WHERE IT RUNS

Works on Ravelry pattern queue pages (ravelry.com/your-username/queue or similar). The script scans the page for pattern entries, extracting metadata from the queue list. It is compatible with Ravelry's queue page layout and pattern entry structure.

HOW TO USE

The panel appears automatically when you visit your Ravelry queue page. It detects all patterns in your queue and displays them with their details. Use the "Sort" dropdown to organize patterns by Added Date, Name, Priority, or Craft—click "Apply" to update the view. Use the "Craft" and "Weight" filters to show only specific types of patterns. Each pattern card shows the name, designer, craft, yarn weight, added date, and current status. Click priority buttons (⭐ High, ➖ Normal, ⬇ Low) to set a priority level. Click status buttons (📋 Queued, ⏭ Up Next, ⏳ In Progress) to track your progress. Add custom tags by typing in the tag input and pressing Enter. The summary shows total patterns, craft breakdown, and yarn weight breakdown. Export your organized queue as CSV for offline planning or sharing. Use "Clear Stored Data" to reset all tags, priorities, and statuses for the current domain.

TECHNICAL MECHANISM: PATTERN EXTRACTION WITH METADATA DETECTION AND LOCAL PERSISTENCE

The script scans the page for pattern entries using multiple strategies: it looks for pattern-specific containers (.pattern-item, .queue-item), pattern title links (a[href*="/patterns/"]), and fallback elements containing pattern names. For each pattern, it extracts the name from the link or heading, the designer using "by [Name]" patterns, the yarn weight from text or common weight keywords (lace, fingering, sport, dk, worsted, aran, bulky, super bulky), the craft type from text or common craft keywords (knitting, crochet, weaving, spinning, dyeing), and the added date from date patterns. Pattern data is merged with stored organization data—tags, priority, and status—using the pattern name as the key. Sorting uses a switch statement for each sort type, filtering uses case-insensitive string matching, and the summary calculates statistics from the detected patterns. All organization data is stored in GM_setValue per domain with a structure containing patterns array (with name, tags, priority, status). The panel rebuilds on each action to reflect changes immediately.

THE PANEL

The Ravelry queue organizer appears in a draggable, resizable panel that remembers its position per site. The panel shows a summary card, a filtered and sorted pattern list with action buttons, and control rows for sorting and filtering. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—sort preference, filter preferences, and panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. The script relies on Ravelry's current queue page structure—if Ravelry updates their layout, pattern detection may need updating. The script does not access your Ravelry account credentials or modify your queue on the server—all organization data is stored locally in your browser. Tags, priorities, and statuses are stored per domain using GM_setValue and are not synced across devices. The script only detects patterns that are visible on the page; if your queue has multiple pages, scroll to load all patterns. The CSV export includes all detected patterns with their metadata and your custom organization data.