GitXplorerGitXplorer
h

developers.home-assistant

public
297 stars
935 forks
74 issues

Commits

List of commits on branch master.
Verified
52159b51160c3428eeddd2872fae27e3c05fa29b

Correct link in blog/2024-09-02-template-hass-required.md (#2325)

eemontnemery committed 16 hours ago
Verified
202dda206a1944ba9815dfda54e3a0a254fd4e7d

Remove information about deprecated properties in switch (#2322)

DDCSBL committed 4 days ago
Verified
1efe6aeb116f6eea7880a5177fde2eeb03299e1c

Bump express from 4.19.2 to 4.21.0 (#2321)

ddependabot[bot] committed 7 days ago
Verified
8aec77ef4e0cc668a71f2fa51af50dc3229ded3e

Bump the docusaurus group with 3 updates (#2318)

ddependabot[bot] committed 7 days ago
Verified
85c85869772b0eb4f767fc49f8c3aae7f890a1c1

Group @docusaurus/* updates (#2317)

lludeeus committed 8 days ago
Verified
f5f51fa125040ad3e1bf874ae9451559d0f8494b

Clarify blog post about entity service action schema changes (#2316)

eemontnemery committed 8 days ago

README

The README file for this repository.

License: CC BY-NC-SA 4.0

Home Assistant Development Documentation

This is the source for the Home Assistant Development documentation.

Updating the docs

Documentation is built using Docusaurus.

Editing on GitHub

Small changes to text can be made directly on GitHub. At the bottom of each page there is an "Edit This Page" link which will load the document in GitHub ready for changes. This method doesn't easily allow for additional documents or images to be added.

Preparing a local environment

There are two options for developing the documentation on a local system.

Visual Studio Code and devcontainer

The easiest way to get started with development is to use Visual Studio Code with devcontainers. This approach will create a preconfigured development environment with all the tools you need. This approach is enabled for all Home Assistant repositories.

Prerequisites

More info about requirements and devcontainer in general

Getting started
  1. Fork the repository.
  2. Clone the repository to your computer.
  3. Open the repository using Visual Studio code.

When you open this repository with Visual Studio code you are asked to "Reopen in Container", this will start the build of the container.

If you don't see this notification, open the command palette and select Remote-Containers: Reopen Folder in Container.

Tasks

The devcontainter comes with some useful tasks to help you with development, you can start these tasks by opening the command palette and select Tasks: Run Task then select the task you want to run.

When a task is currently running (like Preview for the docs), it can be restarted by opening the command palette and selecting Tasks: Restart Running Task, then select the task you want to restart.

When using devcontainers and starting a preview via yarn start, script/setup or the Task in Code, a browser window will not be opened automatically, instead you will need to open a browser window to localhost:3000. If port 3000 was already in use, Docusaurus will use the next available port. You can check the port used in the terminal window of Visual Studio Code. Look for the line Project is running at http://0.0.0.0:XXXX/ where XXXX 3000 or greater, open a browser window to <http://localhost:XXXX>.

Setting Up Your Own Environment

Running the documentation locally requires NodeJS and Yarn to be installed. Inside a cloned fork of this repository, run:

$ script/setup

Or in Windows, just run:

yarn

This will install docusaurus amongst other things.

Running docs locally
$ script/server

In Windows, just run

yarn start

It will start a server at localhost:3000.

Adding a page

  • Create new page in docs/
  • Add new doc to sidebars.js