[SOC] Dev run in Windows (#409)

* Update registry_spi.md

Add about building dev branch development environment in Windows environment

* Create dev_run.md

dev branch builds in Windows.

* Update registry_spi.md

* Update docsdev.js

* Update dev_run.md
3 files changed
tree: 24049b9bf1d91bfc9a607e84950c628289871df7
  1. .github/
  2. asset/
  3. blog/
  4. community/
  5. development/
  6. docs/
  7. download/
  8. file/
  9. img/
  10. site_config/
  11. src/
  12. utils/
  13. .asf.yaml
  14. .babelrc
  15. .docsite
  16. .eslintrc
  17. .gitignore
  18. .htaccess
  19. .nojekyll
  20. docsite.config.yml
  21. gulpfile.js
  22. LICENSE
  23. package.json
  24. README.md
  25. redirect.ejs
  26. sitemap.xml
  27. template.ejs
  28. webpack.config.js
README.md

Apache DolphinScheduler Official Website

This project keeps all sources used for building up DolphinScheduler official website which is served at https://dolphinscheduler.apache.org/.

Prerequisite

DolphinScheduler website is powered by docsite.

Please also make sure your node version is 10+, version lower than 10.x is not supported yet.

Build instruction

  1. Run npm install in the root directory to install the dependencies.
  2. Run npm run start in the root directory to start a local server, you will see the website in ‘http://127.0.0.1:8080’.
  3. Run npm run build to build source code into dist directory.
  4. Verify your change locally: python -m SimpleHTTPServer 8000, when your python version is 3 use :python3 -m http.server 8000 instead.

If you have higher version of node installed, you may consider nvm to allow different versions of node coexisting on your machine.

  1. Follow the instructions to install nvm
  2. Run nvm install v10.23.1 to install node v10
  3. Run nvm use v10.23.1 to switch the working environment to node v10

Then you are all set to run and build the website. Follow the build instruction above for the details.

How to send a PR

  1. Do not use git add . to commit all the changes.
  2. Just push your changed files, such as:
    • *.md
    • blog.js or docs.js or site.js
  3. Send a PR to master branch.

SEO

Make sure each .md starts with the following texts:

---
title: title
keywords: keywords1,keywords2, keywords3
description: some description
---

Guide for adding a new document

Add a new blog

  1. Add new .md file under blog/en-us or blog/zh-cn.
  2. Update site_config/blog.js, add a new entry to the blog in either en-us or zh-cn.
  3. Run docsite start locally to verify the blog can be displayed correctly.
  4. Send the pull request contains the .md and blog.js only.

Add a new article for development

  1. Add new .md file under docs/en-us/development or docs/zh-cn/development.
  2. Update site_config/development.js, add a new entry in either en-us or zh-cn.
  3. Run docsite start locally to verify the article can be displayed correctly.
  4. Send the pull request contains the *.md and development.js only.

Add a new article for docs

  1. Add new .md file under docs/en-us or docs/zh-cn.
  2. Update site_config/docs.js, add a new entry in either en-us or zh-cn.
  3. Run docsite start locally to verify the article can be displayed correctly.
  4. Send the pull request contains the *.md and development.js only.

Best Regards.
Thanks for reading :)