Site Search Grounding & Custom CSS

1. Site Search Grounding #

From section 5.1 & 5.4:

• Free:
  • Optional site search grounding on posts/pages.
• Pro:
  • Additional scopes like products and extended options.

Relevant options:

• enable_site_search
• search_posts
• search_pages
• search_products (Pro-related scope)
• include_items, exclude_items (shared with bubble/layout logic for scoping).

2. Step-by-Step: Enable Site Search #

1. Go to Davix AI Engine → Chatbot → OpenAI Integration.
2. Find the toggle Enable Site Search (enable_site_search).
3. Turn it ON.
4. Choose which content to search:
   • search_posts – include posts.
   • search_pages – include pages.
   • search_products – include WooCommerce products (Pro scope).
5. Save changes.

Internally, when handle_chat_request() runs:

• It uses these toggles to query appropriate content and feed summaries to OpenAI as context.

image IMAGE PLACEHOLDER: Screenshot of OpenAI Integration tab showing site search toggles for posts/pages/products and enable_site_search. IMAGE image

3. Include/Exclude Items for Site Search #

The same include_items and exclude_items options are used by visibility logic and also referenced for search scopes.

Step-by-step:

1. In Chatbot settings, find Include Items and Exclude Items fields.
2. To ensure certain URLs/IDs are always considered for search context:
   • Add them to Include Items.
3. To avoid using content from certain URLs/IDs:
   • Add them to Exclude Items.
4. Save changes.

4. Advanced / Custom CSS #

Docs mention:

“Advanced / Custom CSS – for additional styling.”

There is an option:

• custom_css – injected into the chatbot UI.

Step-by-step:

1. Go to Davix AI Engine → Chatbot → Advanced / Custom CSS tab.
2. Paste CSS into the Custom CSS field.
   • This might include adjustments to margins, fonts, or other visual tweaks, as long as they target the chatbot’s CSS selectors.
3. Save.
4. Reload pages and verify that the custom CSS is applied.

5. Theming Tips from Docs #

Section 5.6 “Tips” includes:

• Always set a valid openai_api_key before testing chat.
• Keep contrast accessible; use default colors as a baseline.
• When upgrading to Pro:
  • Previously hidden Pro fields become visible and can be configured.
  • Ensure sanitize_options() is now allowed to store them (which happens automatically when my_fs()->can_use_premium_code() is true).

These guidelines apply to all theming and OpenAI-related configuration.

image IMAGE PLACEHOLDER: Screenshot of chat demonstrating readable light/dark themes after customizing colors and adding custom CSS. IMAGE image