diff --git a/.github/workflows/build-and-release.yaml b/.github/workflows/build-and-release.yaml
index 74103d7..4e72dcf 100644
--- a/.github/workflows/build-and-release.yaml
+++ b/.github/workflows/build-and-release.yaml
@@ -1,4 +1,4 @@
-name: Build and release
+name: Build and publish artefacts and documentation
 
 on:
   push:
@@ -7,51 +7,193 @@ on:
 
 jobs:
 
+  create_release:
+    name: Create Release
+    runs-on: ubuntu-latest
+    outputs:
+      upload_url: ${{ steps.create_release.outputs.upload_url }}
+      job_status: ${{ job.status }}
+    steps:
+      - name: Checkout project
+        uses: actions/checkout@v3
+
+      - name: Create Release
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: ${{ github.ref_name }} 
+          release_name: Release ${{ github.ref_name }} 
+          body_path: CHANGELOG.md
+          draft: false
+          prerelease: false
+
   build:
 
-    runs-on: ubuntu-latest
+    name: Build artefacts
+    needs: create_release
+    outputs:
+      job_status: ${{ job.status }}
+    strategy:
+      max-parallel: 2
+      fail-fast: true
+      matrix:
+        include:
+          - os: ubuntu-20.04
+            python-version: "3.8"
+          - os: ubuntu-22.04
+            python-version: "3.10"
+
+    runs-on: ${{ matrix.os }}
 
     steps:
-      - uses: actions/checkout@v3
+      - name: Checkout project
+        uses: actions/checkout@v3
 
-      - name: Set up Python 3.8
+      - name: Setup python
         uses: actions/setup-python@v4
         with:
-          python-version: "3.8"
+          python-version: ${{ matrix.python-version }}
           cache: 'pip'
-          cache-dependency-path: '**/setup.py'
+          cache-dependency-path: '**/pyproject.toml'
 
-      - name: Install dependencies
+      - name: Install system dependencies
         run: |
-
           sudo apt update
-          sudo apt install python3-rados
-          python -m pip install --upgrade pip
-          python -m pip install --upgrade pip setuptools wheel
+          sudo apt -y install python3-rados python3-gdal
 
-      - name: Build wheel
+      - name: Install python dependencies
         run: |
-          VERSION=${{ github.ref_name }} python setup.py bdist_wheel
+          python3 -m venv .venv
+          source .venv/bin/activate
+          python3 -m pip install --upgrade build bump2version
+          bump2version --current-version 0.0.0 --new-version ${{ github.ref_name }} patch pyproject.toml src/rok4_tools/__init__.py
 
-      - name: Create Release
-        id: create_release
-        uses: actions/create-release@v1
+      - name: Build package
+        if: "(${{ matrix.os }}=='ubuntu-20.04')&&(${{ matrix.python-version }}=='3.8')"
+        run: |
+          source .venv/bin/activate
+          python3 -m build
+
+      - name: Copy documentation
+        if: "(${{ matrix.os }}=='ubuntu-20.04')&&(${{ matrix.python-version }}=='3.8')"
+        run: |
+          cp README.md CHANGELOG.md dist/
+          cp docs/images dist/
+
+      - name: Upload packages
+        if: "(${{ matrix.os }}=='ubuntu-20.04')&&(${{ matrix.python-version }}=='3.8')"
+        uses: actions/upload-artifact@v3
+        with:
+          name: dist-py3
+          path: dist/
+          if-no-files-found: error
+          retention-days: 1
+
+  publish_artefacts:
+    name: Add built artefacts to release and PyPI
+    needs: [create_release, build]
+    if: "always()&&(needs.create_release.outputs.job_status=='success')&&(needs.build.outputs.job_status=='success')"
+    runs-on: ubuntu-latest
+
+    steps:
+
+      - uses: actions/download-artifact@v3
+        with:
+          name: dist-py3
+          path: dist/
+
+      - name: Add wheel package to release
+        id: upload-release-whl
+        uses: actions/upload-release-asset@v1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          tag_name: ${{ github.ref }}
-          release_name: Release ${{ github.ref_name }}
-          body_path: CHANGELOG.md
-          draft: false
-          prerelease: false
+          upload_url: ${{ needs.create_release.outputs.upload_url }}
+          asset_path: ./dist/rok4_tools-${{ github.ref_name }}-py3-none-any.whl
+          asset_name: rok4_tools-${{ github.ref_name }}-py3-none-any.whl
+          asset_content_type: application/zip
 
-      - name: Add wheel package to release
-        id: upload-release-asset 
+      - name: Add tarball package to release
+        id: upload-release-targz 
         uses: actions/upload-release-asset@v1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          upload_url: ${{ steps.create_release.outputs.upload_url }}
-          asset_path: ./dist/rok4tools-${{ github.ref_name }}-py3-none-any.whl
-          asset_name: rok4tools-${{ github.ref_name }}-py3-none-any.whl
+          upload_url: ${{ needs.create_release.outputs.upload_url }}
+          asset_path: ./dist/rok4-tools-${{ github.ref_name }}.tar.gz
+          asset_name: rok4-tools-${{ github.ref_name }}.tar.gz
           asset_content_type: application/zip
+
+      - name: Isolate wheel and tarball
+        run: |
+          mkdir to_publish
+          cp ./dist/*.whl ./dist/*.tar.gz to_publish/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          packages_dir: to_publish/
+
+  commit_documentation:
+    name: Add documentation into gh-pages branch
+    needs: build
+    if: "always()&&(needs.create_release.outputs.job_status=='success')&&(needs.build.outputs.job_status=='success')" 
+    runs-on: ubuntu-latest
+
+    steps:
+
+      - name: Checkout project on gh-pages
+        uses: actions/checkout@v3
+        with:
+          ref: 'gh-pages'
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - uses: actions/download-artifact@v3
+        with:
+          name: dist-py3
+          path: artifact/
+
+      - name: Copy version elements to final location
+        run: |
+          mkdir -p docs/versions/${{ github.ref_name }}/docs
+          cp -r artifact/images docs/versions/${{ github.ref_name }}/docs/
+
+      - name: Add pages from templates
+        run: |
+          sed "s#__version__#${{ github.ref_name }}#" templates/CHANGELOG.template.md >docs/versions/${{ github.ref_name }}/CHANGELOG.md
+          cat artifact/CHANGELOG.md >>docs/versions/${{ github.ref_name }}/CHANGELOG.md
+          sed "s#__version__#${{ github.ref_name }}#" templates/README.template.md >docs/versions/${{ github.ref_name }}/README.md
+          cat artifact/README.md >>docs/versions/${{ github.ref_name }}/README.md
+          sed -i "s#x.y.z#${{ github.ref_name }}#" docs/versions/${{ github.ref_name }}/README.md
+          sed "s#__version__#${{ github.ref_name }}#" templates/index.template.md >docs/index.md
+          echo "# Versions" >docs/versions.md
+          echo "" >>docs/versions.md
+          for v in `ls -t docs/versions`; do sed "s#__version__#$v#" templates/versions.template.md >>docs/versions.md; done
+          rm -r artifact
+
+      - name: Publish on gh-pages branch
+        run: |
+          git config user.name github-actions
+          git config user.email github-actions@github.com
+          git add -v docs/versions/${{ github.ref_name }}/ docs/index.md docs/versions.md
+          git commit -m "Add documentation for version ${{ github.ref_name }}"
+          git push
+
+  delete_version:
+    name: Remove release and tag if error occured
+    needs: build
+    if: "always()&&(needs.create_release.outputs.job_status=='success')&&(needs.build.outputs.job_status!='success')" 
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Remove release and tag
+        uses: dev-drprasad/delete-tag-and-release@v0.2.0
+        with:
+          tag_name: ${{ github.ref_name }}
+          delete_release: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 572904f..ec7d4d3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,15 +1,21 @@
-# Outils ROK4 Python
-
 ## Summary
 
-Ajout de l'outil make-layer
+Ajout de l'outil make-layer et suivi des recommandations PyPA pour la gestion du projet.
 
 ## Changelog
 
 ### [Added]
 
 * Outil MAKE-LAYER : génère un descripteur de couche compatible avec le serveur à partir des pyramides de données à utiliser
+* Ajout de la publication PyPI dans la CI GitHub 
+
+### [Changed]
 
+* Renommage pour plus de cohérence avec les pratiques :
+    * Le module rok4 est renommé : rok4lib -> rok4
+    * Le module d'outil est renommé : rok4tools -> rok4_tools. Le package a le nom rok4-tools
+    * Le script make-layer.py -> make_layer.py
+* Passage de la configuration du projet dans le fichier `pyproject.toml`
 
 <!-- 
 ### [Added]
diff --git a/LICENSE.txt b/LICENSE.txt
new file mode 100644
index 0000000..d6eb151
--- /dev/null
+++ b/LICENSE.txt
@@ -0,0 +1,517 @@
+
+CeCILL-C FREE SOFTWARE LICENSE AGREEMENT
+
+
+    Notice
+
+This Agreement is a Free Software license agreement that is the result
+of discussions between its authors in order to ensure compliance with
+the two main principles guiding its drafting:
+
+    * firstly, compliance with the principles governing the distribution
+      of Free Software: access to source code, broad rights granted to
+      users,
+    * secondly, the election of a governing law, French law, with which
+      it is conformant, both as regards the law of torts and
+      intellectual property law, and the protection that it offers to
+      both authors and holders of the economic rights over software.
+
+The authors of the CeCILL-C (for Ce[a] C[nrs] I[nria] L[ogiciel] L[ibre])
+license are:
+
+Commissariat à l'Energie Atomique - CEA, a public scientific, technical
+and industrial research establishment, having its principal place of
+business at 25 rue Leblanc, immeuble Le Ponant D, 75015 Paris, France.
+
+Centre National de la Recherche Scientifique - CNRS, a public scientific
+and technological establishment, having its principal place of business
+at 3 rue Michel-Ange, 75794 Paris cedex 16, France.
+
+Institut National de Recherche en Informatique et en Automatique -
+INRIA, a public scientific and technological establishment, having its
+principal place of business at Domaine de Voluceau, Rocquencourt, BP
+105, 78153 Le Chesnay cedex, France.
+
+
+    Preamble
+
+The purpose of this Free Software license agreement is to grant users
+the right to modify and re-use the software governed by this license.
+
+The exercising of this right is conditional upon the obligation to make
+available to the community the modifications made to the source code of
+the software so as to contribute to its evolution.
+
+In consideration of access to the source code and the rights to copy,
+modify and redistribute granted by the license, users are provided only
+with a limited warranty and the software's author, the holder of the
+economic rights, and the successive licensors only have limited liability.
+
+In this respect, the risks associated with loading, using, modifying
+and/or developing or reproducing the software by the user are brought to
+the user's attention, given its Free Software status, which may make it
+complicated to use, with the result that its use is reserved for
+developers and experienced professionals having in-depth computer
+knowledge. Users are therefore encouraged to load and test the
+suitability of the software as regards their requirements in conditions
+enabling the security of their systems and/or data to be ensured and,
+more generally, to use and operate it in the same conditions of
+security. This Agreement may be freely reproduced and published,
+provided it is not altered, and that no provisions are either added or
+removed herefrom.
+
+This Agreement may apply to any or all software for which the holder of
+the economic rights decides to submit the use thereof to its provisions.
+
+
+    Article 1 - DEFINITIONS
+
+For the purpose of this Agreement, when the following expressions
+commence with a capital letter, they shall have the following meaning:
+
+Agreement: means this license agreement, and its possible subsequent
+versions and annexes.
+
+Software: means the software in its Object Code and/or Source Code form
+and, where applicable, its documentation, "as is" when the Licensee
+accepts the Agreement.
+
+Initial Software: means the Software in its Source Code and possibly its
+Object Code form and, where applicable, its documentation, "as is" when
+it is first distributed under the terms and conditions of the Agreement.
+
+Modified Software: means the Software modified by at least one
+Integrated Contribution.
+
+Source Code: means all the Software's instructions and program lines to
+which access is required so as to modify the Software.
+
+Object Code: means the binary files originating from the compilation of
+the Source Code.
+
+Holder: means the holder(s) of the economic rights over the Initial
+Software.
+
+Licensee: means the Software user(s) having accepted the Agreement.
+
+Contributor: means a Licensee having made at least one Integrated
+Contribution.
+
+Licensor: means the Holder, or any other individual or legal entity, who
+distributes the Software under the Agreement.
+
+Integrated Contribution: means any or all modifications, corrections,
+translations, adaptations and/or new functions integrated into the
+Source Code by any or all Contributors.
+
+Related Module: means a set of sources files including their
+documentation that, without modification to the Source Code, enables
+supplementary functions or services in addition to those offered by the
+Software.
+
+Derivative Software: means any combination of the Software, modified or
+not, and of a Related Module.
+
+Parties: mean both the Licensee and the Licensor.
+
+These expressions may be used both in singular and plural form.
+
+
+    Article 2 - PURPOSE
+
+The purpose of the Agreement is the grant by the Licensor to the
+Licensee of a non-exclusive, transferable and worldwide license for the
+Software as set forth in Article 5 hereinafter for the whole term of the
+protection granted by the rights over said Software. 
+
+
+    Article 3 - ACCEPTANCE
+
+3.1 The Licensee shall be deemed as having accepted the terms and
+conditions of this Agreement upon the occurrence of the first of the
+following events:
+
+    * (i) loading the Software by any or all means, notably, by
+      downloading from a remote server, or by loading from a physical
+      medium;
+    * (ii) the first time the Licensee exercises any of the rights
+      granted hereunder.
+
+3.2 One copy of the Agreement, containing a notice relating to the
+characteristics of the Software, to the limited warranty, and to the
+fact that its use is restricted to experienced users has been provided
+to the Licensee prior to its acceptance as set forth in Article 3.1
+hereinabove, and the Licensee hereby acknowledges that it has read and
+understood it.
+
+
+    Article 4 - EFFECTIVE DATE AND TERM
+
+
+      4.1 EFFECTIVE DATE
+
+The Agreement shall become effective on the date when it is accepted by
+the Licensee as set forth in Article 3.1.
+
+
+      4.2 TERM
+
+The Agreement shall remain in force for the entire legal term of
+protection of the economic rights over the Software.
+
+
+    Article 5 - SCOPE OF RIGHTS GRANTED
+
+The Licensor hereby grants to the Licensee, who accepts, the following
+rights over the Software for any or all use, and for the term of the
+Agreement, on the basis of the terms and conditions set forth hereinafter.
+
+Besides, if the Licensor owns or comes to own one or more patents
+protecting all or part of the functions of the Software or of its
+components, the Licensor undertakes not to enforce the rights granted by
+these patents against successive Licensees using, exploiting or
+modifying the Software. If these patents are transferred, the Licensor
+undertakes to have the transferees subscribe to the obligations set
+forth in this paragraph.
+
+
+      5.1 RIGHT OF USE
+
+The Licensee is authorized to use the Software, without any limitation
+as to its fields of application, with it being hereinafter specified
+that this comprises:
+
+   1. permanent or temporary reproduction of all or part of the Software
+      by any or all means and in any or all form.
+
+   2. loading, displaying, running, or storing the Software on any or
+      all medium.
+
+   3. entitlement to observe, study or test its operation so as to
+      determine the ideas and principles behind any or all constituent
+      elements of said Software. This shall apply when the Licensee
+      carries out any or all loading, displaying, running, transmission
+      or storage operation as regards the Software, that it is entitled
+      to carry out hereunder.
+
+
+      5.2 RIGHT OF MODIFICATION
+
+The right of modification includes the right to translate, adapt,
+arrange, or make any or all modifications to the Software, and the right
+to reproduce the resulting software. It includes, in particular, the
+right to create a Derivative Software.
+
+The Licensee is authorized to make any or all modification to the
+Software provided that it includes an explicit notice that it is the
+author of said modification and indicates the date of the creation thereof.
+
+
+      5.3 RIGHT OF DISTRIBUTION
+
+In particular, the right of distribution includes the right to publish,
+transmit and communicate the Software to the general public on any or
+all medium, and by any or all means, and the right to market, either in
+consideration of a fee, or free of charge, one or more copies of the
+Software by any means.
+
+The Licensee is further authorized to distribute copies of the modified
+or unmodified Software to third parties according to the terms and
+conditions set forth hereinafter.
+
+
+        5.3.1 DISTRIBUTION OF SOFTWARE WITHOUT MODIFICATION
+
+The Licensee is authorized to distribute true copies of the Software in
+Source Code or Object Code form, provided that said distribution
+complies with all the provisions of the Agreement and is accompanied by:
+
+   1. a copy of the Agreement,
+
+   2. a notice relating to the limitation of both the Licensor's
+      warranty and liability as set forth in Articles 8 and 9,
+
+and that, in the event that only the Object Code of the Software is
+redistributed, the Licensee allows effective access to the full Source
+Code of the Software at a minimum during the entire period of its
+distribution of the Software, it being understood that the additional
+cost of acquiring the Source Code shall not exceed the cost of
+transferring the data.
+
+
+        5.3.2 DISTRIBUTION OF MODIFIED SOFTWARE
+
+When the Licensee makes an Integrated Contribution to the Software, the
+terms and conditions for the distribution of the resulting Modified
+Software become subject to all the provisions of this Agreement.
+
+The Licensee is authorized to distribute the Modified Software, in
+source code or object code form, provided that said distribution
+complies with all the provisions of the Agreement and is accompanied by:
+
+   1. a copy of the Agreement,
+
+   2. a notice relating to the limitation of both the Licensor's
+      warranty and liability as set forth in Articles 8 and 9,
+
+and that, in the event that only the object code of the Modified
+Software is redistributed, the Licensee allows effective access to the
+full source code of the Modified Software at a minimum during the entire
+period of its distribution of the Modified Software, it being understood
+that the additional cost of acquiring the source code shall not exceed
+the cost of transferring the data.
+
+
+        5.3.3 DISTRIBUTION OF DERIVATIVE SOFTWARE
+
+When the Licensee creates Derivative Software, this Derivative Software
+may be distributed under a license agreement other than this Agreement,
+subject to compliance with the requirement to include a notice
+concerning the rights over the Software as defined in Article 6.4.
+In the event the creation of the Derivative Software required modification 
+of the Source Code, the Licensee undertakes that:
+
+   1. the resulting Modified Software will be governed by this Agreement,
+   2. the Integrated Contributions in the resulting Modified Software
+      will be clearly identified and documented,
+   3. the Licensee will allow effective access to the source code of the
+      Modified Software, at a minimum during the entire period of
+      distribution of the Derivative Software, such that such
+      modifications may be carried over in a subsequent version of the
+      Software; it being understood that the additional cost of
+      purchasing the source code of the Modified Software shall not
+      exceed the cost of transferring the data.
+
+
+        5.3.4 COMPATIBILITY WITH THE CeCILL LICENSE
+
+When a Modified Software contains an Integrated Contribution subject to
+the CeCILL license agreement, or when a Derivative Software contains a
+Related Module subject to the CeCILL license agreement, the provisions
+set forth in the third item of Article 6.4 are optional.
+
+
+    Article 6 - INTELLECTUAL PROPERTY
+
+
+      6.1 OVER THE INITIAL SOFTWARE
+
+The Holder owns the economic rights over the Initial Software. Any or
+all use of the Initial Software is subject to compliance with the terms
+and conditions under which the Holder has elected to distribute its work
+and no one shall be entitled to modify the terms and conditions for the
+distribution of said Initial Software.
+
+The Holder undertakes that the Initial Software will remain ruled at
+least by this Agreement, for the duration set forth in Article 4.2.
+
+
+      6.2 OVER THE INTEGRATED CONTRIBUTIONS
+
+The Licensee who develops an Integrated Contribution is the owner of the
+intellectual property rights over this Contribution as defined by
+applicable law.
+
+
+      6.3 OVER THE RELATED MODULES
+
+The Licensee who develops a Related Module is the owner of the
+intellectual property rights over this Related Module as defined by
+applicable law and is free to choose the type of agreement that shall
+govern its distribution under the conditions defined in Article 5.3.3.
+
+
+      6.4 NOTICE OF RIGHTS
+
+The Licensee expressly undertakes:
+
+   1. not to remove, or modify, in any manner, the intellectual property
+      notices attached to the Software;
+
+   2. to reproduce said notices, in an identical manner, in the copies
+      of the Software modified or not;
+
+   3. to ensure that use of the Software, its intellectual property
+      notices and the fact that it is governed by the Agreement is
+      indicated in a text that is easily accessible, specifically from
+      the interface of any Derivative Software.
+
+The Licensee undertakes not to directly or indirectly infringe the
+intellectual property rights of the Holder and/or Contributors on the
+Software and to take, where applicable, vis-à-vis its staff, any and all
+measures required to ensure respect of said intellectual property rights
+of the Holder and/or Contributors.
+
+
+    Article 7 - RELATED SERVICES
+
+7.1 Under no circumstances shall the Agreement oblige the Licensor to
+provide technical assistance or maintenance services for the Software.
+
+However, the Licensor is entitled to offer this type of services. The
+terms and conditions of such technical assistance, and/or such
+maintenance, shall be set forth in a separate instrument. Only the
+Licensor offering said maintenance and/or technical assistance services
+shall incur liability therefor.
+
+7.2 Similarly, any Licensor is entitled to offer to its licensees, under
+its sole responsibility, a warranty, that shall only be binding upon
+itself, for the redistribution of the Software and/or the Modified
+Software, under terms and conditions that it is free to decide. Said
+warranty, and the financial terms and conditions of its application,
+shall be subject of a separate instrument executed between the Licensor
+and the Licensee.
+
+
+    Article 8 - LIABILITY
+
+8.1 Subject to the provisions of Article 8.2, the Licensee shall be
+entitled to claim compensation for any direct loss it may have suffered
+from the Software as a result of a fault on the part of the relevant
+Licensor, subject to providing evidence thereof.
+
+8.2 The Licensor's liability is limited to the commitments made under
+this Agreement and shall not be incurred as a result of in particular:
+(i) loss due the Licensee's total or partial failure to fulfill its
+obligations, (ii) direct or consequential loss that is suffered by the
+Licensee due to the use or performance of the Software, and (iii) more
+generally, any consequential loss. In particular the Parties expressly
+agree that any or all pecuniary or business loss (i.e. loss of data,
+loss of profits, operating loss, loss of customers or orders,
+opportunity cost, any disturbance to business activities) or any or all
+legal proceedings instituted against the Licensee by a third party,
+shall constitute consequential loss and shall not provide entitlement to
+any or all compensation from the Licensor.
+
+
+    Article 9 - WARRANTY
+
+9.1 The Licensee acknowledges that the scientific and technical
+state-of-the-art when the Software was distributed did not enable all
+possible uses to be tested and verified, nor for the presence of
+possible defects to be detected. In this respect, the Licensee's
+attention has been drawn to the risks associated with loading, using,
+modifying and/or developing and reproducing the Software which are
+reserved for experienced users.
+
+The Licensee shall be responsible for verifying, by any or all means,
+the suitability of the product for its requirements, its good working
+order, and for ensuring that it shall not cause damage to either persons
+or properties.
+
+9.2 The Licensor hereby represents, in good faith, that it is entitled
+to grant all the rights over the Software (including in particular the
+rights set forth in Article 5).
+
+9.3 The Licensee acknowledges that the Software is supplied "as is" by
+the Licensor without any other express or tacit warranty, other than
+that provided for in Article 9.2 and, in particular, without any warranty
+as to its commercial value, its secured, safe, innovative or relevant
+nature.
+
+Specifically, the Licensor does not warrant that the Software is free
+from any error, that it will operate without interruption, that it will
+be compatible with the Licensee's own equipment and software
+configuration, nor that it will meet the Licensee's requirements.
+
+9.4 The Licensor does not either expressly or tacitly warrant that the
+Software does not infringe any third party intellectual property right
+relating to a patent, software or any other property right. Therefore,
+the Licensor disclaims any and all liability towards the Licensee
+arising out of any or all proceedings for infringement that may be
+instituted in respect of the use, modification and redistribution of the
+Software. Nevertheless, should such proceedings be instituted against
+the Licensee, the Licensor shall provide it with technical and legal
+assistance for its defense. Such technical and legal assistance shall be
+decided on a case-by-case basis between the relevant Licensor and the
+Licensee pursuant to a memorandum of understanding. The Licensor
+disclaims any and all liability as regards the Licensee's use of the
+name of the Software. No warranty is given as regards the existence of
+prior rights over the name of the Software or as regards the existence
+of a trademark.
+
+
+    Article 10 - TERMINATION
+
+10.1 In the event of a breach by the Licensee of its obligations
+hereunder, the Licensor may automatically terminate this Agreement
+thirty (30) days after notice has been sent to the Licensee and has
+remained ineffective.
+
+10.2 A Licensee whose Agreement is terminated shall no longer be
+authorized to use, modify or distribute the Software. However, any
+licenses that it may have granted prior to termination of the Agreement
+shall remain valid subject to their having been granted in compliance
+with the terms and conditions hereof.
+
+
+    Article 11 - MISCELLANEOUS
+
+
+      11.1 EXCUSABLE EVENTS
+
+Neither Party shall be liable for any or all delay, or failure to
+perform the Agreement, that may be attributable to an event of force
+majeure, an act of God or an outside cause, such as defective
+functioning or interruptions of the electricity or telecommunications
+networks, network paralysis following a virus attack, intervention by
+government authorities, natural disasters, water damage, earthquakes,
+fire, explosions, strikes and labor unrest, war, etc.
+
+11.2 Any failure by either Party, on one or more occasions, to invoke
+one or more of the provisions hereof, shall under no circumstances be
+interpreted as being a waiver by the interested Party of its right to
+invoke said provision(s) subsequently.
+
+11.3 The Agreement cancels and replaces any or all previous agreements,
+whether written or oral, between the Parties and having the same
+purpose, and constitutes the entirety of the agreement between said
+Parties concerning said purpose. No supplement or modification to the
+terms and conditions hereof shall be effective as between the Parties
+unless it is made in writing and signed by their duly authorized
+representatives.
+
+11.4 In the event that one or more of the provisions hereof were to
+conflict with a current or future applicable act or legislative text,
+said act or legislative text shall prevail, and the Parties shall make
+the necessary amendments so as to comply with said act or legislative
+text. All other provisions shall remain effective. Similarly, invalidity
+of a provision of the Agreement, for any reason whatsoever, shall not
+cause the Agreement as a whole to be invalid.
+
+
+      11.5 LANGUAGE
+
+The Agreement is drafted in both French and English and both versions
+are deemed authentic.
+
+
+    Article 12 - NEW VERSIONS OF THE AGREEMENT
+
+12.1 Any person is authorized to duplicate and distribute copies of this
+Agreement.
+
+12.2 So as to ensure coherence, the wording of this Agreement is
+protected and may only be modified by the authors of the License, who
+reserve the right to periodically publish updates or new versions of the
+Agreement, each with a separate number. These subsequent versions may
+address new issues encountered by Free Software.
+
+12.3 Any Software distributed under a given version of the Agreement may
+only be subsequently distributed under the same version of the Agreement
+or a subsequent version.
+
+
+    Article 13 - GOVERNING LAW AND JURISDICTION
+
+13.1 The Agreement is governed by French law. The Parties agree to
+endeavor to seek an amicable solution to any disagreements or disputes
+that may arise during the performance of the Agreement.
+
+13.2 Failing an amicable solution within two (2) months as from their
+occurrence, and unless emergency proceedings are necessary, the
+disagreements or disputes shall be referred to the Paris Courts having
+jurisdiction, by the more diligent Party.
+
+
+Version 1.0 dated 2006-09-05.
diff --git a/README.md b/README.md
index 66d21ff..3a6f12d 100644
--- a/README.md
+++ b/README.md
@@ -1,79 +1,54 @@
-# Outils Python
-
-Ce projet contient des outils de gestion des pyramides de données, écrits en Python.
-
-- [Compilations](#compilations)
-    - [Outils](#outils)
-    - [Documentation](#documentation)
-- [Installation](#installation)
-- [PYR2PYR](#pyr2pyr)
-    - [Fonctionnement](#fonctionnement)
-    - [Configuration](#configuration)
-- [MAKE-LAYER](#make-layer)
+# Outils ROK4 Python
 
+![ROK4 Logo](https://rok4.github.io/assets/images/rok4.png)
 
-## Compilations
-
-### Outils
-
-`VERSION=1.0.0 python setup.py bdist_wheel`
+Ce projet contient des outils de gestion des pyramides de données, écrits en Python.
 
-### Documentation
+- [Installer les outils](#installer-les-outils)
+- [Utiliser les outils](#utiliser-les-outils)
+    - [PYR2PYR](#pyr2pyr)
+        - [Fonctionnement](#fonctionnement)
+        - [Configuration](#configuration)
+    - [MAKE-LAYER](#make-layer)
+- [Compiler la suite d'outils](#compiler-la-suite-doutils)
+- [Publier la suite d'outils sur Pypi](#publier-la-suite-doutils-sur-pypi)
 
-```sh
-pip install json-schema-for-humans pdoc3 jsonschema2md
-mkdir html
-generate-schema-doc bin/*.schema.json ./html/
-```
+## Installer les outils
 
-## Installation
+Installations système requises :
 
-Récupération des artefacts sur GitHub :
+* debian : `apt install python3-rados python3-gdal`
 
-* [Fichier Wheel des librairies](https://github.com/rok4/core-python/releases)
-* [Fichier Wheel des outils](https://github.com/rok4/pytools/releases)
+Depuis [PyPI](https://pypi.org/project/rok4-tools/) : `pip install rok4-tools`
+Depuis [GitHub](https://github.com/rok4/pytools/releases/) : `pip install https://github.com/rok4/pytools/releases/download/x.y.z/rok4_tools-x.y.z-py3-none-any.whl`
 
-Installation dans un environnement :
+L'environnement d'exécution doit avoir accès aux librairies système. Dans le cas d'une utilisation au sein d'un environnement python, précisez bien à la création `python3 -m venv --system-site-packages .venv`.
 
-```sh
-sudo apt install python3-rados
-python -m venv --system-site-packages venv
-source venv/bin/activate
-pip install rok4lib-<VERSION>-py3-none-any.whl
-pip install rok4tools-<VERSION>-py3-none-any.whl
-```
+## Utiliser les outils
 
-Installation système :
-
-```sh
-sudo apt install python3-rados
-sudo pip install rok4lib-<VERSION>-py3-none-any.whl
-sudo pip install rok4tools-<VERSION>-py3-none-any.whl
-```
-
-## PYR2PYR
+### PYR2PYR
 
 PYR2PYR est un outil de copie d'une pyramide d'un stockage à un autre. Il est possible de filtrer les dalles transférée en précisant une taille limite sous laquelle les données ne sont pas recopiées. La copie des dalles est parallélisable. Si des signatures MD5 sont présente dans le fichier liste, elles sont contrôlées après recopie.
 
-Un exemple de configuration est affichable avec la commande `pyr2pyr.py --role example` et l'appel `pyr2pyr.py --role check --conf conf.json` permet de valider un fichier de configuration. Le fichier de configuration peut être un objet, auquel cas le chemin doit être préfixé par le type de stockage (exemple : `s3://bucket/configuration.json`)
+Un exemple de configuration est affichable avec la commande `pyr2pyr --role example` et l'appel `pyr2pyr --role check --conf conf.json` permet de valider un fichier de configuration. Le fichier de configuration peut être un objet, auquel cas le chemin doit être préfixé par le type de stockage (exemple : `s3://bucket/configuration.json`)
 
-### Fonctionnement
+#### Fonctionnement
 
 Une copie complète d'une pyramide implique l'utilisation de l'outil avec les 3 modes suivants, dans cet ordre (tous les modes utilisent le fichier de configuration) :
 
 1. Rôle `master`
     * Actions : génération des N TODO lists, déposé dans un dossier précisé dans la configuration (peut être un stockage objet).
-    * Appel : `pyr2pyr.py --role master --conf conf.json`
+    * Appel : `pyr2pyr --role master --conf conf.json`
 2. Rôle `agent` : 
     * Actions : lecture de la TODO list depuis le dossier de traitement et recopie des dalles
-    * Appel (un appel par TODO list) : `pyr2pyr.py --role agent --conf conf.json --split X`
+    * Appel (un appel par TODO list) : `pyr2pyr --role agent --conf conf.json --split X`
 3. Rôle `finisher` : 
     * Actions : lecture des TODO lists pour écrire le fichier liste final et écriture du descripteur de la pyramide en sortie.
-    * Appel : `pyr2pyr.py --role finisher --conf conf.json`
+    * Appel : `pyr2pyr --role finisher --conf conf.json`
 
-![Enchaînement PYR2PYR](./docs/pyr2pyr.png)
+![Enchaînement PYR2PYR](./docs/images/pyr2pyr.png)
 
-### Configuration
+#### Configuration
 
 Possibilités de contenu du fichier JSON (généré à partir du schéma JSON avec `jsonschema2md bin/pyr2pyr.schema.json /dev/stdout`)
 
@@ -96,8 +71,31 @@ Possibilités de contenu du fichier JSON (généré à partir du schéma JSON av
     - **`slab_limit`** *(integer)*: Minimum slab size (if under, we do not copy). Minimum: `0`. Default: `0`.
 
 
-## MAKE-LAYER
+### MAKE-LAYER
 
 MAKE-LAYER est un outil générant un descripteur de couche compatible avec le serveur à partir des pyramides de données à utiliser
 
-Utilisation : `make-layer [-h] --pyramids storage://path/to/pyr.json[>BOTTOM>TOP] [storage://path/to/pyr.json[>BOTTOM>TOP] ...] --name my data [--styles normal [normal ...]] [--title my data]`
\ No newline at end of file
+Utilisation : `make-layer [-h] --pyramids storage://path/to/pyr.json[>BOTTOM>TOP] [storage://path/to/pyr.json[>BOTTOM>TOP] ...] --name my data [--styles normal [normal ...]] [--title my data]`
+
+
+## Compiler la suite d'outils
+
+```sh
+apt install python3-venv
+python3 -m venv .venv
+source .venv/bin/activate
+python3 -m pip install --upgrade build bump2version
+bump2version --allow-dirty --current-version 0.0.0 --new-version x.y.z patch pyproject.toml src/rok4_tools/__init__.py
+
+# Build artefacts
+python3 -m build
+```
+
+## Publier la suite d'outils sur Pypi
+
+Configurer le fichier `$HOME/.pypirc` avec les accès à votre compte PyPI.
+
+```sh
+python3 -m pip install --upgrade twine
+python3 -m twine upload --repository pypi dist/rok4_tools-x.y.z-py3-none-any.whl dist/rok4_tools-x.y.z.tar.gz
+```
\ No newline at end of file
diff --git a/README.pypi.md b/README.pypi.md
new file mode 100644
index 0000000..67fdea7
--- /dev/null
+++ b/README.pypi.md
@@ -0,0 +1,69 @@
+# ROK4 Python tools
+
+![ROK4 Logo](https://rok4.github.io/assets/images/rok4.png)
+
+The `rok4-tools` package help to use [ROK4 project](https://rok4.github.io/) concepts, like Tile Matrix Sets, data pyramids or layers.
+
+## Installation
+
+Required system packages :
+* debian : `apt install python3-rados python3-gdal`
+
+The `rok4` package is available on :
+* [PyPI](https://pypi.org/project/rok4/) : `pip install rok4`
+* [GitHub](https://github.com/rok4/core-python/releases/) : `pip install https://github.com/rok4/core-python/releases/download/<version>/rok4-<version>-py3-none-any.whl`
+
+## Tools
+
+### PYR2PYR
+
+PYR2PYR allow to copy a pyramid from a storage to another one. It is possible to ignore slab under a provided size. Copy is parallelized. If MD5 hash are in the pyramid's list file, they are used to check integrity after copy.
+
+To obtain an example of JSON configuration, call `pyr2pyr --role example`. To check a JSON configuration, call `pyr2pyr --role check --conf conf.json`. JSON configuratio can be a file or a S3 object(use a path's prefix, for example : `s3://bucket/configuration.json`)
+
+#### Usage
+
+A full copy requires the tool call with the three modes (all need the JSON configuration), in this order :
+
+1. `master` role
+    * Actions : write N TODO lists, in a file or s3 directory.
+    * Call : `pyr2pyr --role master --conf conf.json`
+2. `agent` role : 
+    * Actions : read the TODO list from the work directory and copy slabs
+    * Call (one by TODO list) : `pyr2pyr --role agent --conf conf.json --split X`
+3. `finisher` role: 
+    * Actions : read all TODO lists and write the output pyramid's list file and its descriptor
+    * Call : `pyr2pyr --role finisher --conf conf.json`
+
+![PYR2PYR workflow](https://rok4.github.io/pytools/versions/latest/docs/images/pyr2pyr.png)
+
+#### Configuration
+
+JSON configuration content (generated from the JSON schema with `jsonschema2md bin/pyr2pyr.schema.json /dev/stdout`)
+
+- **`logger`** *(object)*: Logger configuration.
+    - **`layout`** *(string)*: Log format, according to logging python library. Default: `%(asctime)s %(levelname)s: %(message)s`.
+    - **`file`** *(string)*: Path to log file. Standard output is used if not provided.
+    - **`level`** *(string)*: Log level. Must be one of: `['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL', 'NOTSET']`. Default: `WARNING`.
+- **`from`** *(object)*: Pyramid to copy.
+    - **`descriptor`** *(string)*: Path to pyramid's descriptor to copy.
+- **`to`** *(object)*: Pyramid to write.
+    - **`name`** *(string)*: Output pyramid's name.
+    - **`storage`** *(object)*
+        - **`type`** *(string)*: Storage type. Must be one of: `['FILE', 'S3', 'CEPH']`.
+        - **`root`** *(string)*: Storage root : a directory for FILE storage, pool name for CEPH storage, bucket name for S3 storage.
+        - **`depth`** *(integer)*: Tree depth, only for FILE storage. Minimum: `1`. Default: `2`.
+- **`process`** *(object)*: Processing parameters.
+    - **`directory`** *(string)*: Directory to write copies to process, FILE directory or S3/CEPH prefix.
+    - **`parallelization`** *(integer)*: Parallelization level, number of todo lists and agents working at the same time. Minimum: `1`. Default: `1`.
+    - **`follow_links`** *(boolean)*: Do we follow links (data slabs in others pyramids than the 'from' one). Default: `False`.
+    - **`slab_limit`** *(integer)*: Minimum slab size (if under, we do not copy). Minimum: `0`. Default: `0`.
+
+
+### MAKE-LAYER
+
+MAKE-LAYER generate a layer's descriptor, [ROK4 server](https://github.com/rok4/server/) compliant, from pyramids' descriptors
+
+#### Usage
+
+`make-layer [-h] --pyramids storage://path/to/pyr.json[>BOTTOM>TOP] [storage://path/to/pyr.json[>BOTTOM>TOP] ...] --name my data [--styles normal [normal ...]] [--title my data]`
\ No newline at end of file
diff --git a/bin/__init__.py b/bin/__init__.py
deleted file mode 100644
index e69de29..0000000
diff --git a/docs/pyr2pyr.png b/docs/images/pyr2pyr.png
similarity index 100%
rename from docs/pyr2pyr.png
rename to docs/images/pyr2pyr.png
diff --git a/pyproject.toml b/pyproject.toml
new file mode 100644
index 0000000..fea6f31
--- /dev/null
+++ b/pyproject.toml
@@ -0,0 +1,56 @@
+[project]
+
+name = "rok4-tools"
+version = "0.0.0"
+
+description = "Python tools for ROK4 project"
+readme = "README.pypi.md"
+requires-python = ">=3.8"
+license = {file = "LICENSE.txt"}
+
+keywords = ["ROK4", "tools", "data pyramids"]
+
+authors = [
+  {name = "Géoportail Developer", email = "tout_rdev@ign.fr" }
+]
+
+classifiers = [
+
+  "Development Status :: 3 - Alpha",
+
+  "Topic :: Software Development :: Build Tools",
+
+  "License :: CeCILL-C Free Software License Agreement (CECILL-C)",
+
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.8",
+  "Programming Language :: Python :: 3.9",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3 :: Only",
+]
+
+dependencies = [
+  "jsonschema",
+  "rok4 >= 1.4.4"
+]
+
+[project.urls]
+"Homepage" = "https://rok4.github.io/documentation/pytools"
+"Bug Reports" = "https://github.com/rok4/pytools/issues"
+"Changelog" = "https://github.com/rok4/pytools/releases"
+"Source" = "https://github.com/rok4/pytools"
+
+[project.scripts]
+pyr2pyr = "rok4_tools.pyr2pyr:main"
+make-layer = "rok4_tools.make_layer:main"
+
+[tool.setuptools.package-data]
+rok4_tools = ["*.json"]
+
+[build-system]
+requires = ["setuptools>=61.0.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]
diff --git a/setup.py b/setup.py
index f0aed3c..fc1f76c 100644
--- a/setup.py
+++ b/setup.py
@@ -1,19 +1,3 @@
-from setuptools import find_packages, setup
-import os
+from setuptools import setup
 
-setup(
-    name='rok4tools',
-    version=os.environ["VERSION"],
-    scripts=["bin/pyr2pyr.py", "bin/make-layer.py"],
-    data_files=[
-        ('bin', [
-            'bin/pyr2pyr.schema.json',
-            'bin/pyr2pyr.example.json'
-        ])
-    ],
-    description='Python tools for ROK4 project',
-    author='Géoportail<tout_rdev@ign.fr>',
-    url='https://github.com/rok4/pytools',
-    install_requires=['rok4lib >= 1.2.0', 'jsonschema'],
-    setup_requires=['wheel']
-)
\ No newline at end of file
+setup()
\ No newline at end of file
diff --git a/src/rok4_tools/__init__.py b/src/rok4_tools/__init__.py
new file mode 100644
index 0000000..3aa0d7b
--- /dev/null
+++ b/src/rok4_tools/__init__.py
@@ -0,0 +1 @@
+__version__ = "0.0.0"
\ No newline at end of file
diff --git a/bin/make-layer.py b/src/rok4_tools/make_layer.py
similarity index 93%
rename from bin/make-layer.py
rename to src/rok4_tools/make_layer.py
index 8251cd0..c4e99ab 100755
--- a/bin/make-layer.py
+++ b/src/rok4_tools/make_layer.py
@@ -83,7 +83,7 @@
     action='store',
     dest='directory',
     metavar="s3://layers_bucket",
-    help="Directory (file or object) where to write layer's descriptor. Print in standard output if ot provided",
+    help="Directory (file or object) where to write layer's descriptor. Print in standard output if not provided",
     required=False
 )
 
@@ -118,14 +118,15 @@ def work():
 
     layer.write_descriptor(args.directory)
 
-if __name__ == "__main__":
-    # try:
-    #     work()
+def main():
+    try:
+        work()
 
-    # except Exception as e:
-    #     logging.error(e)
-    #     sys.exit(1)
-
-    work()
+    except Exception as e:
+        logging.error(e)
+        sys.exit(1)
 
     sys.exit(0)
+
+if __name__ == "__main__": 
+    main()
\ No newline at end of file
diff --git a/bin/pyr2pyr.example.json b/src/rok4_tools/pyr2pyr.example.json
similarity index 100%
rename from bin/pyr2pyr.example.json
rename to src/rok4_tools/pyr2pyr.example.json
diff --git a/bin/pyr2pyr.py b/src/rok4_tools/pyr2pyr.py
similarity index 98%
rename from bin/pyr2pyr.py
rename to src/rok4_tools/pyr2pyr.py
index 7201e10..402d139 100755
--- a/bin/pyr2pyr.py
+++ b/src/rok4_tools/pyr2pyr.py
@@ -14,6 +14,7 @@
 
 from rok4.Pyramid import Pyramid
 from rok4 import Storage
+from rok4_tools import __version__
 
 # Default logger
 logging.basicConfig(format='%(asctime)s %(levelname)s: %(message)s', level=logging.WARNING)
@@ -25,6 +26,12 @@
     epilog = ''
 )
 
+parser.add_argument(
+    '--version',
+    action='version',
+    version='%(prog)s ' + __version__
+)
+
 parser.add_argument(
     '--role',
     choices=["master", "agent", "finisher", "example", "check"],
@@ -371,7 +378,7 @@ def finisher_work():
     except Exception as e:
         raise Exception(f"Cannot concatenate splits' done lists and write the final output pyramid's list to the final location: {e}")
 
-if __name__ == "__main__": 
+def main():
 
     if args.role == "example":
         # On veut juste afficher la configuration en exemple
@@ -416,4 +423,7 @@ def finisher_work():
         logging.error(e)
         sys.exit(1)
 
-    sys.exit(0)
\ No newline at end of file
+    sys.exit(0)
+
+if __name__ == "__main__": 
+    main()
\ No newline at end of file
diff --git a/bin/pyr2pyr.schema.json b/src/rok4_tools/pyr2pyr.schema.json
similarity index 100%
rename from bin/pyr2pyr.schema.json
rename to src/rok4_tools/pyr2pyr.schema.json