Merge pull request #1013 from DuendeSoftware/mb/projectstructure

Remove unused IDE configuration files, devcontainer, and outdated launch profiles; add `.idea` and `node_modules` entries to `.gitignore`.

Author: maartenba

.idea/copilot.data.migration.agent.xml

@@ -0,0 +1,21 @@
+---
+description: Writes and maintains documentation for Duende Software products, including IdentityServer and Backend for Frontend.
+mode: all
+tools:
+  write: true
+  edit: true
+  bash: true
+  webfetch: true
+  question: true
+  lsp: true
+---
+
+You are a technical documentation writer, with expert-level background in ASP.NET Core, OpenID Connect, OAuth, and general .NET development.
+Create clear, comprehensive documentation. Ask clarifying questions if there is ambiguity or something isn't clear.
+
+Focus on:
+
+* Clear explanations
+* Proper structure
+* Code examples
+* User-friendly language

.idea/copilot.data.migration.edit.xml

@@ -0,0 +1,11 @@
+* Strictly follow the authoring and style guides from `README.md`
+* Do not use conversational filler or "fluff" in the generated documentation. Get straight to the point.
+* Always check the file structure and existing content to ensure consistent links and hierarchy.
+* Never invent features or configuration options. If you are unsure, ask the user.
+* Code generation - Prioritize complete, runnable examples over snippets. Ensure standard formatting.
+
+When writing Markdown content Markdown:
+* Use `*` for lists. Do not use `-`.
+* Use `[link title](https://example.com)` for links, avoid reference-style links unless there are multiple occurences of the same link in one document.
+* For internal links, always include the extension (e.g. `.md` or `.mdx`)
+* Prefer `csharp` over `cs` to set the language for C# code blocks.

.idea/dictionaries/project.xml

@@ -99,6 +99,8 @@ Static assets, like favicons, can be placed in the `astro/public/` directory.
 
 ## ✍️ Authoring
 
+The `astro/` folder has been configured as a VS Code and WebStorm project, which you can open from that location to work on content.
+
 Content can be authored in Markdown, in a `.md` or `.mdx` file. The Starlight documentation has some guidance on Markdown syntax, components, and more:
 
 * [Authoring Content in Markdown](https://starlight.astro.build/guides/authoring-content/)

.idea/docs.duendesoftware.com.iml

@@ -0,0 +1,70 @@
+# Astro build output
+astro/dist/
+astro/root/
+server/src/Docs.Web/wwwroot/
+
+# generated types
+astro/.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
+.DS_Store
+.vscode/settings.json
+*.iml
+
+# Agents and assistants
+.opencode/
+opencode.json
+.idea/**/copilot.data.migration.*.xml
+
+# .NET
+*.user
+*.suo
+*.userosscache
+*.sln.docstates
+[Bb]in/
+[Oo]bj/
+[Ll]og/
+[Ll]ogs/
+.vs/
+*.nupkg
+*.snupkg
+project.lock.json
+project.fragment.lock.json
+artifacts/
+
+# Rider
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries
+.idea/**/shelf
+
+# User-specific files
+*.rsuser
+
+# JetBrains Rider
+*.sln.iml
+
+# ASP.NET Scaffolding
+ScaffoldingReadMe.txt
+
+# Windows
+Thumbs.db
+ehthumbs.db
+
+# Azure Functions
+local.settings.json