Feature Enhancement Request: Related Listings Widget
Hello eDirectory Team, First, I'd like to thank your for continuing to improve the platform. I've been building a tourism directory and have found the Related Listings widget to be a valuable feature. D uring implementation, however, I identified an enhancement that I believe would greatly increase its flexibility while remaining fully backward compatible. Current Limitation The Related Listings widget currently supports three display methods: By Category By Location By Category & Location When By Category or By Category & Location is selected, the widget automatically displays listings from the same category as the page where the widget is placed. Likewise, when By Location or By Category & Location is selected, the widget automatically uses the same location as the current listing. While this works well for traditional "related listings," it prevents site owners from displaying complementary content from other categories or locations without custom development. Proposed Enhancement Add two optional override fields to the existing widget configuration. Override Category (Optional) Display this field whenever: By Category By Category & Location is selected. The field would present a dropdown containing all available listing categories. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's category. If a category is selected, the widget displays listings from the selected category instead. Override Location (Optional) Display this field whenever: By Location By Category & Location is selected. The field would allow the administrator to select a specific location. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's location. If a location is selected, the widget displays listings from that selected location instead. Suggested Configuration Display Method □ By Category □ By Location □ By Category & Location Override Category (Optional) [Dropdown] Override Location (Optional) [Dropdown] Sort By [Highest Rated] Number of Listings [10] If either override field is left empty, the widget simply falls back to its current behavior. Backward Compatibility One of the biggest advantages of this enhancement is that it is completely optional. Existing websites require no changes. Existing widgets continue to function exactly as they do today. Site owners only use the new functionality when desired. No existing implementations wo
Lurquilla 6 days ago
Feature Enhancement Request: Related Listings Widget
Hello eDirectory Team, First, I'd like to thank your for continuing to improve the platform. I've been building a tourism directory and have found the Related Listings widget to be a valuable feature. D uring implementation, however, I identified an enhancement that I believe would greatly increase its flexibility while remaining fully backward compatible. Current Limitation The Related Listings widget currently supports three display methods: By Category By Location By Category & Location When By Category or By Category & Location is selected, the widget automatically displays listings from the same category as the page where the widget is placed. Likewise, when By Location or By Category & Location is selected, the widget automatically uses the same location as the current listing. While this works well for traditional "related listings," it prevents site owners from displaying complementary content from other categories or locations without custom development. Proposed Enhancement Add two optional override fields to the existing widget configuration. Override Category (Optional) Display this field whenever: By Category By Category & Location is selected. The field would present a dropdown containing all available listing categories. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's category. If a category is selected, the widget displays listings from the selected category instead. Override Location (Optional) Display this field whenever: By Location By Category & Location is selected. The field would allow the administrator to select a specific location. Behavior If left blank, the widget behaves exactly as it does today by using the current listing's location. If a location is selected, the widget displays listings from that selected location instead. Suggested Configuration Display Method □ By Category □ By Location □ By Category & Location Override Category (Optional) [Dropdown] Override Location (Optional) [Dropdown] Sort By [Highest Rated] Number of Listings [10] If either override field is left empty, the widget simply falls back to its current behavior. Backward Compatibility One of the biggest advantages of this enhancement is that it is completely optional. Existing websites require no changes. Existing widgets continue to function exactly as they do today. Site owners only use the new functionality when desired. No existing implementations wo
Lurquilla 6 days ago
Sticky (Floating) Sidebar for Listing Detail Pages
Hello Team, I would like to suggest adding an optional Sticky (Floating) Sidebar feature for Listing Detail Pages. Current Situation On listing pages containing substantial content such as descriptions, videos, image galleries, reviews, nearby attractions, and other information, the right sidebar is only visible near the top of the page. Once visitors begin scrolling through the content, important sidebar elements disappear from view and remain inaccessible unless the user manually scrolls back to the top of the page. This is particularly noticeable on longer listings where users spend significant time reading and exploring content. Proposed Enhancement Introduce an optional Sticky (Floating) Sidebar that remains visible as users scroll through the page. The sidebar would stay within the visible viewport while respecting the page layout and automatically stop when reaching the end of the content area. This behavior is commonly found on modern travel, directory, real estate, e-commerce, and hospitality websites because it keeps key actions accessible throughout the user's browsing experience. Elements That Would Benefit A sticky sidebar could keep the following items visible throughout the page: Reservation and booking buttons Contact and inquiry buttons Maps and directions Social media links Nearby listings and recommendations Promotional widgets Advertising placements Other sidebar widgets configured by the site owner Benefits Improved User Experience Eliminates the need to scroll back to the top to access important actions. Creates a smoother and more intuitive browsing experience. Improves usability on long-form content pages. Increased Conversion Opportunities Reservation, booking, contact, and inquiry buttons remain visible at all times. Visitors can take action the moment they decide to engage. May increase lead generation and conversion rates for listing owners. Improved Advertising Visibility Sidebar advertisements remain visible for a greater portion of the visit. Potential increase in ad impressions and click-through rates. Better Engagement Across the Platform Maps, social links, and nearby recommendations remain easily accessible. Encourages visitors to explore additional listings and content. Suggested Configuration To maximize flexibility, consider making this a configurable option within the widget or page settings, allowing administrators to choose between: Standard Sidebar Sticky (Floating) Sidebar This would enable site owners to select the behavior that best fits their design and user experience goals. Additional Consideration Before implementing a completely new feature, it may be worth confirming whether the platform or theme framework already supports sticky widgets or sticky sidebars internally and simply does not expose the option within the current settings interface. If such functionality already exists, exposing it as a configurable setting could provide a quick and efficient enhancement with minimal development effort. Use Cases This feature would be particularly valuable for: Tourism attractions Restaurants Hotels and accommodations Event venues Tour operators Activity providers Long-form directory listings with extensive c
Lurquilla about 1 month ago
Sticky (Floating) Sidebar for Listing Detail Pages
Hello Team, I would like to suggest adding an optional Sticky (Floating) Sidebar feature for Listing Detail Pages. Current Situation On listing pages containing substantial content such as descriptions, videos, image galleries, reviews, nearby attractions, and other information, the right sidebar is only visible near the top of the page. Once visitors begin scrolling through the content, important sidebar elements disappear from view and remain inaccessible unless the user manually scrolls back to the top of the page. This is particularly noticeable on longer listings where users spend significant time reading and exploring content. Proposed Enhancement Introduce an optional Sticky (Floating) Sidebar that remains visible as users scroll through the page. The sidebar would stay within the visible viewport while respecting the page layout and automatically stop when reaching the end of the content area. This behavior is commonly found on modern travel, directory, real estate, e-commerce, and hospitality websites because it keeps key actions accessible throughout the user's browsing experience. Elements That Would Benefit A sticky sidebar could keep the following items visible throughout the page: Reservation and booking buttons Contact and inquiry buttons Maps and directions Social media links Nearby listings and recommendations Promotional widgets Advertising placements Other sidebar widgets configured by the site owner Benefits Improved User Experience Eliminates the need to scroll back to the top to access important actions. Creates a smoother and more intuitive browsing experience. Improves usability on long-form content pages. Increased Conversion Opportunities Reservation, booking, contact, and inquiry buttons remain visible at all times. Visitors can take action the moment they decide to engage. May increase lead generation and conversion rates for listing owners. Improved Advertising Visibility Sidebar advertisements remain visible for a greater portion of the visit. Potential increase in ad impressions and click-through rates. Better Engagement Across the Platform Maps, social links, and nearby recommendations remain easily accessible. Encourages visitors to explore additional listings and content. Suggested Configuration To maximize flexibility, consider making this a configurable option within the widget or page settings, allowing administrators to choose between: Standard Sidebar Sticky (Floating) Sidebar This would enable site owners to select the behavior that best fits their design and user experience goals. Additional Consideration Before implementing a completely new feature, it may be worth confirming whether the platform or theme framework already supports sticky widgets or sticky sidebars internally and simply does not expose the option within the current settings interface. If such functionality already exists, exposing it as a configurable setting could provide a quick and efficient enhancement with minimal development effort. Use Cases This feature would be particularly valuable for: Tourism attractions Restaurants Hotels and accommodations Event venues Tour operators Activity providers Long-form directory listings with extensive c
Lurquilla about 1 month ago
Planned
Serve Markdown content on Accept: text/markdown requests for full AI Content score - Part 2
Following on from the llms.txt feature request — once llms.txt and llms-full.txt are in place, the remaining gap to a full score on the Content dimension of isitagentready.com is Markdown content negotiation. When an AI agent requests a page, it sends an Accept: text/markdown header. If your server returns HTML, the agent has to parse out navigation, scripts, ads, and markup noise to get to the actual content — burning tokens and often getting it wrong. If your server detects that header and returns clean Markdown instead, the agent gets exactly what it needs, efficiently. The request: When eDirectory detects an Accept: text/markdown request header, return a clean Markdown version of the page instead of HTML — covering at minimum: Category pages (name, description, listing summaries) Listing detail pages (business name, description, contact info, category) Key static pages (About, Contact, Add a Listing) This doesn't need to replace the HTML response for normal browsers — just intercept the header and serve an alternate clean representation to agents that ask for it. Why it matters: This is the difference between an AI agent being able to read your directory and being able to use it as a reliable source. Combined with llms.txt, a proper robots.txt with AI bot rules, and a sitemap, this completes the first three AI readiness categories and puts eDirectory sites at the top of the scoring curve. Most platforms haven't implemented this yet. It's a genuine differentiator right now. Aaron
Aaron B about 2 months ago
Planned
Serve Markdown content on Accept: text/markdown requests for full AI Content score - Part 2
Following on from the llms.txt feature request — once llms.txt and llms-full.txt are in place, the remaining gap to a full score on the Content dimension of isitagentready.com is Markdown content negotiation. When an AI agent requests a page, it sends an Accept: text/markdown header. If your server returns HTML, the agent has to parse out navigation, scripts, ads, and markup noise to get to the actual content — burning tokens and often getting it wrong. If your server detects that header and returns clean Markdown instead, the agent gets exactly what it needs, efficiently. The request: When eDirectory detects an Accept: text/markdown request header, return a clean Markdown version of the page instead of HTML — covering at minimum: Category pages (name, description, listing summaries) Listing detail pages (business name, description, contact info, category) Key static pages (About, Contact, Add a Listing) This doesn't need to replace the HTML response for normal browsers — just intercept the header and serve an alternate clean representation to agents that ask for it. Why it matters: This is the difference between an AI agent being able to read your directory and being able to use it as a reliable source. Combined with llms.txt, a proper robots.txt with AI bot rules, and a sitemap, this completes the first three AI readiness categories and puts eDirectory sites at the top of the scoring curve. Most platforms haven't implemented this yet. It's a genuine differentiator right now. Aaron
Aaron B about 2 months ago
Planned
Add llms.txt and llms-full.txt support for AI agent readiness - Part 1
AI agents (ChatGPT, Claude, Perplexity, Gemini) are increasingly how people find businesses and services — and they need a different signal than Google does. The emerging standard is llms.txt and llms-full.txt, two plain Markdown files served from your web root that give AI agents a clean, structured map of your site — what it covers, your main categories, key pages. Think of it as robots.txt but for LLMs. The spec is documented at llmstxt.org. Cloudflare recently launched a free AI readiness scanner at isitagentready.com that scores your site 0–100 across five dimensions. The llms.txt files directly impact the Content score. Without them, AI agents have to scrape HTML and often skip the site entirely. The request: Add a dedicated AI Identity section in the eDirectory admin panel where directory owners can provide: Directory name and tagline Purpose and description of the directory Who the directory is for (target audience) What regions, industries, or niches it covers When the directory was founded/launched Primary contact name and email Owner/operator website or social links Auto-generate llms.txt and llms-full.txt by combining that AI Identity information with the directory's live category structure, key pages, and site description — similar to how sitemaps are already generated Serve both files from the web root with correct Content-Type: text/plain headers and keep them updated as categories and pages change The AI Identity section is important because auto-generating from categories alone gives AI agents the structure of the directory but not the context — who runs it, why it exists, who it serves. That context is what helps an AI agent decide whether your directory is the right source to cite for a given query. For sites already on Cloudflare, this would also push scores significantly on isitagentready.com. Worth noting that full marks on the Content dimension also requires serving Markdown on Accept: text/markdown requests, which could be a natural follow-on feature. See Part 2 This is a quick win that puts eDirectory sites ahead of the vast majority of the web right now. The window where this is a differentiator rather than table stakes won't be open long. Aaron
Aaron B about 2 months ago
Planned
Add llms.txt and llms-full.txt support for AI agent readiness - Part 1
AI agents (ChatGPT, Claude, Perplexity, Gemini) are increasingly how people find businesses and services — and they need a different signal than Google does. The emerging standard is llms.txt and llms-full.txt, two plain Markdown files served from your web root that give AI agents a clean, structured map of your site — what it covers, your main categories, key pages. Think of it as robots.txt but for LLMs. The spec is documented at llmstxt.org. Cloudflare recently launched a free AI readiness scanner at isitagentready.com that scores your site 0–100 across five dimensions. The llms.txt files directly impact the Content score. Without them, AI agents have to scrape HTML and often skip the site entirely. The request: Add a dedicated AI Identity section in the eDirectory admin panel where directory owners can provide: Directory name and tagline Purpose and description of the directory Who the directory is for (target audience) What regions, industries, or niches it covers When the directory was founded/launched Primary contact name and email Owner/operator website or social links Auto-generate llms.txt and llms-full.txt by combining that AI Identity information with the directory's live category structure, key pages, and site description — similar to how sitemaps are already generated Serve both files from the web root with correct Content-Type: text/plain headers and keep them updated as categories and pages change The AI Identity section is important because auto-generating from categories alone gives AI agents the structure of the directory but not the context — who runs it, why it exists, who it serves. That context is what helps an AI agent decide whether your directory is the right source to cite for a given query. For sites already on Cloudflare, this would also push scores significantly on isitagentready.com. Worth noting that full marks on the Content dimension also requires serving Markdown on Accept: text/markdown requests, which could be a natural follow-on feature. See Part 2 This is a quick win that puts eDirectory sites ahead of the vast majority of the web right now. The window where this is a differentiator rather than table stakes won't be open long. Aaron
Aaron B about 2 months ago
Open AI Provider Settings — Custom API Endpoint + Model Name
I'd like to raise what I think is one of the most impactful feature improvements you could make to the AI section of eDirectory: opening up the AI provider configuration to allow a custom API base URL and model name, rather than locking users to just OpenAI. The OpenAI API standard is to AI what S3 is to object storage The best way to understand this is by analogy. Years ago, Amazon S3 defined an API standard for object storage. Today, dozens of providers — Cloudflare R2, Backblaze B2, Wasabi, MinIO, and many others — all implement that same S3-compatible API. The result is that any application built to talk to S3 can switch providers by simply changing an endpoint URL and credentials. No code changes. No re-integration work. The OpenAI /v1/chat/completions API has become exactly the same thing for AI inference. It is now the de facto industry standard protocol, and virtually every major AI provider in the world has adopted it as a drop-in compatible interface. Western providers OpenAI — api.openai.com/v1 Google Gemini — generativelanguage.googleapis.com/v1beta/openai xAI / Grok — api.x.ai/v1 Mistral AI — api.mistral.ai/v1 Groq — api.groq.com/openai/v1 Together AI — api.together.xyz/v1 Fireworks AI — api.fireworks.ai/inference/v1 Perplexity — api.perplexity.ai OpenRouter — openrouter.ai/api/v1 (routes to 100+ models via one key) Ollama (self-hosted) — localhost:11434/v1 LM Studio (self-hosted) — localhost:1234/v1 Chinese providers (all OpenAI-compatible) DeepSeek — api.deepseek.com/v1 Z.ai / GLM (Zhipu AI) — api.z.ai/api/openai/v1 Qwen / Alibaba — dashscope.aliyuncs.com/compatible-mode/v1 MiniMax — api.minimax.chat/v1 Moonshot / Kimi — api.moonshot.ai/v1 ByteDance / Doubao — ark.cn-beijing.volces.com/api/v3 Baidu / ERNIE — qianfan.baidubce.com/v2 StepFun — api.stepfun.com/v1 Xiaomi / MiMo — via OpenRouter Tencent Hunyuan — api.hunyuan.cloud.tencent.com/v1 They all speak the same protocol. If eDirectory simply exposed a custom API base URL and model name field, every single one of these becomes instantly usable — with zero additional development work on your end. One implementation unlocks the entire ecosystem, now and for every provider that emerges in the future. Just like S3 compatibility did for storage. The cost case
Aaron B about 2 months ago
Open AI Provider Settings — Custom API Endpoint + Model Name
I'd like to raise what I think is one of the most impactful feature improvements you could make to the AI section of eDirectory: opening up the AI provider configuration to allow a custom API base URL and model name, rather than locking users to just OpenAI. The OpenAI API standard is to AI what S3 is to object storage The best way to understand this is by analogy. Years ago, Amazon S3 defined an API standard for object storage. Today, dozens of providers — Cloudflare R2, Backblaze B2, Wasabi, MinIO, and many others — all implement that same S3-compatible API. The result is that any application built to talk to S3 can switch providers by simply changing an endpoint URL and credentials. No code changes. No re-integration work. The OpenAI /v1/chat/completions API has become exactly the same thing for AI inference. It is now the de facto industry standard protocol, and virtually every major AI provider in the world has adopted it as a drop-in compatible interface. Western providers OpenAI — api.openai.com/v1 Google Gemini — generativelanguage.googleapis.com/v1beta/openai xAI / Grok — api.x.ai/v1 Mistral AI — api.mistral.ai/v1 Groq — api.groq.com/openai/v1 Together AI — api.together.xyz/v1 Fireworks AI — api.fireworks.ai/inference/v1 Perplexity — api.perplexity.ai OpenRouter — openrouter.ai/api/v1 (routes to 100+ models via one key) Ollama (self-hosted) — localhost:11434/v1 LM Studio (self-hosted) — localhost:1234/v1 Chinese providers (all OpenAI-compatible) DeepSeek — api.deepseek.com/v1 Z.ai / GLM (Zhipu AI) — api.z.ai/api/openai/v1 Qwen / Alibaba — dashscope.aliyuncs.com/compatible-mode/v1 MiniMax — api.minimax.chat/v1 Moonshot / Kimi — api.moonshot.ai/v1 ByteDance / Doubao — ark.cn-beijing.volces.com/api/v3 Baidu / ERNIE — qianfan.baidubce.com/v2 StepFun — api.stepfun.com/v1 Xiaomi / MiMo — via OpenRouter Tencent Hunyuan — api.hunyuan.cloud.tencent.com/v1 They all speak the same protocol. If eDirectory simply exposed a custom API base URL and model name field, every single one of these becomes instantly usable — with zero additional development work on your end. One implementation unlocks the entire ecosystem, now and for every provider that emerges in the future. Just like S3 compatibility did for storage. The cost case
Aaron B about 2 months ago
Sitemgr must approve
This is a much needed and great feature however it is of little use if the sponsors or listing claimer has to pay upfront and then we have to do a manual refund if we are not excepting the listing. It really is an easy work around with stripe to have charges deducted only once approved. That will make this feature usable. Please fix this. Thank you
Els about 2 months ago
Sitemgr must approve
This is a much needed and great feature however it is of little use if the sponsors or listing claimer has to pay upfront and then we have to do a manual refund if we are not excepting the listing. It really is an easy work around with stripe to have charges deducted only once approved. That will make this feature usable. Please fix this. Thank you
Els about 2 months ago
Listing Template Prompts
It would be very beneficial if we could add prompts and/or examples in the long and short description blocks to ensure sponsors are giving good information for their listings
Els about 2 months ago
Listing Template Prompts
It would be very beneficial if we could add prompts and/or examples in the long and short description blocks to ensure sponsors are giving good information for their listings
Els about 2 months ago
UX and design consistency
The sponsor dashboard does not align with personalisation of fonts, colours etc Like this page for example very outdated look and can this not be editable to just display available plans? This then redirects the sponsor to the list with us page which is not good UX
Els about 2 months ago
UX and design consistency
The sponsor dashboard does not align with personalisation of fonts, colours etc Like this page for example very outdated look and can this not be editable to just display available plans? This then redirects the sponsor to the list with us page which is not good UX
Els about 2 months ago
Geração de Conteúdo
O eDirectory tem muitas ferramentas para um portal ou guia local e aproveitando a AI, acho muito interessante criar conteúdo com API da AI. Buscar eventos e notícias atuais e inserir no site, agregando conteúdo diário ao mesmo.
Agência BRQuality 2 months ago
Geração de Conteúdo
O eDirectory tem muitas ferramentas para um portal ou guia local e aproveitando a AI, acho muito interessante criar conteúdo com API da AI. Buscar eventos e notícias atuais e inserir no site, agregando conteúdo diário ao mesmo.
Agência BRQuality 2 months ago
Create a more robust Deals management system
Would like to request this functionality, the abilty to add Deals to Mobile Wallet. Also can Deals be tied to a user to have it marked as redeemed once it is used?
WheresThatDeal 3 months ago
Create a more robust Deals management system
Would like to request this functionality, the abilty to add Deals to Mobile Wallet. Also can Deals be tied to a user to have it marked as redeemed once it is used?
WheresThatDeal 3 months ago
Sizing of images
Can we use AI to right-size an image for the Card page? Users who set up a listing do not have the time nor the inclination to size an image. They post what they have available. On the detail page it usually looks good, but for the card page it is more than likely wrong-sized. It looks bad.
Gibraan Ali 3 months ago
Sizing of images
Can we use AI to right-size an image for the Card page? Users who set up a listing do not have the time nor the inclination to size an image. They post what they have available. On the detail page it usually looks good, but for the card page it is more than likely wrong-sized. It looks bad.
Gibraan Ali 3 months ago
Including website and social media clicks to summary report
Hi, It would be great to include website, social media etc, to the summary report so subscribers or sponsors can see what visitors are interested in and where to focus his activities it also shows how visitors actually acting in sponsors page Thanks
R. Harb 3 months ago
Including website and social media clicks to summary report
Hi, It would be great to include website, social media etc, to the summary report so subscribers or sponsors can see what visitors are interested in and where to focus his activities it also shows how visitors actually acting in sponsors page Thanks
R. Harb 3 months ago
Enhanced Category Widget Flexibility
I’d like to suggest an enhancement for the category widget. Currently, it only allows selecting first-level categories, and the main categories and they cannot be reorganized. It would be very useful if the widget could: Include second- or third-level subcategories so users can find popular areas faster. Allow reordering of categories and subcategories, giving admins control over display order to optimize user navigation and experience. This improvement would make the directory more flexible, easier to navigate, and allow highlighting of the most relevant subcategories for users, improving both discoverability and engagement.
Shay Williams 3 months ago
Enhanced Category Widget Flexibility
I’d like to suggest an enhancement for the category widget. Currently, it only allows selecting first-level categories, and the main categories and they cannot be reorganized. It would be very useful if the widget could: Include second- or third-level subcategories so users can find popular areas faster. Allow reordering of categories and subcategories, giving admins control over display order to optimize user navigation and experience. This improvement would make the directory more flexible, easier to navigate, and allow highlighting of the most relevant subcategories for users, improving both discoverability and engagement.
Shay Williams 3 months ago
Feedback for eDirectory UI/UX Improvements
I really appreciate the AI module—it looks modern, functional, and refreshed. However, much of the rest of the UI feels outdated. The gray outlines and neutral backgrounds on pages, particularly in the listing area, make it look old-fashioned. A white background option and less rigid styling would modernize the interface. The spacing between sections is minimal, forcing me to manually add headers or delete content just to create breathing room. Consistency in fonts, sizes, and bolding across titles, headers, and sections—like in the pricing section—needs improvement, as inconsistencies make the interface less polished. It would be great to have more flexible content-building modules, allowing one-, two-, or three-row layouts with text, images, buttons, and content blocks. Being able to see edits live while building would significantly improve the experience compared to the current save-and-preview workflow. Overall, a small visual refresh—modern colors, consistent typography, improved padding, and more flexible content blocks—would make a huge difference in usability and perception, complementing the AI features that already feel up-to-date.
Shay Williams 3 months ago
Feedback for eDirectory UI/UX Improvements
I really appreciate the AI module—it looks modern, functional, and refreshed. However, much of the rest of the UI feels outdated. The gray outlines and neutral backgrounds on pages, particularly in the listing area, make it look old-fashioned. A white background option and less rigid styling would modernize the interface. The spacing between sections is minimal, forcing me to manually add headers or delete content just to create breathing room. Consistency in fonts, sizes, and bolding across titles, headers, and sections—like in the pricing section—needs improvement, as inconsistencies make the interface less polished. It would be great to have more flexible content-building modules, allowing one-, two-, or three-row layouts with text, images, buttons, and content blocks. Being able to see edits live while building would significantly improve the experience compared to the current save-and-preview workflow. Overall, a small visual refresh—modern colors, consistent typography, improved padding, and more flexible content blocks—would make a huge difference in usability and perception, complementing the AI features that already feel up-to-date.
Shay Williams 3 months ago
Make AI Mode Optional on Listing Pages
The AI mode on the directory is a great feature and works well when intentionally used. However, on listing category pages, it automatically populates AI recommendations, which disrupts the natural scrolling experience. It would be better if users could control when to see recommendations on every page they visit, allowing for seamless browsing without waiting for AI content to load. Maybe adjust this copy: AI-generated response. Personalized summary based on your search. To: Want AI-Generated Recommendations? Get a personalized summary based on your search. This gives users the choice to activate AI suggestions only when they want them, keeping the browsing experience smooth and uninterrupted while still providing personalized insights when desired. This adjustment ensures clarity and respects user control over content
Shay Williams 3 months ago
Make AI Mode Optional on Listing Pages
The AI mode on the directory is a great feature and works well when intentionally used. However, on listing category pages, it automatically populates AI recommendations, which disrupts the natural scrolling experience. It would be better if users could control when to see recommendations on every page they visit, allowing for seamless browsing without waiting for AI content to load. Maybe adjust this copy: AI-generated response. Personalized summary based on your search. To: Want AI-Generated Recommendations? Get a personalized summary based on your search. This gives users the choice to activate AI suggestions only when they want them, keeping the browsing experience smooth and uninterrupted while still providing personalized insights when desired. This adjustment ensures clarity and respects user control over content
Shay Williams 3 months ago
Back button or previous version
Add a back or undo button, or a restore to previous version button to undo unwanted changes.
Eileen Reimann 3 months ago
Back button or previous version
Add a back or undo button, or a restore to previous version button to undo unwanted changes.
Eileen Reimann 3 months ago
Category Management Improvements
Drag-and-Drop Category Reordering Ability to easily move categories and subcategories within the hierarchy This would eliminate the need to manually recreate categories when restructuring Duplicate/Clone Category Function Ability to duplicate an existing category (including subcategories and settings) This would significantly speed up setup for large directory structures
Shay Williams 4 months ago
Category Management Improvements
Drag-and-Drop Category Reordering Ability to easily move categories and subcategories within the hierarchy This would eliminate the need to manually recreate categories when restructuring Duplicate/Clone Category Function Ability to duplicate an existing category (including subcategories and settings) This would significantly speed up setup for large directory structures
Shay Williams 4 months ago
In Progress
Event Venues Displayed in Listing Summary Card
Event venue information is no longer displayed on the listing summary card (the preview shown in search results) like it used to. It now only shows on detail page. It would be great it you could bring it back like the screenshot below.
Mark D 4 months ago
In Progress
Event Venues Displayed in Listing Summary Card
Event venue information is no longer displayed on the listing summary card (the preview shown in search results) like it used to. It now only shows on detail page. It would be great it you could bring it back like the screenshot below.
Mark D 4 months ago
Pricing options in widget
Allow default pricing for listing, there should be a toggle that allows the site owner to have three options to choose from: - Price - Starts At - Price Range Allowing the site owner to allow sponsors only one option will keep the display pricing consistent. Allowing sponsors to choose which option to display would create confusion in comparing pricing for end users.
Mark R 4 months ago
Pricing options in widget
Allow default pricing for listing, there should be a toggle that allows the site owner to have three options to choose from: - Price - Starts At - Price Range Allowing the site owner to allow sponsors only one option will keep the display pricing consistent. Allowing sponsors to choose which option to display would create confusion in comparing pricing for end users.
Mark R 4 months ago
AI Usage Control & External Controller Routing for AI Mode
As AI usage scales, one of the main challenges for platform owners is managing and optimizing API costs. Currently, AI Mode sends all queries directly to OpenAI without an option to control or filter requests. We would like to suggest the following enhancements for future versions of eDirectory: External Controller / API Routing Option Allow AI Mode queries to be routed to a configurable external endpoint before calling OpenAI This would enable custom logic such as: • Filtering simple queries (handled internally) • Deciding when OpenAI is necessary • Integrating with external AI systems or knowledge bases AI Usage Controls Ability to define query limits (per user / per day) Option to restrict AI access by membership level (e.g., Premium only) Toggle to enable/disable AI Mode per page or module Cost Management Visibility Basic usage tracking (e.g., number of AI queries triggered) Optional logging or reporting to help monitor API consumption 🎯 Why this matters: These features would allow directory owners to: Scale AI responsibly Align AI usage with monetization (e.g., Premium listings) Avoid uncontrolled API costs Extend eDirectory’s AI capabilities beyond default OpenAI behavior We believe this would significantly enhance the flexibility and long-term scalability of AI Mode across all eDirectory-powered platforms.
redila 4 months ago
AI Usage Control & External Controller Routing for AI Mode
As AI usage scales, one of the main challenges for platform owners is managing and optimizing API costs. Currently, AI Mode sends all queries directly to OpenAI without an option to control or filter requests. We would like to suggest the following enhancements for future versions of eDirectory: External Controller / API Routing Option Allow AI Mode queries to be routed to a configurable external endpoint before calling OpenAI This would enable custom logic such as: • Filtering simple queries (handled internally) • Deciding when OpenAI is necessary • Integrating with external AI systems or knowledge bases AI Usage Controls Ability to define query limits (per user / per day) Option to restrict AI access by membership level (e.g., Premium only) Toggle to enable/disable AI Mode per page or module Cost Management Visibility Basic usage tracking (e.g., number of AI queries triggered) Optional logging or reporting to help monitor API consumption 🎯 Why this matters: These features would allow directory owners to: Scale AI responsibly Align AI usage with monetization (e.g., Premium listings) Avoid uncontrolled API costs Extend eDirectory’s AI capabilities beyond default OpenAI behavior We believe this would significantly enhance the flexibility and long-term scalability of AI Mode across all eDirectory-powered platforms.
redila 4 months ago