Add CHANGELOG and Update Documents

[ChengShi-1]

What this PR does / why we need it:

Based on Changelog Strategy doc, and #804 , we discussed on the frontend meeting Sep11th 2025, we decide to move forward and create an issue to add CHANGELOG to the front repo.

Which issue(s) this PR closes:

• Closes Add CHANGELOG and Update Documents #828

Special notes for your reviewer:

Suggestions on how to test this:

Documents change only, it'll be good if you could review the markdown format and wording

Is there a release notes update needed for this change?:

Add Changelog.md to the repo and update related markdown files, such as README, Contributing...

[ekraffmiller]

A general question, I think in our meeting we decided that each PR would have a corresponding update to the Changelog? If so, we could make the documentation more clear about that.

[coveralls]

coverage: 97.448% (-0.6%) from 98.052%
when pulling 774e465 on 828-add-changelog-and-update-documents
into ca0c27f on develop.

[ChengShi-1]

@ekraffmiller sorry, I didn't update it to my draft so forgot this. I add a folder named releases-note to collect the changelog fragments, which is similar to what we did in dataverse repo. Thanks for reviewing

[ekraffmiller]

In our meeting I think we discussed updating the CHANGELOG.md directly, rather than creating individual fragments for each PR. We discussed how there would be merge conflicts but they would be relatively straightforward to resolve. Unless I am misremembering?

[ChengShi-1]

Ohh, I see—I misunderstood. I thought the part about merge conflicts was explaining why we don’t need an automation tool, and I also thought you were referring to me missing the fragment part last comment. Sorry about that! But it makes sense now, and I can change it back.

[ekraffmiller]

looks good, approved!