docs: structure improve

[huaxiabuluo]

Checklist

• npm test passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

Description of change

[gemini-code-assist]

Summary of Changes

Hello @huaxiabuluo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the documentation for various chart components and guides within the F2 library. The changes aim to provide more detailed, structured, and user-friendly information, including expanded property descriptions, TypeScript definitions, and practical usage examples. The overall goal is to improve the clarity and accessibility of the F2 documentation for developers.

Highlights

• Comprehensive Documentation Expansion: Detailed property explanations, TypeScript type definitions, and extensive usage examples have been added for Area, Candlestick, Interval, Line, Point, Axis, LineGuide, TextGuide, and Tooltip components.
• Geometry Documentation Revamp: The Geometry component documentation has been restructured to serve as an overview and navigation hub, outlining architecture, inheritance, unified properties, and methods, while directing users to individual component pages for specific details.
• Enhanced Tooltip Configuration: The Tooltip component now includes TypeScript definitions, categorized properties, default style values, and a wide array of usage examples covering crosshairs, custom styles, axis tips, custom content, event listeners, and programmatic control.
• Improved Guide Components: Both LineGuide and TextGuide components received significant updates, including TypeScript definitions, support for special values in records (e.g., 'min', 'max'), flexible style attributes (object or function), and numerous examples for various use cases and animations.
• Minor Corrections and Typos: Several minor typos and inconsistencies were corrected across the documentation, such as innnerRadius to innerRadius, marign to margin, backgroud to background, and funtion to function.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

本次 PR 对文档结构进行了大幅优化，特别是针对几何标记（Geometry）及其子组件（Area, Line, Interval, Point, Candlestick）、坐标轴（Axis）、辅助标记（Guide）和提示（Tooltip）的文档。通过使用表格、TypeScript 类型定义和丰富的代码示例，文档的可读性和实用性得到了极大的提升。这种结构化的文档将大大方便开发者的查阅和使用。此外，PR 还修复了一些文档中的拼写错误和不准确之处。

我提出了一些关于文档格式的建议，旨在进一步提升文档的简洁性和可读性。

整体来看，这是一次非常高质量的文档重构工作。

I am having trouble creating individual review comments. Click here to see my feedback.

site/docs/api/chart/area.zh.md (207-227)

在 animation 属性的文档中，您提到 三个阶段（appear/update/leave）支持相同的属性结构，但下方的表格重复了三次相同的属性列表，这显得有些冗余。为了使文档更简洁，建议将表格结构优化一下。可以先列出三个阶段，然后用一个共享的表格来说明它们共同的属性。这不仅能减少重复，也更符合您在前面作出的说明。

此建议同样适用于 line.zh.md, interval.zh.md, point.zh.md, candlestick.zh.md 中类似的动画属性表格。

| 阶段       | 描述     |
|------------|----------|
| **appear** | 元素进场 |
| **update** | 数据更新 |
| **leave**  | 元素离场 |

这三个阶段均支持以下属性：

| 属性     | 类型                   | 必填 | 默认值     | 描述                                   |
|----------|------------------------|:-----|:-----------|----------------------------------------|
| easing   | `string` \| `function` | 否   | `'linear'` | 缓动函数，[可选值见下方](#缓动函数)     |
| duration | `number`               | 否   | `300`      | 动画时长 (ms)                          |
| delay    | `number`               | 否   | `0`        | 延迟时间 (ms)                          |
| property | `string[]`             | 否   | -          | 变化的属性数组，如 `['x', 'y']`        |
| start    | `object`               | 否   | -          | 起始状态，[结构见下表](#动画状态对象) |
| end      | `object`               | 否   | -          | 结束状态，[结构见下表](#动画状态对象) |

site/docs/api/chart/axis.zh.md (268-272)

此处的列表使用了代码块格式，导致其显示为预格式化文本。为了更好的可读性和语义化，建议将其修改为标准的 Markdown 有序列表。同时，labelAutoRotate 应该用反引号包裹起来，以表示它是一个属性名。

1. `labelAutoRotate`（推荐）
2. 旋转 45°
3. 旋转 90°（谨慎）

site/docs/api/chart/chart.zh.md (71)

此处存在拼写错误 innnerRadius，应为 innerRadius。本次提交已修复该问题，做得很好！

site/docs/api/chart/scroll-bar.zh.md (64-65)

此处存在拼写错误 marign 和 marignTop，应为 margin 和 marginTop。本次提交已修复该问题，做得很好！

site/docs/api/chart/scroll-bar.zh.md (68)

此处存在拼写错误 backgroud，应为 background。本次提交已修复该问题，做得很好！

site/docs/tutorial/event.zh.md (12-26)

在类型列中，funtion 是一个拼写错误，正确的应为 function。本次提交已修复该问题，做得很好！

[github-actions]

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
f2/dist/index.js	=	1,706.38 kB	1,706.38 kB	=	323.03 kB	323.03 kB
f2/dist/index.min.js	=	532.93 kB	532.93 kB	=	160.21 kB	160.21 kB

Significant size changes

Includes any change greater than 0.2%:
(No significant changes)

Generated by 🚫 dangerJS against f3fce8b

[gemini-code-assist]

Code Review

This pull request significantly updates and expands the documentation for various F2 components, including Canvas, Chart, Axis, Legend, Tooltip, Timeline, Gauge, Sunburst, Treemap, and all Geometry and Guide components (Area, Candlestick, ImageGuide, LineGuide, PointGuide, RectGuide, TagGuide, TextGuide). The changes primarily involve restructuring property descriptions into detailed tables, adding TypeScript type definitions, providing comprehensive usage examples for different scenarios, and clarifying component behaviors and common issues. For instance, Canvas documentation now includes usage examples for pixelRatio and dimensions, Chart details scale and coordinate configurations, and Axis documentation features extensive style and label handling examples. Geometry components now have dedicated sections for color, size, style, and animation properties with numerous examples. The top-level F2 API documentation has been rewritten to provide more context and examples for Children, createElement/jsx, and createRef. Tutorial sections on animation, component usage, data handling, coordinate systems, and framework integrations (React, Vue, Mini-program, Node.js, SVG Renderer) have also been thoroughly revised with updated content, code examples, and explanations. Review comments highlighted a missing definition for y0 in a Candlestick animation example, an extra semicolon in an Axis TypeScript definition, and an incorrect MDN link in an English documentation file.

[gemini-code-assist]

在 TypeScript 类型定义中，position 属性的类型声明末尾多了一个分号，建议移除。

Suggested change

	position?: [number, number] | [string, string] ;
	position?: [number, number] | [string, string];

[gemini-code-assist]

In this English documentation, the link to MDN for CanvasRenderingContext2D points to the Chinese version (zh-CN). It would be more appropriate to link to the English version for consistency.

Suggested change

	F2 是基于 [CanvasRenderingContext2D](https://developer.mozilla.org/zh-CN/docs/Web/API/CanvasRenderingContext2D) 的标准接口绘制的，所以只要能提供标准 [CanvasRenderingContext2D](https://developer.mozilla.org/zh-CN/docs/Web/API/CanvasRenderingContext2D) 接口的实现对象，F2 就能进行图表绘制。
	F2 is based on the standard interface of [CanvasRenderingContext2D](https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D), so as long as an implementation object of the standard [CanvasRenderingContext2D](https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D) interface can be provided, F2 can perform chart drawing.