Guide reformats HTML code
Respondido
Publicado 25 de out. de 2017
We have created some nicely formated and very basic HTML pages that we want to incorporate as part of our customer FAQ. Nevertheless, when we try to copy/paste the code, initially it is correctly previewed, but when we click the update button, then it gets re-formated and all the magic goes away. We have already invested some time into this and would like to know if there is any chance of working around this very inconvenient product "feature".
0
25
25 comentários
Nicole Saunders
Hi Lily -
It looks like Brett responded to you in your other post, but you should be able to limit the indexing of a single article by removing the URL in your Google Webmaster's tool as outlined in this article: How do I exclude a Help Center page from being indexed by Google
Check that out and let us know if it works for you.
0
Lily Dodge
I am having a similar problem - I want to add the <meta name="robots" content="noindex"> to just one of my Help Center articles, but that html keeps getting stripped. Help!
0
Nicole Saunders
Hey Niclas -
Thanks for sharing the solution! Glad you got things working. :)
0
Niclas Kårlin
Thanks Dan for reaching out. I got help from Zendesk support with this tip and that works.
What I ended up is to include the actual HTML in my style.css, like this:
.OrangeButton {
color: white;
background-color: #d86633;
cursor: pointer;
border-radius: 32px;
border: 1px solid #d86633;
padding: 8px 16px;
}
.OrangeButton:hover {color: #d86633;background-color: white;}
... and then this in my header.hbs:
<a class="OrangeButton" href="https://www.ndcsolutions.com/partner-portal ">Visit the Partner Portal</a>
...so now I am a css guru!
0
Dan Ross
Hi Niclas,
Did you include the stylesheet
<link rel="stylesheet" href="https://www.w3schools.com/w3css/4/w3.css">
If not, you will need to do this, otherwise the buttons won't be styled and then you may need to specify your own CSS for a .button class in your theme. Can you perhaps include some more info about what your code looks like now and what results you're getting?
0
Niclas Kårlin
Are there any topics about this more than this? It's not so easy to work with "Zendesk HTML" as the documentation on w3 school do not always apply, afaik.
I'm trying to make buttons...
0
Juan Eusse
I understand the technical reason behind the reported issue, and also kinda understand the motivation of having an homogeneous look and feel for the articles by having a unified CSS style.This may work for companies where customization is not a major concern, and where homogeneity is favored.
What I think that is a very bad idea is to limit the options. The idea of having an HTML editor parallel to a WYSIWYG one is to enable people to create their own HTML code, and parsing their input seems counter intuitive to say the least. I am not happy with the approach, as this means that the company now needs to pay two different people, one to create the web page, and another to import it in a way that is compatible with zendesk. I would kindly ask if you are planning to create an option in which the user can instruct the HTML code parser not to cut away ANY stuff from custom HTML code, so that the page is rendered as is when the article is updated.
Thanks for the help,
Juan
0
Trapta Singh
@Paul Toomey,
Please don't get misunderstood, I haven't done anything so nothing is going to break if you make any edits.
Thanks
0
Paul Toomey
thats fine for now - I will just have to keep in mind that any edits I make will break anything you have done.
I am just concerned that your WYSIWYG editor provided in the help centre is anything but that and what we see is pretty much NEVER what we end up getting on the published articles :(
As can be seen from Juan - even if you have people creating actual HTML/CSS and the like to ensure the articles meet customer and corporate expectations/standards - they just don't end up that way online.
Thanks
Paul
0
Trapta Singh
Oh no, I haven't made any changes in the editor itself but I can guide you to do it if you want to.
Thanks
0
Publicação fechada para comentários.