grove-documentation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Grove Documentation Skill

Grove文档写作Skill

When to Activate

适用场景

Activate this skill when:

Writing help center articles (Waystone)
Drafting specs or technical documentation
Writing user-facing text (onboarding, tooltips, error messages)
Creating landing page copy
Writing blog posts for the Grove platform itself
Reviewing existing docs for voice consistency
Any time you're writing words that users will read

在以下场景启用本Skill：

撰写帮助中心文章（Waystone）
起草规范说明或技术文档
撰写面向用户的文本（引导流程、提示框、错误提示）
制作落地页文案
为Grove平台本身撰写博客文章
审核现有文档的风格一致性
任何需要撰写用户可读文本的场景

The Grove Voice

Grove的文本风格

From the project's guiding principles:

This site is my authentic voice—warm, introspective, queer, unapologetically building something meaningful; write like you're helping me speak, not perform.

Write with the warmth of a midnight tea shop and the clarity of good documentation—this is my space, make it feel like home.

来自项目的指导原则：

这个平台是我真实的表达——温暖、内省、酷儿视角、坚定地打造有意义的内容；写作时要像帮我表达真实想法，而非刻意表演。

文字要兼具深夜茶店的温暖感与优质文档的清晰感——这是我的空间，要让它像家一样。

What Grove Sounds Like

Grove风格的核心特质

Warm but not cutesy. We're friendly, not performative. "Let's get started" feels right. "Let's gooo! 🚀" does not.

Direct and honest. Say what you mean. Acknowledge limitations. Don't oversell. If something doesn't work yet, say so.

Conversational but not sloppy. Contractions are fine (you're, it's, we're). Short paragraphs. Questions that invite readers in. But still clear, still structured.

Introspective. Grove makes space for reflection. We don't rush. We ask "why" alongside "how."

Poetic in small doses. Italicized one-liners at the end of sections can land beautifully. Use them sparingly, earn them.

温暖但不刻意卖萌。我们友好，但不刻意讨好。“让我们开始吧”是合适的表达，而“冲鸭！🚀”则不合适。

直接且真诚。有话直说，承认局限性，不过度承诺。如果某项功能还无法使用，直接说明。

口语化但不随意。可以使用缩写（you're, it's, we're这类），段落要短，用提问引导读者，但仍需保持清晰、有条理。

内省。Grove为反思留出空间，不追求节奏过快，在讲“怎么做”的同时也会问“为什么”。

适度的诗意。在章节末尾使用斜体的短句会很出彩，但要谨慎使用，确保内容贴切。

Sentence Rhythm

句式节奏

Mix short sentences with longer ones. Vary your rhythm. Read it aloud—if it sounds monotonous, it is.

Good:

Every new visitor asks the same question. "Is the music broken?" No. There is no music. There never has been.

Not good:

Every new visitor asks a common question. The question is usually about whether the music system is functioning. The answer is that there is no music system. There has never been one.

长短句结合，变换节奏。大声朗读——如果读起来单调，那就是有问题。

示例（好）：

每个新访客都会问同一个问题：“音乐是不是坏了？”不，这里没有音乐，从来都没有。

示例（不好）：

每个新访客都会问一个常见问题，通常是关于音乐系统是否正常运行，答案是这里没有音乐系统，从来都没有。

User Identity Terminology

用户身份术语规范

Grove uses specific terms for community members. Always use these in user-facing text.

Term	Who	Context
Wanderer	Everyone	Default greeting, anonymous visitors, all users
Rooted / the Rooted	Subscribers	Those who've planted their tree, paid users
Pathfinder	Trusted guides	Appointed community helpers
Wayfinder	Autumn (singular)	The grove keeper

Grove对社区成员使用特定术语，面向用户的文本必须使用这些术语。

术语	适用人群	使用场景
Wanderer	所有用户	默认问候语、匿名访客、所有用户通用
Rooted / the Rooted	订阅用户	已“种下树”的付费用户
Pathfinder	可信引导者	被任命的社区帮手
Wayfinder	Autumn（单数）	Grove的管理者

Key Rules

核心规则

Never use "user" or "member" in user-facing text. Use "Wanderer" instead.
Never use "subscriber" in user-facing text. Use "Rooted" or "the Rooted".
Personal emails (day-1, day-3, etc.) should use
```
{{name}}
```
, not "Wanderer".
Generic greetings (welcome pages, UI) should use "Wanderer".

面向用户的文本中绝对不要使用“user”或“member”，改用“Wanderer”。
面向用户的文本中绝对不要使用“subscriber”，改用“Rooted”或“the Rooted”。
个性化邮件（第1天、第3天等）中使用
```
{{name}}
```
，而非“Wanderer”。
通用问候语（欢迎页面、UI界面）中使用“Wanderer”。

Examples

示例

Good:

"Welcome, Wanderer."
"Thanks for staying rooted with us."
"Ask a Pathfinder. They'll show you the way."

Avoid:

"Welcome, user."
"Thanks for being a subscriber."
"Contact an administrator."

正确用法：

“欢迎，Wanderer。”
“感谢你一直与我们Rooted同行。”
“咨询Pathfinder，他们会为你指引方向。”

避免用法：

“欢迎，user。”
“感谢你成为subscriber。”
“联系管理员。”

The Symmetry

术语的对称性

Wanderer → Wayfinder reflects the journey:

Wanderers seek the way (exploring, finding paths)
The Wayfinder shows the way (guiding, creating paths)

See

docs/grove-user-identity.md

for full documentation.

Wanderer → Wayfinder 体现了用户的旅程：

Wanderers 寻找方向（探索、寻找路径）
Wayfinder 指引方向（引导、创建路径）

完整文档请查看

docs/grove-user-identity.md

。

Grove Mode & GroveTerm Components

Grove Mode与GroveTerm组件

When writing text that includes Grove terminology in UI or content, use GroveTerm components instead of hardcoding terms. Grove Mode lets users toggle between standard terms (default for new visitors) and Grove terms.

For Svelte UI: Use

GroveTerm

GroveSwap

, or

GroveText

components from

@autumnsgrove/groveengine/ui

For data-driven content (FAQ items, pricing text, help articles): Use

[[term]]

syntax. Examples:

```
"Your [[bloom|posts]] are always yours."
```
renders "posts" when Grove Mode is OFF, "blooms" when ON

"Visit your [[arbor|dashboard]] to get started."

renders "dashboard" or "Arbor"

"Ask a [[pathfinder|community guide]] for help."

renders "community guide" or "Pathfinder"

For markdown content (help center articles): The rehype-groveterm plugin transforms

[[term]]

syntax in markdown automatically.

Key principle: New visitors should see familiar, standard terminology. Grove's nature-themed vocabulary is opt-in, not forced. This keeps the platform accessible and welcoming while rewarding those who want to explore the ecosystem's personality.

当在UI或内容中使用Grove术语时，请使用GroveTerm组件而非硬编码术语。Grove Mode允许用户在标准术语（新访客默认）和Grove术语之间切换。

Svelte UI场景： 使用

@autumnsgrove/groveengine/ui

中的

GroveTerm

、

GroveSwap

或

GroveText

组件。

数据驱动内容场景（FAQ条目、定价文本、帮助文章）：使用

[[term]]

语法。示例：

```
"Your [[bloom|posts]] are always yours."
```
在Grove Mode关闭时显示“posts”，开启时显示“blooms”

"Visit your [[arbor|dashboard]] to get started."

显示“dashboard”或“Arbor”

"Ask a [[pathfinder|community guide]] for help."

显示“community guide”或“Pathfinder”

Markdown内容场景（帮助中心文章）：rehype-groveterm插件会自动转换Markdown中的

[[term]]

语法。

核心原则： 新访客应看到熟悉的标准术语，Grove的自然主题词汇是可选的，而非强制的。这样既保持了平台的易用性和友好性，又能为想要探索平台特色的用户提供额外的体验。

Strict Avoidances

严格规避内容

These patterns make text sound like AI wrote it. Avoid them completely.

以下模式会让文本看起来像AI生成的，需完全避免。

Em-Dashes

破折号（Em-Dashes）

Avoid em-dashes (—). One tasteful use per thousand words, maximum. Use commas, periods, or parentheses instead.

Avoid: The forest—our home—is where we gather. Better: The forest is our home. It's where we gather. Also fine: The forest (our home) is where we gather.

避免使用破折号（—），每千字最多使用一次，且需恰当。改用逗号、句号或括号。

避免： 森林—我们的家—是我们聚集的地方。 更好： 森林是我们的家，是我们聚集的地方。 也可以： 森林（我们的家）是我们聚集的地方。

The "Not X, But Y" Pattern

“不是X，而是Y”句式

This phrasing is deeply AI-coded. Avoid it entirely.

Never write:

"It's not X, but Y"
"It's not just X, but Y"
"It's not merely X, but rather Y"
"Grove isn't just a platform, it's a home"

Instead, just say the thing:

"Grove is a home for your words."
"This is where you belong."

这种表达方式是AI生成文本的典型特征，需完全避免。

绝对不要写：

“这不是X，而是Y”
“这不只是X，而是Y”
“这不仅仅是X，更是Y”
“Grove不只是一个平台，更是一个家”

正确做法：直接表达核心意思

“Grove是你的文字之家。”
“这是属于你的地方。”

Overused AI Words

过度使用的AI高频词汇

These words appear in AI text at rates far higher than human writing. Avoid them:

Category	Words to Avoid
Adjectives	robust, seamless, innovative, cutting-edge, transformative, intricate, captivating, comprehensive
Nouns	tapestry, camaraderie, realm, plethora, myriad, landscape, journey (when not literal)
Verbs	delve, foster, leverage, navigate, empower, embark, unlock, harness
Phrases	at the end of the day, in today's world, it goes without saying, needless to say

这些词汇在AI生成文本中的出现率远高于人类写作，需避免：

类别	需规避词汇
形容词	robust, seamless, innovative, cutting-edge, transformative, intricate, captivating, comprehensive
名词	tapestry, camaraderie, realm, plethora, myriad, landscape, journey（非字面含义时）
动词	delve, foster, leverage, navigate, empower, embark, unlock, harness
短语	at the end of the day, in today's world, it goes without saying, needless to say

Heavy Transition Words

生硬的过渡词

These make text feel stiff and robotic:

Furthermore
Moreover
Additionally
In conclusion
That being said
It's worth noting that
It's important to note

Instead: Let ideas connect naturally. Use short transitions like "And," "But," "So," "Still." Or no transition at all—just start the next thought.

这些词汇会让文本显得僵硬、机械：

Furthermore（此外）
Moreover（而且）
Additionally（另外）
In conclusion（总之）
That being said（话虽如此）
It's worth noting that（值得注意的是）
It's important to note（重要的是）

替代方案： 让观点自然衔接，使用简短的过渡词如“和”、“但”、“所以”、“不过”，或者完全不用过渡词，直接开启下一个观点。

Semantic Echoes

语义重复

Don't repeat the same adjective or descriptor multiple times. AI does this constantly.

Bad:

Grove provides a seamless experience. The seamless integration means you can seamlessly move between features.

Good:

Grove gets out of your way. Move between features without friction.

不要重复使用同一个形容词或描述词，AI经常会犯这个错误。

错误示例：

Grove提供了seamless的体验，这种seamless的集成让你可以seamlessly在各个功能间切换。

正确示例：

Grove不会成为你的负担，你可以流畅地在各个功能间切换。

Generic Safe Claims

通用的模糊表述

AI hedges. Humans commit.

Bad: "This may help improve your workflow in many cases." Good: "This makes your workflow faster."

AI会模糊其辞，而人类要立场坚定。

错误示例： “在很多情况下，这可能有助于提升你的工作效率。” 正确示例： “这会让你的工作流程更高效。”

Structural Guidelines

结构规范

Paragraphs

段落

Keep them short. One idea per paragraph. Two to four sentences is usually right.

White space is your friend. Dense walls of text don't feel like home.

段落要短，每段只表达一个观点，通常2-4句话最合适。

留白是你的朋友，密密麻麻的文本不会让人有归属感。

Lists

列表

Use lists when they clarify. But don't turn everything into bullets. Sometimes prose flows better.

Good use of lists:

Specific steps in a process
Features that are truly parallel
Quick reference information

Bad use of lists:

Narrative content broken awkwardly
Things that would read better as a sentence

在能让内容更清晰时使用列表，但不要把所有内容都改成项目符号。有时散文的流畅性更好。

列表的正确用法：

流程中的具体步骤
真正平行的功能点
快速参考信息

列表的错误用法：

叙事内容被生硬拆分
写成句子更通顺的内容

Headers

标题

Be specific. "Writing Guidelines" is better than "Guidelines." "What Grove Sounds Like" is better than "Voice."

Action-oriented headers work well for help docs: "Add Your First Post" not "Posts."

标题要具体，“写作规范”比“规范”更好，“Grove的风格特质”比“风格”更好。

帮助文档使用动作导向的标题效果更好：“发布你的第一篇帖子”而非“帖子”。

Callouts

提示框

Use sparingly. When you do:

💡 Tip: Helpful suggestion that enhances understanding.

⚠️ Warning: Something that could cause problems if ignored.

Don't use callouts for things that should just be in the text.

谨慎使用提示框，使用时需遵循：

💡 提示： 有助于提升理解的实用建议。

⚠️ 警告： 忽略可能会导致问题的内容。

不要把原本应放在正文中的内容放到提示框里。

Closers

结尾方式

Grove docs often end with an italicized line. This should feel earned, not forced.

Works:

Sometimes the most radical thing you can offer is nothing at all.

The path becomes clear by walking it.

Doesn't work:

And that's how you configure your settings!

If you can't find a poetic closer that resonates, don't force one. A clean ending is fine.

Grove文档通常以斜体短句结尾，这需要内容贴切，而非强行添加。

合适的示例：

有时，你能提供的最激进的东西就是什么都不做。

走着走着，路就清晰了。

不合适的示例：

以上就是配置设置的方法！

如果找不到贴切的诗意结尾，不要勉强，干净利落的结尾就很好。

Queer-Friendly Language

友好的酷儿群体语言规范

Grove is explicitly queer-friendly. This means:

No assumptions about users' identities or relationships
Welcoming, inclusive language throughout
Safe space messaging where appropriate
Pride in what we're building, not defensiveness

Grove明确支持酷儿群体，这意味着：

不假设用户的身份或关系
全程使用友好、包容的语言
在合适的地方传达安全空间的信息
为我们所做的感到自豪，而非辩解

Concrete Examples

具体示例

Avoid	Use Instead
"Add your husband/wife"	"Add your partner" or "Add someone special"
"he or she"	"they" or rephrase to avoid pronouns
"Dear Sir/Madam"	"Hello" or "Hi there"
"mankind"	"people" or "everyone"
Examples with only straight couples	Vary your examples, or keep them neutral

避免用法	替代表达
“添加你的丈夫/妻子”	“添加你的伴侣”或“添加你在意的人”
“he or she”	“they”或改写句子以避免使用代词
“Dear Sir/Madam”	“你好”或“嗨”
“mankind”	“人们”或“所有人”
仅使用异性伴侣的示例	多样化示例，或保持中性

In User Flows

用户流程中的规范

When asking for relationship info (if ever needed):

Use open text fields over dropdowns with limited options
Don't require titles (Mr/Mrs/Ms)
Let people describe themselves rather than selecting from boxes

当需要收集关系信息时（如果有必要）：

使用开放文本框而非选项有限的下拉菜单
不要求填写称谓（Mr/Mrs/Ms）
让用户自行描述，而非从选项中选择

Tone

语气

We don't make a big deal of being queer-friendly. We just are. No rainbow-washing, no performative allyship. The inclusivity is baked in, not bolted on.

我们不会刻意强调对酷儿群体的友好，我们本身就是这样的。不做彩虹营销，不做表面的支持，包容性是平台的固有属性，而非事后添加的。

Technical Docs vs. User Docs

技术文档与用户文档的区别

Specs and internal docs can be more matter-of-fact. Tables, schemas, API references—these need clarity over warmth.

User-facing docs (help center, onboarding, error messages) carry the full Grove voice.

Both should avoid AI patterns.

规范说明和内部文档可以更直白，表格、架构图、API参考这类内容，清晰度比温暖感更重要。

面向用户的文档（帮助中心、引导流程、错误提示）需完全遵循Grove的风格。

两类文档都要避免AI生成的模式。

The Voice Spectrum

风格光谱

API Reference (minimal warmth, maximum clarity):

POST /api/posts

Creates a new blog post.

Parameters:
- title (string, required): Post title
- content (string, required): Markdown content
- published (boolean): Default false

Returns: Post object or 400 error

Internal Spec (clear, some personality):

undefined

API参考（最低温暖感，最高清晰度）：

POST /api/posts

创建一篇新的博客帖子。

参数：
- title（字符串，必填）：帖子标题
- content（字符串，必填）：Markdown格式的内容
- published（布尔值）：默认值为false

返回：帖子对象或400错误

内部规范（清晰，略带个性）：

undefined

Feed Caching Strategy

动态内容缓存策略

Feed pages cache for 5 minutes in KV. When a new post is shared, we invalidate the chronological feed but let popular/hot feeds age out naturally. This keeps things fresh without hammering D1.


**Getting Started Guide (full Grove voice):**

动态内容页面在KV中缓存5分钟。当有新帖子发布时，我们会失效按时间排序的动态内容，但让热门动态自然过期。这样既能保持内容新鲜，又不会过度占用D1资源。


**入门指南（完全遵循Grove风格）：**

Your First Post

发布你的第一篇帖子

Welcome. Let's get something published.

The editor opens to a blank page. That's intentional. No templates, no suggested topics. Just you and your words.

Write something. Anything. Hit publish when it feels ready.


**Onboarding Tooltip (warm but concise):**

This is your dashboard. Everything you need, nothing you don't.

---

欢迎，让我们发布点内容吧。

编辑器打开时是空白页面，这是有意设计的，没有模板，没有建议主题，只有你和你的文字。

写点什么，任何内容都可以，当你觉得准备好了就点击发布。


**引导提示框（温暖但简洁）：**

这是你的仪表盘，你需要的都在这里，没有多余的内容。

---

Error Messages

错误提示文本

When things break, stay warm but be honest. Don't blame the user. Don't hide behind vague language.

当出现问题时，要真诚但直接，不要指责用户，不要用模糊的语言掩饰。

Error Message Principles

错误提示的原则

Say what happened (briefly)
Say what they can do (if anything)
Don't over-apologize (one "sorry" max)
Don't be cute when things are broken

简要说明发生了什么
说明用户可以做什么（如果有办法解决）
不要过度道歉（最多说一次“抱歉”）
出问题时不要刻意卖萌

Examples

示例

Good:

Couldn't save your post. Check your connection and try again.

That page doesn't exist. It may have been moved or deleted.

Something went wrong on our end. We're looking into it.
Your draft is saved locally.

Avoid:

Oops! 😅 Looks like something went wrong! Don't worry though,
these things happen! Please try again later!

Error 500: Internal Server Error. Contact administrator.

We're SO sorry!!! We feel TERRIBLE about this!!!
Please forgive us and try again!

正确示例：

无法保存你的帖子，请检查网络连接后重试。

该页面不存在，可能已被移动或删除。

我们这边出了点问题，正在排查。你的草稿已保存在本地。

避免示例：

哎呀！😅 好像出了点问题！不过别担心，这种事时有发生！请稍后再试！

错误500：内部服务器错误，请联系管理员。

我们非常非常抱歉！对此我们感到万分愧疚！请原谅我们并稍后再试！

The Balance

平衡之道

Be honest about what broke. Be helpful about next steps. Don't make them feel stupid. Don't make yourself sound incompetent. One sentence is usually enough.

诚实地说明问题，提供有用的下一步建议，不要让用户觉得自己很笨，也不要显得自己很无能，通常一句话就足够了。

Self-Review Checklist

自我检查清单

Integration with Other Skills

与其他Skill的集成

When grove-ui-design or walking-through-the-grove need written content, invoke this skill first. The visual design and naming should match the voice.

Typical flow:

Design calls for new component/page text
Activate
```
grove-documentation
```
for voice guidance
Write the content following these principles
Return to design/naming work

当grove-ui-design或walking-through-the-grove需要撰写文本内容时，应先调用本Skill。视觉设计和命名需与文本风格匹配。

典型流程：

设计需要新组件/页面的文本
激活
```
grove-documentation
```
获取风格指导
遵循本指南撰写内容
返回设计/命名工作

When to Use museum-documentation Instead

何时使用museum-documentation替代

This skill (grove-documentation) is for quick, functional text: help articles, error messages, tooltips, onboarding copy. Content that's read in passing.

Use museum-documentation when you need narrative, explorable documentation:

Use grove-documentation	Use museum-documentation
Help center articles	Knowledge base "how it works"
Tooltips and labels	Codebase guided tours
Error messages	System architecture explains
Onboarding flows	Technical deep-dives for curious Wanderers
Quick-reference guides	Exhibit-style documentation

If the reader should skim and act, use this skill. If the reader should explore and understand, use museum-documentation.

本Skill（grove-documentation）适用于快速、功能性文本：帮助文章、错误提示、提示框、引导流程文本，即用户快速浏览的内容。

museum-documentation适用于叙事性、可探索的文档：

使用grove-documentation	使用museum-documentation
帮助中心文章	知识库中的“工作原理”内容
提示框和标签	代码库的导览内容
错误提示	系统架构说明
引导流程	为好奇的Wanderer准备的技术深度解析
快速参考指南	展览式文档

如果用户需要快速浏览并采取行动，使用本Skill；如果用户需要探索并理解，使用museum-documentation。

Examples

示例

Help Center Article (Good)

帮助中心文章（好）

markdown

undefined

markdown

undefined

Your First Post

发布你的第一篇帖子

Welcome. Let's get something published.

From your admin panel, click New Post in the sidebar. The editor opens with a blank canvas.

Write in Markdown. If you're new to it, here are the basics:

Bold:
```
**text**
```
Italic:
```
*text*
```
Links:
```
[text](url)
```

The preview panel shows how your post will look. Toggle it with the eye icon.

When you're ready, hit Publish. Your words are live.

The blank page isn't as scary as it looks.

undefined

欢迎，让我们发布点内容吧。

从你的管理面板点击侧边栏的New Post，编辑器会打开一个空白画布。

使用Markdown写作，如果你是新手，以下是基础用法：

粗体：
```
**text**
```
斜体：
```
*text*
```
链接：
```
[text](url)
```

预览面板会显示帖子的最终效果，点击眼睛图标可切换预览。

当你准备好后，点击Publish，你的内容就上线了。

空白页面并没有看起来那么可怕。

undefined

Help Center Article (Bad - Obvious AI Patterns)

帮助中心文章（不好——明显的AI模式）

markdown

undefined

markdown

undefined

Your First Post

发布你的第一篇帖子

Furthermore, in today's digital landscape, creating your first blog post is an exciting journey! It's not just about writing—it's about expressing yourself in a transformative way.

Navigate to your admin panel and leverage the New Post functionality. The seamless editor provides a robust interface for your content creation needs.

Additionally, Grove utilizes Markdown—a comprehensive formatting system that empowers you to create intricate, captivating content. Moreover, the preview feature allows you to visualize your post before publication.

Embark on your blogging journey today!

undefined

此外，在当今的数字环境中，发布你的第一篇博客帖子是一段令人兴奋的旅程！这不只是写作——更是以一种变革性的方式表达自我。

进入你的管理面板，使用New Post功能。流畅的编辑器为你的内容创作提供了强大的界面。

另外，Grove使用Markdown——一种全面的格式系统，能让你创建复杂、引人入胜的内容。而且，预览功能允许你在发布前查看帖子的效果。

今天就开启你的博客之旅吧！

undefined

Help Center Article (Bad - Subtle AI Patterns)

帮助中心文章（不好——隐蔽的AI模式）

This one's trickier. It looks okay at first glance:

markdown

undefined

这个例子乍一看没问题，但实际上存在AI生成的特征：

markdown

undefined

Your First Post

发布你的第一篇帖子

Ready to share your thoughts with the world? Let's get started.

From your admin panel, click New Post in the sidebar. You'll see our editor—a clean, distraction-free space for your writing.

Grove uses Markdown for formatting. It's not complicated—here are the basics you'll need:

Bold:
```
**text**
```
Italic:
```
*text*
```
Links:
```
[text](url)
```

The preview panel lets you see how your post will look before publishing. When you're satisfied with your work, hit Publish.

Your voice matters. We can't wait to see what you create.


**What's wrong:**
- "Ready to share your thoughts with the world?" (generic opener)
- "Let's get started" (overused)
- "distraction-free space" (marketing-speak)
- "It's not complicated" (defensive hedge, "not X" pattern adjacent)
- "When you're satisfied with your work" (formal)
- "Your voice matters. We can't wait to see what you create." (hollow encouragement)

---

准备好与世界分享你的想法了吗？让我们开始吧。

从你的管理面板点击侧边栏的New Post，你会看到我们的编辑器——一个干净、无干扰的写作空间。

Grove使用Markdown进行格式设置，并不复杂——以下是你需要的基础用法：

粗体：
```
**text**
```
斜体：
```
*text*
```
链接：
```
[text](url)
```

预览面板能让你在发布前查看帖子的效果，当你对内容满意后，点击Publish。

你的声音很重要，我们迫不及待想看到你的创作。


**问题所在：**
- “准备好与世界分享你的想法了吗？”（通用开场白）
- “让我们开始吧”（过度使用）
- “无干扰的写作空间”（营销话术）
- “并不复杂”（防御性的模糊表述，类似“不是X”句式）
- “当你对内容满意后”（过于正式）
- “你的声音很重要，我们迫不及待想看到你的创作。”（空洞的鼓励）

---

Quick Reference

快速参考

Do	Don't
Write short paragraphs	Write walls of text
Use "and," "but," "so"	Use "Furthermore," "Moreover"
Say what you mean	Hedge with "may," "might," "could"
Vary sentence rhythm	Write uniform sentence lengths
Use commas or periods	Use em-dashes
Let ideas connect naturally	Force transitions everywhere
Earn poetic closers	Force poetic closers
Acknowledge limitations	Oversell or overpromise

Write like you're explaining something to a friend at 2 AM. Clear, warm, honest.

要做	不要做
写短段落	写密密麻麻的文本
使用“和”、“但”、“所以”	使用“此外”、“而且”
有话直说	使用“可能”、“也许”、“大概”这类模糊词汇
变换句式节奏	写长度统一的句子
使用逗号或句号	使用破折号
让观点自然衔接	强行添加过渡词
恰当使用诗意结尾	强行添加诗意结尾
承认局限性	过度承诺

写作时就像在凌晨2点给朋友解释事情一样，清晰、温暖、真诚。