Single page / repository migration
Adopt weapp-vite + Tailwind and leave CI green.
Core compilers and plugins stay MIT open source. This page lists human-delivered services and sponsorship; other commercial capabilities are still in development.
Adopt weapp-vite + Tailwind and leave CI green.
Routes, sub-packages, multi-target output, and bundle baseline.
Up to 20 people, including a lab repository.
Per-page customization, or 15% revenue share after listing.
Services stay tied to the toolchain and do not become unrelated product outsourcing. New work pauses if services exceed 50% of total revenue for two consecutive months.
Chinese open source needs sustained time, infrastructure, and maintenance. Sponsorship is not a service purchase; it helps this toolchain keep shipping and supporting its community.
To support another open-source project, add “Donate to XXX project” to your donation note. You can also message me privately afterwards with the project name.
After I confirm the details, donations for a named project are handled separately for that purpose. Donations without a designated project follow the published default allocation.

Scan to add me, or save the original image and scan it from your photos in the app.

Scan to add me, or save the original image and scan it from your photos in the app.
Use the contact icons to ask via WeChat, QQ, or email before donating. This site has no online payment backend.
Write “Donate to XXX project” in the note. Include a repository link if the name could be ambiguous.
Forgot the note? Message me privately with the project name and donation details so I can match the donation and confirm its purpose.
A permanent public thank-you after confirmation and authorization.
Request sponsorship detailsAfter identity confirmation and authorization, show a GitHub avatar, username, and profile link.
Request sponsorship detailsFeatured individual recognition, including Bronze benefits.
Request sponsorship detailsSingle-site monthly ¥2,000 / 30 days; dual-site monthly ¥3,000 / 30 days; dual-site quarterly ¥8,000 / 90 days; custom terms by discussion.
Request sponsorship detailsDefault allocation without a designated project
For confirmed donations without a designated project, the net amount after payment fees is allocated 60% to core maintenance, 25% to the contributors fund, and 15% to upstream and adjacent open source. Confirmed project-specific donations are handled separately and excluded from this default split.
Sponsorship is not a service purchase and does not include technical support, template source, cloud-build minutes, or subscription access. Public display requires GitHub identity confirmation, maintainer review, and explicit authorization; approved records may appear on weapp.dev, tw.weapp.dev, and vite.weapp.dev.
gold
The public Varo Registry is available. Cloud builds, official templates, and private component registries will open after a stable delivery path exists.
This is a direction, not a live catalog or purchasable inventory. Future publishing will be invite-only and focused on reviewable, rebrandable scenarios.
Local services
Store, coupons, redemption, orders
Healthcare / beauty / education
Services, calendar, checkout, reminders
Brand
Activation, points, tiers
Publishing
Feed, detail, paywall
Commerce
Catalog, cart, orders
Company site
Cases, lead forms
The future path is to pull from GitHub / Gitee, build for a target platform, upload a trial version, and return a QR code and logs. No availability or quota is promised today.
| Tier | Channel | Response |
|---|---|---|
| Open source | GitHub Issues | Public discussion, no time promise |
| Human services | WeChat / QQ / email | Confirmed per project scope |
| Sponsors | No dedicated support | Sponsorship does not buy service benefits |
Compilers, plugins, local CLI, starter template skeletons
Cloud queues, complete official templates, private registries, and enterprise support only after real delivery exists.
License checks in MIT packages, docs walls, paid-only Issues
Sponsorship supports open-source maintenance and does not include technical support, template source, cloud-build minutes, or other commercial benefits.
For confirmed donations without a designated project, the net amount after payment fees is allocated 60% to core maintenance, 25% to the contributors fund, and 15% to upstream and adjacent open source. Confirmed project-specific donations are handled separately and excluded from this default split.
Yes. Add “Donate to XXX project” to your donation note, or message me privately afterwards. Once I confirm the details, the donation is handled separately for that project and excluded from the default 60% / 25% / 15% split.
Message me privately afterwards with the project name and donation details so I can match the donation. Once confirmed, it will be handled separately for the designated project.
Public recognition requires confirmed GitHub or business details, maintainer review, and explicit authorization, following the relevant tier rules. Donation notes and private messages are not automatically published as acknowledgements.
No. These capabilities are still in development. The page describes direction, not an open checkout or payment commitment.
Contact me via WeChat, QQ, or email about sponsorship, a donation to a specific project, or migration and training. Open an icon for account details and a QR code. GitHub remains available for public discussions.

Scan to add me, or save the original image and scan it from your photos in the app.

Scan to add me, or save the original image and scan it from your photos in the app.