Revert "feat: update changelog and other related files"

This reverts commit fbf203e.

Author: ChengShi-1

.github/CONTRIBUTING.md

@@ -103,50 +103,26 @@ Thanks for your contribution!
 
 ## Changelog Guidelines
 
-**Every pull request must include a changelog fragment.** This helps users and developers track what has been added, changed, fixed, or removed between versions. The changelog maintains transparency about project evolution and helps users understand the impact of updates.
+When contributing to this project, it's important to document your changes in the changelog to help users and developers understand what has been added, changed, fixed, or removed between versions. The changelog helps maintain transparency about project evolution and assists users in understanding the impact of updates. We also have another changelog for design system, so for any design system changes, please include them in that changelog.
 
-We maintain separate changelogs for different components:
+### When to Add Changelog Entries
 
-- **Main application changes**: Create fragments in [`docs/release-notes/`](../docs/release-notes/)
-- **Design system changes**: For changes affecting design system components, update to [`packages/design-system/CHANGELOG.md`](../packages/design-system/CHANGELOG.md)
-
-### What Needs to Be in the Changelog?
-
-Include developer-visible changes that affect the product, APIs, or workflows:
-
-- **UI changes** (new buttons, wording, layouts)
-- **Behavior changes** (URLs, shortcuts, keyboard navigation)
-- **Bug fixes** that alter what users experience
-- **Performance or accessibility improvements** users benefit from
-- **Breaking changes** (anything that requires action to upgrade)
-- **Developer-relevant refactors** (if they affect interfaces, tooling, or expected dev workflows)
-
-**All pull requests require a changelog entry.** Document your changes in the appropriate category:
+Add a changelog entry for changes, including:
 
 - **Added**: New features, components, or functionality
 - **Changed**: Changes to existing functionality, API modifications, or behavior updates
 - **Fixed**: Bug fixes and issue resolutions
 - **Removed**: Deprecated features or removed functionality
-  If breaking, prefix with BREAKING: and include a 1-line upgrade note.
 
 ### How to Add Changelog Entries
 
-1. **Create a changelog fragment**: Create a new markdown file in `docs/release-notes/` with a descriptive name related to your change and issue number (if applicable)
-
-2. **File naming convention**: Use format like `ISSUE_NUMBER-brief-description.md` or `brief-description.md`
-
-3. **Add your entry**: In the file, add your entry under the appropriate category (`Added`, `Changed`, `Fixed`, or `Removed`)
-
-### Example Changelog Fragments
-
-**Example 1: Documents Addition (Issue #828)**
-File: `docs/release-notes/add-changelog.md`
+1. **Edit the CHANGELOG.md file**: Add your entry under the `[Unreleased]` section in the appropriate category (`Added`, `Changed`, `Fixed`, or `Removed`)
 
-```markdown
-### Added
+2. **Follow the format**: Use this structure for entries:
 
-- Add new CHANGELOG.md and its guidance to the repository (#828)
-```
+   ```markdown
+   - Brief description of the change (#ISSUE_NUMBER)
+   ```
 
 ## Other ways to contribute to the code
 

docs/release-notes/CHANGELOG.md CHANGELOG.mddocs/release-notes/CHANGELOG.md renamed to CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to **Dataverse Frontend** are documented here. We also maintain a separate [Design System Changelog](../../packages/design-system/CHANGELOG.md) for component-specific changes.
+All notable changes to **Dataverse Frontend** are documented here. We also maintain a separate [Design System Changelog](./packages/design-system/CHANGELOG.md) for component-specific changes.
 
 This changelog follows the principles of [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and adheres to [Semantic Versioning](https://semver.org/). This document is intended for developers, contributors, and users who need to understand the technical details.
 

DEVELOPER_GUIDE.md

@@ -580,7 +580,7 @@ This project maintains a changelog following the [Keep a Changelog](https://keep
 #### When Working on Features
 
 1. **During Development**: Add entries to the `[Unreleased]` section as you implement changes
-2. **Before PR Submission**: PR should include a changelog fragment if it should be included
+2. **Before PR Submission**: Ensure all user-facing changes have appropriate changelog entries
 3. **PR Review**: Reviewers will verify changelog entries are complete and properly formatted
 
 #### Changelog Entry Guidelines

README.md

@@ -282,11 +282,11 @@ For more information on the Dataverse re-architecture project, see the original
 
 ## Changelog
 
-All notable changes to this project are documented in our [CHANGELOG.md](docs/release-notes/CHANGELOG.md). The changelog follows the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format and adheres to [Semantic Versioning](https://semver.org/).
+All notable changes to this project are documented in our [CHANGELOG.md](CHANGELOG.md). The changelog follows the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format and adheres to [Semantic Versioning](https://semver.org/).
 
 We also maintain a separate [Design System Changelog](./packages/design-system/CHANGELOG.md) for component-specific changes.
 
-**For Contributors**: **Every pull request must include a changelog entry.** See our [Changelog Guidelines](.github/CONTRIBUTING.md#changelog-guidelines) for details on format and requirements.
+**For Contributors**: Please ensure you add appropriate changelog entries for user-facing changes when submitting pull requests. See our [Changelog Guidelines](.github/CONTRIBUTING.md#changelog-guidelines) for details.
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 <br>

docs/making-releases.md

@@ -40,16 +40,49 @@ npm version 3.5.0 --no-git-tag-version
 
 This command will update the version in the `package.json` and `package-lock.json`.
 
-## Consolidate Changelog Fragments
+## Update the Changelog
 
-Before releasing, consolidate all changelog fragments into the main changelog:
+Before releasing, ensure the changelog is properly prepared:
 
-1. **Collect all fragments** from [`docs/release-notes/`](../docs/release-notes/) directory (all `.md` files)
-2. **Group entries by category** from all fragments (`Added`, `Changed`, `Fixed`, `Removed`)
-3. **Create the release section** in the main changelog [`docs/release-notes/CHANGELOG`](../docs/release-notes/CHANGELOG.md) by consolidating all fragment entries
-4. **Clear the fragment directory** - Delete all processed fragment files after consolidation
-5. **Update version links** at the bottom of the changelog file
-6. **Commit the changelog updates** as part of the release preparation
+1. **Review the [Unreleased] section** in `CHANGELOG.md` and `packages/design-system/CHANGELOG.md`
+2. **Move entries from [Unreleased] to the new version section**:
+
+   ```markdown
+   ## [vX.X.X] -- YYYY-MM-DD
+
+   ### Added
+
+   - Feature descriptions from unreleased section
+
+   ### Changed
+
+   - Changes from unreleased section
+
+   ### Fixed
+
+   - Bug fixes from unreleased section
+
+   ### Removed
+
+   - Removals from unreleased section
+   ```
+
+3. **Clear the [Unreleased] section** but keep the structure:
+
+   ```markdown
+   ## [Unreleased]
+
+   ### Added
+
+   ### Changed
+
+   ### Fixed
+
+   ### Removed
+   ```
+
+4. **Update the version links** at the bottom of the changelog files
+5. **Commit the changelog updates** as part of the release preparation
 
 ## Use the Latest Dataverse Client Javascript Version