Content Library

The Content Library provides a centralized repository for reusable content blocks in SPEAR. Teams can create, manage, and insert standardized content across multiple reports while maintaining version history and optional real-time synchronization.

Overview

The Content Library enables:

• Centralized storage of reusable content blocks
• Version history with rollback capabilities
• Import/export for content portability
• Usage tracking across reports
• Linked content that auto-updates when source changes
• Bulk operations for efficient management

Content Types

Global Content

Content blocks available across all reports regardless of service type:

• Executive summary templates
• Standard methodology descriptions
• Compliance boilerplate
• Legal disclaimers
• Company introductions

Service Content

Content specific to service types (e.g., Web Application Testing, Network Penetration):

• Service-specific methodology sections
• Standard scope definitions
• Technology-specific findings templates
• Remediation guidance by service area

Snippets

Small, frequently-used text fragments:

• Standard phrases
• Severity definitions
• Risk rating explanations
• Technical terminology definitions

Key Features

🖥️ Content Library Management Interface Screenshot

Version History

Every content block maintains a complete version history:

Field	Description
Version Number	Sequential version identifier
Created At	Timestamp of version creation
Created By	User who made the change
Content	Full content at that version
Change Notes	Optional description of changes

Version Operations

// Get version history
const history = await contentLibraryService.getHistory(contentId);

// Restore previous version
await contentLibraryService.restoreVersion(contentId, versionId);

Import/Export

Content can be exported and imported as JSON for:

• Backup and recovery
• Sharing between SPEAR instances
• Template distribution
• Migration workflows

Export Format:

{
  "version": "1.0",
  "exportDate": "2024-01-15T10:30:00Z",
  "content": [
    {
      "id": "abc123",
      "title": "Executive Summary Template",
      "type": "global",
      "content": "<p>HTML content...</p>",
      "tags": ["executive", "summary"],
      "metadata": {}
    }
  ]
}

Usage Tracking

Track where content blocks are used across reports:

• Count of reports using each block
• List of specific report references
• Last used timestamp
• Usage frequency metrics

Bulk Operations

Efficiently manage multiple content blocks:

Operation	Description
Bulk Duplicate	Copy multiple blocks at once
Bulk Archive	Move to archive state
Bulk Restore	Restore from archive
Bulk Delete	Permanently remove multiple blocks

Linked Content Blocks

🖥️ Linked Content Blocks with Visual Indicators Screenshot

How Linking Works

When content from the library is inserted into a report, it can be:

1. Copied - Content is duplicated, no ongoing connection
2. Linked - Content maintains connection to source

Linked content displays visual indicators and can auto-update when the source changes.

Link States

State	Description	Visual
Linked	Connected to source, auto-updates	Chain icon
Unlinked	Was linked, now independent	Broken chain
Locked	Linked but protected from auto-update	Lock icon

Auto-Update Behavior

When source content changes:

• Linked blocks update automatically
• Locked blocks retain current content
• Unlinked blocks are not affected

Manual Unlink

Users can manually unlink content to:

• Make local modifications
• Prevent unwanted updates
• Create independent variations

Implementation Reference

frontend/src/lib/components/edra/extensions/linked-content/LinkedContent.js

Content Library Button

🖥️ Content Library Button in Editor Toolbar Screenshot

The editor toolbar includes a Content Library button for inserting content.

Features

• Quick access from editor toolbar
• Tabbed interface: Global | Service-specific
• Search and filter functionality
• Preview before insertion
• Link or copy options

Component Reference

frontend/src/lib/components/edra/shadcn/components/toolbar/ContentLibraryButton.svelte

Usage Flow

1. Click Content Library button in toolbar
2. Browse or search available content
3. Preview selected content
4. Choose “Insert Linked” or “Insert Copy”
5. Content inserted at cursor position

API Operations

Content Library Service

Located at frontend/src/lib/services/content-library.service.ts:

import { contentLibraryService } from '$lib/services/content-library.service';

// Get all content blocks
const content = await contentLibraryService.list();

// Get single block with history
const block = await contentLibraryService.getById(id);

// Create new content
await contentLibraryService.create({
  title: 'New Template',
  content: '<p>Content here</p>',
  type: 'global',
  tags: ['template']
});

// Update content (creates new version)
await contentLibraryService.update(id, {
  content: '<p>Updated content</p>',
  changeNotes: 'Fixed typo in paragraph 2'
});

// Get version history
const history = await contentLibraryService.getHistory(id);

// Restore version
await contentLibraryService.restoreVersion(id, versionId);

// Bulk operations
await contentLibraryService.bulkDuplicate([id1, id2, id3]);
await contentLibraryService.bulkArchive([id1, id2]);
await contentLibraryService.bulkRestore([id1, id2]);
await contentLibraryService.bulkDelete([id1, id2]);

// Export/Import
const exported = await contentLibraryService.exportContent([id1, id2]);
await contentLibraryService.importContent(exportedJson);

// Preview content (with shortcode resolution)
const preview = await contentLibraryService.previewContent(id, context);

// Track usage
await contentLibraryService.trackUsage(contentId, reportId);

Backend API

Backend routes at backend/api/content_library/:

Endpoint	Method	Description
/api/content-library	GET	List all content
/api/content-library	POST	Create content
/api/content-library/{id}	GET	Get single content
/api/content-library/{id}	PATCH	Update content
/api/content-library/{id}	DELETE	Delete content
/api/content-library/{id}/history	GET	Get version history
/api/content-library/{id}/restore/{versionId}	POST	Restore version
/api/content-library/bulk/duplicate	POST	Bulk duplicate
/api/content-library/bulk/archive	POST	Bulk archive
/api/content-library/bulk/restore	POST	Bulk restore
/api/content-library/bulk/delete	POST	Bulk delete
/api/content-library/export	POST	Export content
/api/content-library/import	POST	Import content

Management Interface

Content Library Page

Access via Reports > Content Library

Features:

• Grid/list view toggle
• Filter by type (global, service, snippet)
• Search by title and tags
• Sort by name, date, usage
• Bulk selection and operations

Routes

• Management: frontend/src/routes/console/reports/content-library/+page.svelte

Creating Content

1. Click New Content
2. Select content type
3. Enter title and tags
4. Edit content in rich text editor
5. Save to create first version

Editing Content

1. Select content block from list
2. Click Edit
3. Make changes in editor
4. Optionally add change notes
5. Save to create new version

Viewing History

🖥️ Version History Interface Screenshot

1. Select content block
2. Click History tab
3. View list of versions with metadata
4. Click version to preview
5. Click Restore to revert

Shortcode Support

Content blocks support shortcodes for dynamic values:

<p>This report was prepared for {{client.name}}
   on {{report.date}}.</p>

Available Shortcodes

Category	Examples
Client	{{client.name}}, {{client.contact}}
Project	{{project.name}}, {{project.dates}}
Report	{{report.title}}, {{report.date}}
Organization	{{org.name}}, {{org.address}}

Resolution

Shortcodes are resolved:

• During PDF export
• In preview mode
• When viewing in report context

Best Practices

Organize with Tags

Use consistent tagging:

• Content type: template, boilerplate, snippet
• Service area: webapp, network, physical
• Section: executive, methodology, findings

Write for Reuse

Content should be:

• Generic enough to apply across reports
• Use shortcodes for variable data
• Avoid report-specific references

Version Strategically

• Add change notes for significant updates
• Review impact before updating linked content
• Consider duplicating before major changes

Monitor Usage

• Regularly review usage statistics
• Archive unused content
• Update frequently-used content carefully

Link vs. Copy

Use Linking when:

• Content should stay synchronized
• Updates should propagate automatically
• Consistency is critical

Use Copying when:

• Content will be customized
• Independence is preferred
• Historical accuracy matters

Technical References

Resource	Location
Content library service	frontend/src/lib/services/content-library.service.ts
LinkedContent extension	frontend/src/lib/components/edra/extensions/linked-content/LinkedContent.js
ContentLibraryButton	frontend/src/lib/components/edra/shadcn/components/toolbar/ContentLibraryButton.svelte
Backend API	backend/api/content_library/
Management page	frontend/src/routes/console/reports/content-library/+page.svelte