Apps doc updates

[andamian]

No description provided.

[andamian]

@molinaro-m - this looks better. Thanks for the tip.

[molinaro-m]

Perfect! Now it works, both locally and on the webtest preview branch

[molinaro-m]

@molinaro-m - this looks better. Thanks for the tip.

it's more like what we will operate tomorrow.
I think the fork+PR will need to be the forward mechanism when this goes production.

[JeremyMcCormick]

Conflict on content/_index.html needs to be fixed. There was a big update to the site style that you probably don't have integrated into your branch.

Second, more minor issue, and not to be too picky about Git stuff since we haven't broadcasted this widely yet, but apps is not a very good branch name. What we are preferring is making an issue in the tracker first, then using it in the name like iss1234 or iss1234-port-apps. I won't block the PR based on this (just the conflict needs to be fixed), but please in the future make an issue first and then name your branch after it.

[gmantele]

This conflict is because of my last commit. All the links are now in a different file: layout/partials/sitemap.html. This way, it can be put at the bottom of all pages.

[JeremyMcCormick]

The date can be left out - this is not correct anyways and Hugo will insert it automatically.

[JeremyMcCormick]

This conflict is because of my last commit. All the links are now in a different file: layout/partials/sitemap.html. This way, it can be put at the bottom of all pages.

Okay, maybe you could resolve this then instead of @andamian ?

[gmantele]

I can, indeed. I will probably wait for the PR #23 to be merged first, as it touches as well the sitemap.html file in the way it is done in this PR.

[gmantele]

By the way, should this PR stay a Draft?

[andamian]

@gmantele and @JeremyMcCormick - thanks for the feedback. This is a draft PR that I've started in preparation for the hackathon. I can probably solve the conflict at the end when the PR is ready which right now is not. The Apps page has not been worked on.

[JeremyMcCormick]

@gmantele and @JeremyMcCormick - thanks for the feedback. This is a draft PR that I've started in preparation for the hackathon. I can probably solve the conflict at the end when the PR is ready which right now is not. The page Apps page has not been worked on.

Understood, we can look at this tomorrow then. 👍

[andamian]

@JeremyMcCormick - I'm probably jumping the gun here without having clear directions on how we are going to proceed. I just assumed that in this PR we will fix all the issues raised in https://docs.google.com/spreadsheets/d/15TE9LCNdDyBhAQF_TyX2AqXSXW8RxQqHkU_bBKxQK7I/edit#gid=0. I will adapt later if that's not the case.

[JeremyMcCormick]

@JeremyMcCormick - I'm probably jumping the gun here without having clear directions on how we are going to proceed. I just assumed that in this PR we will fix all the issues raised in https://docs.google.com/spreadsheets/d/15TE9LCNdDyBhAQF_TyX2AqXSXW8RxQqHkU_bBKxQK7I/edit#gid=0. I will adapt later if that's not the case.

Yes, we are hoping to fix at least some of those issues.

Please read the contribution guide:

https://github.com/ivoa/ivoa-web/blob/main/CONTRIBUTING.md

It may clear some things for you in terms of recommended developer workflow.

[gmantele]

Now that the main conflicting changes are done, maybe we should try to fix the conflict in this branch so that the editing team can work with no problem this afternoon.

[JeremyMcCormick]

Now that the main conflicting changes are done, maybe we should try to fix the conflict in this branch so that the editing team can work with no problem this afternoon.

@gmantele @andamian

I have a strong preference that we do not use freeform branch names for major updates to the site.

Can we instead put these changes on a branch that references an issue in the tracker and then open a new PR?

I have made a new issue for adding the applications page:

#25

@andamian You may keep existing changes by branching from your existing one like git checkout apps && git checkout -b iss25, which will keep your work. Then you can just open a PR on the new branch. This will be useful for bookkeeping so we can easily see how branches are connected to which issues.

[andamian]

Replaced with #26