replace danse links (without documentations)

[Tieqiong]

This PR is for replacing the danse links (not including the links related to documentations). Those will be included in a later PR. Together will closes the two previous PRs (#202 and #203 )

@sbillinge As for the documentation links, it seems like some of them were not deployed (even though we have run the deploy workflows). This can be checked under the Action tab Management field. The good ones (like structure) has the Deployment link and GitHub-pages bot ran. But for packages like pdfgui, pdffit2, cookiecutter they don't have the api/documentation pages release.

I think there are configurations needed to be changed in the repo settings-Code and automation-Pages

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.11%. Comparing base (dd9f989) to head (a52ab22).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #239   +/-   ##
=======================================
  Coverage   95.11%   95.11%           
=======================================
  Files          23       23           
  Lines        1126     1126           
=======================================
  Hits         1071     1071           
  Misses         55       55           

Files with missing lines	Coverage Δ
tests/test_aboutdialog.py	96.96% <100.00%> (ø)

[sbillinge]

This PR is for replacing the danse links (not including the links related to documentations). Those will be included in a later PR. Together will closes the two previous PRs (#202 and #203 )

@sbillinge As for the documentation links, it seems like some of them were not deployed (even though we have run the deploy workflows). This can be checked under the Action tab Management field. The good ones (like structure) has the Deployment link and GitHub-pages bot ran. But for packages like pdfgui, pdffit2, cookiecutter they don't have the api/documentation pages release.

I think there are configurations needed to be changed in the repo settings-Code and automation-Pages

Thanks for this Tieqiong. Please can you make an issue to re-cookiecut gui and fit2? I will merge this for now

[Tieqiong]

@sbillinge Thanks. Just to make sure, we want to re-cookiecut gui and fit2 again? (as I thought we are almost there for releasing them). So we added more things to the cookiecutter?

[sbillinge]

@sbillinge Thanks. Just to make sure, we want to re-cookiecut gui and fit2 again? (as I thought we are almost there for releasing them). So we added more things to the cookiecutter?

I thought you mentioned that the GitHub workflows need to be updated so the docs will build correctly.

[Tieqiong]

@sbillinge ah I think it's not about the workflows, as they are all using the same one. It's the GitHub repository settings that make sure GitHub-pages bot can generate and deploy pages on Github's side. I believe cookiecutter is the one that bob recutted lately, and it also doesn't have docs deployed, even if it has a deploy docs workflow.

I think it's just the GitHub-page bot is not setup correctly in the repository setting. I guess it's related to some configurations at Settings-Code and automation-Pages

[sbillinge]

@sbillinge ah I think it's not about the workflows, as they are all using the same one. It's the GitHub repository settings that make sure GitHub-pages bot can generate and deploy pages on Github's side. I believe cookiecutter is the one that bob recutted lately, and it also doesn't have docs deployed, even if it has a deploy docs workflow.

I think it's just the GitHub-page bot is not setup correctly in the repository setting. I guess it's related to some configurations at Settings-Code and automation-Pages

Ah, ok, I can work on that.