readme added and files moved to folders with same name as file

.vscode/settings.json

@@ -0,0 +1,5 @@
+{
+    "java.project.sourcePaths": [
+        "docs"
+    ]
+}

README.md

@@ -272,3 +272,8 @@ Plugin developers wanting to support JCasC in their plugin should [check out our
 As configuration as code is demonstrated to be a highly requested topic in the Jenkins community, we have published
 [JEP 201](https://github.com/jenkinsci/jep/tree/master/jep/201) as a proposal to make this a standard component
 of the Jenkins project. The proposal was accepted. :tada:
+
+## Developer Guide
+
+For detailed information about recent changes made by developers, including configurations, adjustments, and guidelines for contributing to the project, please see the [Developer Changes README](docs\developer\README.md).
+

docs/developer/README.md

@@ -0,0 +1,9 @@
+Developer Changes Guide
+
+## Current Status
+At the moment, there have been no changes made by the developer. Once the developer starts contributing, all changes will be tracked and documented here.
+
+## Future Changes 
+Once the developer begins making changes, the following will be tracked:  Code modifications Configuration updates Any new features or bug fixes
+## How to Track Changes 
+Make Changes Locally Developers should make their changes in a local branch.  Commit Changes Once changes are made, commit them with a descriptive message indicating what was changed.  Push Changes After committing, push the changes to the remote repository.  Document Changes Here Document any significant changes here, with details about what was modified and why.