Reusable H5 Marketing Activity Pages: Technical Solutions and Centralized Workspace Management

Background

Large‑scale promotional marketing H5 activity pages can reuse existing capabilities to be built and launched quickly, establishing a generic method that improves development efficiency by about 40% in subsequent projects.

Technical Implementation

Five Technical Solutions

Advantages and disadvantages of each solution are briefly listed.

Centralized Workspace Management

The first three approaches are not described.

Project Structure

Single Floor Development

Public Modules

Workspace configuration example:

packages:
# dependencies used by floor components
- "packages/*"
# floor components
- "floors/*"
- "floors-fem/*"
# floor applications
- "apps/*"
# exclude packages that are inside test directories
- "!**/test"

Module dependencies example:

"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"
},

Reference: “Tongtian Tower ihub floor mono‑repository management”.

Central Repository Management

Brief introduction:

Based on workspace upgrade.

Independent main repository with centralized configuration files.

Independent sub‑repositories sharing co‑built resources.

Independent sub‑repositories managing service 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 standardized governance, though the central repository method may not always be the optimal choice.

Scan the QR code to join the technical discussion group.