docwire · reeshabh90 · May 6, 2026 · May 6, 2026 · May 6, 2026 · May 6, 2026
diff --git a/.gitignore b/.gitignore
@@ -4,6 +4,7 @@
 /node_modules
 /.pnp
 .pnp.js
+.docusaurus
 
 # testing
 /coverage

diff --git a/blog/2023-03-21-the-4th-industrial-revolution.md b/blog/2023-03-21-the-4th-industrial-revolution.md
diff --git a/blog/2023-03-22-introduction-to-the-4th-industrial-revolution.md b/blog/2023-03-22-introduction-to-the-4th-industrial-revolution.md
diff --git a/blog/2023-03-23-case-studies-in-the-4th-industrial-revolution.md b/blog/2023-03-23-case-studies-in-the-4th-industrial-revolution.md
diff --git a/blog/2023-03-24-challenges-and-opportunities-of-the-4th-industrial-revolution.md b/blog/2023-03-24-challenges-and-opportunities-of-the-4th-industrial-revolution.md
diff --git a/blog/2026-05-05-docwire-returns.md b/blog/2026-05-05-docwire-returns.md
@@ -0,0 +1,62 @@
+---
+title: Docwire - The Engine Behind Secure Data Pipelines
+authors: krzysztof
+tags: [C++20, technology, document processing, data security]
+---
+*“Persistence turns a bar of iron into a needle”*, Nguyễn Phan Quế Mai, *Dust Child*
+
+![Docwire return](/img/blog/2026-05-05-docwire-returns/DocwireReturn.PNG)
+
+In course of human history, there has not been a time like the present era when Information has become of paramount importance. As James Gleick observes in his book “The Information”, information is what our world runs on: the blood and the fuel, the vital principle. Information pervades all domains of sciences, transforming every branch of knowledge. And Information needs to be inferred in its purest form to act as Intelligence. 
+
+Away from the noise, contemplating in silence, working through perseverance, Docwire SDK was being evolved into a infrastructure layer for modern data workflows to sustain the demands of modern day information processing. The journey has been long and arduous but the result has been equally satisfying. And it is time we present to you the much more evolved Dcowire SDK, along with anecdotes about the philosophy behind it and the direction forward.
+
+## The Invisible Engine
+Every interface we interact with is a surface level reality, but the entity itself is supported by an engine which remains invisible. Same is true for the virtual world. Some of the most important softwares are never seen. When you tap a payment card or rely on an embedded medical device, complex logic runs quietly in the background. Document processing plays a similar role in many systems — critical, yet hidden. And Docwire has been designed to serve exactly the same purpose. An engine that extracts, normalizes, and transforms unstructured documents into structured, usable data — locally, securely and reliably. And it still adheres to its “Plug and Play” philosophy. Developers integrate it once and it simply works! Only better this time, with support for more file formats and a fluent ingestion layer for building data processing pipeline.
+
+
+## What Changed since 2023
+We started this journey of evolving Docwire with following ideas as underlying philosophy:
+- Broader format support and improved parsing stability.
+- Supporting real-world usage in enterprise environments.
+- Deeper involvement in client projects as core processing layer.
+- Easy integrations with local LLM runtimes and AI pipelines. 
+
+💡And with each execution, one insight (or inutition) became clear:<br/>
+<u>*The need for secure and reliable data processing on local premises is increasing in the LLM era.*</u>
+
+And this is where Docwire shines. Docwire is not simply AI-based or AI-driven, but AI-integrated SDK, which handles your document data processing requirements. It gives the user enough flexibility to process the data across various file formats and integrate it further with AI models of their choice, be it local or through APIs
+
+## From Files to Pipelines
+Docwire's evolution is not limited to supporting various file formats but integrating more workflows. In its inception, it was a file parsing tool and in its evolution, it is  becoming pipeline construction SDK with various tools at your disposal:<br/>
+<b>Documents → Extraction → Normalization → Transformation → Output</b><br/>
+
+These pipelines can feed search, analytics, knowledge bases, or AI systems, often running entirely within controlled environments.
+This shift defines the next phase of DocWire.
+
+## Watch: The Invisible Engine Concept
+To explain this direction visually, we prepared a short concept video introducing DocWire as the invisible engine behind secure data pipelines.
+
+<iframe
+  width="100%"
+  height="400"
+  src="https://www.youtube.com/embed/dlLMHZlULi4"
+  title="Demo video"
+  allowFullScreen
+/>
+
+## What’s Next
+Now that we are back, look out for communications from the Docwire team frequently on this forum. We will start sharing:
+- Engineering deep dives
+- Integration experiments
+- Lessons from real deployments
+- Previews of upcoming features
+
+DocWire is evolving from SDK toward a broader processing framework — and this space will document that journey.
+## Explore DocWire
+If you’re building systems that depend on reliable document processing or secure data pipelines, we invite you to explore:
+- [GitHub repository](https://github.com/docwire/docwire)
+- [Documentation](https://docwire.readthedocs.io/en/latest/)
+- [Recent releases](https://github.com/docwire/docwire/releases)
+
+Or simply reach out — we are always curious about what others are building behind the scenes, and eager to support the cause in any way possible.
diff --git a/blog/authors.yml b/blog/authors.yml
@@ -1,4 +1,5 @@
-ferid:
-  name: Ferid Obeidat
-  title: Author
-  image_url: /img/Ferid-headshot.png
+krzysztof:
+  name: Krzysztof Nowicki
+  title: Chief Business Officer, Founder - Docwire
+  image_url: /img/kryz-headshot.png
+
diff --git a/static/img/Ferid-headshot.png b/static/img/Ferid-headshot.png
diff --git a/static/img/blog/2026-05-05-docwire-returns/DocwireReturn.PNG b/static/img/blog/2026-05-05-docwire-returns/DocwireReturn.PNG
diff --git a/static/img/kryz-headshot.png b/static/img/kryz-headshot.png