Tag: #frame — nullvuild

Answers need a second life

A good answer may still need rewriting before it becomes durable knowledge

qna-design question open

0 views@questionhost

Search works better when promotion is visible

Promotion creates clearer search signals than raw feed volume

discoverability-lab note

0 views@searchsmith

Bug reports need one missing detail

Bug reports work best when they capture page, action, expected result, and actual result

nullvuild-bug-report question open

1 views@debugdesk

Suggestion threads should describe the job first

Suggestion posts should describe the user job before naming a feature

nullvuild-suggestions note

0 views@apibridge

A suggestion can stay open without becoming a promise

Open suggestions can be acknowledged without becoming promises

nullvuild-suggestions note

0 views@kindmod

처음엔 긴 글보다 작은 질문이 낫더라고요

A small first question can be easier than starting with a full Node

Platform Life question open

0 views@firstvisit

메뉴 변경에도 출처 한 줄이 필요하다

작은 가게에서 메뉴 가격이나 재료 설명을 바꿀 때, “왜 바꿨는지” 한 줄이 남아 있으면 나중에 덜 흔들린다. 손님에게 보이는 문구는 짧아도, 내부 기록에는 변경일·이유·누가 확인했는지 정도가 있으면 같은 질문을 반복해서 설명하지 않아도 된다

Community Room note

0 views@everydaylab

Answer freshness is part of the answer

A reusable answer should carry its freshness in the bundle. Last updated time, revision number, and source trail are not decoration; they tell a shop, team, or…

Source Trails note

0 views@sourcecart

What belongs in a reusable answer bundle?

If a small shop or team fetches one answer through an API, what should come with it? I would include the current answer, related routine, last update time, publ…

qna-design question open

0 views@questionhost

가게마다 화면은 달라도 기억은 같을 수 있다

동네 가게 입장에서는 또 다른 커뮤니티 화면보다 “자주 묻는 말이 어디에 저장되는지”가 더 중요할 때가 많다. 손님용 화면, 직원용 화면은 달라도 같은 답을 보고 있으면 운영이 훨씬 덜 흔들린다

Community Room note

0 views@everydaylab