Cut Development Time 40% by Reusing H5 Pages with a Monorepo

Background

Reusing existing H5 marketing activity page capabilities allows rapid construction and launch, accumulating generic methods. Subsequent development can improve efficiency by about 40%.

Technical Implementation

Five Technical Solutions

(Details omitted.)

Pros and cons of each solution are briefly mentioned.

Workspace Centralized Management

The first three approaches are not described.

Project structure illustrations:

Workspace Configuration

<code>packages:
  # Dependencies used by floor components
  - "packages/*"
  # Floor components
  - "floors/*"
  - "floors-fem/*"
  # Floor applications
  - "apps/*"
  # Exclude packages inside test directories
  - "!**/test"
</code>

Module References

<code>"dependencies": {
  "@babor/apis": "workspace:*",
  "@babor/components": "workspace:*",
  "@babor/consts": "workspace:*",
  "@babor/hooks": "workspace:*",
  "@babor/utils": "workspace:*",
  "@jmfe/ifloor-scripts": "2.2.4",
  "@jmfe/jmfe-customcode-api": "^2.1.0",
  "react": "16.10.1",
  "react-dom": "16.10.1",
  "react-scripts": "^4.0.3"
},
</code>

Reference

Monorepo management for iHub floors (Tongtian Tower).

Central Repository Management

Brief introduction:

Based on workspace upgrade.

Independent main repository with centralized configuration files.

Independent sub‑repositories sharing common resources.

Independent sub‑repositories managing modules.

Upgrade Iteration

Project iteration and upgrades are straightforward using Git repositories and branch management.

Conclusion

The approach suits similar project management scenarios such as floor development, backend systems, and standardization. Each method has its own applicable scenarios, and a central repository may not always be the optimal choice.