Since 2006, the Firewise Communities/USA Recognition Program has shared its quarterly How-To newsletter with participating communities in more than 40 states. Countless residents have learned about Firewise principles from the newsletter while mastering “how-to” become more Firewise.
Now, with many Firewise Communities increasingly using social media to share helpful tips and preparedness lessons with residents and neighbors, the program is changing its newsletter format to keep up.
Starting this month, we’re moving the valued content of How-To from a quarterly newsletter to recurring blogs that you’ll see here two to three times a month on FireBreak.
The new “How-To” logo banner you see above will brand this unique content, and an archive of blogs will be listed chronologically for quick and easy connection to past stories.
As each quarterly season unfolds, you’ll see blogs touting “Firewise Communities in the Spotlight,” in which we’ll share their best practices for success; insightful “Q&A"; “Firewise Leader” pieces on how the Firewise program’s resources can be used; and “Around the Firewise Home” information focused on sharing the latest science and preparedness guidance for your own knowledge and for presenting to your neighbors.
Our coming installment of “Around the Firewise Home” will offer guidance on how drought affects vegetation, as well as lessons learned from communities that have already renewed in 2015, steps communities can take to mentor neighboring communities — and much more.
Toward the end of each quarter, “Firewise by the Numbers” will highlight new and renewed communities, along with the investments they’ve made and projects they’ve accomplished.
As we post these blogs, we encourage you to share them on your community’s Facebook page or Twitter feed. Feel free to use the content in your community newsletter, or via links in community-wide e-mails.
We hope this new format will help you to get the safety conversation going in your community as you strive to make a difference in the wildland/urban interface.