Contact DFM2HTML: Get Help, Report Issues, Share Feedback

This is the contact page for DFM2HTML, the Windows desktop HTML editor. Whether you have a support question, need to report a problem, want to suggest a documentation improvement, or have a general inquiry, this page explains how to reach out and what to expect. Below you will find guidance on support questions, issue reporting, documentation feedback, response expectations, and a contact form. Before submitting a request, check the self-service resources listed here. The support hub, FAQ, tutorials, and community forum answer most questions faster than a direct message can.

Support Questions

If you have a question about using DFM2HTML, the fastest path to an answer usually starts with the existing documentation. The FAQ covers the most commonly asked questions about installation, export, templates, browser behavior, JavaScript menus, publishing, and caching. The tutorials provide step-by-step workflow guides organized by learning path. The support page organizes troubleshooting by symptom so you can find the right resource based on what went wrong rather than which feature is involved.

If you have worked through those resources and your question is not answered, use the contact form at the bottom of this page to describe your situation. Include as much context as possible: what you were trying to do, what happened instead, the version of Windows you are running, and any error messages you encountered. The more detail you provide in your initial message, the fewer follow-up exchanges it takes to reach a resolution.

For workflow questions where you want to discuss your approach with other users, the community forum is often the best venue. Other DFM2HTML users may have solved the exact problem you are facing, and forum threads remain searchable for future visitors with the same question.

Reporting Issues

If you have found a bug, a rendering problem, an export error, or any behavior that does not match what the documentation describes, a clear issue report helps get the problem addressed efficiently. When reporting an issue, include the following details:

• Steps to reproduce: What exactly did you do, in what order, that triggered the problem? If you can reproduce it consistently, describe the sequence. If it happens intermittently, note that and describe the circumstances where it tends to occur.
• Expected result: What should have happened based on the documentation or the normal behavior you have experienced previously?
• Actual result: What actually happened? Include error messages verbatim if any appeared. If the issue is visual, describe what you see or note that a screenshot would be helpful.
• Environment details: Your Windows version, display scaling setting, and the browser you tested in (if the issue involves exported output viewed in a browser). If the issue involves the editor itself, note whether it happens immediately on launch or only during specific operations.

Well-structured reports save time on both sides. A report that says "menus do not work" requires several rounds of follow-up. A report that says "dropdown menu items do not appear on hover when using the two-column template in Chrome 124 on Windows 11 at 150% display scaling" can be investigated immediately.

Documentation Feedback

If you find a documentation page that is unclear, incomplete, outdated, or contains an error, that feedback is genuinely valuable. Documentation improves through real reader experience, and knowing which sections cause confusion or leave gaps helps prioritize updates.

When sending documentation feedback, mention which page or section you are referring to and describe what was unclear or missing. If you found the answer to your question elsewhere after the documentation failed you, mention where you found it. That information helps identify where the documentation should have provided the answer so the gap can be closed.

The tutorials, FAQ, and support page are all maintained based on real questions and real feedback. If a topic keeps coming up in support requests, it gets added to the appropriate documentation section. Your feedback directly influences what gets documented next.

Response Expectations

Setting clear expectations matters more than making promises. Here is what you should know about response timing and process.

Messages submitted through the contact form are read by a real person, not processed by an automated ticketing system. That means responses are thoughtful but not instantaneous. Most messages receive a reply within a few business days. Complex issues that require investigation or testing may take longer, and in those cases you will receive an acknowledgment that your message was received and is being looked into.

Weekends and holidays may extend response times. If your question is urgent, check the self-service resources first. The FAQ and support page are available around the clock and cover the most common problems. The community forum may also have active members who can help outside of normal response windows.

If you sent a message and have not received a reply within a reasonable timeframe, it is fine to follow up. Messages occasionally get lost in transit, and a follow-up ensures your request is not sitting in a void.

Self-Service Resources

Before using the contact form, these resources answer the majority of questions people reach out about. Going through them first often gets you to an answer faster than waiting for a reply.

Contact Form

Use the form below to send a message. Fill in all fields so your inquiry can be addressed without needing follow-up for basic details. If your message is about a specific issue, include the environment and reproduction details described in the reporting section above.

Your Name

Email Address

Message Category Select a category Support question Bug or issue report Documentation feedback Feature suggestion General inquiry

Subject

Message

Windows Version (optional)

Send Message

This form is a placeholder and does not currently submit data. It will be connected to a message handler in a future update. In the meantime, you can copy the details you would enter here and send them through the channels described on the support page.