{"id":29906,"date":"2026-08-30T08:00:00","date_gmt":"2026-08-30T07:00:00","guid":{"rendered":"https:\/\/e-lia.io\/?p=29906"},"modified":"2026-08-21T16:11:58","modified_gmt":"2026-08-21T15:11:58","slug":"how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library","status":"publish","type":"post","link":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/","title":{"rendered":"How do you move from separate toolbox files to one central toolbox library?"},"content":{"rendered":"<p>You move from separate toolbox files to one central toolbox library by auditing what you already have, choosing a single hosting platform, and building a clear folder structure with defined ownership before migrating any content. The shift matters most for organisations where <a href=\"https:\/\/e-lia.io\/en\/toolbox-talks\/\">toolbox talks are spread across email inboxes<\/a>, shared drives, USB sticks, and printed binders, making it hard to know which version is current or who has actually read what. The sections below walk through each step of that process, from diagnosing the problem to measuring whether the library is genuinely being used.<\/p>\n<h2>Why do separate toolbox files become unmanageable over time?<\/h2>\n<p>Separate toolbox files become unmanageable because they multiply without a single owner, drift out of sync with each other, and leave no reliable way to confirm which version is current. When every team leader saves their own copy of a toolbox talk, you quickly end up with dozens of near-identical files that differ only in small but potentially important details, and nobody has a complete picture of what exists.<\/p>\n<p>The practical consequences build up gradually. A safety coordinator updates a toolbox on working at height, but the site manager is still using last year&#8217;s version saved to a local drive. A new colleague joins and receives a PDF that was already outdated when it was printed. Someone requests proof that a specific topic was covered, and the search through folders, email threads, and WhatsApp chats takes hours rather than minutes.<\/p>\n<p>Three patterns tend to accelerate the problem:<\/p>\n<ul>\n<li><strong>Version sprawl:<\/strong> Files get renamed with suffixes like &#8220;final,&#8221; &#8220;final v2,&#8221; or &#8220;updated March&#8221; without a clear system, so the actual current version becomes ambiguous.<\/li>\n<li><strong>Format inconsistency:<\/strong> Some toolbox files are PDFs, others are PowerPoint decks, others are Word documents or printed sheets. Different formats make it hard to apply a consistent structure or track engagement.<\/li>\n<li><strong>No central ownership:<\/strong> When everyone can save and share toolbox files independently, nobody is responsible for keeping the collection coherent, which means gaps and duplicates accumulate unchecked.<\/li>\n<\/ul>\n<p>The result is a toolbox library that exists in practice but not in name: scattered, inconsistent, and difficult to rely on when you need to demonstrate that safety topics have been covered.<\/p>\n<h2>What should a central toolbox library actually contain?<\/h2>\n<p>A central toolbox library should contain all active toolbox talks organised by topic, a version history for each file, clear metadata showing who owns each item and when it was last reviewed, and a record of which teams or individuals have completed each talk. The library is not just a file store; it is a structured resource that supports both delivery and documentation.<\/p>\n<p>In practical terms, a well-built toolbox library typically includes:<\/p>\n<ul>\n<li><strong>Topic-organised content:<\/strong> Toolbox talks grouped by theme, such as working at height, manual handling, hazardous materials, machinery safety, and emergency procedures.<\/li>\n<li><strong>Standardised file formats:<\/strong> A consistent format for every talk, whether that is a short video, a slide deck, or a structured text module, so users know what to expect and delivery is predictable.<\/li>\n<li><strong>Version control:<\/strong> Each file carries a version number and a review date, so it is always clear which is the current approved version and when it is due for an update.<\/li>\n<li><strong>Ownership and review schedule:<\/strong> Every topic has a named owner responsible for keeping it accurate and flagging when circumstances change.<\/li>\n<li><strong>Participation records:<\/strong> A log showing which employees completed which toolbox talk, when, and whether they passed any associated knowledge check.<\/li>\n<li><strong>Language variants:<\/strong> For organisations with multilingual teams, translated versions of each talk stored alongside the original.<\/li>\n<\/ul>\n<p>The library should also distinguish between evergreen content that stays relevant year after year and time-sensitive content tied to specific projects, seasons, or regulatory updates. Keeping these categories separate makes maintenance much easier.<\/p>\n<h2>How do you audit and categorise existing toolbox files before migrating?<\/h2>\n<p>Before migrating, collect every toolbox file from every location, remove duplicates, identify the most current version of each topic, and assign each surviving file to a category. This audit step is what prevents you from simply moving the mess from one place to another.<\/p>\n<p>A practical audit follows these steps:<\/p>\n<ol>\n<li><strong>Collect everything:<\/strong> Ask all team leaders, safety coordinators, and department heads to submit every toolbox file they use, regardless of format or age. Include shared drives, email attachments, printed materials, and anything stored on personal devices.<\/li>\n<li><strong>Create a master inventory:<\/strong> List every file in a simple spreadsheet with columns for topic, format, date created or last modified, source, and language.<\/li>\n<li><strong>Identify duplicates and near-duplicates:<\/strong> Group files that cover the same topic and compare them. Flag which version is most current and most accurate.<\/li>\n<li><strong>Assess quality:<\/strong> For each surviving file, check whether the content is still accurate, whether it matches your current working practices, and whether it meets the format standard you want to apply going forward.<\/li>\n<li><strong>Categorise by topic and audience:<\/strong> Assign each approved file to a topic category and note which teams or roles it applies to.<\/li>\n<li><strong>Flag gaps:<\/strong> Note topics that your organisation covers in practice but for which no good toolbox file currently exists. These become items to create after migration.<\/li>\n<\/ol>\n<p>The audit often reveals that organisations have far fewer unique, usable toolbox talks than they thought. Many files turn out to be duplicates or outdated versions. That is a useful finding: it means the library you actually need to build is smaller and more manageable than the raw file count suggested.<\/p>\n<h2>What platform or tool should you use to host a central toolbox library?<\/h2>\n<p>The right platform for a central toolbox library is one that your employees will actually use, that makes delivery and tracking straightforward, and that fits the way your teams work day to day. For office-based teams with reliable computer access, a shared intranet or document management system can work. For operational, field-based, or multilingual teams, a mobile-first solution is a better fit.<\/p>\n<p>When evaluating platforms, consider these factors:<\/p>\n<ul>\n<li><strong>Accessibility:<\/strong> Can every employee reach the library without a company laptop or a complex login? For workers on the floor or in the field, friction at the access point means the library goes unused.<\/li>\n<li><strong>Delivery mechanism:<\/strong> Does the platform let you push toolbox talks to employees, or do employees have to remember to go looking? Active delivery is more reliable than passive availability.<\/li>\n<li><strong>Participation tracking:<\/strong> Does the platform record who completed each talk, when, and with what result? Without this, the library supports delivery but not documentation.<\/li>\n<li><strong>Version control:<\/strong> Can you update a toolbox talk and be confident that everyone receives the new version rather than an old cached copy?<\/li>\n<li><strong>Language support:<\/strong> If your workforce includes speakers of multiple languages, can the platform serve each person content in their preferred language?<\/li>\n<li><strong>Integration:<\/strong> Does the platform connect with your HR system or existing learning management tools so that records stay consistent across systems?<\/li>\n<\/ul>\n<p>Common options range from SharePoint and Google Drive for simpler document-based libraries, to dedicated learning management systems for more structured programmes, to mobile-first platforms that deliver content through channels employees already use daily, such as WhatsApp.<\/p>\n<h2>How do you keep a central toolbox library up to date?<\/h2>\n<p>You keep a central toolbox library up to date by assigning a named owner to every topic, setting a review schedule for each file, and building a process for flagging urgent updates when working conditions or regulations change. A library without active maintenance becomes outdated faster than the scattered files it replaced.<\/p>\n<p>The most practical approach combines scheduled reviews with event-triggered updates:<\/p>\n<ul>\n<li><strong>Scheduled reviews:<\/strong> Set a review date for every toolbox talk at the point of creation. Topics tied to stable, well-established practices may need reviewing less frequently than those linked to equipment, chemicals, or procedures that change more often. The review date should be visible in the library so owners are prompted before content becomes stale.<\/li>\n<li><strong>Event-triggered updates:<\/strong> Define the events that automatically trigger a review, such as a near-miss incident, a change in working method, new equipment being introduced, or updated guidance from a relevant authority. Make it easy for anyone in the organisation to flag that a toolbox talk may need updating.<\/li>\n<li><strong>Clear ownership:<\/strong> Every topic in the library should have a named owner, typically a safety coordinator, team leader, or subject matter expert. Ownership without accountability does not work, so the owner&#8217;s name should be visible in the library alongside the review date.<\/li>\n<li><strong>Change log:<\/strong> Keep a brief record of what changed in each version and why. This helps anyone using the library understand whether a recent update affects how they deliver the talk.<\/li>\n<\/ul>\n<p>If your library includes content from an external provider, check how updates are handled on their side. Some providers refresh their content libraries regularly and push updates automatically; others require you to download new versions manually.<\/p>\n<h2>How do you measure whether your toolbox library is actually being used?<\/h2>\n<p>You measure toolbox library usage by tracking completion rates per talk, monitoring which topics are being delivered and which are being skipped, and reviewing participation data across teams and time periods. Without measurement, a central library can look organised on the surface while remaining largely unused in practice.<\/p>\n<p>Useful metrics to track include:<\/p>\n<ul>\n<li><strong>Completion rate per talk:<\/strong> What percentage of the intended audience completed each toolbox talk? Low completion on a specific topic may indicate a delivery problem, a relevance issue, or a gap in access.<\/li>\n<li><strong>Coverage across topics:<\/strong> Are certain categories of toolbox talk being delivered regularly while others are consistently skipped? Gaps in coverage are worth investigating.<\/li>\n<li><strong>Team and location breakdowns:<\/strong> Are some teams or sites engaging with the library significantly less than others? This can point to a local access or adoption problem rather than a platform-wide issue.<\/li>\n<li><strong>Knowledge check results:<\/strong> If your toolbox talks include a short knowledge check, track scores over time. Consistently low scores on a particular topic may suggest the content needs to be clearer or the talk needs to be repeated.<\/li>\n<li><strong>Library access patterns:<\/strong> Which talks are being accessed most often? Which have not been opened in months? This helps you prioritise content maintenance and identify what is genuinely useful versus what is just taking up space.<\/li>\n<\/ul>\n<p>Review these metrics at a regular interval that makes sense for your organisation, and share the summary with the people responsible for safety and training. Measurement only drives improvement when the data reaches the people who can act on it.<\/p>\n<h2>How E-lia helps you build and manage a central toolbox library<\/h2>\n<p>E-lia is built specifically for organisations that need to reach operational, field-based, and multilingual employees with toolbox talks, safety instructions, and training without relying on company laptops, email addresses, or complex login systems. Everything runs through WhatsApp, which means your employees receive toolbox content directly on the phone they already carry, with no extra app to download and no password to remember.<\/p>\n<p>Here is what that looks like in practice:<\/p>\n<ul>\n<li><strong>Ready-to-use content library:<\/strong> We give you access to a library of more than 60 practical toolbox topics, updated regularly by a qualified safety professional, so you are not starting from scratch.<\/li>\n<li><strong>Your own content, centralised:<\/strong> You can build your own toolbox modules in minutes using our content creation tools, and store everything in one place with clear version control.<\/li>\n<li><strong>Automatic multilingual delivery:<\/strong> AI-powered translation into more than 50 languages means every employee receives the toolbox talk in their own language, without you having to manage separate files for each language variant.<\/li>\n<li><strong>Built-in participation tracking:<\/strong> Completion is recorded automatically. Knowledge checks confirm understanding, and a live dashboard shows you exactly who has completed what and when.<\/li>\n<li><strong>Physical meetings, digitally registered:<\/strong> If you run face-to-face toolbox meetings, you can register attendance and outcomes through the platform as well, keeping all your records in one place.<\/li>\n<\/ul>\n<p>If you want to see how E-lia can help your organisation move from scattered toolbox files to a structured, measurable library, <a href=\"https:\/\/e-lia.nl\/en\/contact\">get in touch with our team<\/a> for a no-obligation conversation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Scattered toolbox files causing version chaos? Learn how to audit, consolidate, and manage one central library.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-29906","post","type-post","status-publish","format-standard","hentry","category-geen-onderdeel-van-een-categorie"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How do you move from separate toolbox files to one central toolbox library? - E-Lia<\/title>\n<meta name=\"description\" content=\"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How do you move from separate toolbox files to one central toolbox library? - E-Lia\" \/>\n<meta property=\"og:description\" content=\"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/\" \/>\n<meta property=\"og:site_name\" content=\"E-Lia\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-30T07:00:00+00:00\" \/>\n<meta name=\"author\" content=\"Kees van Nuland\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kees van Nuland\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/\"},\"author\":{\"name\":\"Kees van Nuland\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#\\\/schema\\\/person\\\/5446f7ef2b87fe46a081549c2cc653dc\"},\"headline\":\"How do you move from separate toolbox files to one central toolbox library?\",\"datePublished\":\"2026-08-30T07:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/\"},\"wordCount\":1984,\"publisher\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#organization\"},\"articleSection\":[\"Geen onderdeel van een categorie\"],\"inLanguage\":\"en-GB\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/\",\"url\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/\",\"name\":\"How do you move from separate toolbox files to one central toolbox library? - E-Lia\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#website\"},\"datePublished\":\"2026-08-30T07:00:00+00:00\",\"description\":\"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/blog\\\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/e-lia.io\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How do you move from separate toolbox files to one central toolbox library?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/e-lia.io\\\/en\\\/\",\"name\":\"E-Lia\",\"description\":\"Leren via Whatsapp\",\"publisher\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/e-lia.io\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#organization\",\"name\":\"E-Lia\",\"url\":\"https:\\\/\\\/e-lia.io\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/e-lia.io\\\/wp-content\\\/uploads\\\/2023\\\/02\\\/E-lia-logo.svg\",\"contentUrl\":\"https:\\\/\\\/e-lia.io\\\/wp-content\\\/uploads\\\/2023\\\/02\\\/E-lia-logo.svg\",\"width\":122,\"height\":44,\"caption\":\"E-Lia\"},\"image\":{\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/69587130\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/e-lia.io\\\/en\\\/#\\\/schema\\\/person\\\/5446f7ef2b87fe46a081549c2cc653dc\",\"name\":\"Kees van Nuland\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g\",\"caption\":\"Kees van Nuland\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How do you move from separate toolbox files to one central toolbox library? - E-Lia","description":"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/","og_locale":"en_GB","og_type":"article","og_title":"How do you move from separate toolbox files to one central toolbox library? - E-Lia","og_description":"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.","og_url":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/","og_site_name":"E-Lia","article_published_time":"2026-08-30T07:00:00+00:00","author":"Kees van Nuland","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kees van Nuland","Estimated reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/#article","isPartOf":{"@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/"},"author":{"name":"Kees van Nuland","@id":"https:\/\/e-lia.io\/en\/#\/schema\/person\/5446f7ef2b87fe46a081549c2cc653dc"},"headline":"How do you move from separate toolbox files to one central toolbox library?","datePublished":"2026-08-30T07:00:00+00:00","mainEntityOfPage":{"@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/"},"wordCount":1984,"publisher":{"@id":"https:\/\/e-lia.io\/en\/#organization"},"articleSection":["Geen onderdeel van een categorie"],"inLanguage":"en-GB"},{"@type":"WebPage","@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/","url":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/","name":"How do you move from separate toolbox files to one central toolbox library? - E-Lia","isPartOf":{"@id":"https:\/\/e-lia.io\/en\/#website"},"datePublished":"2026-08-30T07:00:00+00:00","description":"Stop losing track of toolbox talk versions. Learn how to audit files, choose the right platform, and build a central library your teams actually use.","breadcrumb":{"@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/e-lia.io\/en\/blog\/how-do-you-move-from-separate-toolbox-files-to-one-central-toolbox-library\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/e-lia.io\/en\/"},{"@type":"ListItem","position":2,"name":"How do you move from separate toolbox files to one central toolbox library?"}]},{"@type":"WebSite","@id":"https:\/\/e-lia.io\/en\/#website","url":"https:\/\/e-lia.io\/en\/","name":"E-Lia","description":"Leren via Whatsapp","publisher":{"@id":"https:\/\/e-lia.io\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/e-lia.io\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/e-lia.io\/en\/#organization","name":"E-Lia","url":"https:\/\/e-lia.io\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/e-lia.io\/en\/#\/schema\/logo\/image\/","url":"https:\/\/e-lia.io\/wp-content\/uploads\/2023\/02\/E-lia-logo.svg","contentUrl":"https:\/\/e-lia.io\/wp-content\/uploads\/2023\/02\/E-lia-logo.svg","width":122,"height":44,"caption":"E-Lia"},"image":{"@id":"https:\/\/e-lia.io\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/69587130\/"]},{"@type":"Person","@id":"https:\/\/e-lia.io\/en\/#\/schema\/person\/5446f7ef2b87fe46a081549c2cc653dc","name":"Kees van Nuland","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/b5819008a7de507cf4fed2e77945c8a3bf39ab060e9e3422cc6dd4f361e1dd7c?s=96&d=mm&r=g","caption":"Kees van Nuland"}}]}},"_links":{"self":[{"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/posts\/29906","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/comments?post=29906"}],"version-history":[{"count":2,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/posts\/29906\/revisions"}],"predecessor-version":[{"id":30005,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/posts\/29906\/revisions\/30005"}],"wp:attachment":[{"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/media?parent=29906"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/categories?post=29906"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/e-lia.io\/en\/wp-json\/wp\/v2\/tags?post=29906"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}