I’m often asked what to do with stories Legacy Givers want to share in a bigger way.
This topic always excites me because I believe all of your stories can influence and inspire others beyond your family and friends. But how?
Here is a list of possibilities. You can find dozens (probably hundreds) of books on these subjects on Amazon and lots of free material if you Google the topics that most interest you. Your local librarian can also help you find what the information you need. A hint for when you search: include the year you are searching because you want the most up-to-date online resources.
- If your story is unique, you can look into traditional publishing. Before you start this journey, visit your public library and take a long look at Amazon to see what is already out there.
- Another option (one of my favorites) is Independent publishing. All the work is up to you, but it’s a way to get your story out there.
- Blog publishing is my favorite way to share my Legacy stories. You can build free websites, but I encourage you to learn more about owning your domain name and hosting with WordPress. Again, there are a lot of books out there on these subjects. One of the best ways to start blogging is to follow other bloggers. You can take a look at mine here: https://joydekok.com/blog/
- A no-cost option is to utilize Facebook Notes. This is a fun and easy way to share your stories. Here’s a link from FB’s Help Center: https://www.facebook.com/help/1003591879683058?helpref=faq_content
In case you’re wondering, I purchased my domain name from GoDaddy. My hosting is with InMotion. And I use the purchased WordPress platform.
Along the way, you’ll want to let people know about your blog. You can share it on Facebook and other social media sites, and you can invite your family and friends personally. If they love it, you can encourage them to invite others.
I’m not good at math (at all!), but I do know this is the organic power of multiplication.
Your Story Matters!
Thanks to Pixabay for the free use of the graphic used in this post.