Meta tags:
description= Give feedback to the Document360 team so we can make more informed product decisions. Powered by Canny.;
Headings (most frequently used words):
feature, request, boards,
Text of the page (most frequently used words):
the (68), and (36), for (15), quotes (14), article (13), editor (11), feedback (10), file (9), that (9), site (9), typographic (9), quote (9), specific (8), not (8), like (8), custom (8), use (7), category (7), decision (7), users (7), have (7), user (7), readers (7), all (7), knowledge (7), base (7), workspace (7), css (7), request (6), drive (6), document360 (6), from (6), within (6), are (6), new (6), currently (6), comma (6), styling (6), export (6), there (5), should (5), this (5), tree (5), content (5), would (5), page (5), also (5), does (5), management (5), feature (5), punctuation (5), before (5), double (5), notifications (5), live (5), exported (5), image (4), tools (4), ability (4), step (4), with (4), articles (4), each (4), they (4), settings (4), their (4), categories (4), eddy (4), copy (4), documentation (4), dashboard (4), email (4), widget (4), ticket (4), rules (4), language (4), straight (4), colon (4), code (4), bulk (4), api (4), add (3), link (3), name (3), directly (3), see (3), window (3), names (3), able (3), help (3), need (3), create (3), filter (3), what (3), date (3), only (3), under (3), last (3), can (3), changes (3), questions (3), complete (3), provided (3), overview (3), search (3), inside (3), logo (3), homepage (3), instead (3), default (3), when (3), languages (3), shape (3), outside (3), single (3), without (3), review (3), zip (3), match (3), read (3), security (3), team (3), suite (3), groups (3), log (3), powered (2), canny (2), line (2), below (2), edit (2), possible (2), case (2), meaningless (2), media (2), files (2), however (2), into (2), receive (2), provide (2), correct (2), backlog (2), interactive (2), want (2), scenario (2), will (2), customer (2), range (2), end (2), published (2), updated (2), days (2), such (2), across (2), updates (2), find (2), chatbot (2), conversation (2), context (2), button (2), citations (2), enhance (2), external (2), emails (2), where (2), option (2), chat (2), deflector (2), better (2), support (2), clicking (2), advanced (2), wysiwyg (2), machine (2), translation (2), apply (2), country (2), style (2), https (2), marks (2), said (2), apples (2), left (2), fallback (2), french (2), implementing (2), curly (2), elements (2), followed (2), operations (2), notification (2), digest (2), control (2), import (2), configured (2), applied (2), output (2), difficult (2), appear (2), html (2), pdf (2), analytics (2), manager (2), extensions (2), trending (2), load, more, location, images, editing, ideally, either, 2nd, quick, tool, bar, example, accessible, renaming, assign, folders, entries, good, first, ensure, flooded, autonumbered, 9999, png, may, still, drag, dropped, authors, editors, thus, upload, easily, change, exact, based, experiencing, unique, combination, lead, eventually, best, customizable, start, offers, preset, options, hours, view, period, particular, month, release, lists, scan, through, unrelated, care, about, filters, responses, along, retain, strips, individual, pairs, entire, thread, while, preserving, formatting, source, links, making, easier, share, transcripts, ticketing, internal, functionality, include, conversations, offer, simple, section, his, status, second, answer, solver, has, asked, having, mail, income, decrease, time, reduced, further, communication, needed, needs, answered, prospect, expecting, tab, allow, application, get, used, platform, home, behavior, any, routes, primary, enable, navigation, both, english, countries, conventions, differ, sometimes, even, observe, linguistic, european, union, gives, here, europa, web, vocabularies, formex, physical, specifications, character, encoding, quotation, different, examples, differing, sagte, lower, upper, dit, aime, les, pommes, est, parti, non, breaking, spaces, semi, exclamation, question, guillemets, nbsp, ways, unicode, characters, blockquote, them, typographically, w3c, github, i18n, discuss, our, recommendation, much, less, hassle, allows, quoting, instance, function, misusing, element, other, done, text, multiple, together, during, publish, reference, many, separate, rapid, succession, customers, these, consolidated, summarizing, publishing, run, enables, sustainably, track, flooding, own, particularly, publishes, common, thank, you, consolidation, publication, exporting, causes, several, inconsistencies, make, deliverable, issues, observed, inline, block, table, hard, hyperlink, font, family, size, letter, spacing, height, correctly, lnb, hyperlinks, using, styles, overall, reflected, visually, matches, essential, distribution, purposes, floik, mcp, guides, collaboration, auditing, receipt, project, trees, markdown, 184, data, transfer, recovery, reuse, billing, authentication, authorization, writer, premium, 118, sandbox, assistant, workflow, designer, variables, deflectors, templates, accounts, tags, smart, bars, announcements, seo, description, roles, permissions, self, registration, 114, customization, restrictions, health, check, metrics, snippets, glossary, replace, pages, cookie, consent, policy, backup, restore, 106, revision, history, reminders, discussions, redirection, 113, 124, 334, integrations, 149, 289, 155, infrastructure, 122, 635, 232, 141, performance, 199, payment, 189, posts, hold, progress, planned, top, sort, showing, post, cancel, select, details, anonymous, boards, your, account, give, roadmap,
Text of the page (random words):
feature request document360 document360 create log in roadmap feedback feature request log in to your document360 account to give feedback log in boards feature request powered by canny feature request anonymous details category select a category cancel create post showing trending sort trending top new filter under review planned in progress on hold backlog complete posts in all categories all categories category management 189 payment 6 search 199 site performance 23 api 141 ui ux 232 editor 635 security 122 infrastructure 28 content tools 155 analytics 289 integrations extensions 149 settings 92 api documentation 97 kb site 334 drive 124 export to pdf 113 article redirection 28 article discussions 17 article review reminders 23 article revision history 49 article settings 106 backup restore 8 bulk operations 62 content security policy 8 cookie consent 2 custom pages 19 extensions 44 feedback manager 78 find replace 25 glossary 63 snippets 50 health check metrics 2 import export 99 ip restrictions 4 kb customization 68 kb site article settings 45 machine translation 38 notifications 94 readers groups 114 readers self registration 17 roles permissions 28 seo description 26 smart bars announcements 11 tags groups 31 team accounts groups 38 article templates 13 ticket deflectors 23 variables 13 workflow designer 52 workspace manager 31 kb assistant 82 sandbox 7 ai eddy 118 dashboard 15 ai premium suite 9 ai search suite 20 ai writer suite 14 article management 82 authentication authorization 7 billing 6 content reuse 26 dashboard analytics 4 data transfer recovery 0 editor advanced wysiwyg 184 editor markdown 2 feedback management 13 widget chat ticket deflector 64 pdf export 24 interactive decision trees 20 project workspace management 8 read receipt 5 team auditing notification 14 team collaboration 6 users and security 47 step by step guides 9 mcp 32 floik ai 4 apply custom css to html export zip file currently when exporting the knowledge base as a zip file custom css configured for the live site is not applied to the exported output this causes several styling inconsistencies that make the exported file difficult to use as a deliverable below are the specific issues observed inline code styling does not match the live knowledge base code block styling is difficult to read table styling does not match the live knowledge base and is hard to read hyperlink styling within articles does not match the live knowledge base font family size letter spacing and line height are not configured correctly lnb hyperlinks appear to be using default document360 css instead of the custom styles overall custom css does not appear to be applied to the exported file at all we would like to request that custom css be reflected in the html export zip file so that the exported output visually matches the live knowledge base this is essential for us to use the exported file for external distribution and documentation purposes 5 import export under review 14 support email digest consolidation for followed article publication notifications when multiple articles in a followed category are published together such as during bulk publish operations on api reference content readers currently receive many separate notification emails in rapid succession customers need these notifications consolidated into a single digest email summarizing all changes from that publishing run this enables readers to sustainably track bulk updates without email flooding or we want to control the end users to be able to control their own notifications particularly for categories like api documentation where bulk publishes are common thank you 1 notifications 7 use country language specific punctuation and typographic quotes currently the editor and the machine translation feature both apply english punctuation and typographic quotes to all languages and countries however punctuation rules and typographic conventions differ by language and sometimes even across languages by country document360 should observe the correct linguistic and style rules for each language the european union gives an overview of typographic quotes here https op europa eu en web eu vocabularies formex physical specifications character encoding use of quotation marks in the different languages examples for differing punctuation rules en us he said i like apples and left comma before quote comma inside of quote straight double quotes or typographic double quotes in 66 99 shape en gb he said i like apples and left comma before quote comma outside of quote straight single quotes or typographic single quotes in 6 9 shape de de and cs cz er sagte colon before quote comma outside of quote typographic double quotes in lower 99 upper 66 shape straight double quotes only as a fallback fr fr il a dit j aime les pommes et il est parti non breaking spaces before colon semi colon exclamation and question marks and directly within french quotes colon before quote typographic french quotes guillemets comma outside of quote straight double quotes without nbsp within only as a fallback there are 2 ways of implementing curly quotes use curly typographic quotes as unicode characters in the editor article code use the q and blockquote elements in the editor article code and language specific css to style them typographically see https w3c github io i18n discuss default quote styling our recommendation would be option 1 as it is much less hassle and allows for quoting for instance ui elements or function names without misusing the q element also implementing the other punctuation rules is better done directly within the text instead of css 0 editor advanced wysiwyg 3 enable workspace specific homepage navigation when clicking the site logo support workspace specific logo home button behavior so that clicking the logo from any workspace routes users to that workspace s homepage instead of the primary default workspace homepage 0 kb site 6 decision tree inside knowledge base widget prospect is expecting decision tree also in kb widget like we have provided ticket deflector as a new tab this will allow the users to have a decision tree inside their application and get used to the platform better 3 widget chat ticket 18 overview of feedback for readers on kb site offer the user a dashboard of their provided feedback to have a simple overview there should be a section where a user can see all his provided feedback and the status of each in a second step there should also be the option for the user to answer questions the feedback solver has asked by having a feedback dashboard for users on the kb site the mail income for each user would decrease and search time can be reduced there is also no further email communication needed in case of questions that needs to be answered by a user 0 feedback management 3 enhance eddy ai chatbot copy functionality to include complete conversations and citations users need the ability to copy eddy ai chatbot responses along with the user s questions and conversation context currently the copy button does not retain the complete q a context and strips citations enhance it to copy individual q a pairs or the entire conversation thread while preserving formatting and source links making it easier to share transcripts in external ticketing tools emails and internal documentation 1 ai eddy 2 custom date range and category filters to the what s new page customer would like to have the ability to filter the what s new page with a custom date range a start and end date currently the page only offers preset options under published updated last 24 hours last 7 days last 30 days so readers can t view changes from a specific period such as a particular month or release window customer would also like to have the ability to filter the what s new page by category currently the page lists all new and updated articles across the knowledge base so readers have to scan through unrelated updates to find changes in the categories they care about 1 kb site 4 decision tree customizable help i want to be able to provide users with the exact help they need based on the specific scenario they are experiencing or the unique combination of settings they have for this i d like to create a decision tree that will lead the user eventually to the best possible help content for their scenario 9 interactive decision backlog 15 add drive link and image name change to article editor image tools request add a link to the drive location and file name of images in the document360 drive to the image editing tools of the article editor ideally either add the link directly as a 2nd line to the quick tool bar see example below or to the edit window accessible from there renaming should be possible from within the edit window use case the ability to assign specific drive folders to category entries is a good first step to ensure that the drive is not flooded with meaningless autonumbered image 0 9999 png media files however files may still be drag and dropped into articles and receive meaningless file names authors and editors should thus be able to a provide a name at each upload and b easily correct media file names from within the editor 0 editor 3 load more powered by canny
|
