@@ -43,7 +43,7 @@ else fails, try removing the virtual environment and reinstalling:
43
43
## Development
44
44
45
45
1 . Run ` pipenv shell ` to spawn a shell with the virtualenv activated
46
- 1 . Run ` lektor server ` to start the Lektor development server. You will be able
46
+ 1 . Run ` lektor server -f webpack ` to start the Lektor development server. You will be able
47
47
to see the website at [ ` http://localhost:5000/ ` ] [ lektorlocal ] . The Lektor
48
48
server will rebuild the site every time you change any content.
49
49
@@ -68,8 +68,7 @@ on production!
68
68
69
69
Here's how the code is structured in the top level of the repository:
70
70
- ** ` assets ` ** : This directory contains the JavaScript and CSS files for the
71
- project. Most of the JavaScript and CSS is third-party code and loaded via
72
- CDN so this is pretty empty.
71
+ project built via webpack. Most of the JavaScript and CSS is third-party code and loaded via CDN so this is pretty empty.
73
72
- ** ` content ` ** : The content of the site lives here. [ Here's an explanation of
74
73
how content works in Lektor] [ lektorcontent ] . This is probably what you'll be
75
74
modifying most often.
@@ -79,6 +78,8 @@ Here's how the code is structured in the top level of the repository:
79
78
- ** ` templates ` ** : This is where the [ Jinja2] [ jinja2 ] templates that render
80
79
content are stored. See the [ Lektor template documentation] [ lektortemplate ]
81
80
for more information.
81
+ - ** ` webpack ` ** : This is where all the webpack config files as well as Sass and
82
+ JavaScript files for the project resides. The JavaScript and Sass files are compiled and saved in assets folder during lektor build process.
82
83
83
84
[ lektorcontent ] :https://www.getlektor.com/docs/content/
84
85
[ lektormodels] :(https://www.getlektor.com/docs/models/
0 commit comments