Tailwind CSS is a utility-first CSS framework that provides a set of predefined classes, each responsible for a single specific property, such as spacing, color, font size, alignment, and more.

1. Reduced custom CSS volume.
   Most styling is handled through ready-to-use utility classes. This significantly reduces the need to write separate CSS files, minimizes code duplication, and keeps the project structure cleaner and more maintainable.
2. Single-responsibility classes.
   Each class serves one clear purpose. This makes styling more transparent and reduces unexpected overrides that often occur with complex selectors in traditional CSS.
3. Consistent design system.
   Tailwind uses a predefined scale for spacing, sizing, and typography. This ensures a more systematic and visually consistent interface, avoiding arbitrary values and fragmented styling decisions.
4. Built-in responsive support.
   Responsive behavior is implemented using built-in screen prefixes. This allows you to control layout and styling across different devices without writing separate media queries.
5. Minimized style conflicts.
   Unlike traditional CSS, where selector specificity can cause conflicts, Tailwind reduces this risk through simple, flat utility classes.
6. Simplified maintenance.
   Since styles are applied directly within the HTML markup, it’s easier to understand both the structure and the appearance of a component at a glance. This speeds up debugging and future updates.
7. Optimized output size.
   During the build process, unused classes are removed. As a result, the final CSS file contains only the styles actually used in the project, improving performance and loading speed.
8. The official Tailwind CSS website provides comprehensive, well-structured documentation with clear examples, allowing even developers with a basic level of experience to quickly understand and apply the framework correctly: Installing Tailwind CSS with Vite - Tailwind CSS.

Overall, Tailwind CSS is a tool focused on structure, predictability, and development efficiency, especially valuable in projects where consistency and a systematic approach to UI design are important.

I didn’t mean to imply that the AI was trained on Tailwind as such. Just that it may have had more exposure to that particular framework from implementing WebinOne’s Figma layouts.
This may or may not have any bearing on the Implementor’s processes - I don’t know.
I would continue to use whichever framework you’re most comfortable with, as that is more critical. I really don’t think it’ll effect the AI all that much, if at all.

If the AI is trained on Tailwind, are we better seeking themes in that space? Has anyone done a Tailwind template? I

Then, we’ll discuss your experiences with the tool and any feedback you can provide for the team.

After watching the recording, please complete the following poll:

What is your current position with using the AI Implementor (in Beta release)?

Click to view the poll.

POLL:
How might you start using the Data Cleanup Rules for your client sites?

Click to view the poll.

Video Review:

0:00 Intro
0:05 Data Cleanup Rules
8:05 Reminders Reporting
10:25 Upgraded Site Subscription Reminder Emails
11:01 FTP Host Address Change
11:55 Bug Fixes

• Improve Navigation: Add standard pagination 10,20,50 to the view. Currently, the fixed 50-item limit.
• Declutter History: Add an Archive or Delete function. Many old cases are no longer relevant; an auto-delete for cases older than 18 months would also be helpful.
• Prioritize View: Split the dashboard to show Active Cases at the top and Solved Cases below. This ensures urgent items aren’t lost in the list.
• Enable Attachments: Add the ability to upload files/screenshots when submitting a case to help resolve issues faster.

Does anyone have any other thoughts?

NOTE:
The new Advanced AI Search extension is currently in BETA, so the team would greatly appreciate any and all feedback you have while trying this out.

Video Review:

0:00 Intro
0:05 SEO Rendering Logic
3:40 SEO Fields in Front-end forms
4:45 Recurring Subscriptions Reminder Improvements
11:20 Partner Site Templates
14:14 Advanced AI Search (BETA)
32:56 Activation Page Summary (upgrading to v7)
33:34 Zapier Invite Link now available

• Keeping meetings to a reasonable length of time: this will allow attendees to better plan their time and know the commitment level. Long meetings could well be putting people off.
• “Naked template”: this was always the idea with the Docs Demo Site (Docs Demo Site for Treepl CMS), but it needs works. I have ideas to make this better, but it’s a big project with lots of nuances.

Changes to the meeting structure, Code snippets and Job Board will likely be the first items to tackle.

Partner Listing/Member Listing
I agree this could be simplified, no roles, maybe run a contributions count, or have some sort of “member since” tag, which would show the term of being a partner with WebInOne. Show country location also.

Meeting Frequency/About Meetings
I agree we could do 6 weeks, but have a driver to why we are meeting - short 15 min presentation about a key topic, then private member section. Keep the meetings to a reasonable time. I find many of the meetings run 1-2 hours.

Get Partners to ask what they want to see for the next meeting. Keep meetings with an agenda and structure.

Complaints, issues - Suggest have a “pain points” | a “new feature” sections of the meeting. Keep the meetings both “secured” and "open’.

We have the opportunity to attract new partners or clients with “open” meetings. Or sections of video as discussed, that are released as public and private.

Resources/Snippets
Agree we need to be aboe to have a simple keyword search, video previews, sections by function/module as per suggestion is good suggestion.

Have a naked template, with some working examples in place. Like a complete blog layout, some custom module samples, menu samples - not just a a simple drop down menu, but more complex menus like Mega Menus, Tab Mega Menus. Find out what frameworks people of using also - Bootstrap, Tailwind, Foundation. Check this example from Squarespace blank templates from Ghost - Paper™ Template Library — Ghost Plugins. Compete templates that make deployment faster with pre-built sections.

Keep snippets for V7

Business Hub - make it part of Treehouse

Job Board - love all the ideas discussed, but also show who those show partners who can take work on or are looking for more work, what they can help with. Jobs could be marked, “whole project”, “part of project” or something to that effect, so quickly at a glance you can see involvement of job. Task are sectioned or displayed by “Looking for work…” tag or filter or section or “Need help with job…”.

Looking forward to hearing more about next steps.

Please continue the discussion in the forum below if you’d like to add or comment on any ideas.

0:00 Intro
0:36 Members & Roles
2:50 Meeting Types (Public / Private)
9:30 Meeting Frequency
10:23 Resources: Code Snippets
15:55 Onboarding Kit
17:26 Agency/Business Hub
23:04 Open Discussion around Site Billing

I started thinking about all this because I didn’t think the settings were intuitive or worked together as intended. What if the settings are moved out of the Settings > Misc. and added to the Members area page under Edit Settings? Like illustrated

With your suggested changes to the “Enable email verification flow” settings, it would seem to me that the “Send Confirm Email Notification” checkbox in the Form Builder would then not be needed at all. Even with the “Soft verification”, I don’t see a use case where not sending the verification email from a registration form would be needed if you have “Enable email verification flow” turned on.

Keeping the “Send Confirm Email Notification” checkbox in the Form Builder would actually create more confusion in cases where the registration form is subscribing to multiple Member Areas (which could have different settings).

If moving the global settings into each individual Member Area settings, this could cause some complex situations (depending on the setting). Perhaps some settings should remain global.
Particularly, the “Remember Me Lifetime” setting, as having different session times for multiple zones that a member could be subscribed to would not be ideal.

We do already have the IsEmailVerified property in the CRMContact component. However, including it in the currentmember request object, as you’ve suggested, would make it more accessible, especially if GDPR settings are turned on.

Thanks for putting the time into detailing this @Rhatch.
If anyone else has thoughts on this from experience using the Members Area feature, please share them here for discussion.

Issue:

• Members Area Settings are in too many places. Members Area, Settings > Misc, and Form Settings.
• Email Verification is not sent if “Enable email verification flow” is not checked in the Settings > Misc But “Send Confirmation Email Notification” is checked in Form Settings.
• If Enable email verification flow" is checked in Settings > Misc, then “Send Confirmation Email Notification” Must be checked in Form Settings, but is not required to be. This causes issues.
• Can not control the Members Area independently.

1. Members Area Settings Change

Move global settings to the specific Member Area to allow for flexibility (e.g., one Member Area requires verification, another does not).

• Remove “Enable email verification flow” and “Remember Me Lifetime” from Settings > Misc > CRM Settings.
• Add these fields to the Members Area > Details page.

2. Form UI/UX Improvement

Prevent human error by using conditional logic in the Form builder.

Form Settings:

1. Hide “Send Confirm Email Notification” and “Send Member Area Login Details Email” by default.
2. These options only become visible if the user selects a specific Members Area in the form configuration.
3. Based on settings in the Members Area

• IF Selected Members Area has Enable email verification flow = TRUE:
• THEN Send Confirm Email Notification is Checked AND Disabled (Greyed out).
• You cannot have a verification flow without sending the email.

3. “Soft” Login Verification

Currently, the system uses Hard Verification: The user cannot log in until they verify. The current Soft login does not send the verification email.

Add Soft Login with Verification:

• The user can register, receive a verification email, and log in immediately without clicking the link.
• It reduces friction for the user. They aren’t immediately blocked from the content.
• Requires the system to still send out the email verification if the option is selected in the form settings.

4. Frontend Requirement: Liquid Data & Notifications

To support the “Soft Verification” mentioned above, we need a boolean exposed in the current member object (e.g., {{ request.currentmember.email_verified }}).

• TRUE: The user is verified.
• FALSE: The user has not verified.

Add the ability to resend the confirmation email from the front end.

Use Case Example: This allows you to create a conditional notification bar on the website:

{% unless request.currentmember.email_verified %}
<div class="alert alert-warning">
Please verify your email address.
<button onclick="triggerResendVerification()">Resend Email</button>
</div>
{% endunless %}

Video Review:

0:00 Intro
0:40 External API Credentials & API Request Component
32:05 API Application Scopes
33:55 HMAC Signature for Outgoing Webhooks
34:59 Open API type for server-side, mobile app
36:30 Special Characters in File Names
39:05 Bugfixes

To make them easy to access, giving the template items names starting with an underscore (eg: “_Event template 1”) will keep them at the top of the list if sorted alphabetically. Otherwise, adding a keyword like “TEMPLATE” to the name, they can use the search to quickly find them.

0:00 Intro
1:40 Public Backlog
3:40 Partners Landscape
6:10 Challenges
9:10 Market Strategy
22:55 Roadmap 2025 - 2026
29:55 Empowering Community
32:12 Availability
34:12 FAQs

Tim… I’m with you with the sites being showcased … I think if partners submit sites to showcase with a short blurb on functionality if will provide more better content for Webinone marketing. I think it gives us all an opportunity to see what other partners are doing and maybe even provide some much-needed inspiration at least for me anyway. But I only have a couple that really features the custom module function …because the rest are simple brochure style sites with plenty of competition .

Sustainability is a big one … I’m painfully aware that my business model needs to change with the platform but I’m not sure I really have the motivation to do so.

Tim with the Webinone Discount Codes in random unannounced Treehouse meetings – my man! Ha! Love the idea!