General | Editorial | Community | Design | Project | Technical | GuideML | Features | Bugs

If you have a question, please read the h2g2 FAQ first to check that your question is not already answered there. Thanks!

Technical Feedback

Welcome to the Technical section of the h2g2 feedback area. If you've got any technical queries or comments about the site, then please post them below by clicking on the 'Discuss' button, and we'll do our best to get back to you. However, if you want to talk specifically about GuideML, you can to that in the GuideML Clinic.

Please note that this section is only for technical feedback - it's for questions and comments about the technology we use, what we do with it, and our plans for the future of the servers and our proprietary systems. This is also where you can get involved in technical discussions about different platforms, processor speeds and so on.

Picking the Right Place for Feedback

We have the following sections in the feedback area, and it will speed up our response time if you pick the right section in which to tell us what you think.

If your question is not specifically about h2g2 then please do not post it here: this section is only for feedback about the site, not about life. General questions not specifically related to h2g2 should be asked in the Ask h2g2 or How do I...? sections.

• Editorial Feedback - For questions and comments about our editorial policies, the editorial process, the contents of the Guide and the future of guidance. This is also where you can ask questions about spelling, grammar, conventions and other uses of English on h2g2, and can point out typos in the Edited Guide for us to fix.

• The Community Soapbox - For questions and comment about the h2g2 Community, the life-blood of the Guide.

• Design Feedback - For questions and comments about the design of the site, whether it's the Alabaster skin, the Classic Goo, illustrations in the Guide or the whole look and feel of the site. It's also where you can get stuck into the pros and cons of the user interface and experience.

• Project Feedback - For questions and comments about things like the development of the project, how it fits into BBCi, and what's going to happen in the future. For specific feature suggestions, please visit the Feature Suggestions section.

• Technical Feedback (this section) - For questions and comments about the technology we use, what we do with it, and what our plans are for the future of the servers and our proprietary systems. This is also where you can get involved in technical discussions about different platforms, processor speeds and so on. If you want to talk specifically about GuideML, you can do that in the GuideML Clinic.

• The GuideML Clinic - For questions and comments about GuideML, the markup language of the Guide. This is your one-stop shop for GuideML advice, support and news.

• Feature Suggestions - If you've got a suggestion for something we can add to h2g2 to make life that much more fantastic for our Researchers, then tell us here. We're always on the lookout for great ideas, so don't hold back. Before posting a suggestion, please check out the h2g2 Feature Ideas page to make sure your idea hasn't already been suggested.

• Bug Reports - Life isn't perfect, and if you've discovered a problem with the site, please let us know. That way we can strive to make things better, for everyone. Before posting a bug report, please check out the h2g2 Bug List to make sure your bug hasn't already been reported.

• Feedback not covered by the above - For questions and comments that don't fit into any of the above categories, as long as they're about h2g2. If you have general questions or comments about life, then please go to Ask h2g2 or How do I...?.

Who Will Respond?

Questions posted to the feedback area are answered either by the h2g2 Gurus or by the in-house team (the Gurus are volunteer Researchers who help to answer the most frequently asked questions on h2g2). We read all comments, respond to the more difficult questions, make a note of good suggestions and administer the bugs database.

Thanks for your input.