ทองสุข สมุนไพรไทย ผสานภูมิปัญญาไทยดั้งเดิมกับสารสกัดจากสมุนไพรที่ทรงพลัง ผลิตภัณฑ์ของเราช่วยบำรุงและเสริมความแข็งแรงให้กับเส้นผม ทำให้ผมสุขภาพดีและเปล่งประกาย
● น้ำมันมะพร้าว: เสริมความแข็งแรงให้กับเซลล์ผม ป้องกันความแห้งและลดการแตกปลายด้วยวิตามินอี เหมาะสำหรับผมอ่อนแอ ขาดหลุดร่วง
● มะกรูดและว่านหางจระเข้: ทำความสะอาดหนังศีรษะ ลดความมันและขจัดรังแค พร้อมบำรุงให้เส้นผมและหนังศีรษะชุ่มชื่น ไม่แห้งคัน เหมาะสำหรับการขจัดรังแค
● อัญชันและใบหมี่: บำรุงเส้นผมและหนังศีรษะ ทำให้ผมนุ่ม ดกดำ เป็นเงางาม และมีกลิ่นหอมธรรมชาติ เหมาะสำหรับการฟื้นฟูผมแห้งเสีย
● ดอกทานตะวันและน้ำมันมะขามป้อม: บำรุงและเสริมความแข็งแรงให้กับเส้นผม ลดการหลุดร่วงและความชี้ฟู ทำให้ผมนุ่ม สลวย จัดทรงง่าย เหมาะสำหรับผมแห้งชี้ฟู
● ทองสุข แชมพู สมุนไพรไทย (250 g) - อัญชัน
● ทองสุข แชมพู สมุนไพรไทย (250 g) - น้ำมันมะพร้าว
● ทองสุข แชมพู สมุนไพรไทย (250 g) - มะกรูด ว่านหางจระเข้
● ทองสุข แชมพู สมุนไพรไทย (250 g) - ทานตะวัน น้ำมันมะขามป้อม
● ทองสุข ทรีทเม้นท์ สมุนไพรไทย (250 g) - อัญชัน
● ทองสุข ทรีทเม้นท์ สมุนไพรไทย (250 g) - น้ำมันมะพร้าว
● ทองสุข ทรีทเม้นท์ สมุนไพรไทย (250 g) - มะกรูด ว่านหางจระเข้
● ทองสุข ทรีทเม้นท์ สมุนไพรไทย(250 g) - ทานตะวัน น้ำมันมะขามป้อม
● ทองสุข แฮร์ โทนิค สมุนไพรไทย (40 ml) - อัญชัน
● ทองสุข แฮร์ โทนิค สมุนไพรไทย (40 ml) - น้ำมันมะพร้าว วิตามิน
● ทองสุข แฮร์ โทนิค สมุนไพรไทย (40 ml) - มะกรูด ว่านหางจระเข้
● ทองสุข แฮร์ โทนิค สมุนไพรไทย (40 ml) - ทานตะวัน น้ำมันมะขามป้อม
● วิธีใช้ แชมพู : ใช้สําหรับสระผม นวดให้เกิดฟองทั่วศีรษะ แล้วล้างออกด้วยนํ้าสะอาด สามารถใช้ได้ทุกวัน
● วิธีใช้ ทรีทเม้นท์ : หลังสระผมทุกครั้ง ชโลมทรีทเม้นท์แล้วนวดให้ทั่วศีรษะ เน้นบริเวณปลายผม แล้วล้างออกด้วยนํ้าสะอาดสามารถใช้ได้ทุกวัน
●วิธีใช้ แฮร์ โทนิค : หยดเซรั่มให้ทั่วหนังศีรษะ ใช้ปลายนิ้ว นวดเบาๆ เป็นวงกลมโดยไม่ต้องล้างออก
● แชมพู: 3.6 kg
● ทรีทเม้นท์: 3.6 kg
● แฮร่ โทนิค 56 kg
● แชมพู: 14.4 x 18.9 x 13.3 cm
● ทรีทเม้นท์ : 17.5 x 18.3 x 20.7 cm
● แฮร์ โทนิค: 18 x 26.8 x 13.8 cm
-
แชมพู
● น้ำมันมะพร้าว: 13-1-6300039969
● มะกรูด & ว่านหางจระเข้: 13-1-6300039755
● อัญชัน ใบหมี่: 13-1-6300040155
● ทานตะวัน น้ำมันมะขามป้อม: 13-1-6700000248
ทรีทเม้นท์
● น้ำมันมะพร้าว: 13-1-6300040397
● มะกรูด & ว่านหางจระเข้: 13-1-6300040399
● อัญชัน ใบหมี่ : 13-1-6300040398
● ทานตะวัน น้ำมันมะขามป้อม: 13-1-6700000249
แฮร์โทนิค
● น้ำมันมะพร้าว: 13-1-6500033179
● มะกรูด & ว่านหางจระเข้: 13-1-6500032538
●อัญชัน ใบหมี่: 13-1-6500033287
● ทานตะวัน น้ำมันมะขามป้อม: 13-1-6700000250
แชมพู
●น้ำมันมะพร้าว: 8851427019050
●มะกรูด & ว่านหางจระเข้: 8851427019043
●อัญชัน ใบหมี่: 8851427019036
●ทานตะวัน มะขนมป้อม: 8851427021954
ทรีทเม้นท์
●น้ำมันมะพร้าว: 8851427019005
●มะกรูด & ว่านหางจระเข้: 8851427019012
●อัญชัน ใบหมี่: 8851427019029
●ทานตะวัน มัขามป้อม: 8851427022036
แฮร์โทนิค
●น้ำมันมะพร้าว: 8851427020971
●มะกรูด & ว่านหางจระเข้: 8851427020988
●อัญชัน ใบหมี่: 8851427020995
●ทานตะวัน มะขามป้อม: 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)
