@atztogo @lan496 For this PR please go ahead and push/merge/rebase however you want on my branch, I will clean things later

$ git remote add LecrisUT git@github.com:LecrisUT/spglib.git
$ git fetch LecrisUT
$ git pull --rebase
$ git push

It would be best to use sphinx-autobuild to get live preview of the contents

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.59%. Comparing base (f1ff014) to head (87cd0f4).
⚠️ Report is 294 commits behind head on develop.

@@           Coverage Diff            @@
##           develop     #450   +/-   ##
========================================
  Coverage    83.59%   83.59%           
========================================
  Files           24       24           
  Lines         8118     8118           
  Branches      1688     1688           
========================================
  Hits          6786     6786           
  Misses        1332     1332           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

My initial sketch of the organization is:

$ tree -I "_build" -I "python-api" --dirsfirst ./doc
./doc
├── api
│   ├── c
│   │   └── index.md
│   ├── fortran
│   │   └── index.md
│   ├── python
│   │   └── index.md
│   ├── develop.md
│   └── index.md
├── development
│   ├── develop.md
│   ├── magnetic_symmetry_flags.md
│   └── performance.md
├── interface
│   ├── c.md
│   ├── fortran.md
│   ├── index.md
│   ├── julia.md
│   ├── python.md
│   ├── rust.md
│   └── variable.md
├── physics
│   ├── dataset.md
│   ├── definition.md
│   ├── magnetic_dataset.md
│   └── variable.md
├── _static
│   ├── change-of-basis.ai
│   └── change-of-basis.png
├── codespell.txt
├── conf.py
├── index.md
├── Makefile
├── README.md
├── references.bib
├── references.md
└── releases.md

But we should look at other references like the ones mentioned in #389

@LecrisUT, I am not familiar with git. I tried to change same as #449 as a part of "Improve the documentation contents" (am I correctly understanding what you mean in this PR?), but failed. I have no immediate change other than that, so please go ahead, and call me whenever you want.

@LecrisUT, I am not familiar with git. I tried to change same as #449 as a part of "Improve the documentation contents" (am I correctly understanding what you mean in this PR?), but failed. I have no immediate change other than that, so please go ahead, and call me whenever you want.

Ok, we can workshop that part in #449, and I will cherry-pick/rebase the contents later. Mainly the content should be in README.md after this PR.

Ok, we can workshop that part in #449, and I will cherry-pick/rebase the contents later. Mainly the content should be in README.md after this PR.

Thanks. In case it is easier, it can be done just copy & paste, and I will close #449.

Ok, we can workshop that part in #449, and I will cherry-pick/rebase the contents later. Mainly the content should be in README.md after this PR.

Thanks. In case it is easier, it can be done just copy & paste, and I will close #449.

No worries, I can handle that, and I would prefer to have it easily navigate the discussions anyway.

I would suggest to rename "physics" section to other more appropirate one line "concepts".