How Are We Doing? Dark Reading Seeks Your Input
Dear Readers,If you've been clicking through the pages of <i>Dark Reading</i> regularly for the past several weeks, you've probably noticed lots of changes. As <a href="http://www.darkreading.com/blog/archives/2008/10/dark_readings_n.html">we told you</a> back in October, the site has undergone an overhaul that included moving to a new server and a new production system, and we've implemented a new design that's intended to make the site easier to navigate and use.
![](https://eu-images.contentstack.com/v3/assets/blt6d90778a997de1cd/bltc94608acf452fd67/655cf371ab171e040a838b2a/329050_DR23_Graphics_Website_V5_Default_Image_v1.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
Dear Readers, If you've been clicking through the pages of Dark Reading regularly for the past several weeks, you've probably noticed lots of changes. As we told you back in October, the site has undergone an overhaul that included moving to a new server and a new production system, and we've implemented a new design that's intended to make the site easier to navigate and use.
As with most new releases, however, the revamped site has encountered a few bugs. You may have noticed that some of the sections haven't worked as usual, or they might have been populated with dated material. If you're a longtime reader, you've probably noticed that the message boards now work much differently than they used to, and that the new boards are a bit spam-prone. And those of you who receive our newsletters may have had trouble getting them in your preferred HTML format.If you've noticed any of these problems, we wanted to take the opportunity to say: Hey, even monkeys fall out of trees once in a while.
Seriously, we're sorry if any of our settling-in glitches have caused you any inconvenience, and we want to assure you that all of them have either been fixed or will be in the very near future. Our own IT folks have been working tirelessly at this for the past month or so, and we think we've got our problems mostly licked.
Which is why I'm writing you today. We've reached that point in the QA process where the developers and power users have identified the problems that they see, and suggested appropriate fixes. Now it's time to hear from our end users -- that's you -- to find out if there are problems or issues that we still haven't caught.
During the next few weeks, we'd love to hear from you. Are there any parts of the site that you think don't work like they should? Have you encountered any trouble searching for content or pulling up articles from our archives? Are you getting any 404 errors or dead links on the pages that you read? If so, we want to know so that we can get the problems fixed and can move on to giving you the best security content on the Web.
If you want to raise any issues, please write us at [email protected]. While you're at it, if you have any suggestions on topics you'd like us to cover, or elements of security that you'd like to see more about, let us know that as well.
We're going through a few growing pains, but our main goal is to help you do your job. If you see anything on the site that needs fixing, or if you'd like us to consider any new areas of coverage, we're all ears. Thanks for your patience -- we look forward to hearing from you.
About the Author
You May Also Like
Catch the Threat Before it Catches you: Proactive Ransomware Defense
September 5, 2024How to Evaluate Hybrid-Cloud Network Policies and Enhance Security
September 18, 2024DORA and PCI DSS 4.0: Scale Your Mainframe Security Strategy Among Evolving Regulations
September 26, 2024Harnessing the Power of Automation to Boost Enterprise Cybersecurity
October 3, 2024
[Virtual Event] The Essential Guide to Cloud Management
October 17, 2024Black Hat Europe - December 9-12 - Learn More
December 10, 2024SecTor - Canada's IT Security Conference Oct 22-24 - Learn More
October 22, 2024