Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
---
README.md | 8 --------
1 file changed, 8 deletions(-)
diff --git a/README.md b/README.md
index bff6c19239..e852af127f 100644
--- a/README.md
+++ b/README.md
@@ -155,14 +155,6 @@ See our [Contributing Guide](CONTRIBUTING.md) for details.
---
-## License
-
-LibreSign (this repository) is licensed under the **GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later)**.
-- ๐ All licenses: [LICENSES/](LICENSES/)
-- ๐ Also in Documentation repository: https://github.com/LibreSign/documentation/blob/main/LICENSE
-
----
-
## Screenshots
From 36d79aef640a433c6f26d0500a337d4f6da639f7 Mon Sep 17 00:00:00 2001
From: yharroch <82467465+yharroch@users.noreply.github.com>
Date: Thu, 26 Feb 2026 14:22:37 +0100
Subject: [PATCH 06/11] Update README.md
deletion of useless line
Co-authored-by: Vitor Mattos
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index e852af127f..5073d129c0 100644
--- a/README.md
+++ b/README.md
@@ -171,6 +171,6 @@ Thanks go to these wonderful people:
-## Star History
+## Star history
[](https://www.star-history.com/#libresign/libresign&Date)
From 845efa0d6da27474728152a32be86a8f83c71fa7 Mon Sep 17 00:00:00 2001
From: yharroch <82467465+yharroch@users.noreply.github.com>
Date: Thu, 26 Feb 2026 14:23:50 +0100
Subject: [PATCH 07/11] Update README.md
Adding application's descriptions about some features
Co-authored-by: Vitor Mattos
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
---
README.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 5073d129c0..7b399bee4a 100644
--- a/README.md
+++ b/README.md
@@ -133,7 +133,11 @@ Developer manual: https://docs.libresign.coop/developer_manual/index.html
## Security
-LibreSign uses certificate-based digital signatures and follows best practices for secure document validation.
+LibreSign uses certificate-based digital signatures built on a private PKI managed within your Nextcloud environment.
+
+It supports certificate revocation (CRL), trusted time-stamping (TSA), and document certification levels (DocMDP), ensuring integrity, authenticity and long-term validation of signed documents.
+
+All cryptographic operations are performed server-side and remain under your infrastructure control.
For responsible disclosure and security policy, please see [SECURITY.md](SECURITY.md).
From 6d3014916a438f861a254c0a542f473bc65d5c7c Mon Sep 17 00:00:00 2001
From: yharroch <82467465+yharroch@users.noreply.github.com>
Date: Thu, 26 Feb 2026 14:24:30 +0100
Subject: [PATCH 08/11] Update README.md
fixing link
Co-authored-by: Vitor Mattos
Signed-off-by: yharroch <82467465+yharroch@users.noreply.github.com>
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 7b399bee4a..1bd407c821 100644
--- a/README.md
+++ b/README.md
@@ -127,7 +127,7 @@ LibreSign manages its own internal Certificate Authority (CA), ensuring full con
## API Documentation
-Developer manual: https://docs.libresign.coop/developer_manual/index.html
+Developer manual: https://docs.libresign.coop/developer_manual/
---
From 362c32531963ac64b1770a5a3e4ec45ed2ef3315 Mon Sep 17 00:00:00 2001
From: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Date: Tue, 28 Apr 2026 17:58:44 -0300
Subject: [PATCH 09/11] docs: refine README copy
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
---
README.md | 182 +++++++++++-------------------------------------------
1 file changed, 37 insertions(+), 145 deletions(-)
diff --git a/README.md b/README.md
index 1bd407c821..f9b4f88b85 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
@@ -8,156 +8,48 @@
[](https://api.reuse.software/info/github.com/LibreSign/libresign)
[](https://github.com/LibreSign/libresign/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22good+first+issue%22)
-# LibreSign for Nextcloud
+# LibreSign
-LibreSign is a digital signature application for Nextcloud that enables secure document signing workflows directly within your self-hosted environment.
+Control how your documents get signed
-It supports internal and external signers, certificate-based signatures, and full document lifecycle management.
+LibreSign helps you control how document signing works in your organization.
+Organizations use it with Nextcloud to run signing workflows that match internal rules, legal requirements, and daily processes.
+It gives teams clear visibility into who signed, when they signed, and how each request moved through the process.
-## Why LibreSign?
+## Key features
-- Fully self-hosted digital signature solution
-- Integrated with Nextcloud ecosystem
-- Supports internal and external signers
-- Open source (AGPL-3.0)
-- Extensible API
+- Define signing order, roles, and rules per document flow
+- Include internal and external signers in the same request
+- Keep a traceable record of requests, actions, and validations
+- Work directly with Nextcloud files, users, and sharing context
+- Configure certificates and identity options to match your signing process
+- Connect signing processes to other systems through API endpoints
----
-## Quick Links
+## Why LibreSign
-- ๐ [Full Documentation](https://github.com/LibreSign/documentation)
-- ๐ [Report a bug](https://github.com/LibreSign/libresign/issues/new?template=bug_report.yml)
-- ๐ก [Request a feature](https://github.com/LibreSign/libresign/issues/new?template=feature_request.yml)
-- ๐ [Translations (Transifex)](https://app.transifex.com/nextcloud/nextcloud/libresign)
----
+LibreSign is for teams where signing is part of a controlled business process.
-## Who is this for?
-
-- ๐ Nextcloud administrators who want to deploy a digital signature solution
-- ๐ค End users who need to sign or request signatures on documents
-- ๐ข Organizations looking for a self-hosted signature workflow
-
----
-
-## Documentation
-
-Complete guides are available for:
-
-- ๐ง Administrators (installation, configuration, certificates)
-- ๐ฅ Users (how to request and sign documents)
-- ๐งช Developers (architecture and API)
-
-๐ https://github.com/LibreSign/documentation
-
----
-
-## Installation
-
-LibreSign can be installed from the Nextcloud App Store or manually.
-
-After enabling the app, administrators must install required standalone dependencies and configure certificates.
-
-### 1๏ธโฃ Install dependencies
-Run the following command as your web server user:
-`occ libresign:install --java --pdftk --jsignpdf`
-
-This will install:
-- Java (standalone JRE)
-- PDFtk
-- JSignPdf
-
-All binaries are installed inside the Nextcloud `data/appdata_*/libresign` directory.
-No system-wide installation is required.
-
-### 2๏ธโฃ Verify installation
-`sudo -u www-data php /path/to/nextcloud/occ libresign:configure:check`
-
-This command verifies:
-- Java availability
-- PDFtk setup
-- JSignPdf setup
-- OpenSSL configuration
-- Certificate environment
-
-### 3๏ธโฃ Configure root certificate
-You can generate a certificate using OpenSSL or CFSSL.
-
-Example using OpenSSL:
-`sudo -u www-data php /path/to/nextcloud/occ libresign:configure:openssl --cn="Your Organization - Digital Signature" --o="Your Organization" --c="FR" --st="Region" --l="City"`
-
-Certificates are generated and stored inside the Nextcloud data directory: `nextcloud_data_dir/appdata_*/libresign`
-
-No additional server-level configuration is required.
-
-๐ For full configuration details, advanced setups, and troubleshooting:
-https://github.com/LibreSign/documentation
-
----
-
-
-LibreSign runs entirely inside your Nextcloud environment.
-
-All cryptographic operations are self-contained and executed server-side. No external services are required and no document data leaves your infrastructure.
-
-LibreSign manages its own internal Certificate Authority (CA), ensuring full control over keys, signatures and alignment with data protection regulations.
-
----
-
-## How it works
-
-1. A user uploads a document.
-2. The user defines signers (internal or external).
-3. Signers receive a notification or link.
-4. The document is signed and stored in Nextcloud.
-5. Signature validation and certificate verification are performed automatically.
----
-
-### Additional dependencies:
-- poppler-utils
-- System locale configured with UTF-8 charset
-
----
-
-## Integrations
-
-* [GLPI](https://github.com/LibreSign/libresign-glpi): Plugin to sign GLPI tickets
-* [Approval](https://github.com/nextcloud/approval): Approve/reject files based on workflows defined by admins
-
----
-
-## API Documentation
-
-Developer manual: https://docs.libresign.coop/developer_manual/
-
----
-
-## Security
-
-LibreSign uses certificate-based digital signatures built on a private PKI managed within your Nextcloud environment.
-
-It supports certificate revocation (CRL), trusted time-stamping (TSA), and document certification levels (DocMDP), ensuring integrity, authenticity and long-term validation of signed documents.
-
-All cryptographic operations are performed server-side and remain under your infrastructure control.
-
-For responsible disclosure and security policy, please see [SECURITY.md](SECURITY.md).
-
----
+- Define clear signing rules by role, stage, or document type
+- Keep traceability for audits, legal checks, and internal reviews
+- Align signing with existing approval and governance processes
+- Adapt workflows to how your organization works instead of following fixed external models
## Contributing
-LibreSign is an open source project and welcomes contributions.
+Contributions are welcome from developers, implementers, and teams that use LibreSign in production.
-You can contribute by:
+- Report bugs and suggest improvements: https://github.com/LibreSign/libresign/issues
+- Start with good first issues: https://github.com/LibreSign/libresign/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
+- Read contribution guidelines: CONTRIBUTING.md
+- Help with translations: https://app.transifex.com/nextcloud/nextcloud/libresign
-- Opening issues for bugs and feature requests
-- Contributing code improvements
-- Improving translations on [Transifex](https://app.transifex.com/nextcloud/nextcloud/libresign)
-- Contributing to the [documentation repository](https://github.com/LibreSign/documentation)
-- Supporting the project via [GitHub Sponsors](https://github.com/sponsors/LibreSign)
+## Contributors
-See our [Contributing Guide](CONTRIBUTING.md) for details.
+Thanks to all the people who contribute to LibreSign:
----
+
+
+
## Screenshots
@@ -165,16 +57,16 @@ See our [Contributing Guide](CONTRIBUTING.md) for details.
----
+## Documentation
-## Contributors โจ
+- Official documentation: https://docs.libresign.coop/
+- Developer manual: https://docs.libresign.coop/developer_manual/
+- Documentation repository: https://github.com/LibreSign/documentation
-Thanks go to these wonderful people:
+## Sponsors
-
-
-
+If your organization depends on LibreSign, please sponsor the project.
-## Star history
+Sponsorship directly supports ongoing maintenance, reliable releases, better documentation, and long-term continuity for teams that rely on LibreSign in real workflows.
-[](https://www.star-history.com/#libresign/libresign&Date)
+Support LibreSign: https://github.com/sponsors/LibreSign
From afff0409629544e0bbbf58e1be597dbe9061b3ae Mon Sep 17 00:00:00 2001
From: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Date: Tue, 28 Apr 2026 18:04:06 -0300
Subject: [PATCH 10/11] chore: small text improvement
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index f9b4f88b85..2cbb0332e4 100644
--- a/README.md
+++ b/README.md
@@ -22,8 +22,8 @@ It gives teams clear visibility into who signed, when they signed, and how each
- Include internal and external signers in the same request
- Keep a traceable record of requests, actions, and validations
- Work directly with Nextcloud files, users, and sharing context
-- Configure certificates and identity options to match your signing process
-- Connect signing processes to other systems through API endpoints
+- Configure certificates and identity options for your signing process
+- Connect signing with other systems through APIs
## Why LibreSign
From cf7491e08b89bc24c075e8c5f8aff04b0b19a64a Mon Sep 17 00:00:00 2001
From: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Date: Tue, 28 Apr 2026 18:07:25 -0300
Subject: [PATCH 11/11] docs: improve README wording
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 2cbb0332e4..42ca00c586 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ It gives teams clear visibility into who signed, when they signed, and how each
- Keep a traceable record of requests, actions, and validations
- Work directly with Nextcloud files, users, and sharing context
- Configure certificates and identity options for your signing process
-- Connect signing with other systems through APIs
+- Integrate signing with other systems through APIs
## Why LibreSign