Improve documentation for sensitivity module (refs #3876)

[lpofredc]

Description

The purpose of this pull request is to integrate sensitive module notices into GeoTrek documentation.

Related Issue

#3876

Checklist

• I have followed the guidelines in our Contributing document
• My code respects the Definition of done available in the Development section of the documentation
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes
• I added an entry in the changelog file
• My commits are all using prefix convention (emoji + tag name) and references associated issues
• I added a label to the PR corresponding to the perimeter of my contribution
• The title of my PR mentionned the issue associated

[babastienne]

Thanks for your much needed contribution to the documentation ! 🙏

Few comments :

• For three files (authors.po changelog.po and install.po), I'm not sure why you put them in the PR as I don't see any modification ? Also it is a good practice to add the parameter --no-location when you run the makemessages command in order to avoid having all the line number modifications.
• I added some context / few minor corrections. It it suits you don't hesitate to commit them and regenerate the translations accordingly.
• I'm in doubt about the organisation of the files. Why did you move this documentation in the "user manual" section ? It seems to me that information about API and import data is quite technical, don't you think ? And I have the feeling that the information is separated in two pages but still quite the same as there will be information about the procedure to import data on one page and the details about the data format on another. (maybe @camillemonchicourt can give us his pov ?)
• I think if we talk about importing data, we should mention at least the possiblity to import all data directly from network. I added a suggestion in this regard.

[camillemonchicourt]

Yes it should grouped in one section, certainly Import, and it is not to go into User manual, but rather in technical parts for administrators.

[cypress]

Passing run #9093 ↗︎

0

22

0

0

0

Details:

Merge 7c937ee into c7475d5...
Project: Geotrek-admin	Commit: b7c3472d36 ℹ️
Status: Passed	Duration: 02:04 💡
Started: May 30, 2024 1:17 PM	Ended: May 30, 2024 1:19 PM

Review all test suite changes for PR #3877 ↗︎

[lpofredc]

Documentation revue et restructurée:

• Activation du module dans docs/install/advanced-configuration.rst
• Import des données (soit depuis BiodivSports soit depuis un shapefile) dans docs/install/import.rst
• Utilisation de l'API dans docs/usage/apis.rst

[lpofredc]

@babastienne, @bruhnild, is there any new missing requirements for that PR or could it be merged?

[babastienne]

It looks good

[babastienne]

Thanks for your contribution @lpofredc, this pull request has been merged.

The official documentation will be updated with your changes when we'll release the next version of Geotrek.