diff --git a/frappe/docs/user/en/bench/guides/diagnosing-the-scheduler.md b/frappe/docs/user/en/bench/guides/diagnosing-the-scheduler.md
index a0661dbb17..492205cf5b 100755
--- a/frappe/docs/user/en/bench/guides/diagnosing-the-scheduler.md
+++ b/frappe/docs/user/en/bench/guides/diagnosing-the-scheduler.md
@@ -1,3 +1,5 @@
+# Diagnosing The Scheduler
+
If you're experiencing delays in scheduled jobs or they don't seem to run, you can run the several commands to diagnose the issue.
diff --git a/frappe/docs/user/en/bench/guides/index.md b/frappe/docs/user/en/bench/guides/index.md
index 0dff60b400..8ab035a2f5 100644
--- a/frappe/docs/user/en/bench/guides/index.md
+++ b/frappe/docs/user/en/bench/guides/index.md
@@ -1 +1,5 @@
+# Guides
+
+
+
{index}
\ No newline at end of file
diff --git a/frappe/docs/user/en/bench/guides/manual-setup.md b/frappe/docs/user/en/bench/guides/manual-setup.md
index a0c55f374f..a9ee314650 100755
--- a/frappe/docs/user/en/bench/guides/manual-setup.md
+++ b/frappe/docs/user/en/bench/guides/manual-setup.md
@@ -1,3 +1,5 @@
+# Manual Setup
+
Manual Setup
--------------
diff --git a/frappe/docs/user/en/bench/guides/setup-multitenancy.md b/frappe/docs/user/en/bench/guides/setup-multitenancy.md
index 8f204cd9eb..1404fd707c 100755
--- a/frappe/docs/user/en/bench/guides/setup-multitenancy.md
+++ b/frappe/docs/user/en/bench/guides/setup-multitenancy.md
@@ -1,3 +1,5 @@
+# Setup Multitenancy
+
Assuming that you've already got your first site running and you've performed
the [production deployment steps](setup-production.html), this section explains how to host your second
site (and more). Your first site is automatically set as default site. You can
diff --git a/frappe/docs/user/en/bench/guides/setup-production.md b/frappe/docs/user/en/bench/guides/setup-production.md
index 414aab10e2..4c5e2a7dc2 100644
--- a/frappe/docs/user/en/bench/guides/setup-production.md
+++ b/frappe/docs/user/en/bench/guides/setup-production.md
@@ -1,3 +1,5 @@
+# Setup Production
+
You can setup the bench for production use by configuring two programs, Supervisor and nginx. If you want to revert your Production Setup to Development Setup refer to [these commands](https://github.com/frappe/bench/wiki/Stopping-Production-and-starting-Development)
####Easy Production Setup
diff --git a/frappe/docs/user/en/bench/index.md b/frappe/docs/user/en/bench/index.md
index 0dff60b400..a91b00e4b9 100644
--- a/frappe/docs/user/en/bench/index.md
+++ b/frappe/docs/user/en/bench/index.md
@@ -1 +1,2 @@
-{index}
\ No newline at end of file
+# Bench
+
diff --git a/frappe/docs/user/en/bench/resources/background-services.md b/frappe/docs/user/en/bench/resources/background-services.md
index d019d25d8c..6e7a20730b 100755
--- a/frappe/docs/user/en/bench/resources/background-services.md
+++ b/frappe/docs/user/en/bench/resources/background-services.md
@@ -1,3 +1,5 @@
+# Background Services
+
External services
-----------------
diff --git a/frappe/docs/user/en/bench/resources/bench-commands-cheatsheet.md b/frappe/docs/user/en/bench/resources/bench-commands-cheatsheet.md
index b412d5f78a..054cd072f6 100755
--- a/frappe/docs/user/en/bench/resources/bench-commands-cheatsheet.md
+++ b/frappe/docs/user/en/bench/resources/bench-commands-cheatsheet.md
@@ -1,3 +1,5 @@
+# Bench Commands Cheatsheet
+
### General Usage
* `bench --version` - Show bench version
* `bench src` - Show bench repo directory
diff --git a/frappe/docs/user/en/bench/resources/bench-procfile.md b/frappe/docs/user/en/bench/resources/bench-procfile.md
index 61ecfc6eec..9a9176556c 100755
--- a/frappe/docs/user/en/bench/resources/bench-procfile.md
+++ b/frappe/docs/user/en/bench/resources/bench-procfile.md
@@ -1,3 +1,5 @@
+# Bench Procfile
+
`bench start` uses [honcho](http://honcho.readthedocs.org) to manage multiple processes in **developer mode**.
### Processes
diff --git a/frappe/docs/user/en/bench/resources/index.md b/frappe/docs/user/en/bench/resources/index.md
index 0dff60b400..48852466ed 100644
--- a/frappe/docs/user/en/bench/resources/index.md
+++ b/frappe/docs/user/en/bench/resources/index.md
@@ -1 +1,5 @@
+# Resources
+
+
+
{index}
\ No newline at end of file
diff --git a/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md b/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md
index 29a1a608b3..1e41bcfa16 100644
--- a/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md
+++ b/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md
@@ -1,3 +1,5 @@
+# Adding Custom Button To Form
+
To create a custom button on your form, you need to edit the javascript file associated to your doctype. For example, If you want to add a custom button to User form then you must edit `user.js`.
In this file, you need to write a new method `add_custom_button` which should add a button to your form.
diff --git a/frappe/docs/user/en/guides/app-development/adding-module-icons-on-desktop.md b/frappe/docs/user/en/guides/app-development/adding-module-icons-on-desktop.md
index 44b014267d..4fbf6fda1e 100755
--- a/frappe/docs/user/en/guides/app-development/adding-module-icons-on-desktop.md
+++ b/frappe/docs/user/en/guides/app-development/adding-module-icons-on-desktop.md
@@ -1,3 +1,5 @@
+# Adding Module Icons On Desktop
+
To create a module icon for a Page, List or Module, you will have to edit the `config/desktop.py` file in your app.
In this file you will have to write the `get_data` method that will return a dict object with the module icon parameters
diff --git a/frappe/docs/user/en/guides/app-development/custom-module-icon.md b/frappe/docs/user/en/guides/app-development/custom-module-icon.md
index 609f7f3803..4a9903fbf7 100755
--- a/frappe/docs/user/en/guides/app-development/custom-module-icon.md
+++ b/frappe/docs/user/en/guides/app-development/custom-module-icon.md
@@ -1,3 +1,5 @@
+# Custom Module Icon
+
If you want to create a custom icon for your module, you will have to create an SVG file for your module and set the path to this file in the `desktop/config.py` of your app.
This icon is loaded via AJAX first time, then it will be rendered.
diff --git a/frappe/docs/user/en/guides/app-development/dialogs-types.md b/frappe/docs/user/en/guides/app-development/dialogs-types.md
index a1aa4f9a07..0c0550688e 100755
--- a/frappe/docs/user/en/guides/app-development/dialogs-types.md
+++ b/frappe/docs/user/en/guides/app-development/dialogs-types.md
@@ -1,3 +1,5 @@
+# Dialogs Types
+
Frappe provide a group of standard dialogs that are very usefull while coding.
## Alert Dialog
diff --git a/frappe/docs/user/en/guides/app-development/executing-code-on-doctype-events.md b/frappe/docs/user/en/guides/app-development/executing-code-on-doctype-events.md
index a5b57e0920..ff03f85236 100755
--- a/frappe/docs/user/en/guides/app-development/executing-code-on-doctype-events.md
+++ b/frappe/docs/user/en/guides/app-development/executing-code-on-doctype-events.md
@@ -1,3 +1,5 @@
+# Executing Code On Doctype Events
+
To execute code when a DocType is inserted, validated (before saving), updated, submitted, cancelled, deleted, you must write in the DocType's controller module.
#### 1. Controller Module
diff --git a/frappe/docs/user/en/guides/app-development/how-enable-developer-mode-in-frappe.md b/frappe/docs/user/en/guides/app-development/how-enable-developer-mode-in-frappe.md
index 5c47385fbd..8895fc7bec 100755
--- a/frappe/docs/user/en/guides/app-development/how-enable-developer-mode-in-frappe.md
+++ b/frappe/docs/user/en/guides/app-development/how-enable-developer-mode-in-frappe.md
@@ -1,3 +1,5 @@
+# How Enable Developer Mode In Frappe
+
When you are in application design mode and you want the changes in your DocTypes, Reports etc to affect the app repository, you must be in **Developer Mode**.
To enable developer mode, update the `site_config.json` file of your site in the sites folder for example:
diff --git a/frappe/docs/user/en/guides/app-development/how-to-create-custom-fields-during-app-installation.md b/frappe/docs/user/en/guides/app-development/how-to-create-custom-fields-during-app-installation.md
index 20b7fdce30..3169297850 100755
--- a/frappe/docs/user/en/guides/app-development/how-to-create-custom-fields-during-app-installation.md
+++ b/frappe/docs/user/en/guides/app-development/how-to-create-custom-fields-during-app-installation.md
@@ -1,3 +1,5 @@
+# How To Create Custom Fields During App Installation
+
Your custom app can automatically add **Custom Fields** to DocTypes outside of your app when it is installed to a new site.
To do this, add the new custom fields that your app requires, using the Frappe web application.
diff --git a/frappe/docs/user/en/guides/app-development/how-to-improve-a-standard-control.md b/frappe/docs/user/en/guides/app-development/how-to-improve-a-standard-control.md
index e3c8ef82c0..df137db2a9 100755
--- a/frappe/docs/user/en/guides/app-development/how-to-improve-a-standard-control.md
+++ b/frappe/docs/user/en/guides/app-development/how-to-improve-a-standard-control.md
@@ -1,3 +1,5 @@
+# How To Improve A Standard Control
+
Frappé has a couple of elegant and useful widgets, but some times we need to edit them to add small improvements. This small article will describe how to add new resources to the standard widgets.
Let me explain first our goal:
diff --git a/frappe/docs/user/en/guides/app-development/insert-a-document-via-api.md b/frappe/docs/user/en/guides/app-development/insert-a-document-via-api.md
index aab15b4ac9..c3a8358ddb 100755
--- a/frappe/docs/user/en/guides/app-development/insert-a-document-via-api.md
+++ b/frappe/docs/user/en/guides/app-development/insert-a-document-via-api.md
@@ -1,3 +1,5 @@
+# Insert A Document Via Api
+
You can insert documents via a script using the `frappe.get_doc` method
### Examples:
diff --git a/frappe/docs/user/en/guides/app-development/overriding-link-query-by-custom-script.md b/frappe/docs/user/en/guides/app-development/overriding-link-query-by-custom-script.md
index cc8c8058fd..4e78d7fd58 100755
--- a/frappe/docs/user/en/guides/app-development/overriding-link-query-by-custom-script.md
+++ b/frappe/docs/user/en/guides/app-development/overriding-link-query-by-custom-script.md
@@ -1,3 +1,5 @@
+# Overriding Link Query By Custom Script
+
You can override the standard link query by using `set_query`
### 1. Adding Fitlers
diff --git a/frappe/docs/user/en/guides/app-development/running-background-jobs.md b/frappe/docs/user/en/guides/app-development/running-background-jobs.md
index ae2972b855..d1823d1bb8 100644
--- a/frappe/docs/user/en/guides/app-development/running-background-jobs.md
+++ b/frappe/docs/user/en/guides/app-development/running-background-jobs.md
@@ -1,3 +1,5 @@
+# Running Background Jobs
+
Sometimes you may not want a user request to be executed immediately but added to a queue that will be executed by a background worker. The advantage of doing this is that your web workers remain free to execute other requests and longer jobs do not eat up all of your resources.
From version 7, Frappe uses Python RQ to run background jobs.
diff --git a/frappe/docs/user/en/guides/app-development/single-type-doctype.md b/frappe/docs/user/en/guides/app-development/single-type-doctype.md
index ee5c24b492..560b2a1a6d 100755
--- a/frappe/docs/user/en/guides/app-development/single-type-doctype.md
+++ b/frappe/docs/user/en/guides/app-development/single-type-doctype.md
@@ -1,3 +1,5 @@
+# Single Type Doctype
+
DocTypes have a table associated with them. For example DocType **Customer** will have a table `tabCustomer` associated with it.
**Single** type DocTypes have no table associated and there is only one Document for it. This is similar to the Singleton pattern in Java. Single DocTypes are ideal for saving Settings (that are globally applicable) and for wizard / helper type forms that have no documents, but when the DocType is used for the Form UI.
diff --git a/frappe/docs/user/en/guides/app-development/trigger-event-on-deletion-of-grid-row.md b/frappe/docs/user/en/guides/app-development/trigger-event-on-deletion-of-grid-row.md
index cc60f6d0b8..776742d4ea 100755
--- a/frappe/docs/user/en/guides/app-development/trigger-event-on-deletion-of-grid-row.md
+++ b/frappe/docs/user/en/guides/app-development/trigger-event-on-deletion-of-grid-row.md
@@ -1,3 +1,5 @@
+# Trigger Event On Deletion Of Grid Row
+
To trigger an event when a row from a Child Table has been deleted (when user clicks on `delete` button), you need to add a handler the `fieldname_remove` event to Child Table, where fieldname is the fieldname of the Child Table in Parent Table declaration.
For example:
diff --git a/frappe/docs/user/en/guides/app-development/using-html-templates-in-javascript.md b/frappe/docs/user/en/guides/app-development/using-html-templates-in-javascript.md
index f6242babb7..13f7073e4d 100755
--- a/frappe/docs/user/en/guides/app-development/using-html-templates-in-javascript.md
+++ b/frappe/docs/user/en/guides/app-development/using-html-templates-in-javascript.md
@@ -1,3 +1,5 @@
+# Using Html Templates In Javascript
+
Often while building javascript interfaces, there is a need to render DOM as an HTML template. Frappe Framework uses John Resig's Microtemplate script to render HTML templates in the Desk application.
> Note 1: In Frappe we use the Jinja-like `{% raw %}{%{% endraw %}` tags to embed code rather than the standard `<%`
diff --git a/frappe/docs/user/en/guides/basics/frappe_ajax_call.md b/frappe/docs/user/en/guides/basics/frappe_ajax_call.md
index a92356843a..657cd3e7f2 100644
--- a/frappe/docs/user/en/guides/basics/frappe_ajax_call.md
+++ b/frappe/docs/user/en/guides/basics/frappe_ajax_call.md
@@ -1,3 +1,5 @@
+# Frappe Ajax Call
+
In Frappe Framework, you can manage ajax calls via frappe.call. The frappe.call works in asynchronous manner ie. send requests and handle response via callback mechanism.
## frappe.call Structure
diff --git a/frappe/docs/user/en/guides/basics/translations.md b/frappe/docs/user/en/guides/basics/translations.md
index e5ff22e9f2..86d630898f 100755
--- a/frappe/docs/user/en/guides/basics/translations.md
+++ b/frappe/docs/user/en/guides/basics/translations.md
@@ -1,3 +1,5 @@
+# Translations
+
diff --git a/frappe/docs/user/en/guides/data/import-large-csv-file.md b/frappe/docs/user/en/guides/data/import-large-csv-file.md
index 5194ebd98d..013d02ac92 100755
--- a/frappe/docs/user/en/guides/data/import-large-csv-file.md
+++ b/frappe/docs/user/en/guides/data/import-large-csv-file.md
@@ -1,3 +1,5 @@
+# Import Large Csv File
+
To import very large CSV files, you can use the bench utility `import-csv`.
The benefit is that this is not subject to timeouts if you use the web interface.
diff --git a/frappe/docs/user/en/guides/deployment/email-notifications-for-failed-background-jobs.md b/frappe/docs/user/en/guides/deployment/email-notifications-for-failed-background-jobs.md
index 03f57eb410..cd9f18e1e1 100755
--- a/frappe/docs/user/en/guides/deployment/email-notifications-for-failed-background-jobs.md
+++ b/frappe/docs/user/en/guides/deployment/email-notifications-for-failed-background-jobs.md
@@ -1,3 +1,5 @@
+# Email Notifications For Failed Background Jobs
+
Frappe handles failure of jobs in the following way,
1) If a job fails, (raises exception), it's logged in Scheduler Log and logs/worker.error.log.
2) Keeps a lock file and would not run anymore if lock file is there.
3) Raises LockTimeoutError in case the lock file is more than 10 minutes old.
diff --git a/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md b/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md
index 441fa64ab0..ad8cc36623 100755
--- a/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md
+++ b/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md
@@ -1,3 +1,5 @@
+# How To Enable Social Logins
+
Use Facebook, Google or GitHub authentication to login to Frappe, and your users will be spared from remembering another password.
The system uses the **Email Address** supplied by these services to **match with an existing user** in Frappe. If no such user is found, **a new user is created** of the default type **Website User**, if Signup is not disabled in Website Settings. Any System Manager can later change the user type from **Website User** to **System User**, so that the user can access the Desktop.
diff --git a/frappe/docs/user/en/guides/deployment/how-to-migrate-doctype-changes-to-production.md b/frappe/docs/user/en/guides/deployment/how-to-migrate-doctype-changes-to-production.md
index 35a15645ab..4bf2ab9351 100755
--- a/frappe/docs/user/en/guides/deployment/how-to-migrate-doctype-changes-to-production.md
+++ b/frappe/docs/user/en/guides/deployment/how-to-migrate-doctype-changes-to-production.md
@@ -1,3 +1,5 @@
+# How To Migrate Doctype Changes To Production
+
#### 1. DocType / Schema Changes
If you are in `developer_mode`, the `.json` files for each **DocType** are automatically updated.
diff --git a/frappe/docs/user/en/guides/desk/formatter_for_link_fields.md b/frappe/docs/user/en/guides/desk/formatter_for_link_fields.md
index ceb2a4474c..586477f32e 100644
--- a/frappe/docs/user/en/guides/desk/formatter_for_link_fields.md
+++ b/frappe/docs/user/en/guides/desk/formatter_for_link_fields.md
@@ -1,3 +1,5 @@
+# Formatter For Link Fields
+
In case where a code and a name is maintained for an entity, (for example for Employee there may be an Employee Code and Employee Name) and we want to show both the ID and name in a link field, we can make a formatter.
#### Example:
diff --git a/frappe/docs/user/en/guides/portal-development/adding-pages.md b/frappe/docs/user/en/guides/portal-development/adding-pages.md
index c8bdd53552..c9cd0191c3 100755
--- a/frappe/docs/user/en/guides/portal-development/adding-pages.md
+++ b/frappe/docs/user/en/guides/portal-development/adding-pages.md
@@ -13,7 +13,7 @@ Either file must be present for the system to make this a valid folder to build
### Markdown
# This is a title
-
+
This is some page content
a [link](/link/to/page)
diff --git a/frappe/docs/user/en/guides/reports-and-printing/getting-information-from-another-document-in-print-format.md b/frappe/docs/user/en/guides/reports-and-printing/getting-information-from-another-document-in-print-format.md
index 321028d7af..afe87c04f8 100755
--- a/frappe/docs/user/en/guides/reports-and-printing/getting-information-from-another-document-in-print-format.md
+++ b/frappe/docs/user/en/guides/reports-and-printing/getting-information-from-another-document-in-print-format.md
@@ -1,3 +1,5 @@
+# Getting Information From Another Document In Print Format
+
In a print format, you can get data from another document. For example in if you have a fields called `sales_order` in Sales Invoice, then you can get the sales order details using `frappe.get_doc`:
{% raw %}
diff --git a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md
index 1e22757d7e..32ed2a016e 100755
--- a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md
+++ b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md
@@ -1,3 +1,5 @@
+# How To Make Query Report
+
You can create tabulated reports using complex SQL queries by creating a new Report. These reports can be created by a System Manager and are stored in the Database
> Note: You will need System Manager Permissions for this.
diff --git a/frappe/docs/user/en/guides/reports-and-printing/where-do-i-find-standard-print-formats.md b/frappe/docs/user/en/guides/reports-and-printing/where-do-i-find-standard-print-formats.md
index 00e351c615..c1816751dd 100755
--- a/frappe/docs/user/en/guides/reports-and-printing/where-do-i-find-standard-print-formats.md
+++ b/frappe/docs/user/en/guides/reports-and-printing/where-do-i-find-standard-print-formats.md
@@ -1,3 +1,5 @@
+# Where Do I Find Standard Print Formats
+
Standard Print formats are auto generated from the layout of the DocType. You can customize the standard format by
diff --git a/frappe/docs/user/en/tutorial/form-client-scripting.md b/frappe/docs/user/en/tutorial/form-client-scripting.md
index a70b8475ff..d4673c55d4 100755
--- a/frappe/docs/user/en/tutorial/form-client-scripting.md
+++ b/frappe/docs/user/en/tutorial/form-client-scripting.md
@@ -1,3 +1,5 @@
+# Form Client Scripting
+
## Scripting Forms
Now we have created a basic system that works out of the box without us having to write any code. Let us now write some scripts to make the application richer and add validations so that the user does not enter wrong data.
diff --git a/frappe/docs/user/es/bench/guides/diagnosing-the-scheduler.md b/frappe/docs/user/es/bench/guides/diagnosing-the-scheduler.md
index d1317c9bcc..18faa2fbe2 100644
--- a/frappe/docs/user/es/bench/guides/diagnosing-the-scheduler.md
+++ b/frappe/docs/user/es/bench/guides/diagnosing-the-scheduler.md
@@ -1,3 +1,5 @@
+# Diagnosing The Scheduler
+
En caso que estes experimentando inconvenientes con las tareas programadas, puedes ejecutar varios comandos para diagnosticar el problema.
diff --git a/frappe/docs/user/es/bench/guides/index.md b/frappe/docs/user/es/bench/guides/index.md
index 0dff60b400..8ab035a2f5 100644
--- a/frappe/docs/user/es/bench/guides/index.md
+++ b/frappe/docs/user/es/bench/guides/index.md
@@ -1 +1,5 @@
+# Guides
+
+
+
{index}
\ No newline at end of file
diff --git a/frappe/docs/user/es/bench/guides/manual-setup.md b/frappe/docs/user/es/bench/guides/manual-setup.md
index e07c56433c..aa60dc61a6 100644
--- a/frappe/docs/user/es/bench/guides/manual-setup.md
+++ b/frappe/docs/user/es/bench/guides/manual-setup.md
@@ -1,3 +1,5 @@
+# Manual Setup
+
Instalación Manual
--------------
diff --git a/frappe/docs/user/es/bench/guides/setup-multitenancy.md b/frappe/docs/user/es/bench/guides/setup-multitenancy.md
index f663704521..ca7469f1fd 100644
--- a/frappe/docs/user/es/bench/guides/setup-multitenancy.md
+++ b/frappe/docs/user/es/bench/guides/setup-multitenancy.md
@@ -1,3 +1,5 @@
+# Setup Multitenancy
+
Asumiento que tiene su primer site corriendo y ha realizado los
[pasos para producción](setup-production.html), esta sección explica como montar su segundo site (y más).
Su primer site se configuró como el site por defecto de forma automática. Puedes cambiarlo ejecutando el comando,
diff --git a/frappe/docs/user/es/bench/guides/setup-production.md b/frappe/docs/user/es/bench/guides/setup-production.md
index 2ab7e290dc..f97c582bd0 100644
--- a/frappe/docs/user/es/bench/guides/setup-production.md
+++ b/frappe/docs/user/es/bench/guides/setup-production.md
@@ -1,3 +1,5 @@
+# Setup Production
+
Puedes configurar el bench para producción configurando dos parametros, Supervisor y nginx. Si quieres volver a ponerlo en desarrollo debes ver [estos comandos](https://github.com/frappe/bench/wiki/Stopping-Production-and-starting-Development)
####Configuración para producción facíl
diff --git a/frappe/docs/user/es/bench/index.md b/frappe/docs/user/es/bench/index.md
index ccd28db145..24baef4875 100644
--- a/frappe/docs/user/es/bench/index.md
+++ b/frappe/docs/user/es/bench/index.md
@@ -1 +1,5 @@
+# Bench
+
+
+
{index}
diff --git a/frappe/docs/user/es/bench/resources/background-services.md b/frappe/docs/user/es/bench/resources/background-services.md
index 093d666e3a..5145897996 100644
--- a/frappe/docs/user/es/bench/resources/background-services.md
+++ b/frappe/docs/user/es/bench/resources/background-services.md
@@ -1,3 +1,5 @@
+# Background Services
+
Servicios Externos
-----------------
diff --git a/frappe/docs/user/es/bench/resources/bench-commands-cheatsheet.md b/frappe/docs/user/es/bench/resources/bench-commands-cheatsheet.md
index e816124fe4..c5277c45bc 100644
--- a/frappe/docs/user/es/bench/resources/bench-commands-cheatsheet.md
+++ b/frappe/docs/user/es/bench/resources/bench-commands-cheatsheet.md
@@ -1,3 +1,5 @@
+# Bench Commands Cheatsheet
+
### Uso General
* `bench --version` - Muestra la versión del bench
* `bench src` - Muestra el directorio repo del bench
diff --git a/frappe/docs/user/es/bench/resources/bench-procfile.md b/frappe/docs/user/es/bench/resources/bench-procfile.md
index c80bf03481..dc357bdd4e 100644
--- a/frappe/docs/user/es/bench/resources/bench-procfile.md
+++ b/frappe/docs/user/es/bench/resources/bench-procfile.md
@@ -1,3 +1,5 @@
+# Bench Procfile
+
`bench start` usa [honcho](http://honcho.readthedocs.org) para manejar múltiples procesos en **developer mode**.
### Procesos
diff --git a/frappe/docs/user/es/bench/resources/index.md b/frappe/docs/user/es/bench/resources/index.md
index 0dff60b400..48852466ed 100644
--- a/frappe/docs/user/es/bench/resources/index.md
+++ b/frappe/docs/user/es/bench/resources/index.md
@@ -1 +1,5 @@
+# Resources
+
+
+
{index}
\ No newline at end of file
diff --git a/frappe/docs/user/es/tutorial/form-client-scripting.md b/frappe/docs/user/es/tutorial/form-client-scripting.md
index b0c4b97f21..26f5410b83 100644
--- a/frappe/docs/user/es/tutorial/form-client-scripting.md
+++ b/frappe/docs/user/es/tutorial/form-client-scripting.md
@@ -1,3 +1,5 @@
+# Form Client Scripting
+
## Añadir Scripts a nuestros formularios
Ya que tenemos creado el sistema básico que funciona sin problemas sin escribir una linea de código. Vamos a escribir algunos scripts
diff --git a/frappe/docs/user/fr/tutorial/form-client-scripting.md b/frappe/docs/user/fr/tutorial/form-client-scripting.md
index f2f2e21894..a6ab64a60c 100644
--- a/frappe/docs/user/fr/tutorial/form-client-scripting.md
+++ b/frappe/docs/user/fr/tutorial/form-client-scripting.md
@@ -1,3 +1,5 @@
+# Form Client Scripting
+
## Codes des formulaires
Jusqu'a maintenant, nous avons développé un système basique qui fonctionne parfaitement sans avoir eu besoin d'écrire une
diff --git a/frappe/docs/user/pt/tutorial/form-client-scripting.md b/frappe/docs/user/pt/tutorial/form-client-scripting.md
index c37196757f..faf453c57a 100755
--- a/frappe/docs/user/pt/tutorial/form-client-scripting.md
+++ b/frappe/docs/user/pt/tutorial/form-client-scripting.md
@@ -1,3 +1,5 @@
+# Form Client Scripting
+
## Escrevendo script de formulários
Até agora nós criamos um sistema básico que funciona fora da caixa, sem ter que escrever nenhum código. Vamos agora escrever alguns scripts para tornar a aplicação mais rica e adicionar validações de formulários para o usuário não inserir dados incorretos.
diff --git a/frappe/website/purifycss.py b/frappe/website/purifycss.py
index 00ca06b0c4..faf5b8b94b 100644
--- a/frappe/website/purifycss.py
+++ b/frappe/website/purifycss.py
@@ -1,8 +1,18 @@
+'''
+Check for unused CSS Classes
+
+sUpdate source and target apps below and run from CLI
+
+ bench --site [sitename] execute frappe.website.purifycss.purify.css
+
+'''
+
import frappe, re, os
+source = frappe.get_app_path('frappe_theme', 'public', 'less', 'frappe_theme.less')
+target_apps = ['erpnext_com', 'frappe_io', 'translator', 'chart_of_accounts_builder', 'frappe_theme']
+
def purifycss():
- source = frappe.get_app_path('frappe_theme', 'public', 'less', 'frappe_theme.less')
- target_apps = ['erpnext_com', 'frappe_io', 'translator', 'chart_of_accounts_builder', 'frappe_theme']
with open(source, 'r') as f:
src = f.read()
diff --git a/frappe/website/utils.py b/frappe/website/utils.py
index 9424ec722e..efd50295f3 100644
--- a/frappe/website/utils.py
+++ b/frappe/website/utils.py
@@ -285,3 +285,24 @@ def extract_title(source, path):
title = os.path.basename(path.rsplit('.', )[0].rstrip('/')).replace('_', ' ').replace('-', ' ').title()
return title
+
+def add_missing_headers():
+ '''Walk and add missing headers in docs (to be called from bench execute)'''
+ path = frappe.get_app_path('erpnext', 'docs')
+ for basepath, folders, files in os.walk(path):
+ for fname in files:
+ if fname.endswith('.md'):
+ with open(os.path.join(basepath, fname), 'r') as f:
+ content = frappe.as_unicode(f.read())
+
+ if not content.startswith('# ') and not '' in content:
+ with open(os.path.join(basepath, fname), 'w') as f:
+ if fname=='index.md':
+ fname = os.path.basename(basepath)
+ else:
+ fname = fname[:-3]
+ h = fname.replace('_', ' ').replace('-', ' ').title()
+ print h
+ content = '# {0}\n\n'.format(h) + content
+ f.write(content.encode('utf-8'))
+