# Introduction

## Introduction

In the Python community, developers have a great programming style reference provided as part of the language enhancement process specifications ([PEP-8](https://www.python.org/dev/peps/pep-0008/)), but in the PowerShell world there has been no official documentation of community preferences.

This document is an attempt to come to an agreement on a style-guide because we know that the more people follow the same set of code-style habits, the more readable the community's code will be. In other words, although the recommendations of this guide are *just recommendations*, if you follow them, you will write PowerShell code that is more easily read, understood, and maintained.

## Table of Contents

* [Code Layout and Formatting](https://poshcode.gitbook.io/powershell-practice-and-style/style-guide/code-layout-and-formatting)
* [Function Structure](https://poshcode.gitbook.io/powershell-practice-and-style/style-guide/function-structure)
* [Documentation and Comments](https://poshcode.gitbook.io/powershell-practice-and-style/style-guide/documentation-and-comments)
* [Readability](https://poshcode.gitbook.io/powershell-practice-and-style/style-guide/readability)
* [Naming Conventions](https://poshcode.gitbook.io/powershell-practice-and-style/style-guide/naming-conventions)