Skip to content

FutureProofHomes/Documentation

Repository files navigation

Contributors Forks Stargazers Issues MIT License


Logo

Documentation

This repository contains all the code for our online product documentation at docs.FutureProofHomes.net.
Explore the docs »

View Main Website · Watch Our YouTube

Table of Contents
  1. About The Documentation
  2. Contributing
  3. License
  4. Contact

About Documentation

FutureProofHomes focuses on building hardware and software for the Home Assistant platform. We specifically focus on AI-powered voice assistance so that you can control your home with intuitive voice conversations instead of interacting with a user interface.

Built With

  • Material for MkDocs

(back to top)

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/DocumentationModification)
  3. Commit your Changes (git commit -m 'Add some DocumentationModification')
  4. Push to the Branch (git push origin feature/DocumentationModification)
  5. Open a Pull Request

Local Development Environment

  1. Ensure Python and pip are installed on your machine (python --version) and (pip --version)
  2. Create a Python Virtual Environment (python -m venv venv)
  3. Start the Python Environment (source venv/bin/activate)
  4. Install the documentation dependencies (pip install -r requirements.txt)
  5. Serve MkDocs locally (mkdocs serve --livereload)

(back to top)

Stable / Beta Documentation

Some pages have content that differs between the Stable and Beta firmware. We use content tabs to let viewers toggle between the two. Because content.tabs.link is enabled, selecting "Stable" or "Beta" on any page syncs the choice across the entire site.

Writing version-specific content

For sections that differ between firmware versions, wrap them in content tabs:

=== "Stable"

    Stable-specific content here...

=== "Beta"

    Beta-specific content here...

Pages where content is identical across versions should not use tabs.

Graduating beta to stable

When a beta version ships as stable:

  1. Replace the "Stable" tab content with the "Beta" tab content.
  2. Remove the tab wrappers (or start a new "Beta" tab for the next cycle).
  3. Search for any remaining === "Beta" / === "Stable" blocks across all docs to ensure nothing is missed.

(back to top)

License

Distributed under the GNU GENERAL PUBLIC LICENSE. See LICENSE.txt for more information.

(back to top)

Contact

FutureProofHomes - Website - [email protected]

(back to top)

Acknowledgments

  • @qulbnsl for getting our firmware CI/CD pipelines operational and dynamically updating ESP Web Tools documentation.
  • Your name here soon. :)

(back to top)

Releases

No releases published

Packages

 
 
 

Contributors