- Landing Page: https://drash.land
- This page serves as the entry point to all Drash modules and documentation.
- deno-drash Production: https://drash.land/docs
- This page includes code that is released and stable.
- deno-drash Staging: https://drash.land/docs/staging
- This page includes code that is still under development, but ready to be realeased soon. This page might not always be accessible.
- deno for its web server;
- Drash for its web server framework;
- dejs for its template engine;
- npm to map console scripts to the
npm run
command; - Vue for its front-end framework;
- webpack to enable bundling of Vue templates and enabling Vue single file components; and
- pug for HTML markup in Vue single file components
Install the prerequisites:
Go to the following directory:
cd deno-drash
Install Sass.
brew install sass/sass/sass
Install watchdog for file watching.
console/install_watchdog
Add the following to your $PATH
variable. The installer warns you about setting Python binaries to your $PATH
variable. Please follow Python's instructions.
~/Library/Python/2.7/bin
Install Node modules.
npm install
Step 1: Run the dev server (make sure you are in the deno-drash
directory).
console/dev
The dev server is watched by watchdog
. watchdog
is like nodemon
for Node.js. Every time you save changes, the dev server will reload with your changes. The browser will not reload on its own. You have to do that yourself.
The dev server starts webpack in the background with the --watch
flag. You do not need to worry about recompiling the Vue components. However, if you make a change to webpack.config.js
, then you will need to reload the dev server. The dev server does not reload with changes made to webpack.config.js
.
Problem with node-sass?
npm rebuild node-sass
Problem with watchdog?
Make sure you have Python 2.7 installed.
npm run sass
.scss
files are currently NOT being watched. So, if you make changes to a .scss
file, then make sure you run the above command to compile your changes.
Sometimes you will need to add screenshots to documentation pages. Screenshots should be 1400x1000.