Breadcrumb Path In Search Bar When Adding Item to List
We are experiencing difficulties when trying to add items to lists that share the same name across different nested structures. To improve the user experience and facilitate easier navigation, we propose implementing a breadcrumb navigation system a forward slash delimiter or a greater than sign delimiter. This will allow users to clearly identify the path to specific lists, especially when dealing with multiple lists of the same name. Steps to Reproduce Create a new item Navigate to the Save To List interface. Attempt to identify any contextual reference to that list or unique identifier. Observe the confusion caused by the lack of clear identification for the lists. Acceptance Criteria Implement a breadcrumb navigation system that displays the full path to a list using dot notation (e.g., Tronspark.YouTubePosts.Document), or using delimiters like a forwardslash / or a greater than symbol Ensure that users can easily type in the breadcrumb path to locate and add items to the correct list. The breadcrumb should dynamically update based on the user's current location within the nested lists. Provide visual indicators for the breadcrumb path to enhance user-friendliness. Ensure that the system can handle multiple levels of nesting without performance degradation. Link to Loom https://loom.com/share/401c2ed52a5040eeb8938c13850788cc?src=composer
Clayton Prickett 12 months ago
💡 Feature Request
Breadcrumb Path In Search Bar When Adding Item to List
We are experiencing difficulties when trying to add items to lists that share the same name across different nested structures. To improve the user experience and facilitate easier navigation, we propose implementing a breadcrumb navigation system a forward slash delimiter or a greater than sign delimiter. This will allow users to clearly identify the path to specific lists, especially when dealing with multiple lists of the same name. Steps to Reproduce Create a new item Navigate to the Save To List interface. Attempt to identify any contextual reference to that list or unique identifier. Observe the confusion caused by the lack of clear identification for the lists. Acceptance Criteria Implement a breadcrumb navigation system that displays the full path to a list using dot notation (e.g., Tronspark.YouTubePosts.Document), or using delimiters like a forwardslash / or a greater than symbol Ensure that users can easily type in the breadcrumb path to locate and add items to the correct list. The breadcrumb should dynamically update based on the user's current location within the nested lists. Provide visual indicators for the breadcrumb path to enhance user-friendliness. Ensure that the system can handle multiple levels of nesting without performance degradation. Link to Loom https://loom.com/share/401c2ed52a5040eeb8938c13850788cc?src=composer
Clayton Prickett 12 months ago
💡 Feature Request
Completed
Add an option to write in markdown (and other code languages like html, json, and javascript) in docs/when creating an item
Markdown is a super versitile language for taking down developer notes. For people to have a good experience creating documentation with our platform, we MUST have the ability to support writing in multiple coding languages. Theres a number of was to solve this, but an ideal solution would look like a dropdown/select option in the editor toolbar that allows a user to select the language they want to write in, i.e. Plaintext, Rich Text (the default - using the formatting options in the toolbar and keyboard formatting options like ctrl+b for bold, etc.), HTML, Markdown, Python, JavaScript, etc. Just like an IDE preformats your text, we should offer the same solution and simalr user experience. There are many times where I need to create a document that involves both code and text, and markdown and html are great languages to communicate from both sides (they can visually display formatted text as well as inline code). For instance, I am developing design documents for new automations and i need a way to clearly display what the API JSON response looks like from a particular scraper module, and there is not a way to effectively do that in our current docs editing system. This has been an outstanding request for months and there has been no traction on it, however, it would offer tremendous value for creating documentation around automations that are being sold on our platform. In regards to writing in JavaScript, it would be incredible if there was a way that we could allow users to run JavaScript (like a cloud function) just by writing the code into a doc (or some other new “Code” item we create) and calling it within the automation. There are some examples of this like 0codekit.com
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Completed
Add an option to write in markdown (and other code languages like html, json, and javascript) in docs/when creating an item
Markdown is a super versitile language for taking down developer notes. For people to have a good experience creating documentation with our platform, we MUST have the ability to support writing in multiple coding languages. Theres a number of was to solve this, but an ideal solution would look like a dropdown/select option in the editor toolbar that allows a user to select the language they want to write in, i.e. Plaintext, Rich Text (the default - using the formatting options in the toolbar and keyboard formatting options like ctrl+b for bold, etc.), HTML, Markdown, Python, JavaScript, etc. Just like an IDE preformats your text, we should offer the same solution and simalr user experience. There are many times where I need to create a document that involves both code and text, and markdown and html are great languages to communicate from both sides (they can visually display formatted text as well as inline code). For instance, I am developing design documents for new automations and i need a way to clearly display what the API JSON response looks like from a particular scraper module, and there is not a way to effectively do that in our current docs editing system. This has been an outstanding request for months and there has been no traction on it, however, it would offer tremendous value for creating documentation around automations that are being sold on our platform. In regards to writing in JavaScript, it would be incredible if there was a way that we could allow users to run JavaScript (like a cloud function) just by writing the code into a doc (or some other new “Code” item we create) and calling it within the automation. There are some examples of this like 0codekit.com
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Proposition to change URL structure
I suggest that instead of having the name of the item as the url, that we use the item id as the url path. This improves indexability and makes searching for items by id easier
Clayton Prickett About 1 year ago
💡 Feature Request
Proposition to change URL structure
I suggest that instead of having the name of the item as the url, that we use the item id as the url path. This improves indexability and makes searching for items by id easier
Clayton Prickett About 1 year ago
💡 Feature Request
Enhance Search Functionality in List Creation
Description: Currently, when a user wants to add items to a list, they have to type in the table in the search bar before anything relevant shows up. This feature request aims to enhance the user experience by providing a list of all available tables that the user can scroll through and select from, in addition to the existing search functionality. Steps to Reproduce: Click into the search bar for table selection. Notice a scrollable box containing a list of all available tables doesn't exist unless you type something. Type some item name Scroll through the list and select the desired item to add to the list. Acceptance Criteria: The user should be able to scroll through a list of all available items for selection. The list should be displayed in a scrollable box within the bounding box. The user should have the option to either select items from the list or type in the item name for selection (or to reduce to matches containing search query). The user experience should be improved by providing both search and scroll options for table selection. Link to Loom https://loom.com/share/57f5101cb57644b1aa5b8af9dd4e0c91?src=composer
Clayton Prickett About 1 year ago
💡 Feature Request
Enhance Search Functionality in List Creation
Description: Currently, when a user wants to add items to a list, they have to type in the table in the search bar before anything relevant shows up. This feature request aims to enhance the user experience by providing a list of all available tables that the user can scroll through and select from, in addition to the existing search functionality. Steps to Reproduce: Click into the search bar for table selection. Notice a scrollable box containing a list of all available tables doesn't exist unless you type something. Type some item name Scroll through the list and select the desired item to add to the list. Acceptance Criteria: The user should be able to scroll through a list of all available items for selection. The list should be displayed in a scrollable box within the bounding box. The user should have the option to either select items from the list or type in the item name for selection (or to reduce to matches containing search query). The user experience should be improved by providing both search and scroll options for table selection. Link to Loom https://loom.com/share/57f5101cb57644b1aa5b8af9dd4e0c91?src=composer
Clayton Prickett About 1 year ago
💡 Feature Request
Completed
Missing Information in Knowledge Base Download
Description: Currently, when downloading the knowledge-based from the KMS, the formatting is not user-friendly and crucial information is missing. Both the JSON output and the Plaintext only includes the first two levels of nesting, disregarding any further nested items. This results in incomplete data that is not suitable for training AI agents like ChatGPT. Steps to Reproduce: Download the knowledge-based JSON from the KMS. Open the downloaded JSON file. Note the lack of complete nesting information beyond the first two levels. Identify missing items and nested lists that should be included in the JSON. Acceptance Criteria: The downloaded JSON should include all nested items and lists within the KMS. Each nested list should be properly formatted with a title, description, and body content/items array. The JSON output should be comprehensive and readable, providing all necessary information for training AI agents. Ensure that the JSON download accurately reflects the entire structure of the KMS, including up to six/seven levels of nesting. The text output of the knowledge base should also include all relevant information, not just titles and descriptions. This issue is critical for ensuring the effectiveness of the KMS in training AI agents and should be addressed promptly. Link to Loom https://loom.com/share/ea96aa79f8534d90acf792a0bef10926?src=composer
Clayton Prickett About 1 year ago
High Priority
🐛 Bug Reports
Completed
Missing Information in Knowledge Base Download
Description: Currently, when downloading the knowledge-based from the KMS, the formatting is not user-friendly and crucial information is missing. Both the JSON output and the Plaintext only includes the first two levels of nesting, disregarding any further nested items. This results in incomplete data that is not suitable for training AI agents like ChatGPT. Steps to Reproduce: Download the knowledge-based JSON from the KMS. Open the downloaded JSON file. Note the lack of complete nesting information beyond the first two levels. Identify missing items and nested lists that should be included in the JSON. Acceptance Criteria: The downloaded JSON should include all nested items and lists within the KMS. Each nested list should be properly formatted with a title, description, and body content/items array. The JSON output should be comprehensive and readable, providing all necessary information for training AI agents. Ensure that the JSON download accurately reflects the entire structure of the KMS, including up to six/seven levels of nesting. The text output of the knowledge base should also include all relevant information, not just titles and descriptions. This issue is critical for ensuring the effectiveness of the KMS in training AI agents and should be addressed promptly. Link to Loom https://loom.com/share/ea96aa79f8534d90acf792a0bef10926?src=composer
Clayton Prickett About 1 year ago
High Priority
🐛 Bug Reports
Preserve Sidebar State on Navigation
Description: Currently, when navigating through nested categories in the application sidebar, the state of the sidebar is not preserved when going back to the previous view. This results in all categories collapsing and the user having to manually expand them again to find their place. The request is to maintain the previous state of the sidebar when navigating back, improving navigation efficiency and user experience. Steps to Reproduce: Navigate to a main category. Navigate to a nested category within the main category. Navigate to a further nested category within the nested category. Click the back button to return to the previous view. Acceptance Criteria: When clicking the back button from a nested category, the sidebar should revert to the previous state before navigating further. The state of the sidebar (expanded/collapsed categories) should be maintained when navigating back. This behavior will improve navigational efficiency and enhance the overall user experience. Link to Loom https://loom.com/share/99291f7a12624388b2c3b539a3b26348?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Preserve Sidebar State on Navigation
Description: Currently, when navigating through nested categories in the application sidebar, the state of the sidebar is not preserved when going back to the previous view. This results in all categories collapsing and the user having to manually expand them again to find their place. The request is to maintain the previous state of the sidebar when navigating back, improving navigation efficiency and user experience. Steps to Reproduce: Navigate to a main category. Navigate to a nested category within the main category. Navigate to a further nested category within the nested category. Click the back button to return to the previous view. Acceptance Criteria: When clicking the back button from a nested category, the sidebar should revert to the previous state before navigating further. The state of the sidebar (expanded/collapsed categories) should be maintained when navigating back. This behavior will improve navigational efficiency and enhance the overall user experience. Link to Loom https://loom.com/share/99291f7a12624388b2c3b539a3b26348?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Create Feature Request Embed in application
Description: Implement an embed feature request button within the application to allow users to easily submit feedback, bug reports, or feature requests directly from the application interface. This will empower users to contribute to the improvement of the application they use on a daily basis. Acceptance Criteria: The feature request button is visible and accessible in the bottom right-hand corner of the application interface. Users can hover over the button to see options for leaving feedback, reporting bugs, or submitting feature requests. Clicking on any option opens a form or pop-up window for users to input their feedback. The feature seamlessly integrates with FeatureBase for tracking and managing user-generated requests. Access keys are provided to team members for testing and implementation. The feature is documented for future reference and maintenance. Link to Loom https://loom.com/share/d990ed8804aa4fffb834e9e7753a5639?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Create Feature Request Embed in application
Description: Implement an embed feature request button within the application to allow users to easily submit feedback, bug reports, or feature requests directly from the application interface. This will empower users to contribute to the improvement of the application they use on a daily basis. Acceptance Criteria: The feature request button is visible and accessible in the bottom right-hand corner of the application interface. Users can hover over the button to see options for leaving feedback, reporting bugs, or submitting feature requests. Clicking on any option opens a form or pop-up window for users to input their feedback. The feature seamlessly integrates with FeatureBase for tracking and managing user-generated requests. Access keys are provided to team members for testing and implementation. The feature is documented for future reference and maintenance. Link to Loom https://loom.com/share/d990ed8804aa4fffb834e9e7753a5639?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Implement Path Display and Search by ID in KMS
Description: When duplicating documents across multiple client folders in the Knowledge Management System (KMS), it becomes challenging to identify the exact location of the document within the nested folder structure. To address this issue, it is proposed to display the path leading to the document or folder and enable searching by ID to locate specific items efficiently. Steps to Reproduce: Duplicate a document. Attempt to identify the exact location of the duplicated document within the nested folder structure. (Not intuitive) Try to search for a specific document by its ID. Acceptance Criteria: The path leading to a document or folder should be displayed in the interface (in the list search drop down, on the public page, and in the edit view) showing the hierarchy of folders from the root to the specific item. Users should be able to search for any item by its unique ID in any search bar. The path display should be visible above the title of the document or folder on the public page. Please implement both the path display feature and the search by ID functionality to enhance the user experience and facilitate efficient navigation within the application. https://loom.com/share/9c0cfbd1fbf74cba809c8bed708fb9ca?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Implement Path Display and Search by ID in KMS
Description: When duplicating documents across multiple client folders in the Knowledge Management System (KMS), it becomes challenging to identify the exact location of the document within the nested folder structure. To address this issue, it is proposed to display the path leading to the document or folder and enable searching by ID to locate specific items efficiently. Steps to Reproduce: Duplicate a document. Attempt to identify the exact location of the duplicated document within the nested folder structure. (Not intuitive) Try to search for a specific document by its ID. Acceptance Criteria: The path leading to a document or folder should be displayed in the interface (in the list search drop down, on the public page, and in the edit view) showing the hierarchy of folders from the root to the specific item. Users should be able to search for any item by its unique ID in any search bar. The path display should be visible above the title of the document or folder on the public page. Please implement both the path display feature and the search by ID functionality to enhance the user experience and facilitate efficient navigation within the application. https://loom.com/share/9c0cfbd1fbf74cba809c8bed708fb9ca?src=composer
Clayton Prickett About 1 year ago
High Priority
💡 Feature Request
Completed
3 Major Bugs
Watch the video below https://jam.dev/c/c15ab3f1-f35d-4a88-b9dd-8c5f11a0a72b Bugs: Description not populating when editing document When saving a document and re-entering to edit the document, the document content reverts to previous state. Loading time takes up to 14 seconds when first initializing application Steps to Reproduce Description not populating when editing document Edit a document with a description Open “Advanced” section Notice the description is not present/visible to the user When saving a document and re-entering to edit the document, the document content reverts to previous state. Edit a document Save document Re-edit same document Notice content reverts to previous state Loading time takes up to 14 seconds when first initializing application Open a new tab and go to snackprompt.com Log in with snackautomations@gmail.com Open the “Combined Lists” section in the right-hand side bar Notice the amount of time the section takes to load Acceptance Criteria Description not populating when editing document Description must always be visible and editable in the edit view for any item When saving a document and re-entering to edit the document, the document content reverts to previous state. Ensure that the state is properly saved/stored sfter editing any item/content Loading time takes up to 14 seconds when first initializing application Improve loading time if possible Add a suspense fallback or loading symbol toimprove user experience
SnackPrompt About 1 year ago
High Priority
🐛 Bug Reports
Completed
3 Major Bugs
Watch the video below https://jam.dev/c/c15ab3f1-f35d-4a88-b9dd-8c5f11a0a72b Bugs: Description not populating when editing document When saving a document and re-entering to edit the document, the document content reverts to previous state. Loading time takes up to 14 seconds when first initializing application Steps to Reproduce Description not populating when editing document Edit a document with a description Open “Advanced” section Notice the description is not present/visible to the user When saving a document and re-entering to edit the document, the document content reverts to previous state. Edit a document Save document Re-edit same document Notice content reverts to previous state Loading time takes up to 14 seconds when first initializing application Open a new tab and go to snackprompt.com Log in with snackautomations@gmail.com Open the “Combined Lists” section in the right-hand side bar Notice the amount of time the section takes to load Acceptance Criteria Description not populating when editing document Description must always be visible and editable in the edit view for any item When saving a document and re-entering to edit the document, the document content reverts to previous state. Ensure that the state is properly saved/stored sfter editing any item/content Loading time takes up to 14 seconds when first initializing application Improve loading time if possible Add a suspense fallback or loading symbol toimprove user experience
SnackPrompt About 1 year ago
High Priority
🐛 Bug Reports
Snack Prompt For Teams page needs a lead capture form and footer needs update
Description: Currently, the element on the join page that has a hover interaction is not clickable. To enhance user engagement and capture leads, it is proposed to update this element to a button. When users click on this button, a modal window should pop up, allowing them to input their information to join a waitlist. Steps to Reproduce: Navigate to the join page. Locate the element with the hover interaction. Click on the element to observe that it is not clickable. Update the element to a button. Verify that clicking on the button triggers a modal window to appear for lead capture. Acceptance Criteria: The element on the join page is updated to a button. Clicking on the button opens a modal window for lead capture. The modal window allows users to input their information to join a waitlist. The updated feature enhances user engagement and captures leads effectively. Update footer links to redirect users to snackprompt.featurebase.app Link to Loom https://loom.com/share/0d05c183c8254584a48db0c6c6fc70d6?src=composer
Clayton Prickett About 1 year ago
🐛 Bug Reports
Snack Prompt For Teams page needs a lead capture form and footer needs update
Description: Currently, the element on the join page that has a hover interaction is not clickable. To enhance user engagement and capture leads, it is proposed to update this element to a button. When users click on this button, a modal window should pop up, allowing them to input their information to join a waitlist. Steps to Reproduce: Navigate to the join page. Locate the element with the hover interaction. Click on the element to observe that it is not clickable. Update the element to a button. Verify that clicking on the button triggers a modal window to appear for lead capture. Acceptance Criteria: The element on the join page is updated to a button. Clicking on the button opens a modal window for lead capture. The modal window allows users to input their information to join a waitlist. The updated feature enhances user engagement and captures leads effectively. Update footer links to redirect users to snackprompt.featurebase.app Link to Loom https://loom.com/share/0d05c183c8254584a48db0c6c6fc70d6?src=composer
Clayton Prickett About 1 year ago
🐛 Bug Reports
Update Browser Extension to be a copy/duplicate of user's sidebar
Description: Currently, the browser extension for the Chrome browser allows users to access snippets while working with ChatGPT, but does not provide access to any of their other items or features of the sidebar in Snack Prompt. There is also a need to enhance the extension by adding a feature that enables users to create prompts directly within the extension (as well as the sidebar in SP). This feature would streamline the process of creating and using prompts during conversations with ChatGPT. Acceptance Criteria: Users should be able to access the full sidebar of the user as well as the "Create” feature directly within the browser extension interface. The item creation interface should resemble the editing view available in the sidebar of Snack Prompt for consistency. The "Create" button should be positioned in an easily accessible location (bottom corner) within the extension interface. The feature should remain visible and accessible even when multiple lists or sections are open within the extension. The design should include a drop-down menu for selecting the type of item to create (prompts, snippets, documents, etc.) for user convenience. Link to Loom https://loom.com/share/5570250bd51341a88902a7df53d55add?src=composer
Clayton Prickett About 1 year ago
Low Priority
💡 Feature Request
Update Browser Extension to be a copy/duplicate of user's sidebar
Description: Currently, the browser extension for the Chrome browser allows users to access snippets while working with ChatGPT, but does not provide access to any of their other items or features of the sidebar in Snack Prompt. There is also a need to enhance the extension by adding a feature that enables users to create prompts directly within the extension (as well as the sidebar in SP). This feature would streamline the process of creating and using prompts during conversations with ChatGPT. Acceptance Criteria: Users should be able to access the full sidebar of the user as well as the "Create” feature directly within the browser extension interface. The item creation interface should resemble the editing view available in the sidebar of Snack Prompt for consistency. The "Create" button should be positioned in an easily accessible location (bottom corner) within the extension interface. The feature should remain visible and accessible even when multiple lists or sections are open within the extension. The design should include a drop-down menu for selecting the type of item to create (prompts, snippets, documents, etc.) for user convenience. Link to Loom https://loom.com/share/5570250bd51341a88902a7df53d55add?src=composer
Clayton Prickett About 1 year ago
Low Priority
💡 Feature Request
Completed
Dropdown Menu for Item Creation Options
Description: A dropdown menu when clicking on the "Create" button would allow users to choose the specific item type they want to create, such as a prompt, snippet, or list, rather than defaulting to a single option. Technical Requirements: Add a dropdown menu to the "Create" button with various item types. Allow users to select from options like "Prompt," "Snippet," "List," etc. Route users to the appropriate creation modal (suggested) or page based on selection. Benefits: Provides flexibility for users to choose what they want to create upfront. Reduces unnecessary steps, creating a more efficient experience. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=7c260baf-5ed0-40af-9469-1390842a0a89
Clayton Prickett Over 1 year ago
💡 Feature Request
Completed
Dropdown Menu for Item Creation Options
Description: A dropdown menu when clicking on the "Create" button would allow users to choose the specific item type they want to create, such as a prompt, snippet, or list, rather than defaulting to a single option. Technical Requirements: Add a dropdown menu to the "Create" button with various item types. Allow users to select from options like "Prompt," "Snippet," "List," etc. Route users to the appropriate creation modal (suggested) or page based on selection. Benefits: Provides flexibility for users to choose what they want to create upfront. Reduces unnecessary steps, creating a more efficient experience. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=7c260baf-5ed0-40af-9469-1390842a0a89
Clayton Prickett Over 1 year ago
💡 Feature Request
Tooltips for Enhanced Accessibility
Description: The platform lacks sufficient tooltips, which could make navigation and understanding of functions challenging for some new users. Tooltips would provide additional information and improve overall usability for new users lacking instinctive navigation capacity. Technical Requirements: Add tooltips to buttons, icons, and other interactive elements where it would make sense to have one. Ensure tooltips provide concise descriptions for accessibility. Use hover and focus events to trigger tooltips, keeping accessibility in mind. Benefits: Improves navigation and user understanding of elements. Makes the platform more intuitive for first-time users. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=7c260baf-5ed0-40af-9469-1390842a0a89
Clayton Prickett Over 1 year ago
💡 Feature Request
Tooltips for Enhanced Accessibility
Description: The platform lacks sufficient tooltips, which could make navigation and understanding of functions challenging for some new users. Tooltips would provide additional information and improve overall usability for new users lacking instinctive navigation capacity. Technical Requirements: Add tooltips to buttons, icons, and other interactive elements where it would make sense to have one. Ensure tooltips provide concise descriptions for accessibility. Use hover and focus events to trigger tooltips, keeping accessibility in mind. Benefits: Improves navigation and user understanding of elements. Makes the platform more intuitive for first-time users. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=7c260baf-5ed0-40af-9469-1390842a0a89
Clayton Prickett Over 1 year ago
💡 Feature Request
Modal Windows
Description: Modal windows are underutilized in the current design. Modal-based interactions for creating and viewing items would make the platform more user-friendly and less jarring, as users won’t need to navigate away to a new page. Technical Requirements: Implement modal windows for item creation and viewing. Dim the background to focus the user’s attention on the modal. Include “close” buttons in modals for efficient navigation and completion. Benefits: Reduces the cognitive load on users by maintaining context. Enhances the platform’s visual hierarchy and usability. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Modal Windows
Description: Modal windows are underutilized in the current design. Modal-based interactions for creating and viewing items would make the platform more user-friendly and less jarring, as users won’t need to navigate away to a new page. Technical Requirements: Implement modal windows for item creation and viewing. Dim the background to focus the user’s attention on the modal. Include “close” buttons in modals for efficient navigation and completion. Benefits: Reduces the cognitive load on users by maintaining context. Enhances the platform’s visual hierarchy and usability. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Carousel for Product/Item Cards
Description: Enhance each product card with a two-section carousel. The first section displays the banner image, and the second shows an overview video (if available). This allows users to gain more context about the product before committing to exploring it in depth. Technical Requirements: Implement a conditional carousel component on product cards. Integrate both image and video components within the carousel, rendering the video only if an overview video exists. Design a simple indicator, such as an arrow icon, to toggle between the image and video. Display the video in a modal window when a user clicks the play button. Benefits: Provides more easily accessible context about products, increasing user engagement. Adds dynamic elements to the interface, reducing the static feel of the platform. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Carousel for Product/Item Cards
Description: Enhance each product card with a two-section carousel. The first section displays the banner image, and the second shows an overview video (if available). This allows users to gain more context about the product before committing to exploring it in depth. Technical Requirements: Implement a conditional carousel component on product cards. Integrate both image and video components within the carousel, rendering the video only if an overview video exists. Design a simple indicator, such as an arrow icon, to toggle between the image and video. Display the video in a modal window when a user clicks the play button. Benefits: Provides more easily accessible context about products, increasing user engagement. Adds dynamic elements to the interface, reducing the static feel of the platform. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Dark and Light Mode Toggle
Description: The platform currently has a static appearance, lacking interactivity in terms of themes. A dark and light mode option would enhance usability and visual appeal, especially given developers' preference for dark mode. Technical Requirements: Implement a toggle for switching between dark and light modes. Utilize Tailwind CSS’s theming capabilities to ensure seamless theme switching. Set a default mode based on system preferences or previous user selection. Benefits: Improved accessibility and user preference alignment. Increased engagement through customizable UI. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Dark and Light Mode Toggle
Description: The platform currently has a static appearance, lacking interactivity in terms of themes. A dark and light mode option would enhance usability and visual appeal, especially given developers' preference for dark mode. Technical Requirements: Implement a toggle for switching between dark and light modes. Utilize Tailwind CSS’s theming capabilities to ensure seamless theme switching. Set a default mode based on system preferences or previous user selection. Benefits: Improved accessibility and user preference alignment. Increased engagement through customizable UI. https://www.loom.com/share/a2f8dcbb56be4bb7934d61557a9c51e7?sid=6431cf18-faca-47c9-aea5-c267db9c117c
Clayton Prickett Over 1 year ago
💡 Feature Request
Completed
Profile photo upload, youtube link, and linkedin link non existent in settings
User was trying to upload photo, youtube link, and linked in link, which are all non existent options in user settings.
Clayton Prickett Over 1 year ago
🐛 Bug Reports
Completed
Profile photo upload, youtube link, and linkedin link non existent in settings
User was trying to upload photo, youtube link, and linked in link, which are all non existent options in user settings.
Clayton Prickett Over 1 year ago
🐛 Bug Reports
Completed
Bug with Automations HTML lists do not display in documents
Description: There is a persistent bug in the automation system where HTML documents with unordered or ordered lists do not display correctly on the front end in SnackPrompt. The issue seems to be related to the transformation process of the data between the API post request and displaying the content on the front end. Steps to Reproduce: Create a prompt for a blog post creation assistant with a task to provide a blog post in simple HTML format with bullet points. Include unordered or ordered lists in the content. Check the output on the front end to see that the lists are not displayed. Acceptance Criteria: The bug causing unordered or ordered lists not to display correctly in HTML documents must be identified and resolved. The transformation process of the data between the API post request and the front end display should be adjusted to correctly render lists. The issue should be fixed within a week to ensure the functionality of the automation system is fully operational for all users. Link to Loom https://loom.com/share/dfc8abad69f548b39ad5ea46f2f4d21c?src=composer
Clayton Prickett Over 1 year ago
🐛 Bug Reports
Completed
Bug with Automations HTML lists do not display in documents
Description: There is a persistent bug in the automation system where HTML documents with unordered or ordered lists do not display correctly on the front end in SnackPrompt. The issue seems to be related to the transformation process of the data between the API post request and displaying the content on the front end. Steps to Reproduce: Create a prompt for a blog post creation assistant with a task to provide a blog post in simple HTML format with bullet points. Include unordered or ordered lists in the content. Check the output on the front end to see that the lists are not displayed. Acceptance Criteria: The bug causing unordered or ordered lists not to display correctly in HTML documents must be identified and resolved. The transformation process of the data between the API post request and the front end display should be adjusted to correctly render lists. The issue should be fixed within a week to ensure the functionality of the automation system is fully operational for all users. Link to Loom https://loom.com/share/dfc8abad69f548b39ad5ea46f2f4d21c?src=composer
Clayton Prickett Over 1 year ago
🐛 Bug Reports
Implement Feed, Gallery Views, and DM's in Snack Prompt
Description: By implementing a feed, a gallery view feature on the public facing user page, and direct messaging capabilities in Snack Prompt will enhance user engagement and interaction within the application. These features will allow users to leisurely browse through prompts, automations, and other user-generated content in a visually appealing manner, have a more visually appealing interface for users to engage with on other user profiles, and create a more connected user community by offering direct messaging. Feed View Add a feed view option to the main interface of Snack Prompt (in the far right views sidebar). Include options for random hot topics, trending prompts, and user likes/saves. Enable users to click on items to view detailed information, comments, and interaction options like liking, searching, and downloading. Gallery View Implement a gallery view for saved items to replace the current list format on the public user profile. Allow users to scroll through different designs and interact with the application in a more engaging way. Direct Messages View Add a direct messages view to bolster community engagement and offer a simple way for creators to provide quick and responsive support for their products User's should also be able to create support channels specifically for products like automations, or community channels for community building and sharing ideas (like teams "discussion" but a public channel) Acceptance Criteria: Users can switch between list and gallery views for saved items. The feed view displays a variety of prompts and automations for user interaction. Detailed information, comments, and interaction options are available for each item in the feed. The gallery view provides a visually appealing way to browse through items on a user's profile The implementation of feed and gallery views enhances user engagement and interaction within Snack Prompt. The implimentation of direct messaging incorporates "channels" and give users the ability to chat with other users on the platform. Link to Loom https://loom.com/share/eaec6065f9404d70aaac93f957ac69d9?src=composer
Clayton Prickett Over 1 year ago
High Priority
💡 Feature Request
Implement Feed, Gallery Views, and DM's in Snack Prompt
Description: By implementing a feed, a gallery view feature on the public facing user page, and direct messaging capabilities in Snack Prompt will enhance user engagement and interaction within the application. These features will allow users to leisurely browse through prompts, automations, and other user-generated content in a visually appealing manner, have a more visually appealing interface for users to engage with on other user profiles, and create a more connected user community by offering direct messaging. Feed View Add a feed view option to the main interface of Snack Prompt (in the far right views sidebar). Include options for random hot topics, trending prompts, and user likes/saves. Enable users to click on items to view detailed information, comments, and interaction options like liking, searching, and downloading. Gallery View Implement a gallery view for saved items to replace the current list format on the public user profile. Allow users to scroll through different designs and interact with the application in a more engaging way. Direct Messages View Add a direct messages view to bolster community engagement and offer a simple way for creators to provide quick and responsive support for their products User's should also be able to create support channels specifically for products like automations, or community channels for community building and sharing ideas (like teams "discussion" but a public channel) Acceptance Criteria: Users can switch between list and gallery views for saved items. The feed view displays a variety of prompts and automations for user interaction. Detailed information, comments, and interaction options are available for each item in the feed. The gallery view provides a visually appealing way to browse through items on a user's profile The implementation of feed and gallery views enhances user engagement and interaction within Snack Prompt. The implimentation of direct messaging incorporates "channels" and give users the ability to chat with other users on the platform. Link to Loom https://loom.com/share/eaec6065f9404d70aaac93f957ac69d9?src=composer
Clayton Prickett Over 1 year ago
High Priority
💡 Feature Request
Improve Table Functionality for Reading and Writing
Description: The current table feature in SnackPrompt lacks the ability to create new rows and columns, limiting the flexibility and usability of the tables. This poses a significant challenge for users who need to read and write data dynamically within the tables. Enhancing the table functionality is crucial to provide a more intuitive and user-friendly experience, especially for automators who heavily rely on this feature. Steps to Reproduce: Attempt to create a new row or column within an existing table using existing SnackPrompt Make Modules. Notice the inability to dynamically add new rows or columns to the table. Try to automate data entry or manipulation within the table and encounter limitations due to the lack of flexibility. Acceptance Criteria: Users should be able to easily create new rows and columns within the table using Make modules. The table feature should support dynamic data entry and manipulation for automators. The functionality of the table should align with industry standards for tabular data management. The improved table feature should enhance the overall user experience and usability of SnackPrompt. The changes should be thoroughly tested to ensure proper functionality before deployment to the live production environment. Link to Loom https://www.loom.com/share/ec709f5bc6514f4998db29e3ec275533
Clayton Prickett Over 1 year ago
High Priority
💡 Feature Request
Improve Table Functionality for Reading and Writing
Description: The current table feature in SnackPrompt lacks the ability to create new rows and columns, limiting the flexibility and usability of the tables. This poses a significant challenge for users who need to read and write data dynamically within the tables. Enhancing the table functionality is crucial to provide a more intuitive and user-friendly experience, especially for automators who heavily rely on this feature. Steps to Reproduce: Attempt to create a new row or column within an existing table using existing SnackPrompt Make Modules. Notice the inability to dynamically add new rows or columns to the table. Try to automate data entry or manipulation within the table and encounter limitations due to the lack of flexibility. Acceptance Criteria: Users should be able to easily create new rows and columns within the table using Make modules. The table feature should support dynamic data entry and manipulation for automators. The functionality of the table should align with industry standards for tabular data management. The improved table feature should enhance the overall user experience and usability of SnackPrompt. The changes should be thoroughly tested to ensure proper functionality before deployment to the live production environment. Link to Loom https://www.loom.com/share/ec709f5bc6514f4998db29e3ec275533
Clayton Prickett Over 1 year ago
High Priority
💡 Feature Request