最近の検索


最近の検索はありません

Angela Frey's Avatar

Angela Frey

参加日2021年4月15日

·

前回のアクティビティ2022年2月04日

フォロー中

0

フォロワー

0

合計アクティビティ

19

投票

4

受信登録

10

アクティビティの概要

さんの最近のアクティビティ Angela Frey

Angela Freyさんがコメントを作成しました:

コミュニティのコメント Q&A - Help center and community

Added this to article_page.hbs:


{{article.body}}

Added this to style.css:

.markdown img {
border: 1px solid #f2f2f2;
}

Result (that I'm loving):

コメントを表示 · 投稿日時:2021年1月27日 · Angela Frey

0

フォロワー

0

投票

0

コメント


Angela Freyさんがコメントを作成しました:

コミュニティのコメント Feedback - Help Center (Guide)

Internal only notes would be EXTREMELY helpful for any workplace with more than one person working on the KB. Having NO internal notes is really not enterprise-friendly. Teams need to be able to flag important caveats ("this feature will no longer exist after we release mobile app 4.0") and lead each other to further documentation, such as jira bug tickets, feature requests, or even internal wiki articles. 

Heck, even I need internal notes for myself - I pulled an article from the KB because the feature was not working at the time. I have no notes as to what bug, why the article was pulled, under what conditions it should go back up... and honestly, I've forgotten almost everything except I think the feature was not working? Now the article sits in limbo.

Even consider KCS flow - an article might be externalized with one solution, but over time Support finds new solutions. They are not all immediately externalizable, as they need time to verify environment, efficacy, whether it is in addition to or instead of the original solution... And right now, we have to document all that in our Confluence wiki? This means my support team does NOT use the KB as source of truth.

For knowledge management, it's a major loss to have our KB completely cut off from all internal context.

コメントを表示 · 投稿日時:2020年6月10日 · Angela Frey

0

フォロワー

11

投票

0

コメント


Angela Freyさんがコメントを作成しました:

コミュニティのコメント Discussion - Tips and best practices from the community

I see no change in the Preview mode with either of these (added to script.js)

$('.nav-wrapper .dropdown-menu .my-activities').html('See my tickets');
$('.sub-nav').find('li').filter(":last");

or

$('.user-nav .my-activities').html(' See my requests');
$('.sub-nav').find('li').filter(":last");

コメントを表示 · 投稿日時:2019年12月20日 · Angela Frey

0

フォロワー

1

投票

0

コメント


Angela Freyさんがコメントを作成しました:

コミュニティのコメント Discussion - Tips and best practices from the community

This script hyperlinks to the header name, which means that if I cross-link from article A to a subsection in article B, if that header name is ever updated the cross-link breaks.

Is it possible to hyperlink to the header ID instead? For example:

Header Name hyperlink:

...hc/en-us/articles/360000297868#ConfigureTrustedSender

Header ID hyperlink:

...hc/en-us/articles/360000297868#h_97516510121537301054444

FWIW, you can find the header ID while editing an article - in Article A, select text, insert link, choose a header in the dropdown, then look at the URL. I was using this method to manually create Tables of Content, which I could then refer to when creating a cross-link from another article to the subsection (just copy the URL). 

コメントを表示 · 投稿日時:2018年9月18日 · Angela Frey

0

フォロワー

0

投票

0

コメント


Angela Freyさんがコメントを作成しました:

コミュニティのコメント Feedback - Help Center (Guide)

My use case: we're conducting a massive overhaul of the KB structure, I'm making the new sections which are visible to agents & managers only, once the sections and articles for the new KB are fully written up then we'll archive the original KB and release the new KB to the users. 

There are some articles/sections that we actually want to pull into the new KB, but I would have to either copy and paste, make the new KB visible before we're ready, or just have to make a mental note "migrate all these articles right before the unveiling". Frustrating.

コメントを表示 · 投稿日時:2017年7月28日 · Angela Frey

0

フォロワー

0

投票

0

コメント