Jump to content

Tim Munyon

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tim Munyon

  • Rank
    Newbie
  1. Tim Munyon

    No access to CSS

    We created the CSS we wanted, and sent it to the "owner" of the knowledge base and governing CSS file. The silence was deafening. The provider did not want to change the "out-of-the-box" code for any reason. The internal stylesheet solution is also not available to us, because the <head> tag is not one of the tags allowed. (If we try to create a <head> tag with internal stylesheet information, the system deletes it when we publish the knowledge article.) Bottom line: There are some users of HTML that have no control over the css. Deprecating useful tags and telling users to put the information in the CSS is not going to work for everyone.
  2. Tim Munyon

    No access to CSS

    I agree with justsomeguy, but we have run into one brick wall after another trying anything we can think of to exercise control over the knowledge base articles. All the third party has to say is, "It will cost $[number] for the enhancement," and the request is off the table. You all know how many budget dollars are typically available to enhance the authoring tool for knowledge articles, right? (It's usually last priority.)
  3. Tim Munyon

    No access to CSS

    It seems that as time passes, more and more HTML tags are deprecated with the note: "The [???] attribute of <???> is not supported in HTML5. Use CSS instead." The problem with that approach is that there organizations that create and maintain Knowledge articles or wiki sites, where the tool and tool output is owned and managed by a third party. I work as a writer at an international company, creating and updating knowledge base articles all the time. My company is in a contract arrangement with a third party who provides the CRM software, the CRM database, and the knowledge base tool. We have asked to make modifications to the CSS, but the third party company will not permit it, because the CSS governs more things than just the knowledge base articles. I realize situations like our may not be the "norm," but there must be others experiencing the same thing. Every time W3C deprecates another HTML tag and says "Use CSS instead," people whose output is controlled by a third party are left out in the cold. What do you expect writers to do in situations like ours?
×