Tuesday, April 11, 2017

Week 15 - #MFRWAuthors 52-Week Blog Challenge Participants

Join us for week 15

Week 15: "My Social Media Hangouts"


Blogging is an opportunity for authors to connect with readers. Despite being writers, blogging is an entirely different style of writing and often stumps us. To help our authors blog consistently, thoughtfully and with purpose, Marketing for Romance Writers is announcing the 2017 Blog Challenge. Each week, authors use our writing prompt to create a meaningful blog post. We'll be posting every Friday... join us as often as possible.

All authors with blogs are welcome to participate. It's very simple!
  1. Sign up in the comments below to commit to the challenge. You will be "buddied" up with another author for support.
  2. Copy the badge onto your blog's sidebar. Share it on your social media networks. Be sure to link it back to this page.
  3. Write your weekly blog post based on the given prompt. Use #MFRWauthor in your title, and be original - don't use "week 2 of 52-week challenge" because that is not unique and won't drive readers to your post.
  4. Return to the MFRW Marketing Blog weekly to add your blog post to the linky list. This will be available each Tuesday for that week's posts. When adding your link, use the post's direct link - not your blog home page.

5 comments:

  1. If you get an error message for Sara Walter Ellwood's post, the correct link is https://sarawalterellwood.wordpress.com/2017/04/14/social-media/

    ReplyDelete
  2. Shari Elder's post can be found at http://sharielder.com/shari-elder/words-pictures-mfrwauthor-amwriting/

    Cathy Brockman's is at http://cathybrockman.com/2017/04/14/a-mixup-mfrwauthor-socialmedia-fixingmymistake-blogchallenge/

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete
  4. If you get an error message for Linda McLaughlin/Lyndi Lamont's post, and you will, the correct link is https://www.lindalyndi.com/2017/04/14/social-media-hangouts/

    ReplyDelete
  5. All the above URLs have been fixed.

    ReplyDelete

Repost.Us