diff --git a/.agents/skills/frontend-design/LICENSE.txt b/.agents/skills/frontend-design/LICENSE.txt
new file mode 100644
index 0000000..f433b1a
--- /dev/null
+++ b/.agents/skills/frontend-design/LICENSE.txt
@@ -0,0 +1,177 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
diff --git a/.agents/skills/frontend-design/SKILL.md b/.agents/skills/frontend-design/SKILL.md
new file mode 100644
index 0000000..5be498e
--- /dev/null
+++ b/.agents/skills/frontend-design/SKILL.md
@@ -0,0 +1,42 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
diff --git a/content/blog/en/2026-03-15-latex-vs-mathml.md b/content/blog/en/2026-03-15-latex-vs-mathml.md
new file mode 100644
index 0000000..bf78225
--- /dev/null
+++ b/content/blog/en/2026-03-15-latex-vs-mathml.md
@@ -0,0 +1,57 @@
+---
+title: "LaTeX vs MathML: Which Format Should You Use?"
+description: A practical comparison of LaTeX and MathML for students and researchers
+slug: latex-vs-mathml
+date: 2026-03-15
+tags: [guide, formats]
+---
+
+# LaTeX vs MathML: Which Format Should You Use?
+
+TexPixel can export your recognized formulas in both LaTeX and MathML. But which one should you choose? Here's a quick guide.
+
+## LaTeX — The Academic Standard
+
+LaTeX is the most widely used format for typesetting math in academic papers, theses, and textbooks.
+
+**Best for:**
+- Writing papers in Overleaf, TeXmaker, or any LaTeX editor
+- Pasting into Markdown documents (with KaTeX or MathJax rendering)
+- Sharing formulas in forums like Stack Exchange or Reddit
+
+**Example:**
+```latex
+\int_{0}^{\infty} e^{-x^2} dx = \frac{\sqrt{\pi}}{2}
+```
+
+## MathML — The Web Standard
+
+MathML is an XML-based format designed for displaying math in web browsers and screen readers.
+
+**Best for:**
+- Embedding formulas in HTML web pages
+- Accessibility — screen readers can interpret MathML
+- Word documents (DOCX uses MathML internally)
+
+**Example:**
+```xml
+
+```
+
+## Quick Decision Guide
+
+| Scenario | Use |
+|----------|-----|
+| Writing a paper | LaTeX |
+| Homework in Google Docs / Word | MathML (via DOCX export) |
+| Posting on a blog or website | LaTeX (with MathJax) |
+| Accessibility-focused content | MathML |
+| Sharing on social media | Image export |
+
+## The TexPixel Advantage
+
+You don't have to choose upfront. TexPixel recognizes your formula once and lets you export in any format — switch freely between LaTeX, MathML, Markdown, Word, and image.
diff --git a/content/blog/en/2026-03-20-handwriting-tips.md b/content/blog/en/2026-03-20-handwriting-tips.md
new file mode 100644
index 0000000..f2f3f66
--- /dev/null
+++ b/content/blog/en/2026-03-20-handwriting-tips.md
@@ -0,0 +1,45 @@
+---
+title: 5 Tips for Better Handwriting Recognition
+description: Get the most accurate results from TexPixel when scanning handwritten formulas
+slug: handwriting-tips
+date: 2026-03-20
+tags: [tutorial, tips]
+---
+
+# 5 Tips for Better Handwriting Recognition
+
+Getting clean, accurate LaTeX from handwritten math doesn't require perfect penmanship. But a few simple habits can dramatically improve your results.
+
+## 1. Use Dark Ink on Light Paper
+
+High contrast is the single biggest factor in recognition accuracy. A dark pen (black or dark blue) on white or light paper gives TexPixel the clearest signal. Pencil works too, but press firmly.
+
+## 2. Give Symbols Room to Breathe
+
+Cramped formulas are harder for both humans and AI to read. Leave clear gaps between:
+- Fraction bars and the expressions above/below them
+- Subscripts and superscripts and their base symbols
+- Parentheses and the terms they enclose
+
+## 3. Be Deliberate with Similar Characters
+
+Some characters are notoriously ambiguous in handwriting:
+- **1, l, |** — make your ones with a serif or flag
+- **0, O, o** — zeros should be narrower and more oval
+- **x, ×** — use a clear multiplication dot (·) when you mean "times"
+- **u, v** — round bottom vs. pointed bottom
+
+## 4. Keep Your Camera Steady
+
+If you're photographing notes with a phone:
+- Hold the phone parallel to the paper (not at an angle)
+- Make sure the lighting is even — no harsh shadows across the formula
+- Get close enough that the formula fills most of the frame
+
+## 5. One Formula Per Upload
+
+TexPixel works best when each image contains a single formula or a closely related set of expressions. If you have a page full of equations, crop them individually for best results.
+
+---
+
+With these habits, you'll see noticeably better accuracy — often 95%+ even for complex handwritten expressions.
diff --git a/content/blog/zh/2026-03-15-latex-vs-mathml.md b/content/blog/zh/2026-03-15-latex-vs-mathml.md
new file mode 100644
index 0000000..0007ed9
--- /dev/null
+++ b/content/blog/zh/2026-03-15-latex-vs-mathml.md
@@ -0,0 +1,48 @@
+---
+title: "LaTeX 和 MathML:你应该用哪种格式?"
+description: 面向学生和研究人员的 LaTeX 与 MathML 实用对比
+slug: latex-vs-mathml
+date: 2026-03-15
+tags: [指南, 格式]
+---
+
+# LaTeX 和 MathML:你应该用哪种格式?
+
+TexPixel 可以将识别出的公式导出为 LaTeX 和 MathML 两种格式。那么你应该选择哪种?这里有一份快速指南。
+
+## LaTeX — 学术标准
+
+LaTeX 是学术论文、学位论文和教材中排版数学公式最广泛使用的格式。
+
+**适用场景:**
+- 在 Overleaf、TeXmaker 或任何 LaTeX 编辑器中写论文
+- 粘贴到 Markdown 文档中(配合 KaTeX 或 MathJax 渲染)
+- 在 Stack Exchange 或 Reddit 等论坛分享公式
+
+**示例:**
+```latex
+\int_{0}^{\infty} e^{-x^2} dx = \frac{\sqrt{\pi}}{2}
+```
+
+## MathML — Web 标准
+
+MathML 是一种基于 XML 的格式,专为在浏览器和屏幕阅读器中显示数学内容而设计。
+
+**适用场景:**
+- 在 HTML 网页中嵌入公式
+- 无障碍访问 — 屏幕阅读器可以解读 MathML
+- Word 文档(DOCX 内部使用 MathML)
+
+## 快速决策指南
+
+| 场景 | 推荐格式 |
+|------|---------|
+| 写论文 | LaTeX |
+| 在 Google Docs / Word 中做作业 | MathML(通过 DOCX 导出) |
+| 发布博客或网站 | LaTeX(配合 MathJax) |
+| 注重无障碍访问 | MathML |
+| 社交媒体分享 | 图片导出 |
+
+## TexPixel 的优势
+
+你不需要提前选择。TexPixel 识别一次公式后,可以导出为任意格式——在 LaTeX、MathML、Markdown、Word 和图片之间自由切换。
diff --git a/content/blog/zh/2026-03-20-handwriting-tips.md b/content/blog/zh/2026-03-20-handwriting-tips.md
new file mode 100644
index 0000000..a067095
--- /dev/null
+++ b/content/blog/zh/2026-03-20-handwriting-tips.md
@@ -0,0 +1,45 @@
+---
+title: 提升手写公式识别准确率的 5 个技巧
+description: 使用 TexPixel 扫描手写公式时,如何获得最准确的识别结果
+slug: handwriting-tips
+date: 2026-03-20
+tags: [教程, 技巧]
+---
+
+# 提升手写公式识别准确率的 5 个技巧
+
+从手写数学公式获得干净、准确的 LaTeX 并不需要完美的书写。但一些简单的习惯可以显著提升识别结果。
+
+## 1. 使用深色墨水和浅色纸张
+
+高对比度是影响识别准确率的最大因素。在白纸或浅色纸上使用深色笔(黑色或深蓝色)能给 TexPixel 最清晰的信号。铅笔也可以,但要用力书写。
+
+## 2. 给符号留出空间
+
+拥挤的公式无论对人还是 AI 都更难辨认。请在以下位置留出清晰的间隔:
+- 分数线与上下表达式之间
+- 上标、下标与基础符号之间
+- 括号与其包含的项之间
+
+## 3. 注意易混淆字符
+
+一些字符在手写中特别容易混淆:
+- **1, l, |** — 写数字 1 时加上衬线
+- **0, O, o** — 零应更窄更椭圆
+- **x, ×** — 表示"乘"时使用乘号点(·)
+- **u, v** — 圆底 vs 尖底
+
+## 4. 保持拍摄稳定
+
+如果你用手机拍摄笔记:
+- 手机保持与纸面平行(不要倾斜)
+- 确保光线均匀,公式上没有阴影
+- 靠近拍摄,让公式占据画面的大部分
+
+## 5. 每次上传一个公式
+
+TexPixel 在每张图片只包含一个公式或一组紧密相关的表达式时效果最好。如果你有一整页方程,建议逐个裁剪后分别上传。
+
+---
+
+养成这些习惯后,你会发现识别准确率明显提升——即使是复杂的手写表达式也能达到 95% 以上。
diff --git a/content/docs/en/faq.md b/content/docs/en/faq.md
new file mode 100644
index 0000000..0b9a485
--- /dev/null
+++ b/content/docs/en/faq.md
@@ -0,0 +1,62 @@
+---
+title: FAQ
+description: Frequently asked questions about TexPixel
+slug: faq
+date: 2026-03-25
+tags: [reference]
+order: 3
+---
+
+# Frequently Asked Questions
+
+## General
+
+### Is TexPixel free?
+
+Yes! You can use TexPixel for free with up to 3 uploads per day. No sign-up or credit card is required. For unlimited uploads and additional features, check our Pro plan.
+
+### Do I need to create an account?
+
+No. You can start using TexPixel immediately as a guest. Creating an account (free) lets you sync history across devices.
+
+### What languages are supported?
+
+TexPixel recognizes mathematical formulas regardless of the surrounding language. The user interface is available in English and Chinese.
+
+## Recognition
+
+### How accurate is the recognition?
+
+TexPixel achieves 90-98% accuracy depending on image quality and formula complexity. Clean, high-contrast images of typed formulas typically achieve the highest accuracy.
+
+### Can it recognize handwritten formulas?
+
+Yes. TexPixel handles both printed and handwritten formulas. For best results with handwriting, use dark ink on white paper and keep characters well-spaced.
+
+### What about complex multi-line equations?
+
+TexPixel can recognize multi-line equations, equation arrays, and systems of equations. Each line is captured and formatted correctly in the output.
+
+### Does it support matrices and tables?
+
+Yes. Matrices, determinants, and tabular expressions are supported and output as proper LaTeX `\begin{matrix}` or `\begin{pmatrix}` environments.
+
+## Export & Integration
+
+### Can I use the output in Overleaf?
+
+Absolutely. Copy the LaTeX output and paste it directly into your Overleaf project. It works immediately.
+
+### How do I use the output in Word?
+
+Use the DOCX export option. This creates a Word file with properly formatted equations that you can edit normally in Microsoft Word or Google Docs.
+
+## Privacy & Data
+
+### Are my uploaded images stored?
+
+Uploaded images are processed for recognition and temporarily cached. They are automatically deleted after processing. We do not use your images for training.
+
+### Is my data encrypted?
+
+Yes. All data is transmitted over HTTPS. Uploaded files and results are handled securely.
diff --git a/content/docs/en/supported-formats.md b/content/docs/en/supported-formats.md
new file mode 100644
index 0000000..3b98405
--- /dev/null
+++ b/content/docs/en/supported-formats.md
@@ -0,0 +1,50 @@
+---
+title: Supported Formats
+description: Input and output formats supported by TexPixel
+slug: supported-formats
+date: 2026-03-25
+tags: [reference]
+order: 2
+---
+
+# Supported Formats
+
+## Input Formats
+
+TexPixel accepts the following file types for formula recognition:
+
+### Images
+- **JPEG / JPG** — Photos from cameras or phones
+- **PNG** — Screenshots, scanned images, or digital drawings
+
+### Documents
+- **PDF** — Single or multi-page documents. All pages are processed and formulas are extracted from each page.
+
+**File size limit:** 10 MB per file.
+
+**Resolution tips:** For best results, use images at least 300 DPI. Phone photos work well when the formula fills most of the frame.
+
+## Output Formats
+
+After recognition, you can export results in multiple formats:
+
+### Code Formats
+- **LaTeX** — Standard math typesetting syntax, compatible with Overleaf, TeXmaker, and Markdown editors
+- **MathML** — XML-based format for web pages and screen readers
+
+### Document Formats
+- **Markdown** — Ready to paste into Markdown files with inline math notation
+- **Word (DOCX)** — Editable Word document with properly formatted equations
+
+### Image Formats
+- **PNG** — High-resolution rendered formula image
+
+## Format Comparison
+
+| Format | Best For | Editable | Web-Ready |
+|--------|----------|----------|-----------|
+| LaTeX | Papers, Markdown | Yes | With MathJax |
+| MathML | Websites, Accessibility | Yes | Native |
+| Markdown | Notes, Docs | Yes | With renderer |
+| Word | Assignments | Yes | No |
+| PNG | Sharing | No | Yes |
diff --git a/content/docs/zh/faq.md b/content/docs/zh/faq.md
new file mode 100644
index 0000000..17856a8
--- /dev/null
+++ b/content/docs/zh/faq.md
@@ -0,0 +1,62 @@
+---
+title: 常见问题
+description: 关于 TexPixel 的常见问题解答
+slug: faq
+date: 2026-03-25
+tags: [参考]
+order: 3
+---
+
+# 常见问题
+
+## 基本信息
+
+### TexPixel 是免费的吗?
+
+是的!你可以每天免费使用 3 次上传。无需注册或绑定信用卡。如需无限上传和更多功能,请查看我们的专业版。
+
+### 需要创建账号吗?
+
+不需要。你可以立即以访客身份使用 TexPixel。创建免费账号后可以跨设备同步历史记录。
+
+### 支持哪些语言?
+
+TexPixel 可以识别任何语言环境中的数学公式。用户界面支持中文和英文。
+
+## 识别相关
+
+### 识别准确率如何?
+
+根据图片质量和公式复杂度,TexPixel 的准确率在 90-98% 之间。清晰、高对比度的印刷体公式通常能达到最高准确率。
+
+### 能识别手写公式吗?
+
+可以。TexPixel 支持印刷体和手写公式。手写公式建议使用深色墨水在白纸上书写,并保持字符间距适当。
+
+### 支持复杂的多行方程吗?
+
+TexPixel 可以识别多行方程、方程组和方程数组。每一行都会被准确捕获并正确格式化输出。
+
+### 支持矩阵和表格吗?
+
+支持。矩阵、行列式和表格表达式都能识别,并输出为正确的 LaTeX `\begin{matrix}` 或 `\begin{pmatrix}` 环境。
+
+## 导出与集成
+
+### 输出可以在 Overleaf 中使用吗?
+
+当然可以。复制 LaTeX 输出,直接粘贴到你的 Overleaf 项目中即可使用。
+
+### 如何在 Word 中使用?
+
+使用 DOCX 导出选项。这会创建一个包含格式正确的公式的 Word 文件,你可以在 Microsoft Word 或 Google Docs 中正常编辑。
+
+## 隐私与数据
+
+### 上传的图片会被存储吗?
+
+上传的图片仅用于识别处理并临时缓存,处理完成后会自动删除。我们不会使用你的图片进行训练。
+
+### 数据是加密的吗?
+
+是的。所有数据通过 HTTPS 传输。上传的文件和结果都经过安全处理。
diff --git a/content/docs/zh/supported-formats.md b/content/docs/zh/supported-formats.md
new file mode 100644
index 0000000..bd8cc44
--- /dev/null
+++ b/content/docs/zh/supported-formats.md
@@ -0,0 +1,50 @@
+---
+title: 支持的格式
+description: TexPixel 支持的输入和输出格式
+slug: supported-formats
+date: 2026-03-25
+tags: [参考]
+order: 2
+---
+
+# 支持的格式
+
+## 输入格式
+
+TexPixel 接受以下文件类型进行公式识别:
+
+### 图片
+- **JPEG / JPG** — 相机或手机拍摄的照片
+- **PNG** — 截图、扫描图片或数字绘图
+
+### 文档
+- **PDF** — 单页或多页文档。所有页面都会被处理,每一页中的公式都会被提取。
+
+**文件大小限制:** 每个文件最大 10 MB。
+
+**分辨率建议:** 为获得最佳效果,建议使用至少 300 DPI 的图片。手机拍照时让公式占据画面的大部分即可。
+
+## 输出格式
+
+识别完成后,你可以将结果导出为多种格式:
+
+### 代码格式
+- **LaTeX** — 标准数学排版语法,兼容 Overleaf、TeXmaker 和 Markdown 编辑器
+- **MathML** — 基于 XML 的格式,适用于网页和屏幕阅读器
+
+### 文档格式
+- **Markdown** — 可直接粘贴到 Markdown 文件中,包含内联数学符号
+- **Word (DOCX)** — 可编辑的 Word 文档,公式格式完整
+
+### 图片格式
+- **PNG** — 高分辨率渲染的公式图片
+
+## 格式对比
+
+| 格式 | 最适合 | 可编辑 | 网页就绪 |
+|------|--------|--------|---------|
+| LaTeX | 论文、Markdown | 是 | 需 MathJax |
+| MathML | 网站、无障碍 | 是 | 原生支持 |
+| Markdown | 笔记、文档 | 是 | 需渲染器 |
+| Word | 作业 | 是 | 否 |
+| PNG | 分享 | 否 | 是 |
diff --git a/docs/superpowers/plans/2026-03-25-website-restructure.md b/docs/superpowers/plans/2026-03-25-website-restructure.md
new file mode 100644
index 0000000..06ab1f8
--- /dev/null
+++ b/docs/superpowers/plans/2026-03-25-website-restructure.md
@@ -0,0 +1,974 @@
+# Website Restructure Implementation Plan
+
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** Restructure the single-page OCR app into a multi-section marketing website with dedicated workspace, docs, and blog pages.
+
+**Architecture:** SPA with react-router-dom layout routes. MarketingLayout (Navbar + Footer) wraps Home/Docs/Blog. AppLayout wraps the OCR workspace at `/app`. Markdown content compiled at build time via a Vite plugin. SEO handled by react-helmet-async + vite-plugin-prerender.
+
+**Tech Stack:** React 18, react-router-dom, Tailwind CSS, react-helmet-async, vite-plugin-prerender, remark/rehype (existing), gray-matter
+
+---
+
+## File Structure
+
+```
+src/
+├── components/
+│ ├── home/
+│ │ ├── HeroSection.tsx — Hero with OCR demo + CTA
+│ │ ├── FeaturesSection.tsx — Feature cards grid
+│ │ ├── HowItWorksSection.tsx — 3-step flow
+│ │ ├── PricingSection.tsx — Price cards
+│ │ └── ContactSection.tsx — Contact info + form
+│ ├── layout/
+│ │ ├── MarketingNavbar.tsx — Full site nav
+│ │ ├── AppNavbar.tsx — Workspace nav (from Navbar.tsx)
+│ │ ├── Footer.tsx — Site footer
+│ │ ├── MarketingLayout.tsx — MarketingNavbar + Outlet + Footer
+│ │ └── AppLayout.tsx — AppNavbar + Outlet
+│ └── seo/
+│ └── SEOHead.tsx — react-helmet-async wrapper
+├── pages/
+│ ├── HomePage.tsx
+│ ├── WorkspacePage.tsx — migrated from App.tsx
+│ ├── DocsListPage.tsx
+│ ├── DocDetailPage.tsx
+│ ├── BlogListPage.tsx
+│ └── BlogDetailPage.tsx
+├── lib/
+│ └── content.ts — Load markdown manifests
+├── routes/
+│ └── AppRouter.tsx — Updated with layout routes
+content/
+├── docs/
+│ ├── en/getting-started.md
+│ └── zh/getting-started.md
+└── blog/
+ ├── en/2026-03-25-introducing-texpixel.md
+ └── zh/2026-03-25-introducing-texpixel.md
+scripts/
+└── build-content.ts — Compile markdown to JSON
+```
+
+---
+
+### Task 1: Install dependencies and setup
+
+**Files:**
+- Modify: `package.json`
+
+- [ ] **Step 1: Install react-helmet-async and gray-matter**
+
+```bash
+npm install react-helmet-async gray-matter
+```
+
+- [ ] **Step 2: Wrap app with HelmetProvider**
+
+In `src/main.tsx`, add `HelmetProvider` wrapping:
+
+```tsx
+import { HelmetProvider } from 'react-helmet-async';
+
+// Wrap inside StrictMode:
+
{language === 'en' ? doc.description : doc.descriptionZh}
+ + ))} +Content coming soon.
+compiled html
" } +``` + +- [ ] **Step 3: Create content loader utility** + +```tsx +// src/lib/content.ts +import type { Language } from './translations'; + +export interface ContentMeta { + slug: string; + title: string; + description: string; + date: string; + tags: string[]; + order?: number; + cover?: string; +} + +export interface ContentManifest { + en: ContentMeta[]; + zh: ContentMeta[]; +} + +export interface ContentItem { + meta: ContentMeta; + html: string; +} + +const BASE = '/content'; + +export async function loadManifest(type: 'docs' | 'blog'): Promise{c.subtitle}
+{c.subtitle}
{f.subtitle}
+{f.subtitle}
{item.description}
+{item.description}
+ +
{t.marketing.hero.subtitle}
+- {t.sidebar.uploadInstruction} -
-+ {t.sidebar.uploadInstruction} +
+
+ {'\\frac{-b \\pm \\sqrt{b^2 - 4ac}}{2a}'}
+
+
- {'\\frac{-b \\pm \\sqrt{b^2 - 4ac}}{2a}'}
-
{step.description}
+ +{step.description}
{p.subtitle}
+{p.subtitle}