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
GRIT Fitness Flagship Video Tour & Update – GRIT BY BRIT

GRIT Fitness Flagship Video Tour & Update

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

Hey Friends!  I hope you had an awesome weekend are looking forward to an even more awesome week ahead. We are enjoying AMAZING weather in Dallas – I’m talking patio chillin’ with no sweater on – HEY!

I have so much exciting news to share with you!  First, we have raised over 20% of our goal for the new GRIT Flagship on @indiegogo. Thank you to everyone who has helped so far, we luv you! Click the link at the bottom of this post check out the campaign and help us make the Flagship the best it can be!

Second, I shot a little video tour of the new FLAGSHIP so you can see what’s in store.  7 Original GRIT Fitness classes + GRIT Revolution (our new indoor cycling format) ALL under 1 roof!  This means more BANG FOR YOUR BUCK for the #GRITFAM.  Take the tour and get excited!

Last but not least, our construction plans were approved by the City of Dallas last Friday – YAY!  This is such a big deal, because often this step in the process can take WEEKS! On Monday morning I have a meeting with our design team to pick out the final materials and confirm the final plans so we can start construction ASAP!  Wish me luck!  I’ve never done anything like this before so I’m pumped up but also feeling a little anxiety because I want to create the BEST fitness environment for the #GRITFAM.

I’ll post continuous updates here on the blog so you can closely track our build out and ramp up in the coming weeks.  Thanks for all of the love, kind emails and contributions to our campaign.  I APPRECIATE YOU!  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.