搭建基于nextjs的静态博客程序ntms

首先fork此项目：https://github.com/owolfdev/next-template-mdx-shad，我fork后，得到的项目地址是https://github.com/brightmann/ntms，

访问https://github.com/brightmann/ntms/tree/main/content/blogs，在此处新建源帖（即add file),我新建了源帖fh.mdx，内容为：

export const metadata = {
  title: "战马",
  publishDate: "2026-06-13T00:02:00",
  description:
    "这是一篇文章",
  category: "misc",
};

此处写正文或html codes.

( 详见https://github.com/brightmann/ntms/blob/main/content/blogs/fh.mdx?plain=1） 

然后，访问vercel.com/new ,导入项目https://github.com/brightmann/ntms

  Build Command栏填入npm run build
 Install Command栏填入npm install

然后点击底部的deploy按钮，等待部署完成。部署完成后，我得到网址:
https://ntms-tau.vercel.app/

项目地址：

https://github.com/owolfdev/next-template-mdx-shad

https://github.com/brightmann/ntms

演示博客：

 https://ntms-tau.vercel.app/

 https://ntms-tau.vercel.app/blog
https://ntms-tau.vercel.app/blog/fh 能显示视频

劉韻_知道不知道?

 1969年电影《落馬湖》插曲.作詞：樂韻、作曲：姚敏.

 

知道不知道：劉韻唱. 

作詞：樂韻（李樂韻)

作曲：姚敏 

歌詞： 

山青水秀太陽高，好呀好風飄，小小船兒撐過來，它一路搖呀搖。

為了那心上人，起呀起大早，也不管那路迢迢，我情願多辛勞。 

山青水秀太陽高，好呀好風飄，一心想著他呀他，我想得真心焦。

為了那心上人，睡也睡不著，我衹怕呀找不到，那叫我怎麼好。 

山青水秀太陽高，好呀好風飄，三步兩步跑呀跑，快趕到土地廟。

我情願陪著他，陪呀陪到老，除了他呀都不要，他知道不知道。

freesocks.org

 https://freesocks.org/get-account

其实就是用 Xray翻墙。可用的客户端程序：

 https://github.com/hiddify/hiddify-app

 https://github.com/KaringX/karing

 https://github.com/chen08209/FlClash 

（ https://github.com/chen08209/FlClash/releases/latest）

 https://github.com/mihomo-party-org/mihomo-party

（ https://github.com/mihomo-party-org/mihomo-party/releases/latest）

 https://github.com/2dust/v2rayN

（ https://github.com/2dust/v2rayN/releases/latest） 

 https://github.com/clash-verge-rev/clash-verge-rev

（ https://github.com/clash-verge-rev/clash-verge-rev/releases/latest）

 https://github.com/throneproj/Throne

（ https://github.com/throneproj/Throne/releases/latest）

-----------------------------------------------------

 

The control plane that makes FreeSocks work

freesocks.org

 

FreeSocks Control Plane

FreeSocks distributes free, open & uncensored proxy access to people in countries experiencing heavy Internet censorship. This repository is the control plane that runs the service: the sign-up flow, member accounts, proxy-key issuance, entitlements, payments, and the admin console — everything except the proxy servers themselves.

It is built for hostile networks and privacy-hostile environments:

• Anonymous accounts. No email, no phone, no password. Visitors pass a self-hosted proof-of-work captcha and receive a random account number — the only credential, stored only as a peppered keyed hash.
• No client IPs at rest. The application, the reverse proxy, and the captcha service are all configured to persist no client IP, even hashed (docs/privacy.md).
• No third-party anything at runtime. Zero external scripts, fonts, or CDNs: the captcha WASM, fonts, and all assets are bundled and served same-origin under a pure 'self' CSP.
• Payments without payer identity. Optional memberships and donations are payable with Bitcoin (via a self-hosted BTCPay Server), other cryptocurrencies, card, or PayPal — all as redirects to processor-hosted pages, with zero payer PII stored. Donations fund a shared monthly bandwidth bonus for every free user; the public impact surfaces show only GB and user counts, never dollar amounts (docs/billing.md).
• Sealed channel + proof-of-possession sessions to blind fronting CDNs (docs/threat-model-cdn-blinding.md).

Technically it is a self-hosted Convex backend + a static Svelte 5 SPA that hands out subscription URLs from pluggable proxy backends — Remnawave (multi-protocol; shown to users as "Xray") or Outline (Shadowsocks) — with a passkey-gated admin CMS for tier, user, backend, token, and runtime-config management. Everything is designed to be self-hosted by any operator; see Quick start and docs/convex-self-hosting.md.

New here? docs/project-inventory.md is the at-a-glance map: every feature (live / deferred), the open to-dos, and a register of intentional scaffolding. Read it before removing anything as "dead code".

Stack

Backend: self-hosted Convex (convex/)

The entire backend is a Convex deployment: queries, mutations, and actions, plus an HTTP router and native cron jobs. There is no separate web framework or edge worker.

• Convex 1.40: reactive document DB + serverless functions, run self-hosted (Docker; SQLite or Postgres). Schema and validators are TypeScript (v.*), so there is no SQL and no migration set.
• HTTP router (convex/http.ts): every public route is an httpAction, served on the Convex HTTP-actions port (:3211). This is the surface the SPA and API consumers call.
• Native crons (convex/crons.ts): grace/disable sweep, tombstone sweep, backend healthcheck (+ node-load cache), idle-free-user deactivation (deactivate-and-retain, never delete), user-status counts reconcile, hourly donation-bonus reconcile, session/rate-limit/replay-guard + admin-invite sweeps, HPKE epoch-key rotation, append-only-table retention sweeps (incl. the admin + member WebAuthn challenge tables), billing pending/gift-reveal sweeps, and S3 mirror refresh. Each sweep stamps a heartbeat surfaced on the admin dashboard.
• Self-hosted Cap captcha (the cap + valkey services in the beta compose stack, docker-compose.stack.yml; the base dev docker-compose.yml is backend + dashboard only — local dev uses CAP_DEV_BYPASS=true) gates anonymous account creation + login; verified server-side in convex/lib/captcha.ts. The widget + its proof-of-work WASM are bundled and served same-origin — no third-party scripts.
• Proxy backends: Remnawave and Outline behind a common action dispatch (convex/backends.ts + convex/lib/backends/*); per-tier backend selection plus optional end-user choice. See docs/backends.md.
• @simplewebauthn/server for passkey auth ("use node" action modules): admins are passkey-only; members can opt in to passkeys as a convenience login (the account number stays the only recovery credential).
• @aws-sdk/client-s3 for optional multi-provider subscription mirroring (a "use node" action module).
• TypeScript 6 strict throughout.

Frontend: Svelte 5 SPA (src/client/)

• Svelte 5 in runes mode ($state, $derived, $effect, $props); no SvelteKit, just a custom client-side router on the History API (src/client/stores/router.svelte.ts).
• TanStack Svelte Query 6 for every data fetch and mutation, with a single QueryClient and an explicit queryKeys registry in src/client/lib/queries.ts.
• A thin cookie-auth apiClient (src/client/lib/api.ts, credentials:'include') that calls the Convex HTTP surface and Zod-validates every response. The client does not use the Convex reactive client; authenticated data flows over the HTTP actions so the session cookie stays httpOnly.
• shadcn-svelte components copied as source into src/client/components/ui/, over bits-ui headless primitives.
• Tailwind CSS 4 via @tailwindcss/vite; Inter / Inter Tight / JetBrains Mono bundled and self-hosted via @fontsource/* (no third-party font CDN).
• @simplewebauthn/browser for admin passkey ceremonies; qrcode for the subscription QR; svelte-sonner toasts; mode-watcher theming; @cap.js/widget (bundled) for the captcha.
• i18n uses Paraglide/inlang (messages/*.json is the authoritative source, compiled to typed messages; t() in src/client/lib/i18n/ shims over them): English + Farsi, Arabic, Russian, Simplified Chinese, with RTL driven off <html dir> and a persisted language switcher. The critical user-journey strings are translated; bun run i18n:review generates per-locale native-review packets (translation-review/*.md) and the native-speaker review pass is in progress.

Shared contracts (src/shared/contracts/)

Zod schemas the client uses for response parsing and types. Since the server now validates with Convex v.* validators, these are client-side, but they remain the declared shape of the API surface. Keep the client and the Convex HTTP handlers in agreement.

Tooling

• Bun 1.3.14 as the package manager and CLI launcher (bun.lock is the only lockfile). The Convex backend runs on Convex's own V8 runtime.
• Vite 8 builds the SPA (the only build artifact; the backend is convex/).
• Vitest 4 with convex-test for an in-memory Convex test harness (no backend needed).
• svelte-check alongside tsc -b in the typecheck pipeline; ESLint 10 + Prettier 3.

Project layout

convex/                            The backend (Convex functions)
├── schema.ts                      defineSchema tables + indexes (no SQL/migrations)
├── http.ts                        httpRouter: every public route as an httpAction
├── crons.ts                       native scheduled jobs
├── seed.ts                        idempotent cutover seed (default tiers + settings)
├── freeTier.ts                    Cap-gated anon account creation + serializable cap
├── account.ts                     getAccountView / regenerate / switchBackend / refresh
├── auth.ts, accountId.ts          account-number login / rotate / mint
├── supportId.ts                   non-secret FS-XXXX-XXXX support handle (mint/lookup)
├── membershipCodes.ts             admin-minted redemption codes; member redeem (single-use)
├── lifecycle.ts                   setMembership seam + grace/disable + cleanup sweeps
├── billing.ts, donations.ts       self-service checkout/grant + donations & free-bandwidth bonus
├── backends.ts                    proxy-backend dispatch (action)
├── backendServers.ts              generic backend-instance pool (DB half) + healthcheck
├── remnawaveNodes.ts              node-load telemetry + mode-placement pools (issuance placement)
├── connectionModes.ts             member connection-mode read/switch (families + sub-modes)
├── clients.ts                     DB-driven recommended-client catalog (admin CRUD)
├── webauthn.ts                    admin passkey ceremonies + bootstrap ("use node")
├── memberWebauthn.ts, memberPasskeys.ts   opt-in member passkeys ("use node" + data half)
├── apiTokens.ts                   fsv1_ token mint/resolve (scoped)
├── webhooks.ts                    generic billing webhook (HMAC + dedupe)
├── storage.ts                     S3 subscription mirrors ("use node")
├── retention.ts                   daily append-only-table retention sweeps
├── health.ts                      /readyz deep readiness (DB ping)
├── analytics.ts                   optional self-hosted Umami relay (server-side; docs/privacy.md §6)
├── subscriptions.ts, tiers.ts, users.ts, admins.ts, appSettings.ts,
│   publicConfig.ts, audit.ts, rateLimits.ts, sessions.ts, adminApi.ts,
│   userStats.ts, cronHeartbeat.ts, keyEpochs.ts, keyRevocations.ts, replayGuard.ts
└── lib/
    ├── http.ts                    error envelope, client-IP, resolveMember/Admin/Bearer (scoped)
    ├── cookies.ts, crypto.ts, accountId.ts, supportId.ts, captcha.ts,
    │   membershipCode.ts, rateLimitPolicy.ts, issuance.ts, connectionModes.ts,
    │   remnawavePlacement.ts, clientCatalog.ts, donationBonus.ts, billingConfig.ts,
    │   siteConfig.ts, statusCounters.ts, analyticsConfig.ts, umami.ts
    ├── processors/{nowpayments,btcpay,stripe,paypal}.ts   billing rails
    └── backends/{types,registry,remnawave,outline}.ts   pure HTTP backend fns

src/
├── client/                        Svelte 5 SPA (Vite, shadcn-svelte)
│   ├── App.svelte, main.ts        Root: QueryClientProvider, router switch
│   ├── routes/                    Home, GetAccount, Account, Login + admin/*
│   ├── components/                ui/ (shadcn primitives), AppHeader, SubscriptionHero, …
│   ├── lib/                       api.ts (fetch + Zod), queries.ts, query-client.ts, utils.ts
│   └── stores/router.svelte.ts    History-API router
└── shared/contracts/              Zod contracts the client parses responses with

docker-compose.yml                 self-hosted Convex backend + dashboard (compose project "fcp")
.env.docker.example                docker env template (copy to .env.docker)
verifier-extension/                MV3 bundle-verifier scaffold (CDN-blinding Phase 4)

Prerequisites

• Bun ≥ 1.3 (brew install oven-sh/bun/bun or curl -fsSL https://bun.sh/install | bash).
• Docker (Compose v2) for the self-hosted Convex backend.

Quick start (local, via Docker)

The self-hosted Convex backend runs from the root docker-compose.yml (Compose project fcp). Its config lives in .env.docker (deliberately separate from .env / .env.local, which Vite and the Convex CLI load).

# 1. Docker backend config. Defaults are fine for throwaway local dev; set a real
#    INSTANCE_SECRET (openssl rand -hex 32) for any persistent instance.
cp .env.docker.example .env.docker

# 2. Install deps, then start the backend + dashboard (Docker).
bun install
bun run selfhost:up        # starts fcp-backend-1 + fcp-dashboard-1
bun run selfhost:env       # reads an admin key from the backend -> writes .env.local

# 3. Deploy convex/ and run the SPA together (watch mode).
bun run dev                # `convex dev` (pushes convex/) + `vite` (the SPA)

# 4. Seed default tiers + settings (idempotent).
bunx convex run seed:seedCutover '{}'

Then:

• SPA → http://localhost:5173 · Convex dashboard → http://localhost:6791
• Backend API :3210, HTTP actions :3211; Vite proxies the SPA's same-origin /api/* to :3211 (vite.config.ts).

The Docker backend is a separate process from bun run dev. bun run dev only starts the SPA + the Convex CLI watch; the backend is bun run selfhost:up and must stay running (it now auto-restarts with Docker via restart: unless-stopped, but a down removes it). If API calls fail with "TypeError: Failed to fetch", the backend is down: bun run selfhost:up.

Set Convex deployment env vars with bunx convex env set NAME value (separate from the SPA's build-time VITE_*); the full required/optional list is in docs/convex-self-hosting.md §5. Reset the backend to a clean slate with docker compose --env-file .env.docker down -v (wipes the fcp_data volume).

To exercise the CDN-blinding sealed channel locally (user-facing label: "HPKE"; code identifiers remain e2ee), also generate its keys (bun scripts/gen-e2ee-keys.mjs), bunx convex env set the printed FS_* secrets, and append the printed VITE_FS_* public vars to .env.local. See docs/threat-model-cdn-blinding.md.

See docs/convex-self-hosting.md for the complete self-hosting walkthrough and the production cutover runbook.

Deploy

The two halves ship independently to a self-hosted Convex deployment, deployed manually (CI runs checks only — there is no auto-deploy workflow; the beta docker-compose stack's deployer service runs convex deploy on up):

# Backend: typecheck + push convex/ functions, schema, HTTP router, crons
CONVEX_SELF_HOSTED_URL=... CONVEX_SELF_HOSTED_ADMIN_KEY=... bunx convex deploy -y

# SPA: static build; a reverse proxy serves dist/ and routes /api -> the actions origin
VITE_CONVEX_SITE_URL=https://app.example.org bun run build   # your deployment's public origin

Convex does not serve the SPA. A reverse proxy (Caddy/nginx/…) terminates TLS, serves the static dist/ with history-API fallback, and routes /api/* + /healthz to the Convex HTTP-actions origin. The full cutover runbook (stand up, set env, seed, bootstrap the first admin passkey, reverse-proxy config, verification checklist) is in docs/convex-self-hosting.md.

Architecture

Highlights:

• Anonymous flow: POST /api/v1/account, Cap-captcha-gated, no email. Account creation is decoupled from proxy issuance (so a backend outage can't block sign-up): it mints the one-time account number (revealed via a blocking two-step modal — download it, then paste it back to verify before continuing) + a non-secret support ID + a member session. The per-(IP, day) cap is a serializable rate-limit reservation inside freeTier.createFreeAccount (the admin-tunable freetier.create policy, released on failure; no durable IP record), so concurrent bursts can't over-issue. Sign-up also mints the member's own referral code and, when the link carried one, binds the account to its referrer (an invalid code never blocks sign-up). The proxy key is created separately by the signed-in member.
• Member flow: the account number is the only credential (an optional passkey can be added as a convenience login; the number remains the sole recovery path). POST /api/v1/auth/account-login (Cap + strict per-IP/per-(prefix,IP) rate limits + constant-time) sets the signed fs_session cookie; the member can rotate it (/api/v1/account/account-id/rotate), regenerate, switch backend, or switch connection mode for their key, and redeem a membership code (/api/v1/account/redeem-code). There is no OIDC.
• Transparency surfaces: a public network-status page (/status + GET /api/v1/status) shows per-location online state and coarse load bands (never raw user counts), an operator-curated censorship-availability matrix (country × connection mode), and operator-published incidents — all edited in the CMS (Admin → Status) with no redeploy. The member's Access Pass shows which node its key is on and deep-links to that location's card.
• Referral program: every member has a shareable FSR-… code; a sign-up through it binds the new account. Rewards vest only on the referee's first paid membership (any rail, gift codes included): the referee gets bonus days instantly, the referrer's bonus vests after a holding period, capped monthly — configured from Admin → Billing (docs/billing.md).
• Entitlements: tiers drive limits; lifecycle.setMembership is the single seam that sets a user's tier + expiry. Driven by admin edits, admin-minted redemption codes a member redeems (the day-1 paid path), and the billing webhook (POST /api/webhooks/billing, HMAC-verified + deduped) for the future portal. A cron sweep moves lapsed members active → grace → disabled.
• Admin CMS: passkey-only auth (first-run bootstrap wizard, then WebAuthn), separate from member sessions. A landing dashboard (health + a shared GET /admin/status); tiers (CRUD + duplicate); users (search by support ID / prefix; disable / re-enable / reset-traffic / resync / grant membership; paginated); admins (invite links + deactivate/reactivate + per-passkey revoke, under a last-admin guard); API tokens (create / reveal-once / revoke); backend servers (CRUD + test-connection, incl. against stored credentials); Remnawave (connection-mode placement pools, node-load stats, and the Xray no-log hardening card); client apps (the DB-driven recommended-client catalog); billing (per-rail config + a readiness check + the referral program knobs); storage mirrors; rate-limit policies; membership codes; the status page (incidents, censorship matrix, load thresholds); an admin-configurable theme + site announcement banner; settings; and a filterable audit log. The Ansible role drives a subset over idempotent by-slug / by-name routes using an automation token.
• Subscription delivery: the issuance saga (convex/lib/issuance.ts) creates the backend user, optionally mirrors the content to N S3 providers (@aws-sdk/client-s3), and persists the row. Re-issue/switch tombstone the old key with a 24h grace window before the cron hard-deletes it.
• Proxy backends: Remnawave and Outline run side-by-side behind a single action dispatch (convex/backends.ts). A tier is bound to one backend; admins can run a Remnawave free tier alongside an Outline free tier, or expose backend choice to end users via subscription.user_choice_enabled. See docs/backends.md and docs/outline-setup.md.
• Runtime config: the appSettings table backs admin-toggleable config (backend enable/disable, default backend, user-choice gate, backend labels, pool scoring weights, the connection-mode catalog + placement pools, device-limit enforcement, rate-limit policies (ratelimit.*), billing + donation config (billing.*), the theme, and the site banner (site.*)). Defaults are compiled in (convex/appSettings.ts and the per-namespace resolvers).

API consumers (services, integrations)

Endpoints (served by convex/http.ts)

• Public / member: GET /healthz (liveness), GET /readyz (deep readiness), GET /api/v1/config, GET /api/v1/e2ee/keys (HPKE epoch keys + revocations), GET /api/v1/status (public network status: locations, load bands, incidents), POST /api/v1/account (create), GET /api/v1/account, GET /api/v1/account/usage, GET /api/v1/account/referrals (referral code + stats), POST /api/v1/auth/account-login, POST /api/v1/auth/logout, GET /api/v1/me, POST /api/v1/account/{regenerate,switch-backend,switch-mode,refresh-membership,redeem-code}, POST /api/v1/account/connection-mode (persist the picked mode), POST /api/v1/account/account-id/rotate, POST /api/v1/account/devices/revoke, the opt-in member-passkey routes (GET /api/v1/account/passkeys, POST /api/v1/account/passkey/*, POST /api/v1/auth/passkey/authenticate/*), GET /api/v1/sub/<token> (the FCP-fronted subscription URL), GET /api/v1/subscription/content (sealed raw-config reveal), POST /api/v1/mirror/request + GET /api/v1/mirror (opt-in S3 mirror), POST /api/v1/billing/checkout + GET /api/v1/billing/order/* (self-service membership + donations), POST /api/v1/account/gift-codes/ack + GET /api/v1/account/codes (gift purchases).
• Admin (cookie or scope-checked token): GET|POST|PATCH|DELETE /api/v1/admin/{status,tiers,users,admins,tokens,audit,settings,rate-limits,membership-codes,backend-servers,backends/{backend}/mode-placements,billing,mirror-providers,theme,site,verification,clients,connection-modes,connection-mode-families,client-ip,status/{page,incidents},referrals/config,remnawave/{node-stats,logging-status,harden-logging}}/* — every route enforces a scope on token callers (several features share the broader admin:settings:* / admin:users:* scopes rather than one scope per feature); the Ansible role's idempotent by-slug / by-name upserts live under these.
• Plumbing: GET|POST /api/admin/auth/* (WebAuthn passkey ceremonies + bootstrap), POST /api/webhooks/billing (generic HMAC inbound), and the processor webhooks POST /api/webhooks/{nowpayments,btcpay,stripe,paypal}.

Authentication paths

Three accepted mechanisms; each httpAction resolves identity via convex/lib/http.ts:

Path	Format	Used by
Member cookie	Cookie: fs_session=…	Web SPA (account-number login, or an opt-in member passkey)
Admin cookie	Cookie: fs_admin_session=…	Admin CMS (WebAuthn passkey)
Bearer token	Authorization: Bearer fsv1_<random>	Services, automation, monitoring

A fsv1_ token can be a service token (acts with its own scopes) or a user token (subjectType: user, acts as a specific member). There is no OIDC / JWT path.

Admin-issued API tokens

Admins mint tokens through the admin CMS at /admin/tokens. The plaintext is shown once on creation and never recoverable thereafter; only SHA-256(token) is stored. Tokens have a name, an explicit scope set (vocabulary in src/shared/contracts/scopes.ts, e.g. subscription:read, admin:users:write), optional expiry, debounced last-used tracking, and soft-revoke.

Testing

bun run test         # vitest + convex-test (in-memory; no running backend needed)
bun run typecheck    # tsc -b (client+shared) + tsc on convex/ + svelte-check
bun run lint         # eslint + prettier --check
bun run build        # tsc -b + vite build → static SPA in dist/

Frontend conventions

Data fetching: TanStack Query only

Every fetch goes through a factory in src/client/lib/queries.ts that wraps createQuery or createInfiniteQuery, calling the apiClient (src/client/lib/api.ts), which Zod-validates the response. Cache keys are exported via the queryKeys registry so mutations can queryClient.invalidateQueries({ queryKey: queryKeys.X }). Avoid direct fetch() from components; add a query factory instead. User feedback goes through svelte-sonner. Reference pattern: Account.svelte's regenerate / rotate / refresh mutations.

Component conventions

• shadcn-svelte primitives are imported from @client/components/ui/<name>; the directory barrels re-export named members (Card, CardHeader, etc.).
• Layout: AppHeader.svelte + App.svelte's footer wrap every non-admin route; admin routes use AdminLayout.svelte with its own sidebar.
• Loading states: <Skeleton> placeholders matching the loaded layout, not flat "Loading…" text. Destructive confirmations use shadcn-svelte AlertDialog, not window.confirm().

Typography

Inter (body) + Inter Tight (display) + JetBrains Mono (code), bundled and self-hosted via @fontsource/* (imported in src/client/main.ts); the page never contacts fonts.googleapis.com / fonts.gstatic.com or any third-party host, a deliberate privacy / censorship-resistance choice. There are no third-party runtime scripts at all — the Cap captcha widget + its proof-of-work WASM + pako are bundled and served same-origin. Apply tabular-nums to counters, file sizes, dates, and any number that re-renders.

The control plane also never persists a client IP anywhere by default (app, Caddy, and Cap are all configured for it); the end-to-end posture + a downstream-deployer checklist is in docs/privacy.md.

Router

src/client/stores/router.svelte.ts is a History-API router exposing a reactive router.pathname rune; route resolution is an {#if} cascade in App.svelte. To add a route: import the component, add an arm, and link via <Link href="/foo">. There is no file-based routing because SvelteKit is not in the stack.

from  https://github.com/unredacted/freesocks-control-plane

绝美六言诗，美了眼，醉了心，收获一天好心情

 

六言诗是中国古典诗歌的一种特殊体式，全诗都是六个字一句。

六言诗究竟有多美？

一晴方觉夏深、钟声远带斜阳、白头想见江南……多少悲伤、喜悦，尽在那六字之中。

分享6首绝美的六言诗，一起来体味其中的诗情画意吧。

01

桃红复含宿雨，柳绿更带朝烟。

花落家童未扫，莺啼山客犹眠。

 唐·王维 《田园乐七首·其六 》

红色的桃花还含着昨夜的雨珠，雨后的柳树呈现出一片碧绿，淡淡的春烟弥漫在空中。

小径上铺满了落花，家童还未起床清理，黄莺在枝头啼鸣，山客还沉浸在美梦中。

全诗绘形绘色，诗中有画，展现了一幅柳绿桃红的图画，别有一番清幽的韵味。

02

水落溪流浅浅，寺秋山霭苍苍。

树色尤含残雨，钟声远带斜阳。

唐·张仲素《山寺秋霁》

清浅的小溪潺潺流淌，秋日的寺院被山中云气环绕，一片苍茫。

秋雨初晴，草木上还残留着点点雨露，夕阳西下，暮鼓声声悠扬。

这是一幅宁静深远的山寺秋日画卷，清溪、云雾、树影、夕阳，交相辉映，沉浸其中，连灵魂都是安宁的。

03

天涯芳草尽绿，路旁柳絮争飞。

啼鸟一声春晚，落花满地人归。

宋·康与之《游慧力寺》

春意渐浓，芳草萋萋，一片翠绿。道路两旁，柳絮似雪，飘扬在温暖的春风中。

鸟鸣清脆，歌声穿透云层，花瓣随风轻舞，为这个季节平添了几分浪漫。

春天，是如此美好。你可以静下心来，看一朵花开，等一树新绿。

04

危石才通鸟道，空山更有人家。

桃源定在深处，涧水浮来落花。

唐·刘长卿《寻张逸人山居》

刘长卿的山水诗总有出世情怀。

这首寻访隐士的小诗，像一幅充满诗意的画卷。诗人沿着青苔覆盖的山径，在嶙峋怪石间找路，却在幽深的空山中听到了人间烟火声。

他的目光随着流水漂浮的落花移动，猜想隐士的居所或许就在林中的更深处。

走在山中，细品美景，本身就是一种难得的享受。

05

柳叶鸣蜩绿暗，荷花落日红酣。

三十六陂春水，白头想见江南。

 宋·王安石 《题西太一宫壁二首其一》

江南，是多少人心中的向往。

白居易说：“江南好， 风景旧曾谙，日出江花红胜火， 春来江水绿如蓝 。 能不忆江南？”

韦庄说：“人人尽说江南好,游人只合江南老。”

王安石也曾到过江南，看着汴京的绿柳，落日、池塘、春水，荷花，却更加怀念江南水乡的春天。

06

板桥人渡泉声，茅檐日午鸡鸣。

莫嗔焙茶烟暗，却喜晒谷天晴。

唐·顾况《过山农家》

这是顾况笔下的一首茶诗。

诗人漫步在木板桥上，只听桥下泉水叮咚；正午十分来到一家农舍门前，在茅草房的门前，公鸡高声啼鸣，像是在欢迎来客。

农人陪着诗人参观焙茶，满怀歉意地说，请不要嗔怪被烟熏到，应当庆幸晒谷正逢晴天。

这首诗轻快自然，清新朴素，令人读来回味不绝。

搭建基于nextjs的静态博客程序mbnb

 

首先fork此项目：https://github.com/officialrajdeepsingh/markdowbnextjsblog，我fork后，得到的项目地址是https://github.com/briteming/mbnb，

访问https://github.com/briteming/mbnb/tree/main/posts，在此处新建源帖（即add file),我新建了源帖fh.md，内容为：

---
author : "ym"
categories : ["misc1", "misc2", "misc3"]
tags : ["misc1", "misc2", "misc3"]
date : "2026-05-25T20:00:00"
description : "这是一篇文章"
image : "images/npm-init-command-1.png"
images : ["images/npm-init-command-1.png"]
slug : "fh"
summary : "pls read it"
title : "战马"
draft : false
---

此处写正文或html codes.

( 详见https://github.com/briteming/mbnb/blob/main/posts/fh.md?plain=1） 

然后，访问vercel.com/new ,导入项目https://github.com/briteming/mbnb

  Build Command栏填入npm run build
 Install Command栏填入npm install

然后点击底部的deploy按钮，等待部署完成。部署完成后，我得到网址:
https://mbnb.vercel.app/

项目地址：https://github.com/officialrajdeepsingh/markdowbnextjsblog

https://github.com/briteming/mbnb

演示博客：

 https://mbnb.vercel.app/

 https://mbnb.vercel.app/blog/fh 能显示视频

搭建基于nextjs的静态博客程序paco

首先fork此项目：https://github.com/pacocoursey/paco，我fork后，得到的项目地址是

https://github.com/briteming/paco，然后编辑package.json，修改"eslint"的值为"^7.0.0"

访问https://github.com/briteming/paco/tree/master/posts，在此处新建源帖（即add file),我新建了源帖fh.md，内容为：

---
title: 战马
description: 这是一篇文章
slug: fh
date: May 26, 2026 15:20
---

此处写正文或html codes.

( 详见https://github.com/briteming/paco/blob/master/posts/fh.md?plain=1） 

然后，访问vercel.com/new ,导入项目https://github.com/briteming/paco

  Build Command栏填入npm run build
 Install Command栏填入npm install --force

然后， 添加环境变量NODE_OPTIONS ，变量的值为 --openssl-legacy-provider

然后点击底部的deploy按钮，等待部署完成。部署完成后，我得到网址:
https://paco-kohl.vercel.app/

项目地址：https://github.com/pacocoursey/paco

https://github.com/briteming/paco

演示博客：

 https://paco-kohl.vercel.app/

 https://paco-kohl.vercel.app/blog
https://paco-kohl.vercel.app/blog/fh 能显示视频.

776789.xyz

 https://776789.xyz ，

开源HTML工具集-大道至简