New in VaultBook: Sections, Links, Images, and Smart Expiry

There is a moment in the life of every note-taking system when the tool either grows with the user or the user outgrows the tool. The early days are simple - a title, a body, a quick thought captured and saved. The tool feels light, fast, and perfectly adequate. But professional knowledge does not stay simple. The project plan that began as three bullet points evolves into a multi-phase initiative with dependencies, deliverables, and stakeholder commitments. The research note that started as a single observation grows into a structured argument with evidence, counterpoints, and bibliographic references. The client file that was once a name and a phone number becomes a living record of meetings, agreements, analyses, and attached documents spanning months or years.

At that inflection point, most note-taking tools reveal their limitations. The entry that needs internal structure has none - just a scrolling wall of text where the project timeline runs into the risk assessment which runs into the meeting notes which runs into the action items. The note that needs to reference an image has no way to display it inline - the image exists as a separate file somewhere else, disconnected from the analysis it supports. The entry that should expire after its relevance window closes lingers indefinitely, cluttering the knowledge base with outdated content that the professional must mentally filter with every search and every browse.

VaultBook was designed to grow with the professional rather than constrain them. The features highlighted in this update - sections for internal entry structure, rich links and embedded images for connected visual knowledge, a sixty-day purge policy for secure deletion, and expiry limits for time-sensitive information - represent a significant deepening of VaultBook’s capability. They transform each entry from a flat container for text into a structured, visual, time-aware knowledge unit that serves the professional’s needs today and adapts to the complexity that tomorrow’s work will demand.

Sections: The Internal Architecture That Professional Entries Need

The most consequential feature in this update is the introduction of sections within entries. Sections transform the fundamental unit of VaultBook’s knowledge architecture from a monolithic text block into a structured document with independently navigable, independently expandable, and independently attachable components.

Each section has its own title, its own rich text body, and its own independent attachments. Sections collapse and expand as accordions, with clip count badges indicating the attachment density within each section. This means that a complex entry - one that documents a multi-faceted professional situation requiring structured internal organization - can present its components in a clear, navigable hierarchy rather than as a continuous scroll of undifferentiated text.

The practical implications for different professional domains are immediately apparent.

A medical professional documenting a patient encounter can create sections for the chief complaint, the history of present illness, the review of systems, the physical examination, the assessment, and the plan. Each section holds its own formatted content - the examination findings in one section, the diagnostic reasoning in another, the treatment plan in a third. Each section can hold its own attachments - the lab report PDF attached to the assessment section, the imaging reference attached to the examination section, the patient education materials attached to the plan section. When the physician returns to this entry weeks later for a follow-up, they can expand just the assessment and plan sections to review the prior clinical reasoning without scrolling through the complete examination documentation.

An attorney managing a complex matter can create sections for the factual background, the legal analysis, the strategic recommendations, the client communications, and the document references. The legal analysis section might contain the formatted argument with case citations, while the document references section holds attached PDFs of the key authorities. When preparing for a hearing, the attorney expands only the legal analysis and strategic recommendations sections, accessing exactly the material they need without navigating through the factual background or client communications.

A project manager overseeing a multi-phase initiative can create sections for the current status, the risk register, the decision log, the stakeholder map, and the action items. Each section serves a distinct function in the project management workflow. The weekly status meeting requires expanding the current status and action items sections. The quarterly risk review requires expanding the risk register section. The decision audit requires expanding the decision log section. No meeting requires scrolling through the entire entry to find the relevant component.

A researcher building a literature review can create sections for the source summary, the key findings, the methodological critique, the connections to other research, and the direct quotations. The source summary provides quick orientation. The methodological critique informs the researcher’s assessment of the evidence quality. The connections section maps the research into the broader intellectual framework. Each section can hold attached PDFs of the referenced papers, screenshots of key figures, and formatted analytical commentary.

The section architecture does not impose a specific structure on any domain. The professional defines the sections that make sense for their entry, names them according to their own conventions, and populates them with whatever combination of formatted text and attachments their work requires. The structure emerges from the professional’s understanding of their content rather than from a template imposed by the tool.

This flexibility is essential because professional knowledge is diverse in its structural requirements. A financial analyst’s quarterly review entry might need sections for market conditions, portfolio performance, risk exposures, and recommended adjustments. An educator’s course planning entry might need sections for learning objectives, lecture outline, reading assignments, assessment design, and student feedback from the prior semester. A compliance officer’s audit finding entry might need sections for the finding description, the regulatory reference, the risk assessment, the remediation plan, and the verification evidence. A software engineer’s architecture decision record might need sections for the context, the decision, the alternatives considered, the consequences, and the implementation notes.

Each of these professionals can create exactly the section structure their work demands, without adapting their thinking to fit a predetermined template. The sections are as numerous or as few as the entry requires. They can be reordered by the professional’s preference. They can be expanded or collapsed independently, allowing the professional to focus on exactly the component they need at any given moment. The clip count badges on each collapsed section indicate at a glance which sections contain attached files, providing navigational intelligence without requiring expansion.

The attachment independence of sections deserves particular emphasis. In most note-taking applications, attachments belong to the entry as a whole - a flat list of files associated with the entire note, with no structural relationship between specific attachments and specific parts of the note’s content. In VaultBook, attachments can be added to individual sections, creating a direct association between the file and the specific content component it supports. The lab report PDF is attached to the assessment section, not floating in a generic attachment list. The contract draft is attached to the commercial terms section, not mixed with technical specification PDFs in an undifferentiated file collection. This structural precision makes the knowledge unit self-documenting - the organization of attachments within sections communicates the role each file plays in the entry’s analytical structure.

The rich text editor within each section provides the complete formatting toolkit. Bold, italic, underline, and strikethrough handle emphasis and editorial conventions. Ordered and unordered lists support structured content - action items, requirement lists, procedural steps, and reference compilations. Headings from H1 through H6 enable hierarchical organization within sections for entries that require deep internal structure. The font family selector supports typographic variety. Case transformation handles uppercase, lowercase, title case, and sentence case conversions. Text color and highlight color pickers provide visual categorization and emphasis within section content.

Tables with size picker and context menu operations handle structured data within sections - comparison matrices, tracking tables, analytical frameworks, and data summaries. Code blocks with language labels serve technical professionals who document alongside code, configurations, or technical specifications. Callout blocks with accent bars and title headers provide visual prominence for critical findings, important warnings, or key decisions within each section. Markdown rendering through the marked.js library supports professionals who prefer plain-text composition with formatted output.

Rich Links and Embedded Images: Visual Knowledge Comes Home

Professional thinking is not exclusively textual. The architect’s knowledge includes floor plans and elevation drawings. The physician’s knowledge includes imaging studies and anatomical references. The data analyst’s knowledge includes charts and dashboards. The designer’s knowledge includes mood boards and reference compositions. The engineer’s knowledge includes schematics and test result plots. The researcher’s knowledge includes figures, tables, and data visualizations from published literature.

A note-taking tool that handles only text forces the professional to maintain a parallel visual archive - images in a folder, screenshots in a camera roll, diagrams in a drawing application - disconnected from the textual analysis that gives them meaning. The professional writes about a design decision in one place and stores the diagram that informed it in another. The written analysis and the visual evidence exist in separate systems, requiring the professional to mentally reconstruct their connection every time either is consulted.

VaultBook’s support for embedded images within entries eliminates this fragmentation. Images can be inserted directly into the rich text flow of an entry or a section, appearing inline alongside the written content that references them. A physician writing about a diagnostic finding can embed the relevant imaging study screenshot directly beneath the written assessment. An architect documenting a design rationale can embed the floor plan directly alongside the written explanation of the spatial choices. A data analyst writing about a trend can embed the chart that visualizes the trend directly within the analytical narrative.

The visual and the textual coexist in the same entry, the same section, the same document flow. The professional does not need to switch between applications, navigate to a separate folder, or maintain a mental mapping between text references and image locations. The knowledge unit is complete - text and image together, structured within sections, organized within the vault’s hierarchical and categorical systems.

Rich links extend this connectivity beyond the visual. Entries can contain clickable links to related resources - external references, internal vault entries, documentation URLs, or any other addressable resource that provides context for the entry’s content. A researcher can link to the published source of a finding they are discussing. A project manager can link to the shared documentation that a project reference points to. An attorney can link to the regulatory text that a compliance analysis interprets. The link exists within the entry’s rich text flow, accessible with a click, integrated into the narrative rather than appended as a separate reference list.

The combination of sections, embedded images, and rich links transforms VaultBook entries from text notes into genuinely rich knowledge documents. A single entry can contain multiple structured sections, each with formatted text, embedded images, clickable links, and independent file attachments. The entry becomes a self-contained knowledge unit that captures not just what the professional knows but the visual evidence, the source connections, and the documentary materials that support and contextualize that knowledge.

Consider the practical richness this enables. A pharmaceutical researcher’s drug interaction entry might contain a section summarizing the interaction mechanism with an embedded molecular diagram, a section documenting the clinical evidence with linked references to the published trials and attached PDFs of the source papers, a section analyzing the dosing implications with an embedded chart showing dose-response relationships, and a section recording the formulary recommendation with an attached PDF of the formulary committee’s decision document. Every dimension of the knowledge - textual analysis, visual evidence, source links, and documentary attachments - coexists in a single structured entry that is fully searchable, fully organized, and fully private.

A civil engineer’s project entry might contain a section for structural calculations with embedded diagrams and attached spreadsheets, a section for site conditions with embedded photographs and linked survey reports, a section for regulatory compliance with linked building codes and attached permit documents, and a section for project timeline with embedded Gantt chart screenshots and attached schedule files. The complete project knowledge lives in one place, structured for navigability, enriched with visual and documentary materials, and protected by VaultBook’s offline encrypted architecture.

The Sixty-Day Purge Policy: Security Through Managed Deletion

The lifecycle of information does not end with creation and storage. Professional information has a temporal dimension - some content is permanently valuable, some is relevant for a specific period, and some should not exist at all after its purpose has been served. A note-taking tool that treats all content as permanently retained fails the professional whose compliance obligations, security requirements, or organizational policies require managed deletion.

VaultBook’s sixty-day purge policy addresses this requirement with a design that balances recovery safety against security assurance. When an entry is marked for deletion, it enters a sixty-day retention period during which the content remains recoverable - protecting against accidental deletion, hasty decisions made under time pressure, and the common experience of deleting something that turns out to be needed a week later. After the sixty-day period, the content is permanently and automatically removed - ensuring that sensitive data does not linger indefinitely in the vault after the professional has determined that it should be eliminated.

This managed deletion lifecycle serves multiple professional contexts. Healthcare professionals operating under data minimization principles can delete patient-specific notes after the clinical purpose has been served, knowing that the data will be permanently removed after the retention period. Legal professionals managing matter files can delete work product after case resolution, with confidence that the deletion will be enforced automatically. Financial professionals handling time-limited client data can delete sensitive information after the engagement concludes. Compliance officers can demonstrate that their data retention practices include automated deletion enforcement rather than relying solely on manual processes that may be inconsistently applied.

The purge policy works alongside VaultBook’s broader data lifecycle features. Expiry dates on entries surface time-sensitive content through sidebar badges and the Expiring tab, ensuring that the professional is aware of approaching deadlines before content becomes stale. Due dates track upcoming obligations. Repeat and recurrence settings handle recurring documentation tasks. Together, these temporal features create a time-aware knowledge management system where content is not just stored and organized but actively managed across its entire lifecycle from creation through relevance to disposal.

Expiry Limits: Time-Sensitive Knowledge Made Visible

Not all knowledge has the same temporal relevance. A pharmaceutical formulary entry is valid until the next formulary revision. A client proposal is valid until its stated expiration date. A compliance certification is valid until its renewal deadline. A competitive analysis is relevant until market conditions change. A travel itinerary is relevant until the trip concludes. A meeting agenda is relevant until the meeting happens.

Most note-taking tools treat all entries as equally permanent. The expired proposal sits alongside the current proposal. The outdated compliance certification appears in search results alongside the current one. The completed travel itinerary occupies the same organizational space as the upcoming one. The professional must mentally filter for temporal relevance with every interaction with their knowledge base - a cognitive overhead that grows with every expired entry that accumulates.

VaultBook’s expiry limits make temporal relevance explicit and visible. When the professional sets an expiry date on an entry, VaultBook tracks the approaching deadline and surfaces visual indicators - badges showing “Expiring soon” as the date approaches and “Expired” after it passes. The sidebar’s Expiring tab collects all entries with approaching expiry dates into a single temporal view, providing an at-a-glance dashboard of what needs attention before it expires.

This visibility serves both proactive and reactive workflows. Proactively, the professional reviewing the Expiring tab before the start of each week can identify entries requiring action - certifications that need renewal, proposals that need updating, time-sensitive analyses that need refreshing. Reactively, the expired badges on entries encountered during search or browsing signal that the content may no longer be current, preventing the professional from acting on outdated information.

For compliance-driven environments, expiry limits provide documented evidence that time-sensitive information is actively monitored and managed. The organization that can demonstrate systematic expiry tracking across its knowledge management practices shows a level of data governance maturity that ad-hoc manual tracking cannot achieve.

The combination of expiry limits and the sixty-day purge policy creates a complete data lifecycle management capability within VaultBook. The professional creates an entry with an expiry date when the content has a known relevance window. As the expiry date approaches, the Expiring tab and visual badges surface the entry for attention. After the expiry date passes, the professional can review the expired content, decide whether to extend its relevance by updating the expiry date, or mark it for deletion. Once marked for deletion, the sixty-day purge policy ensures automatic permanent removal. At every stage, the professional maintains control - nothing is deleted without their initiation, but once deletion is initiated, the enforcement is automatic and reliable.

This lifecycle management is particularly important for professionals in regulated industries. HIPAA requires documented data retention and disposal practices. Financial regulations require evidence of systematic record management. Legal professional responsibility rules require appropriate retention and destruction of client materials. Corporate governance standards require documented information lifecycle policies. VaultBook’s combination of expiry tracking, deletion initiation, and automated purge enforcement provides the technical foundation that these regulatory frameworks require.

How Sections, Images, Links, and Expiry Work With Everything Else

These features do not exist in isolation. They integrate with every other capability in VaultBook’s architecture, creating compound capabilities that exceed what any individual feature provides alone.

Sections integrate with search. VaultBook’s Ask a Question feature in the QA sidebar assigns a weight of three to section text, ensuring that content within sections contributes to search relevance. The professional who searches for a term that appears in a specific section of an entry finds that entry through the search system, even if the term does not appear in the entry’s title or main body. Section text carries a weight of three in the scoring system where titles carry eight, labels carry six, inline OCR text carries five, and body content carries four. This weighting ensures that section content is discoverable while reflecting its role as a component of the entry rather than its primary identifier.

Section attachments integrate with deep file indexing. Attachments added to sections are indexed by the same deep extraction systems that handle entry-level attachments. PDF text extraction via pdf.js handles contracts, specifications, reports, and regulatory filings attached to individual sections. XLSX and XLSM extraction via SheetJS handles spreadsheets attached to analytical sections. PPTX extraction via JSZip handles presentation materials. ZIP archive indexing and MSG email parsing apply equally to section attachments. OCR of embedded images within these documents - images inside ZIP archives, rendered pages from scanned PDFs, images embedded inside DOCX and XLSX files - all extend to section-level attachments. The specification PDF attached to the technical analysis section of an engineering entry is as searchable as a PDF attached at the entry level. The scanned legacy document attached to a historical reference section has its pages OCR-processed into searchable text. Section attachment content carries a weight of one in the QA scoring system, ensuring that it contributes to search results while reflecting its position as deeply nested content. Background warm-up ensures that section-level attachment text for top search results is pre-loaded for scoring. File extension bucketing groups all attachments by type across both entry-level and section-level positions.

Embedded images integrate with inline OCR. Images embedded within entry text or section text are processed by VaultBook’s automatic OCR system, which extracts text from images, caches it per item, and indexes it for search with a weight of five. A screenshot embedded in a research note, a photograph of a whiteboard embedded in a meeting record, or a chart image embedded in an analytical report - each becomes searchable text within the vault through OCR processing that happens automatically and locally.

Typeahead search provides real-time dropdown suggestions as the professional types, searching across titles, details, labels, attachment names, section content, and OCR-extracted text. The professional who remembers embedding a specific diagram in an entry months ago can type a keyword from the diagram’s text labels and see matching entries appear in the typeahead suggestions. Query suggestions from history surface recurring retrieval patterns.

Vote-based reranking allows the professional to upvote results they find genuinely useful and downvote irrelevant ones, training the relevance engine to prioritize entries that serve their actual workflow. All votes are stored locally in the repository and persist across sessions. Related Entries surface contextual similarity suggestions when browsing any entry - including entries with rich section structures. The professional reading a structured project entry with multiple sections might see related entries suggesting similar projects, relevant reference materials, or prior analyses that share thematic connections. Smart Label Suggestions analyze entry content including section text and suggest relevant labels as pastel-styled chips with frequency counts, accelerating categorization.

Expiry dates integrate with the sidebar time tabs. The Expiring tab in the sidebar collects all entries with approaching expiry dates, providing temporal navigation alongside the Recent tab for recently modified entries and the Due tab for entries with approaching deadlines. The professional can switch between temporal views to see what was recently worked on, what is coming due, and what is about to expire - three complementary temporal perspectives on their knowledge base.

Expiry dates integrate with the AI Suggestions carousel. The first page of the four-page suggestions carousel shows upcoming scheduled entries alongside weekday reading patterns, and entries with approaching expiry dates may surface as relevant items that the professional should attend to on the current day of the week. The intelligence learns the professional’s personalized relevance distribution across their library, and expiring content factors into that relevance assessment.

Sections integrate with version history. When VaultBook creates per-entry snapshots in the local versions directory with sixty-day retention, the snapshots capture the complete section structure of the entry at the point of save. The professional reviewing version history sees the evolution of the entry’s internal structure - sections added, section content revised, section attachments updated - providing a complete audit trail of how the structured entry developed over time.

The Organizational Context That Surrounds These Features

Sections, images, links, and expiry operate within VaultBook’s comprehensive organizational architecture, which provides the structural context that makes individual entry features useful at scale.

Pages provide hierarchical notebook organization with unlimited nesting depth. Nested parent-child trees with disclosure arrows, drag-and-drop reordering, page context menus, page icons, and color dots create an intuitive navigational framework for knowledge bases of any size. Activity-based sorting surfaces the most active organizational areas. The All Pages root view provides a comprehensive overview.

Labels provide cross-cutting categorical organization independent of the page hierarchy. Color-coded label pills enable instant filtering by any combination of categories. The professional who labels entries by urgency, domain, project, or status gains multidimensional navigation that works alongside the page hierarchy.

Inline hashtags within entry content are used by the Kanban Board tool to auto-generate workflow columns. Favorites provide a dedicated quick-access panel. Pagination with configurable items per page keeps the interface manageable at scale. Sort controls with multiple sort fields and order toggle provide complete presentational control.

Multi-Tab Views allow multiple entry list tabs open simultaneously, each maintaining independent page filter, label filter, search state, and sort configuration. The professional comparing structured entries from different projects or domains - each with their own sections, images, and expiry dates - can work across concurrent views without losing context.

Advanced Filters provide compound query dimensions including file type filtering with match-any or match-all logic and date field filtering with configurable ranges. The professional who needs to find all entries with attached PDFs expiring in the next thirty days and carrying a specific project label produces that targeted view in a single filter operation.

The Random Note Spotlight surfaces a randomly selected entry hourly, occasionally rediscovering a structured entry with sections, images, and approaching expiry that the professional had not revisited recently - providing the serendipitous reconnection with older content that makes a knowledge base more than a filing system.

Privacy and Encryption: Structure That Stays Secure

The structural richness that sections, images, links, and expiry provide does not compromise VaultBook’s privacy architecture. Every feature operates within the same offline-first, locally stored, optionally encrypted environment that defines VaultBook’s security model.

VaultBook runs entirely offline, accessing a local folder through the browser’s File System Access API. No content - including section content, embedded images, linked resources, or expiry metadata - is transmitted to any server at any point. The application functions identically whether the device is connected to the internet or completely isolated.

Per-entry encryption uses AES-256-GCM with PBKDF2 key derivation at one hundred thousand iterations of SHA-256. Each encryption operation generates a random sixteen-byte salt and a twelve-byte initialization vector. The encryption protects the complete entry including its sections, its metadata, and its organizational references. There is no master key, no recovery mechanism, and no server holding any key material. Session password caching preserves workflow fluidity. The lock screen provides full-page blur with pointer-event blocking.

The storage architecture remains transparent and portable. The vault is a local folder. Repository state lives in repository.json as human-readable JSON. Entry bodies including section content are stored as sidecar markdown files. Attachments including section attachments are stored as files in original formats with a JSON manifest. Version history snapshots capture the complete section structure as standard markdown. Every piece of data is in an open format that can be inspected, backed up, and migrated without VaultBook running.

The save system protects structured entries through autosave with dirty flag tracking and debouncing, a concurrent-write guard preventing corruption, a status badge confirming save state, and a close confirmation dialog preventing accidental loss.

The Built-In Tools: Structure Meets Workflow

VaultBook’s thirteen built-in professional tools complement the structural capabilities that sections, images, links, and expiry provide.

The Kanban Board auto-generates from vault labels and inline hashtags, providing visual workflow management for entries that may now contain complex section structures. The File Analyzer processes CSV and TXT data files locally. The Reader manages RSS and Atom feeds. The Threads tool provides rapid sequential capture. The Save URL to Entry tool captures web content. The PDF tools handle document operations. The MP3 Cutter and Joiner handles audio. The File Explorer navigates attachments - including section-level attachments - by type, entry, or page. The Photo and Video Explorer scans media folders. The Password Generator creates credentials locally. The Folder Analyzer provides storage visibility. The Import from Obsidian tool migrates markdown notes.

Every tool operates within the vault’s local architecture, keeping all professional content - structured entries with sections and images included - completely private and completely under the professional’s control.

Analytics: Visibility Into a Richer Knowledge Base

VaultBook’s analytics reflect the growing richness of the knowledge base as sections, images, and time-aware entries accumulate. The basic analytics sidebar shows total entry count, entries with attached files, total file count, and total storage size. As section-level attachments and embedded images grow within the vault, these metrics capture the expanding multimedia depth of the professional’s knowledge practice.

The four canvas-rendered analytics charts provide behavioral and organizational insight into the increasingly structured knowledge base. The Last Fourteen Days Activity line chart reveals documentation rhythm across the preceding two weeks. The Month Activity chart extends this temporal view to three months. The Label Utilization pie chart shows how the professional’s categorical vocabulary distributes across the vault. The Pages Utilization pie chart shows how entries distribute across the hierarchical organizational structure. File type breakdown chips show attachment composition including the images embedded within entries. All analytics are computed locally and visible only within the vault.

Built to Evolve

The introduction of sections, rich links, embedded images, smart expiry, and the sixty-day purge policy represents a significant maturation of VaultBook’s knowledge management capability. But these features are not endpoints - they are foundations. Each deepens the structural, visual, temporal, and lifecycle dimensions of what VaultBook entries can represent, and each integrates with the existing architecture of search, organization, encryption, analytics, and tools to create compound capabilities that grow more powerful as the professional’s knowledge base grows more complex.

VaultBook was built to evolve alongside the professionals who use it. The knowledge base that begins with simple text entries grows into a richly structured, visually integrated, temporally managed, deeply searchable, strongly encrypted private knowledge system - and VaultBook grows with it at every step.

The onboarding experience reflects this evolution-friendly design. The storage tutorial for first-time users explains the local folder architecture transparently. The floating action button provides quick entry creation from anywhere in the application. The responsive layout adapts from desktop to tablet to mobile. The light theme with CSS custom properties provides a clean aesthetic for extended working sessions. Frosted glass effects and smooth transitions add visual refinement. The interface invites the new user to begin simply and discover structural depth as their needs grow.

For multi-device access, the vault folder can be placed inside a Dropbox, OneDrive, iCloud, or organizational server directory. VaultBook itself never initiates synchronization. The professional controls when, how, and through what channel their structured, image-rich, time-managed entries move between devices. The vault’s transparent storage - repository.json for state, sidecar markdown files for entry bodies including section content, original-format files for attachments, and standard markdown for version history - ensures that the complete richness of structured entries is preserved across every backup, migration, and archival operation.

Your knowledge deserves structure as sophisticated as your thinking. VaultBook is built to provide it.