您可以使用 HTML 块快速访问和编辑内容块和文章中的复杂 HTML 代码。通过 HTML 块，您可以处理本来无法在编辑器中编辑的代码块，并在帮助中心以安全的方式显示它们。
关于 HTML 块
使用 HTML 块，您可以将 不受支持的 HTML 元素代码 复制粘贴到源代码编辑器中。然后代码将被包装在 HTML 块中，并显示在文章或内容块中。您可以单击 HTML 块以打开仅显示该块代码的源代码编辑器。您可以使用此聚焦视图来操作选定内容的 HTML，而无需滚动查看整个内容块或文章的源代码。
更新内容块或文章时，与该 HTML 块关联的 HTML 元素将显示在所有已发布文章或包含该 HTML 块的内容块中。您可以将 HTML 块用于任何不受支持的 HTML 代码块，包括复杂的 HTML 脚本或元素，例如目录、折叠、标签或步进器。
创建 HTML 块
），然后选择 HTML 块。
编辑 HTML 块
HTML 块使您可以轻松找到并使用该块的源代码。您可以直接从内容块或文章编辑器访问和编辑 HTML 块的源代码，而无需滚动源代码。
- 在 编辑 模式中打开包含您要编辑的 HTML 块的文章或内容块。
- 单击您要编辑的 HTML 块以显示选项图标，然后选择 编辑 图标 (
）。HTML 块编辑器在编辑模式下打开。
- 在 HTML 块编辑器中进行必要的更改。
- 单击应用。
您的更新已保存，并在所有文章和包含该 HTML 块的内容块中可见。您无需重新发布文章即可显示内容块中的更改。
取消链接 HTML 块
您可以取消链接 HTML 块以内联 HTML 块，并从内容中删除任何不受支持的标记。您可以在取消链接之前预览将要移除的代码。
- 在编辑模式中打开包含您要编辑的 HTML 块的文章或内容块。
- 单击您要删除的 HTML 块以显示选项图标，然后选择 取消链接 图标 (
）。 -
审阅将要取消链接的代码，以确保您了解将移除哪些内容。要继续，单击 取消链接。
HTML 块已取消链接，不受支持的代码已移除。
- 单击 更新 （对于内容块）或 保存 （对于文章）。
该 HTML 块在所有内容块和文章中都未链接。
删除 HTML 块
删除 HTML 块会将 HTML 块（包括该块中的文本和代码）从文章中移除。当您删除 HTML 块时，该块将立即移除，无需确认，且不可撤消。
- 在 编辑 模式中打开包含您要编辑的 HTML 块的文章或内容块。
- 单击您要删除的 HTML 块以显示选项图标，然后选择 删除 图标 (
）。HTML 块将被移除，而不进行确认。
- 单击 更新 （对于内容块）或 保存 （对于文章）。
该 HTML 块将在所有显示该内容块的文章中删除。
翻译免责声明：本文章使用自动翻译软件翻译，以便您了解基本内容。 我们已采取合理措施提供准确翻译，但不保证翻译准确性
如对翻译准确性有任何疑问，请以文章的英语版本为准。
11 条评论
Vinicius Henrique da Silva
I'd like to express my dissatisfaction regarding the removal of
<iframe>support in the new article editor for non-Enterprise plans.Previously, it was completely possible to embed PowerPoint Online presentations in articles using a simple
<iframe>. This was a basic, functional, and very useful feature to enrich Help Center content. Now, with the new editor, this capability has been restricted to Enterprise plans only through the new HTML block component.In practice, this is not an improvement. It's a downgrade for everyone on lower plans. A feature that worked perfectly before has been intentionally removed, and the only way to get it back is to upgrade to a more expensive plan. That feels more like a business decision than a technical one.
Is this really acceptable from a platform that promotes itself as customer experience focused? Taking away core features after years of use might even be seen as unfair practice or a form of forced upselling.
I hope this decision is reconsidered. Removing useful tools is not product improvement. It's the opposite.
0
C.W. Holeman III
This is Really Quite Unacceptable!
I was super excited for this update, until I started using it. The forced HTML code blocks are utterly atrocious. Every single one of my agents has complained about it! It's terrible!
As numerous others have already stated above:
Most of my people don't know HTML! Forcing my agents to learn a new language is just not going to happen. Every single one of them is back to the legacy editor.
I have already seen a sharp decline in the quantity and quality of articles that are being produced since this editor update was released. I can already see the wasted hours.
Whoever was in charge of this design decision needs to take a good long look at how they're making choices. This is a case of one step forward, three steps backward! The ability to add an <hr> is the best part of this update. And that's a pretty sad statement.
We often have to pull content from other sources, such as an old knowledge base that we're migrating into Zendesk, or other files from a wide assortment of places. If anything that we copy and paste into the editor has any kind of styles or unsupported anything in it it now renders the entire page utterly uneditable! The only workaround is to do a paste-as-unformatted which completely strips out all the important formatting like headers, lists, and italics. At which point my agents have to completely rebuild every line of pasted content one by one.
In summary: FIX THIS FAST! You are costing us money!
3
Brooke
+1 to everyone else's negative feedback. I go into the HTML to create admonition / callout boxes, and up until the new editor, I've always been able to quickly modify the copy inside the admonition box by editing it in the WYSIWYG editor.
With this new update, I now have to go into the HTML view every single time I need to see what the original text inside the box is, and to make edits. This is very frustrating and time consuming every time I need to edit the article. Not to mention, if I need to format the text inside the box, I now have to write this out as HTML rather than using the options available in the WYSIWYG editor / keyboard shortcuts.
This feature is a huge step back in making things more efficient for myself and other writers, and I like to consider myself a Zendesk Guide power user. Please allow all text to be visible like it was with the legacy editor while in the WYSIWYG editor.
2
Rob Roberts
I agree with some of the other complaints. It's ridiculous to force ALL the plain text into one of these blocks simply because one word or element has basic HTML applied to it.
For example, I have a series of 10 steps in an article. In step 1, I have an inline icon image that I applied a class to. Because of that, all 10 steps get automatically jammed into an HTML block. And as a result, we can no longer perform basic texts edits on the steps - we now need to go into the HTML editor to update the text, manually add new steps (<li>), etc. This is absurd and opens the door to wasting MORE time that it's saving.
One of our help centers is internal with a large group of non-savvy contributors. We can't expect them to suddenly all know HTML if someone needs to add some very basic code to a single element in a section.
And on top of that, it doesn't even seem necessary. I found that if I unlink an HTML block, it says it will remove certain code but it doesn't. It does, however, remove the HTML block from the editor while leaving everything else intact. So this seemed like a decent workaround at least - the HTML I entered worked just fine and the content appeared as it normally does in the editor. Until I found that the next time I went into the full HTML editor, made any other unrelated change and clicked Apply, those HTML blocks came right back.
Please don't force this feature on us in its current state. It's going to require us to either remove / go without all the simple HTML we've been using up to this point without issue or keep it and resort to much more manual and labor-intensive editing.
3
Summer Polacek
This is a very frustrating feature. It's putting simple html, such as markup-bullet points, into an HTML block. Then I am forced to do simple text edits within the code editor intead of the front end wysiwyg.
I can't seem to find a way to turn it off, or remove it, or make it STOP inserting in my articles.
I was excited about some other features that were added, but this one was so frustrating that I am going to make sure i use the legacy editor. I cannot stand this.
8
David Wexelblat
This isn't correct with the new editor, is it? It should be applicable (for Articles) for any with Guide, right?
0
Molly Exten
HTML blocks are wreaking havoc on my code blocks. I use an LMS to manage translations for Zendesk articles, and every time I import a translation back to Zendesk now, code blocks that use angle brackets get swallowed up by an HTML block.
Really not a fan of this feature.
2
Katarzyna Karpinska
Hi 4594924564378 ,
Thank you for this question. At the moment the HTML blocks are only available in Content blocks, which are an enterprise feature (we have updated the banner at the top of the article). Later this year they'll be available also on lower plans in the article editor.
0
Mario Guisado
Is this available in the Professional Plan? I don't have the ability to add a content block in Professional but the header to this article shows that this is available in all plans?
How do we use this if we can't create content blocks?
0
Patrick Morgan
I tried to edit the HTML code in a content block (only trying to add two special characters not supported by the WYSIWYG editor). After saving, all the content in the content block was converted into the HTML block and is no longer editable in the WYSIWYG editor. Is this expected behavior? I have no control over what content gets put in the HTML block.
1
登录以发表评论。