Files
.devcontainer
.github
.vscode
plugins
sass
source
.well-known
_dashboards
_data
_docs
_faq
404.markdown
addon_not_starting.markdown
after-upgrading.markdown
browser.markdown
character_t.markdown
component.markdown
configuration-file.markdown
connection-error.markdown
dependencies.markdown
distutils.markdown
documentation-tool.markdown
ha-vs-hassio.markdown
libyaml.markdown
missing-documentation.markdown
pip.markdown
pip3.markdown
problems-with-dependencies.markdown
release.markdown
rpi4_8gb.markdown
sdcard_files.markdown
unique_id.markdown
usb_boot.markdown
usb_config.markdown
_includes
_integrations
_layouts
_posts
addons
android
assets
blog
blue
blueprints
changelogs
cloud
code_of_conduct
common-tasks
conference
connectzbt1
dashboards
developers
docs
faq
getting-started
green
help
home-energy-management
images
installation
integrations
ios
javascripts
more-info
privacy
security
state-of-the-open-home
static
stylesheets
tag
tos
voice_control
yellow
404.html
CNAME
_headers
_redirects
atom.xml
favicon.png
googlef4f3693c209fe788.html
index.html
integrations.json
robots.txt
service_worker.js
version.json
.editorconfig
.gitattributes
.gitignore
.markdownlint.json
.nvmrc
.powrc
.remarkignore
.remarkrc.js
.ruby-version
.textlintrc.json
CLA.md
CODEOWNERS
CODE_OF_CONDUCT.md
Gemfile
Gemfile.lock
LICENSE.md
README.md
Rakefile
_config.yml
config.rb
config.ru
package-lock.json
package.json
home-assistant.io/source/_faq/documentation-tool.markdown
Franck Nijhof 1833c32a2c Cleans up front matter ()
* Sets front matter defaults

* Removes default front matter from section templates/pages

* Removes default front matter from addon pages

* Removes default front matter from integration pages

* Removes default front matter from posts

* Removes default front matter from docs pages

* Removes default front matter from other pages

* Fixes blog category pages
2019-07-11 14:35:08 -07:00

285 B

title, description, ha_category
title description ha_category
Documentation tools Tools for creating the documentation Documentation

Why are you not using tools X for the documentation? Because the current solution works for us and we see no additional value in using a separate publishing platform.