Add maintenance-mode announcement to documentation

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,31 +1,56 @@
 ---
 name: Bug report
-about: Report a problem
-title: ''
-labels: bug
-assignees: ''
-
+about: Report a reproducible problem in AllenSDK
+title: "[Bug]: "
+labels: ["bug"]
+assignees: ""
 ---
 
-**Describe the bug**
-A summary of what the bug is. 
+<!--
+Thanks for reporting this issue.
+
+AllenSDK is in selective maintenance mode:
+- We prioritize bug fixes, security fixes, docs/tests, and targeted compatibility updates.
+- Some issues may be closed as "not planned" based on scope and maintainer capacity.
+-->
+
+## Describe the bug
+
+A clear and concise description of the problem.
+
+## To reproduce
+
+Please provide a minimal, reproducible example.
 
-**To Reproduce**
-Steps to reproduce the behavior. Please include all relevant code!
+1.
+2.
+3.
+
+Include code, command line calls, config, and relevant input data details where possible.
+
+## Expected behavior
 
-**Expected behavior**
 What you expected to happen.
 
-**Actual Behavior**
-What actually happened. If the bug produced an error message or incorrect values, please include them here!
+## Actual behavior
+
+What actually happened.
+Please include full error messages/tracebacks and unexpected outputs.
+
+## Environment
+
+- OS and version:
+- Python version:
+- AllenSDK version:
+- Install method (pip/conda/source):
+- Execution context (local/CI/notebook/cluster):
+- Any pinned dependencies or unusual environment details:
+
+## Additional context
 
-**Environment (please complete the following information):**
- - OS & version: [e.g. Ubuntu 18.04]
- - Python version [e.g. 3.7]
- - AllenSDK version [e.g. v1.0.0]
+Any other context, screenshots, logs, links to related issues, or workarounds tried.
 
-**Additional context**
-Add any other context about the problem here.
+## Are you willing to submit a fix?
 
-**Do you want to work on this issue?**
-Are you willing and able to fix this bug? If so, let us know here (and see [the guide](https://github.com/AllenInstitute/AllenSDK/blob/master/CONTRIBUTING.md)). Thank you!
+- [ ] Yes, I can work on a PR for this
+- [ ] No, but I can help test a proposed fix

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Allen Brain Map Community Forum
+    url: https://community.brain-map.org
+    about: Ask general Allen Brain Map or data/tool questions here.
+  - name: AllenSDK documentation
+    url: https://allensdk.readthedocs.io/en/latest/
+    about: Check install, API, and usage docs before filing an issue.
+  - name: Support guide
+    url: https://github.com/AllenInstitute/AllenSDK/blob/master/SUPPORT.md
+    about: Where to ask questions, report bugs, and request features.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,23 +1,42 @@
 ---
 name: Feature request
-about: Suggest a new feature
-title: ''
-labels: enhancement
-assignees: ''
-
+about: Propose a new capability for AllenSDK
+title: "[Feature]: "
+labels: ["enhancement"]
+assignees: ""
 ---
 
-**Describe the use case that is addressed by this feature.**
-The problem that this feature would solve.
+<!--
+Thanks for the suggestion.
+
+AllenSDK is in selective maintenance mode:
+- Maintainers are not planning new feature development.
+- Community feature PRs are welcome.
+- Requests or PRs may be closed as "not planned" if maintenance burden is too high.
+-->
+
+## Problem / use case
+
+Describe the user problem this feature would solve and who benefits.
+
+## Proposed solution
+
+Describe what you want to happen.
+
+## Alternatives considered
+
+Describe alternative approaches, including why they are not sufficient.
+
+## Maintenance considerations
+
+Briefly describe any backward compatibility, dependency, or long-term maintenance concerns.
 
-**Describe the solution you'd like**
-What you want to happen.
+## Additional context
 
-**Describe alternatives you've considered**
-Any alternative solutions or features you've considered.
+Add examples, mock APIs, references, or related issues/PRs.
 
-**Additional context**
-Add any other information about the feature request here.
+## Implementation interest
 
-**Do you want to work on this issue?**
-Are you willing and able to work on this feature? If so, let us know here (and see [the guide](https://github.com/AllenInstitute/AllenSDK/blob/master/CONTRIBUTING.md)). Thank you!
+- [ ] I can work on a PR
+- [ ] I can help with design/review/testing
+- [ ] I cannot contribute implementation right now

.github/ISSUE_TEMPLATE/question.md

@@ -1,8 +1,39 @@
 ---
 name: Question
-about: Question about the AllenSDK
-title: ''
-labels: 'question'
-assignees: ''
-
+about: Ask a usage question about AllenSDK
+title: "[Question]: "
+labels: ["question"]
+assignees: ""
 ---
+
+<!--
+For general Allen Brain Map / data-tool questions, please use the community forum:
+https://community.brain-map.org
+
+Use this template for AllenSDK-specific usage questions.
+For broad roadmap/new-feature discussions, please open a Feature request issue instead.
+-->
+
+## Question
+
+What are you trying to do, and what is your specific question?
+
+## What you tried
+
+Please include code snippets, commands, and links to docs/examples you already checked.
+
+## Minimal example (recommended)
+
+Provide a small reproducible snippet or pseudo-code showing the issue/question context.
+
+## Environment
+
+- OS and version:
+- Python version:
+- AllenSDK version:
+- Install method (pip/conda/source):
+- Execution context (local/CI/notebook/cluster):
+
+## Additional context
+
+Anything else that may help (tracebacks, screenshots, data modality, related issues/PRs).

.github/MAINTAINER_RESPONSES.md

@@ -0,0 +1,40 @@
+### Not planned (feature out of scope)
+
+Thanks for the proposal. This could be useful, but this project is in
+selective maintenance mode and maintainers are not taking on new feature
+development right now.
+
+Given current scope/capacity, we're closing as **not planned**.
+
+If you'd like to contribute this, we're open to reviewing a focused PR with
+tests and a clear long-term maintenance story.
+
+---
+
+### Not planned (compatibility cost too high)
+
+Thanks for the report. We confirmed this compatibility gap, but addressing it
+would require substantial refactoring and ongoing maintenance beyond current
+project scope/capacity.
+
+For that reason, we're closing as **not planned**.
+
+If someone wants to propose a minimal, low-risk patch with tests, we can reconsider.
+
+---
+
+### Needs contributor follow-through
+
+Thanks -- we're open to this direction, but we can't prioritize implementation
+right now.
+
+Marking this as **help wanted**. A PR is welcome.
+
+---
+
+### Stale / inactive
+
+This issue has had no activity for an extended period. Closing for now to keep
+the tracker focused.
+
+If this is still relevant, feel free to reopen with updated context or a linked PR.