Natural benefits of Thongsuk Thai Herbal hair care, where traditional Thai wisdom meets powerful herbal extracts for effective hair care. Our products nourish and strengthen your hair, promoting health and vibrancy. Each formula is designed to enhance your hair's natural beauty, providing the care it deserves. With Thongsuk, you can enjoy healthy, radiant hair that reflects the rich heritage of Thai herbal traditions.
● Coconut Oil: This powerful ingredient strengthens hair cells, prevents dryness, and reduces split ends thanks to its rich Vitamin E content. Perfect for those seeking effective hair care solutions for weak and brittle hair, coconut oil is a must-have in your hair care routine.
● Bergamot & Aloe Vera: Known for their cleansing properties, these ingredients help reduce oiliness and eliminate dandruff while keeping both hair and scalp moisturized. Ideal for dandruff control, this combination is essential in any hair care regimen.
● Butterfly Pea & Litsea Glutinosa: These natural ingredients nourish the scalp and hair, leaving them soft, shiny, and naturally aromatic. They are particularly great for restoring dry and damaged hair, making them a fantastic choice for your hair care needs.
● Sunflower & Amla Oil: This nourishing blend strengthens hair, reduces hair fall, and controls frizziness, resulting in soft and easily styled locks. Perfect for those battling dry, frizzy hair, it’s an essential component of effective hair care.
● Thongsuk Thai Herbal Shampoo 250g - Butterfly Pea
● Thongsuk Thai Herbal Shampoo 250g - Coconut Oil
● Thongsuk Thai Herbal Shampoo 250g - Bergamot Aloe Vera
● Thongsuk Thai Herbal Shampoo 250g - Sunflower Amla Seed Oil
● Thongsuk Thai Herbal Treatment 250g - Butterfly Pea
● Thongsuk Thai Herbal Treatment 250g - Coconut Oil
● Thongsuk Thai Herbal Treatment 250g - Bergamot Aloe Vera
● Thongsuk Thai HerbalTreatment 250g - Sunflower Amla Seed Oil
● Thongsuk Thai Herbal Intense Hair Tonic 40ml - Butterfly Pea
● Thongsuk Thai Herbal Intense Hair Tonic 40ml - Coconut Oil Vitamin E
● Thongsuk Thai Herbal Intense Hair Tonic 40ml - Bergamot Aloe Vera
● Thongsuk Thai Herbal Intense Hair Tonic 40ml - Sunflower Amla Seed Oil
● To Use Shampoo: Apply shampoo and gentle massage all around the head. Then rinse with clean water. Use daily.
● To Use Treatment: After shampoo, Apply hair treatment over the hair and gentle massage all around the head, Focus the end of the hair. Then rinse with clean water. Use daily.
● To Use Hair Tonic: Drop the serum over the scalp, Use your fingertips to gently massage in a circle with rinse off with water.
● Shampoo: 3.6 kg
● Treatment: 3.6 kg
● Hair Tonic: 1.56 kg
● Shampoo: 14.4 x 18.9 x 13.3 cm
● Treatment: 17.5 x 18.3 x 20.7 cm
● Hair Tonic: 18 x 26.8 x 13.8 cm
-
Shampoo
● Coconut Oil: 13-1-6300039969
● Bergamot & Aloe Vera: 13-1-6300039755
● Butterfly Pea & Litsea Glutinosa: 13-1-6300040155
● SunFlower & Amla Oil: 13-1-6700000248
Treatment
● Coconut Oil: 13-1-6300040397
● Bergamot & Aloe Vera: 13-1-6300040399
● Butterfly Pea & Litsea Glutinosa: 13-1-6300040398
● SunFlower & Amla Oil: 13-1-6700000249
Hair Tonic
● Coconut Oil: 13-1-6500033179
● Bergamot & Aloe Vera: 13-1-6500032538
● Butterfly Pea & Litsea Glutinosa: 13-1-6500033287
● SunFlower & Amla Oil: 13-1-6700000250
Shampoo
● Coconut Oil: 8851427019050
● Bergamot & Aloe Vera: 8851427019043
● Butterfly Pea & Litsea Glutinosa: 8851427019036
● SunFlower & Amla Oil: 8851427021954
Treatment
● Coconut Oil: 8851427019005
● Bergamot & Aloe Vera: 8851427019012
● Butterfly Pea & Litsea Glutinosa: 8851427019029
● SunFlower & Amla Oil: 8851427022036
Hair Tonic
● Coconut Oil: 8851427020971
● Bergamot & Aloe Vera: 8851427020988
● Butterfly Pea & Litsea Glutinosa: 8851427020995
● SunFlower & Amla Oil: 8851427022043
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
export@carebeau-enjoy.com
info@carebeau-enjoy.com
.webp)
.webp)
