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
Dallas GRIT Fitness Flagship | Construction Progress – GRIT BY BRIT

Dallas GRIT Fitness Flagship | Construction Progress

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

Hey hey friends!  I’m SO THRILLED to share a construction progress update today because SO MUCH has been accomplished in so little time.

So, this week all of the former walls in the facility were demolished leaving this huge open space…

and by the end of the week, the new wall frames and sheet rock were constructed –  YAY!

This is a major milestone because the new GRIT FITNESS flagship studio will have 2 studios under 1 roof: 1 group fitness studio + 1 indoor cycling studio. (It’s also just super cool to actually see the future floor plan in real life – not just on construction drawings).

I’m big believer that variety is the spice of life and the key to an effective fitness regimen, so I’m super keen on providing continuous variety to my clients AKA the #GRITFAM.  Offering cycling classes in additional to our 7 original group fitness classes is a phenomenal sweaty combo!

Furthermore, we made more great progress on the locker room.  Last week the locker room looked like this (NO plumbing)…

This week the trenching for plumbing got underway and we are on track to install showers!

We still have lots of work to do (e.g. flooring, lighting, sound, decor) but the BIG construction efforts are well underway and almost done.  Summer will be here before we know it and I can’t wait to offer more of our fun, fierce fabulous fitness classes to the Dallas community.

It’s not too late to back our campaign and help make this vision come to life.  We can’t do it without you!  Thank you so much for the contributions, kind emails and words of encouragement so far.  You are loved and appreciated.  #thebestisyettocome

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.