Welcome to the GitHub repository for [Telerik Reporting](https://www.telerik.com/reporting) documentation. This repository contains the source content — written in Markdown — that we use to power the Telerik Reporting Documentation at [docs.telerik.com/reporting](https://docs.telerik.com/reporting). If you've arrived here wanting to search and use our docs, head over to [docs.telerik.com/reporting](https://docs.telerik.com/reporting) where our content is prettified and searchable.
We believe that the documentation for a product is at its best when the content is a collaboration between the builders and consumers of that product. As such, this documentation is both public, and open sourced under and MIT license (see below). That means you can clone this repository, or read the docs offline.
It also means that you can play a role in making our docs better for everyone, and if helping us make the Telerik Reporting docs better sounds interesting to you, read on.
## Contributing
There are two ways you can contribute to the public Telerik Reporting documentation: either create an issue in this repository, or fork the repo, make the change and send us a pull request!
* **Create an issue** - If you find an issue with our docs that needs to be addressed, the best way to let us know about it is by [creating an issue in this repository](https://github.com/telerik/reporting-docs/issues). When creating an issue, provide a descriptive title, be as specific as possible and link to the document in question (If you can provide a link to the closest anchor to the issue, all the better). Here's an example:
Title: implementer-guide/integration-with-report-viewers.md is missing an image
Description : Example 3 is missing an image right after the code sample.
> Note: When creating issues, please don't modify the assignee or milestone fields. Also, please create one issue per fix or change. "Bundled" entries will be deleted.
* **Send us a pull request** - Creating an issue is great — and we certainly appreciate them — but what we really love are pull requests. So, if you find an issue in the docs, or even feel like creating new content, we'd be happy to have your contributions! If you're just getting started with open source, Git and GitHub, we suggest you first read up on [forking repositories](https://help.github.com/articles/fork-a-repo) and [sending pull requests](https://help.github.com/articles/using-pull-requests).
Start by creating a local clone of our repo either using [GitHub for Windows](http://windows.github.com/), [GitHub for Mac](http://mac.github.com/) or your friendly command-line:
Then, open up the reporting-docs folder in your favorite text editor. Of course, as you work with the docs, we do ask that you follow a couple of guidelines:
- Fixing grammar, punctuation and other general errors is always appreciated. So are changes that expand on key ideas or correct errors in logic phrasing or otherwise. If your ambitions are greater, however, and you want to add completely new content to the site — like a new tutorial, for instance — we suggest you contact a member of the team first (or enter an issue!).
- Each document in this repo contains a section of YAML Front Matter at the very top. This content, which looks like the text below, is used by our auto-import tool when content is processed for the live documentation site. Please don't edit the content in this section of a document.
---
title: Introduction
page_title: Introduction
description: Introduction
slug: introduction
tags: introduction
published: True
position: 1
---
- When adding content or making changes, please use only standard Markdown syntax, and make sure to preview your additions or changes before sending us a pull request. You can use an online tool like [Dillinger.io](http://dillinger.io/) or [Marked](http://markedapp.com/) on OSX to view what your changes will look like when ported to HTML.
Once you've made your changes, commit, pull, merge, push and [send us a pull request](https://help.github.com/articles/using-pull-requests)! We — and Report Server users everywhere — thank you for improving our documentation!
## Running locally
You can generate a static web site from the Telerik Reporting documentation and browse it locally.
Detailed instructions on how to achieve this can be found in the [docs-seed repository](https://github.com/telerik/docs-seed#local-setup).
## License
The Telerik Reporting Documentation is licensed under an MIT license. This license applies to the markdown (.md) files in this site **ONLY**, and does not convey, override or modify any existing licenses covering the runtime source and components of Telerik Reporting. For information about available licenses for the Telerik Reporting click [here](https://www.telerik.com/purchase/license-agreement/reporting-dlw-s).
### MIT License
Copyright (c) 2012-2018 Telerik EAD
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software" ), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
