-> "📊 市场数据快照"
- Then four boxes with labels: "24h Change", "7d Change", "Fear & Greed", "Sentiment"
- Values: "+0.00%", "+0.00%", "34 Fear", "🔴 slightly bearish"
We need to translate the labels and the sentiment text. Also "Fear" in the Fear & Greed index is usually kept as "恐惧" but we can translate. The value "34 Fear" -> "34 恐惧" but we need to keep the number. We'll translate "Fear" to "恐惧" and "slightly bearish" to "略微看跌". Also the emojis stay.
We'll preserve the style attributes exactly.
Fourth part: Heading: "Why order books could thin" -> "为什么订单簿可能变薄"
Text: "For crypto traders, the immediate risk isn't the wind — it's connectivity. Power outages and internet interruptions can knock market makers and retail traders offline in affected regions. That reduces participation, thins order books, and widens bid-ask spreads. On major exchanges like Binance and OKX, a sudden drop in depth can turn a routine move into a sharp wick. The storm's peak is when liquidity gaps are most likely to appear."
Translate: "对于加密货币交易者而言，直接风险不是风——而是连接性。停电和互联网中断可能使受影响地区的做市商和散户交易者离线。这会减少参与，使订单簿变薄，并扩大买卖价差。在币安和OKX等主要交易所，深度突然下降可能将常规走势变成急剧的影线。风暴高峰期最可能出现流动性缺口。"
We used "币安" for Binance, "OKX" is fine. "sharp wick" is a candlestick wick, we can say "尖锐的影线" or "长影线". We'll use "急剧的影线".
Fifth part: Heading: "Mining hardware and energy" -> "挖矿硬件与能源"
Text: "There's also a supply chain angle that most coverage will miss. Bitmain and MicroBT, the two biggest mining rig makers, have production and logistics hubs in southern China, including Shenzhen. If Typhoon Dolphin delays shipping, new hardware could be held up for weeks. That would tighten supply and potentially slow hash rate growth over the next one to three months. Separately, the storm could disrupt LNG imports or coal transport in the region, nudging global energy prices higher. That would raise electricity costs for miners in the U.S., Kazakhstan, and elsewhere, squeezing margins if they persist."
Translate: "还有一个大多数报道会忽略的供应链角度。比特大陆和MicroBT这两家最大的矿机生产商在中国南方设有生产和物流枢纽，包括深圳。如果台风‘海豚’延误运输，新硬件可能会被推迟数周。这将收紧供应，并可能在未来一到三个月内减缓算力增长。另外，风暴可能扰乱该地区的液化天然气进口或煤炭运输，推高全球能源价格。这将提高美国、哈萨克斯坦等地矿工的电力成本，如果持续下去，将挤压利润率。"
We used "比特大陆" for Bitmain, "MicroBT" stays as is. "LNG" we translate as "液化天然气". "hash rate" as "算力". "margins" as "利润率".
Sixth part: Heading: "A sentiment excuse" -> "情绪借口"
Text: "The crypto market is already in a cautious mood, with the Fear & Greed index stuck in "fear" territory. A headline like this — even with no direct crypto link — can be an excuse for profit-taking or risk-off positioning. Traders have seen it before: a macro-negative news item during a low-confidence period triggers a dip that has nothing to do with fundamentals. The storm doesn't change the crypto thesis, but it could add noise to a short-term chart."
Translate: "加密货币市场已经处于谨慎情绪中，恐惧与贪婪指数停留在‘恐惧’区域。这样的头条新闻——即使没有直接的加密货币关联——也可能成为获利了结或避险定位的借口。交易者以前见过这种情况：在信心低迷时期，宏观负面新闻引发与基本面无关的下跌。风暴不会改变加密货币的基本面论点，但可能给短期图表增加噪音。"
We used "恐惧与贪婪指数" for Fear & Greed index. "profit-taking" as "获利了结", "risk-off" as "避险". "dip" as "下跌".
Last paragraph: "For now, the best move is to watch order book depth on Asian exchanges during the storm's peak. If spreads widen suddenly, that's a signal — and for market makers, an opportunity. For everyone else, it's a reminder that external shocks can still ripple through the market, even when the direct connection is nil."
Translate: "目前，最好的做法是在风暴高峰期观察亚洲交易所的订单簿深度。如果价差突然扩大，那是一个信号——对做市商而言，也是一个机会。对其他所有人来说，这提醒我们，即使直接关联为零，外部冲击仍可能波及市场。"
Now we need to combine all into the HTML structure. We'll preserve the original HTML tags and attributes, but replace the text content with Chinese translations. We must be careful to keep the style attributes exactly as they are, and the class names.
We'll produce the content as a string with the tags.
Also meta description: "China's red alert for Typhoon Dolphin cancels over 1,000 flights. Crypto traders watch for thinner order books and wider spreads as connectivity drops."
Translate: "中国对台风‘海豚’发布红色警报，取消超千个航班。加密货币交易者关注订单簿变薄和价差扩大，因为连接性下降。"
We'll put that in meta.description.
Now we need to output JSON. We'll ensure it's valid JSON.
Let's write the JSON with the translated title, content (the full article HTML), and meta.
We'll use double quotes for JSON strings, escape any inner double quotes
