Community guidelines
VSD Community works because people share real experience, not marketing copy. These guidelines cover what we welcome from members and contributors, and how we handle disagreements over technical content.
What's welcome here
- Practical, project-grounded content. Articles, tips and case studies drawn from real modeling, shop drawing or erection experience — not generic content written to rank rather than to help.
- Honest disagreement. If a published article gets something wrong, or describes a practice that doesn't hold up on your projects, say so — technical corrections make the whole Knowledge Hub more useful and are always welcome.
- Questions, even basic ones. Detailers at every experience level are part of this community. A question that feels basic to one member is often exactly what a newer detailer needed answered.
- Sharing sample drawings and resources. Redacted or generic shop and GA drawings shared for others to learn from, consistent with your own confidentiality obligations to your employer or clients.
What's not welcome
- Confidential project or client information. Don't post drawings, specifications or details you're not authorized to share — if you're unsure whether something is confidential, don't post it and ask your employer first.
- Unsafe or non-compliant practices presented as standard. Content that recommends skipping code-required checks, QC steps or safety procedures to save time isn't published here, regardless of how common the shortcut might be in practice.
- Disguised advertising. Articles submitted primarily to promote a specific company, software product or service, rather than to share genuinely useful technical content, aren't a fit for the Knowledge Hub.
- Personal attacks. Disagree with a technical claim as sharply as you like — critique the work, not the person who shared it.
Submitting an article
Email a draft, an outline, or even just a topic idea to jodiephan@hotmail.com. Articles are reviewed for technical accuracy and edited for clarity before publishing — see About for more on how that review works. You don't need to be a professional writer; the priority is real, correct, useful content, not polish.
Reporting an error or a concern
If you find a technical error in a published article, a broken link, or content that shouldn't be here, email jodiephan@hotmail.com with the page and a description of the issue. Corrections to published articles are made once the technical point is verified.