ProppFrexx ONAIR User-Forum

I would like to suggest an improvement for the forum structure itself: adding a new dedicated section called "Guides, Tutorials & Best Practices" (perhaps under the "ProppFrexx ONAIR v4" category, right next to Questions & Answers).

While the official documentation and starter video tutorials are great for learning the basics, ProppFrexx is an incredibly deep and powerful software. Broadcasters often face highly specific, complex scenarios (e.g., advanced script rules, custom routing, PowerShell automation, or API integrations) that a standard manual simply cannot cover.

Here are the main arguments for creating this section:

1. Bridging the Gap Between Manual and Real-World Workflows: The manual explains what a feature does, but users often need to know how to combine multiple features to solve a real broadcasting task. A Guides section would focus on complete workflows and practical use cases rather than dry technical definitions.

2. Harnessing Community Expertise: There are many experienced "power users" in this community who have successfully built complex systems within ProppFrexx. Allowing users to submit well-structured, step-by-step guides (subject to moderation/approval by you) would create a massive, crowd-sourced knowledge base.

3. Preventing Knowledge Loss: Currently, brilliant solutions and detailed workarounds are frequently posted in the Questions & Answers or General Discussion boards. However, they quickly get buried under new posts and are hard to find via search. A dedicated section acts as a permanent library for these high-quality solutions.

4. Reducing Q&A Clutter and Support Load: Many Q&A topics are repetitive. If a detailed, approved guide exists for a common complex scenario (e.g., "How to properly set up Sweepers and Promos using Script Rules"), you or the community can simply link to that guide, saving time and reducing the repetitive support burden.

Users could submit a guide in the Q&A section, and if it is highly valuable, a moderator could move it to the official "Guides" section. This would significantly improve the learning curve for new and intermediate users.

Thank you for considering this idea!

Such a "Best Practice" would mainly live from real-world examples from (as you correctly say) power users.
I suggest, that everyone here can open in the section "General OnAir Discussion" a new Topic and name is "[Best Practise]: ...".
I will then make sure, that these topics stay sticky and on top.

My experience here is however, that the culture of sharing knowledge is not very extensive... but let's give it a try!

Thank you for being open to the idea! I completely understand your skepticism regarding the community's sharing culture, and starting with a [Best Practice]: ... prefix in the "General OnAir Discussion" is a very reasonable way to test the waters.

Once we reach a critical mass of these posts, we can definitely evaluate moving them into their own dedicated category. However, I would gently suggest that creating the dedicated section right from the start might actually be the better approach, for two main reasons:

The Psychological Factor: Users are often more encouraged to contribute when they see an official, dedicated space for it. An empty "Guides & Best Practices" sub-board acts as a clear, permanent invitation (like an empty bookshelf waiting to be filled). Mixing tutorials into general chatter, even as sticky threads, might make the initiative feel less significant.

Avoiding Administrative Double-Work: If the initiative succeeds and users start posting, you will eventually have to manually migrate all those sticky threads into a new section later. Setting it up now prevents this future maintenance overhead.

Either way, I am perfectly fine with the prefix approach as a starting point.

p.s. One additional quick request regarding forum formatting: could you please enable the [spoiler][/spoiler] BBCode tag? It appears to be disabled at the moment.
If we are going to write comprehensive 'Best Practice' guides, they will inevitably include multiple screenshots, long script snippets, and detailed log outputs. Without a spoiler tag, these posts will turn into massive, hard-to-read walls of text and images. Enabling spoilers would allow us to keep the tutorials clean, structured, and easy to navigate, as users could expand only the specific visual references or code blocks they need.