pages boilerplate

páginas repetitivas

Siempre es un placer desarrollar tus increíbles sitios estáticos.

Empezando

 # clone repo
$ git clone https://github.com/zce/pages-boilerplate.git my-awesome-pages
$ cd my-awesome-pages
# install dependencies
$ yarn # or npm install 

Uso

$ yarn < task > [options]

p.ej

 # Runs the app in development mode
$ yarn serve --port 5210 --open
# Builds the app for production to the `dist` folder
$ yarn build --production

Guiones disponibles

yarn lint o npm run lint

Lint los archivos de estilos y scripts.

yarn compile o npm run compile

Compile el archivo de estilos, scripts y páginas.

yarn serve o npm run serve

Ejecuta la aplicación en modo de desarrollo con un servidor automatizado.

opciones

• open : abre el navegador al iniciar, predeterminado: false
• port : especifique el puerto del servidor, predeterminado: 2080

yarn build o npm run build

Crea la aplicación para producción en la carpeta dist . Minimiza la fuente en modo de producción para obtener el mejor rendimiento.

opciones

• production : indicador del modo de producción, predeterminado: false
• prod : Alias ​​de production

yarn start o npm run start

Ejecución de proyectos en modo producción.

opciones

• open : abre el navegador al iniciar, predeterminado: false
• port : especifique el puerto del servidor, predeterminado: 2080

yarn deploy o npm run deploy

Implemente la carpeta dist en GitHub Pages.

opciones

• branch : el nombre de la rama a la que enviarás, predeterminado: 'gh-pages'

yarn clean o npm run clean

Limpia los archivos dist y temp .

Estructura de carpetas

 └── my-awesome-pages ································· project root
   ├─ public ········································· static folder
   │  └─ favicon.ico ································· static file (unprocessed)
   ├─ src ············································ source folder
   │  ├─ assets ······································ assets folder
   │  │  ├─ fonts ···································· fonts folder
   │  │  │  └─ pages.ttf ····························· font file (imagemin)
   │  │  ├─ images ··································· images folder
   │  │  │  └─ logo.png ······························ image file (imagemin)
   │  │  ├─ scripts ·································· scripts folder
   │  │  │  └─ main.js ······························· script file (babel / uglify)
   │  │  └─ styles ··································· styles folder
   │  │     ├─ _variables.scss ······················· partial sass file (dont output)
   │  │     └─ main.scss ····························· entry scss file (scss / postcss)
   │  ├─ layouts ····································· layouts folder
   │  │  └─ basic.html ······························· layout file (dont output)
   │  ├─ partials ···································· partials folder
   │  │  └─ header.html ······························ partial file (dont output)
   │  ├─ about.html ·································· page file (use layout & partials)
   │  └─ index.html ·································· page file (use layout & partials)
   ├─ .csscomb.json ·································· csscomb config file
   ├─ .editorconfig ·································· editor config file
   ├─ .gitignore ····································· git ignore file
   ├─ .travis.yml ···································· travis ci config file
   ├─ CHANGELOG.md ··································· repo changelog
   ├─ LICENSE ········································ repo license
   ├─ README.md ······································ repo readme
   ├─ gulpfile.js ···································· gulp tasks file
   ├─ package.json ··································· package file
   └─ yarn.lock ······································ yarn lock file

Relacionado

• zce/x-pages: un flujo de trabajo gulp totalmente administrado para sitios de páginas estáticas.

Contribuyendo

1. ¡ Bifurquelo en GitHub!
2. Clona el fork en tu propia máquina.
3. Consulte su rama de funciones: git checkout -b my-awesome-feature
4. Confirme sus cambios en su propia rama: git commit -am 'Add some feature'
5. Lleva tu trabajo de regreso a tu bifurcación: git push -u origin my-awesome-feature
6. Envíe una solicitud de extracción para que podamos revisar sus cambios.

NOTA : ¡Asegúrese de fusionar lo último de "upstream" antes de realizar una solicitud de extracción!

Licencia

MIT © 汪磊