tec3/five-for-the-future
tec3/five-for-the-future
1
0
Fork 0
mirror of https://github.com/WordPress/five-for-the-future.git synced 2025-04-21 18:43:43 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
five-for-the-future/themes/wporg-5ftf
History
Ian Dunn 1db9ec9203
Theme: Add editor styles.
2019-09-26 15:38:53 -07:00
..
css Theme: Add editor styles. 2019-09-26 15:38:53 -07:00
images Theme: Initial commit. 2019-09-24 16:23:39 -07:00
js Theme: Initial commit. 2019-09-24 16:23:39 -07:00
template-parts Theme: Initial commit. 2019-09-24 16:23:39 -07:00
404.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
archive.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
footer.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
functions.php Theme: Add editor styles. 2019-09-26 15:38:53 -07:00
Gruntfile.js Theme: Add editor styles. 2019-09-26 15:38:53 -07:00
header.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
index.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
package-lock.json Theme: Initial commit. 2019-09-24 16:23:39 -07:00
package.json Theme: Initial commit. 2019-09-24 16:23:39 -07:00
page.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
README.md Theme: Add editor styles. 2019-09-26 15:38:53 -07:00
screenshot.png Theme: Initial commit. 2019-09-24 16:23:39 -07:00
search.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
searchform.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
single.php Theme: Initial commit. 2019-09-24 16:23:39 -07:00
style.css Theme: Move above pub/ folder to avoid clutter from sync commits. 2019-09-24 16:49:35 -07:00

README.md

WordPress.org Five for the Future theme

WordPress theme for the Five for the Future subsite.

Developing

npm install
grunt watch

Make CSS changes in the css/ folder, and css/style.css will be rebuilt automatically.

Committing

Before committing changes to css/, please run grunt build to keep the file size down.

Miscellaneous

The canonical source for this project is github.com/WordPress/five-for-the-future. The contents are synced to the dotorg SVN repo to run on production, because we don't deploy directly from GitHub, for reliability reasons.

The production copy lives in themes/ instead of themes/pub, because it's already open in GitHub, and we don't want to clutter the Meta repo logs and Slack channels with noise from "Syncing w/ Git repository..." commits.