Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+)/feedback is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+)/refill is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/(?P[\d]+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/collection-data is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes/(?P[\d]+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes/(?P[\d]+)/terms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for content-forms/v1/check is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for content-forms/v1/submit is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/save_post_meta/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/save_block_meta/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/get_plugins is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/get_plugin is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/fetch_templates is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/import_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: rest_validate_value_from_schema was called incorrectly. The "type" schema keyword for id can only be one of the built-in types: array, object, string, number, integer, boolean, and null. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: rest_sanitize_value_from_schema was called incorrectly. The "type" schema keyword for id can only be one of the built-in types: array, object, string, number, integer, boolean, and null. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225
Happy New Year + 2014 Highlights – GRIT BY BRIT

Happy New Year + 2014 Highlights

Share on facebook
Share on google
Share on twitter
Share on linkedin

HAPPY NEW YEAR MY FRIENDS!  I want to take a moment and send you all of my love and good vibes.  I expect great things for you in 2015, but you must BELIEVE that good things are in store. It’s a matter of our mind-set 😉

Instead of focusing on “resolutions” for the New Year, I want to simply bask in gratitude for all of the amazing things that happened in 2014.  I figure if I just focus on the positive, the good vibes will carry over into 2015.  So here it goes, my Top 10 Most Amazing Moments of 2014…

1. Making Greatist Top Blogs of 2014 – Just before celebrating my 2 year blogiversary, I was so honored to make the Greatist list of best fitness and happiness blogs.

Greatist.com 2014 Best Fitness & Wellness Blogs

2. Undergoing a Successful Surgery & Maintaining a Healthy Body – After finding out that I had 13 uterine fibroids, I decided to have a laparoscoic myomectomy to have them all removed.  The surgery was a successful and I feel amazing.  God is good!

3. Watching my lil sis graduate from Texas Tech University & visiting my lil brother at University of Tampa – I had so many proud big sis moments this year.  I’m so grateful that my siblings are doing well and enjoying life.

My dad, lil sis, and mom at Kortani’s graduation (I took the photo)
Me and my broskie in Tampa

4. Awesome weekly turnouts at Piyo on the Wetdeck at W Dallas Hotel – OMG week after week we had over 75 members of the Dallas Community come out to my PiYo classes at the W Dallas Hotel.  D Magazine wrote us a raving review which was also super cool!

5. Celebrating my 30th Birthday – My dirty 30 was amazing!  In addition to throwing the party of my life, my best friends flew into Dallas from all over the country to the celebrate the weekend with me.  It was a magical!

6. Traveling to California for IDEA World Fitness Convention & Blog Fest – This was a huge turning point in my blogging journey.  I learned so many helpful tips and met so many members of the fitness blogging community.  I’ve already paid my deposit to attend again next summer – hope to see you there!

Just arriving to Anaheim,CA and soaking up the sun and cool California vibes!

7. Getting invited to join POPSUGAR Select + and SELF Magazine #SELFMade Collective – I feel so legit now!  Be sure to check out some of my special features on popsugar.com and self.com

8. Teaching at BEYOND Pedaling – I finally made time to start teaching at my favorite cycling studio in Dallas.  After putting it off for a year, the stars finally aligned and now I lead classes 2 days each week.

Posing after class with this fabulous crew! I love their energy!

9. Transitioning from a corporate career to an entrepreneurial path – After 2 long years of prayer and indecision, I finally took the leap of faith out of corporate America and into the world of entrepreneurship.  You can click here to read my special feature about this decision on SELF.com.

My employee/contractor badges from the last 4 years…I’ve seen some things

10. Opening my first fitness studio – DREAMS COMING TRUE – I’m SO excited to start 2015 by opening Dallas Grit Fitness. This will be the first of several fitness studios I open year (stay tuned!)

So here’s to 2014, an amazing year.  But as I truly believe, THE BEST IS YET TO COME!  xoxo, Brit

Brit Rettig

Brit Rettig

Leave a Reply

Sign up for Brit's Newsletter

Let’s keep in touch! Get alerted when a new blog is released.