Report notes, methods, and issues
methodatlas depends on methods being described precisely, sourced well, and placed in the right context. If something is missing, noticeable, or worth improving, send a quick email.
A form will make sense once the right technical mechanism is in place. For now, email is the deliberately simple path because suggestions often need context, links, and short explanations.
methodatlas is a personal project, so a reply can take a few days. If no mail app opens, copy the address into your mail service.
How you can help
Each card opens an email with a matching subject and short template.
Suggest a method
If a method is missing from the atlas, send the name, context, short rationale, and ideally a credible source.
Report an issue
Notes about broken links, wrong descriptions, unclear visuals, or technical problems directly help maintain the catalog.
Add a source
If a method needs better primary sources, books, papers, or official documentation, a source note is very welcome.
Give feedback
Feedback on search, recommendation, comparison, or clarity of method entries is useful too.
What a good submission includes
The more concrete the note is, the easier it is to review and include it in the JSON-based catalog. Sources, clear boundaries to similar methods, and a short practice case are especially useful.
- Which method or page does the note concern?
- What is unclear, wrong, broken, or missing?
- Which source supports the addition?
- In which practice context is the method useful?
Direct contact
Email: michael@meierhoff-systems.dePlease do not send confidential customer data, API keys, or internal documents. Publicly accessible sources and a short description are enough for method suggestions.