Skip to main content
weapp.dev

Migration and training for your project

Core compilers and plugins stay MIT open source. This page lists human-delivered services and sponsorship; other commercial capabilities are still in development.

Implementation tied to the toolchain

01

Single page / repository migration

Adopt weapp-vite + Tailwind and leave CI green.

¥8,000-15,000
02

Full project migration

Routes, sub-packages, multi-target output, and bundle baseline.

¥20,000-40,000
03

Enterprise training

Up to 20 people, including a lab repository.

¥12,000 / day
04

Template customization

Per-page customization, or 15% revenue share after listing.

¥2,000-8,000 / key page

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.

Capabilities in development

The public Varo Registry is available. Cloud builds, official templates, and private component registries will open after a stable delivery path exists.

The first official templates

This is a direction, not a live catalog or purchasable inventory. Future publishing will be invite-only and focused on reviewable, rebrandable scenarios.

01

Store redemption

Local services

Store, coupons, redemption, orders

02

Booking

Healthcare / beauty / education

Services, calendar, checkout, reminders

03

Membership card

Brand

Activation, points, tiers

04

Content subscription

Publishing

Feed, detail, paywall

05

Light commerce

Commerce

Catalog, cart, orders

06

B2B showcase

Company site

Cases, lead forms

Cloud builds are still in development

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.

  1. 01Pull from GitHub / Gitee
  2. 02Build for a target
  3. 03Upload trial version
  4. 04Return QR, logs, and bundle report

Current support boundaries

TierChannelResponse
Open sourceGitHub IssuesPublic discussion, no time promise
Human servicesWeChat / QQ / emailConfirmed per project scope
SponsorsNo dedicated supportSponsorship does not buy service benefits

The open-source boundary is explicit

Always open

Compilers, plugins, local CLI, starter template skeletons

Potentially paid later

Cloud queues, complete official templates, private registries, and enterprise support only after real delivery exists.

Never

License checks in MIT packages, docs walls, paid-only Issues

Frequently asked questions

What do sponsors receive?

Sponsorship supports open-source maintenance and does not include technical support, template source, cloud-build minutes, or other commercial benefits.

How is sponsorship income used?

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.

Can I donate to another open-source project?

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.

What if I forgot to name a project?

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.

How can I appear in the public acknowledgements?

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.

Can I buy Pro, Team, or Enterprise today?

No. These capabilities are still in development. The page describes direction, not an open checkout or payment commitment.

Give open source a budget to keep going

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.

WeChat add-friend QR code

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

QQ add-friend QR code

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

Discuss publicly on GitHub

Analytics preferences

Baidu Analytics and Google Analytics are enabled by default on the production site to measure visits and limited interactions. You can turn them off at any time.