diff --git a/erpnext/docs/assets/img/accounts/account-settings.png b/erpnext/docs/assets/img/accounts/account-settings.png
new file mode 100644
index 0000000..943aa3d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/account-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/accounts-receivable.png b/erpnext/docs/assets/img/accounts/accounts-receivable.png
new file mode 100644
index 0000000..b03f254
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/accounts-receivable.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/advance-payment-1.png b/erpnext/docs/assets/img/accounts/advance-payment-1.png
new file mode 100644
index 0000000..17a8b30
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/advance-payment-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/advance-payment-2.png b/erpnext/docs/assets/img/accounts/advance-payment-2.png
new file mode 100644
index 0000000..373220d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/advance-payment-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/advance-payment-3.png b/erpnext/docs/assets/img/accounts/advance-payment-3.png
new file mode 100644
index 0000000..d35329e
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/advance-payment-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/bank-reconciliation.png b/erpnext/docs/assets/img/accounts/bank-reconciliation.png
new file mode 100644
index 0000000..86872d9
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/bank-reconciliation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/chart-of-accounts-1.png b/erpnext/docs/assets/img/accounts/chart-of-accounts-1.png
new file mode 100644
index 0000000..50ef62d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/chart-of-accounts-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/chart-of-accounts-2.png b/erpnext/docs/assets/img/accounts/chart-of-accounts-2.png
new file mode 100644
index 0000000..490d248
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/chart-of-accounts-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/chart-of-accounts-3.png b/erpnext/docs/assets/img/accounts/chart-of-accounts-3.png
new file mode 100644
index 0000000..10fe4a4
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/chart-of-accounts-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/credit-limit-1.png b/erpnext/docs/assets/img/accounts/credit-limit-1.png
new file mode 100644
index 0000000..60d8e1f
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/credit-limit-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/credit-limit-2.png b/erpnext/docs/assets/img/accounts/credit-limit-2.png
new file mode 100644
index 0000000..916daa7
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/credit-limit-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/financial-analytics-bl.png b/erpnext/docs/assets/img/accounts/financial-analytics-bl.png
new file mode 100644
index 0000000..1b01c3d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/financial-analytics-bl.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/financial-analytics-pl.png b/erpnext/docs/assets/img/accounts/financial-analytics-pl.png
new file mode 100644
index 0000000..ad754c1
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/financial-analytics-pl.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/fiscal-year.png b/erpnext/docs/assets/img/accounts/fiscal-year.png
new file mode 100644
index 0000000..2dbf0a2
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/fiscal-year.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/general-ledger.png b/erpnext/docs/assets/img/accounts/general-ledger.png
new file mode 100644
index 0000000..b787119
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/journal-entry.png b/erpnext/docs/assets/img/accounts/journal-entry.png
new file mode 100644
index 0000000..d4a4e21
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/journal-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/make-payment.png b/erpnext/docs/assets/img/accounts/make-payment.png
new file mode 100644
index 0000000..917432e
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/make-payment.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/account.png b/erpnext/docs/assets/img/accounts/multi-currency/account.png
new file mode 100644
index 0000000..7973e8d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/account.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/accounts-receivable.png b/erpnext/docs/assets/img/accounts/multi-currency/accounts-receivable.png
new file mode 100644
index 0000000..74f3e5c
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/accounts-receivable.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/bank-transfer.png b/erpnext/docs/assets/img/accounts/multi-currency/bank-transfer.png
new file mode 100644
index 0000000..6af0848
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/bank-transfer.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/chart-of-accounts.png b/erpnext/docs/assets/img/accounts/multi-currency/chart-of-accounts.png
new file mode 100644
index 0000000..f4a62b5
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/chart-of-accounts.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/customer.png b/erpnext/docs/assets/img/accounts/multi-currency/customer.png
new file mode 100644
index 0000000..35408c9
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/customer.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/general-ledger.png b/erpnext/docs/assets/img/accounts/multi-currency/general-ledger.png
new file mode 100644
index 0000000..de5e4d0
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-multi-currency.png b/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-multi-currency.png
new file mode 100644
index 0000000..17f3a71
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-multi-currency.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-row.png b/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-row.png
new file mode 100644
index 0000000..a27287d
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/journal-entry-row.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/payment-entry.png b/erpnext/docs/assets/img/accounts/multi-currency/payment-entry.png
new file mode 100644
index 0000000..3bfe102
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/payment-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/multi-currency/sales-invoice.png b/erpnext/docs/assets/img/accounts/multi-currency/sales-invoice.png
new file mode 100644
index 0000000..7b576ab
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/multi-currency/sales-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/new-bank-entry.png b/erpnext/docs/assets/img/accounts/new-bank-entry.png
new file mode 100644
index 0000000..803797b
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/new-bank-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/opening-account-1.png b/erpnext/docs/assets/img/accounts/opening-account-1.png
new file mode 100644
index 0000000..2e19363
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/opening-account-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/payment-reconcile-tool.png b/erpnext/docs/assets/img/accounts/payment-reconcile-tool.png
new file mode 100644
index 0000000..c507f19
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/payment-reconcile-tool.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/payment-tool-1.png b/erpnext/docs/assets/img/accounts/payment-tool-1.png
new file mode 100644
index 0000000..9e6d625
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/payment-tool-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/payment-tool-2.png b/erpnext/docs/assets/img/accounts/payment-tool-2.png
new file mode 100644
index 0000000..535e0a2
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/payment-tool-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/payment-tool-3.png b/erpnext/docs/assets/img/accounts/payment-tool-3.png
new file mode 100644
index 0000000..19ac8fa
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/payment-tool-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/period-closing-voucher.png b/erpnext/docs/assets/img/accounts/period-closing-voucher.png
new file mode 100644
index 0000000..2e9078f
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/period-closing-voucher.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/purchase-invoice.png b/erpnext/docs/assets/img/accounts/purchase-invoice.png
new file mode 100644
index 0000000..0235520
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/purchase-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/sales-invoice.png b/erpnext/docs/assets/img/accounts/sales-invoice.png
new file mode 100644
index 0000000..421e398
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/sales-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/sales-register.png b/erpnext/docs/assets/img/accounts/sales-register.png
new file mode 100644
index 0000000..5dc7f1a
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/sales-register.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/tax-rule-1.png b/erpnext/docs/assets/img/accounts/tax-rule-1.png
new file mode 100644
index 0000000..7d3c22c
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/tax-rule-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/tax-rule-2.png b/erpnext/docs/assets/img/accounts/tax-rule-2.png
new file mode 100644
index 0000000..a0dae13
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/tax-rule-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/tax-rule.png b/erpnext/docs/assets/img/accounts/tax-rule.png
new file mode 100644
index 0000000..a82741f
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/tax-rule.png
Binary files differ
diff --git a/erpnext/docs/assets/img/accounts/trial-balance.png b/erpnext/docs/assets/img/accounts/trial-balance.png
new file mode 100644
index 0000000..d96d439
--- /dev/null
+++ b/erpnext/docs/assets/img/accounts/trial-balance.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/buying-settings.png b/erpnext/docs/assets/img/buying/buying-settings.png
new file mode 100644
index 0000000..946776e
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/buying-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/material-request.png b/erpnext/docs/assets/img/buying/material-request.png
new file mode 100644
index 0000000..34005b2
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/material-request.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/purchase-order-uom.png b/erpnext/docs/assets/img/buying/purchase-order-uom.png
new file mode 100644
index 0000000..f5c062d
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/purchase-order-uom.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/purchase-order.png b/erpnext/docs/assets/img/buying/purchase-order.png
new file mode 100644
index 0000000..846164d
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/purchase-order.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/supplier-master.png b/erpnext/docs/assets/img/buying/supplier-master.png
new file mode 100644
index 0000000..7c6a950
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/supplier-master.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/supplier-quotation.png b/erpnext/docs/assets/img/buying/supplier-quotation.png
new file mode 100644
index 0000000..a07b4cb
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/supplier-quotation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/buying/supplier-type.png b/erpnext/docs/assets/img/buying/supplier-type.png
new file mode 100644
index 0000000..a9641c3
--- /dev/null
+++ b/erpnext/docs/assets/img/buying/supplier-type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/campaign-new-lead.png b/erpnext/docs/assets/img/crm/campaign-new-lead.png
new file mode 100644
index 0000000..e73bcd6
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/campaign-new-lead.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/campaign-view-leads.png b/erpnext/docs/assets/img/crm/campaign-view-leads.png
new file mode 100644
index 0000000..3288787
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/campaign-view-leads.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/campaign.png b/erpnext/docs/assets/img/crm/campaign.png
new file mode 100644
index 0000000..475c1c4
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/campaign.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/contact-from-cust.png b/erpnext/docs/assets/img/crm/contact-from-cust.png
new file mode 100644
index 0000000..09a9c7f
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/contact-from-cust.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/contact.png b/erpnext/docs/assets/img/crm/contact.png
new file mode 100644
index 0000000..3c63ccf
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/contact.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/customer-group-tree.png b/erpnext/docs/assets/img/crm/customer-group-tree.png
new file mode 100644
index 0000000..11bb9a9
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/customer-group-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/customer.png b/erpnext/docs/assets/img/crm/customer.png
new file mode 100644
index 0000000..d4357a7
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/customer.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/lead-to-opportunity.png b/erpnext/docs/assets/img/crm/lead-to-opportunity.png
new file mode 100644
index 0000000..5c82dac
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/lead-to-opportunity.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/lead.png b/erpnext/docs/assets/img/crm/lead.png
new file mode 100644
index 0000000..2b82464
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/lead.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/newsletter-new.png b/erpnext/docs/assets/img/crm/newsletter-new.png
new file mode 100644
index 0000000..da8f6a3
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/newsletter-new.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/newsletter-test.png b/erpnext/docs/assets/img/crm/newsletter-test.png
new file mode 100644
index 0000000..0ceb8ed
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/newsletter-test.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/opportunity.png b/erpnext/docs/assets/img/crm/opportunity.png
new file mode 100644
index 0000000..fb3747a
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/opportunity.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/sales-person-tree.png b/erpnext/docs/assets/img/crm/sales-person-tree.png
new file mode 100644
index 0000000..0cd79a6
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/sales-person-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/img/crm/territory-tree.png b/erpnext/docs/assets/img/crm/territory-tree.png
new file mode 100644
index 0000000..b027394
--- /dev/null
+++ b/erpnext/docs/assets/img/crm/territory-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/img/customize/customize-title.gif b/erpnext/docs/assets/img/customize/customize-title.gif
new file mode 100644
index 0000000..7881a10
--- /dev/null
+++ b/erpnext/docs/assets/img/customize/customize-title.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/customize/editable-title.gif b/erpnext/docs/assets/img/customize/editable-title.gif
new file mode 100644
index 0000000..4eda213
--- /dev/null
+++ b/erpnext/docs/assets/img/customize/editable-title.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/appraisal-employee.png b/erpnext/docs/assets/img/human-resources/appraisal-employee.png
new file mode 100644
index 0000000..5c8f5dd
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/appraisal-employee.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/appraisal.png b/erpnext/docs/assets/img/human-resources/appraisal.png
new file mode 100644
index 0000000..b3f769c
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/appraisal.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/attendence-upload.png b/erpnext/docs/assets/img/human-resources/attendence-upload.png
new file mode 100644
index 0000000..d3394c2
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/attendence-upload.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/attendence.png b/erpnext/docs/assets/img/human-resources/attendence.png
new file mode 100644
index 0000000..880c9a4
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/attendence.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/branch.png b/erpnext/docs/assets/img/human-resources/branch.png
new file mode 100644
index 0000000..0c5846b
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/branch.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/deduction-type.png b/erpnext/docs/assets/img/human-resources/deduction-type.png
new file mode 100644
index 0000000..86aba4c
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/deduction-type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/department.png b/erpnext/docs/assets/img/human-resources/department.png
new file mode 100644
index 0000000..78cdcc9
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/department.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/designation.png b/erpnext/docs/assets/img/human-resources/designation.png
new file mode 100644
index 0000000..f625cc8
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/designation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/earning-type.png b/erpnext/docs/assets/img/human-resources/earning-type.png
new file mode 100644
index 0000000..ca5f484
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/earning-type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/email-account.png b/erpnext/docs/assets/img/human-resources/email-account.png
new file mode 100644
index 0000000..089891e
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/email-account.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employee-birthday-report.png b/erpnext/docs/assets/img/human-resources/employee-birthday-report.png
new file mode 100644
index 0000000..c6ca377
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employee-birthday-report.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employee-information-report.png b/erpnext/docs/assets/img/human-resources/employee-information-report.png
new file mode 100644
index 0000000..dc276f3
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employee-information-report.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employee-leave-approver.png b/erpnext/docs/assets/img/human-resources/employee-leave-approver.png
new file mode 100644
index 0000000..2ae98d7
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employee-leave-approver.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employee-leave-balance-report.png b/erpnext/docs/assets/img/human-resources/employee-leave-balance-report.png
new file mode 100644
index 0000000..5af5ae7
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employee-leave-balance-report.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employee.png b/erpnext/docs/assets/img/human-resources/employee.png
new file mode 100644
index 0000000..ec2e70e
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employee.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/employment-type.png b/erpnext/docs/assets/img/human-resources/employment-type.png
new file mode 100644
index 0000000..eb44807
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/employment-type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/expense_claim.png b/erpnext/docs/assets/img/human-resources/expense_claim.png
new file mode 100644
index 0000000..ddca100
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/expense_claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/holiday-list.png b/erpnext/docs/assets/img/human-resources/holiday-list.png
new file mode 100644
index 0000000..94dbee8
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/holiday-list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/hr-settings.png b/erpnext/docs/assets/img/human-resources/hr-settings.png
new file mode 100644
index 0000000..fe2e735
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/hr-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/job-applicant.png b/erpnext/docs/assets/img/human-resources/job-applicant.png
new file mode 100644
index 0000000..17a372b
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/job-applicant.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/job-opening.png b/erpnext/docs/assets/img/human-resources/job-opening.png
new file mode 100644
index 0000000..148193a
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/job-opening.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/leave-allocation-tool.png b/erpnext/docs/assets/img/human-resources/leave-allocation-tool.png
new file mode 100644
index 0000000..867b8fb
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/leave-allocation-tool.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/leave-allocation.png b/erpnext/docs/assets/img/human-resources/leave-allocation.png
new file mode 100644
index 0000000..4a154e9
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/leave-allocation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/leave-application.png b/erpnext/docs/assets/img/human-resources/leave-application.png
new file mode 100644
index 0000000..761e76b
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/leave-application.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/leave-type.png b/erpnext/docs/assets/img/human-resources/leave-type.png
new file mode 100644
index 0000000..4f04291
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/leave-type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/monthly-attendance-sheet-report.png b/erpnext/docs/assets/img/human-resources/monthly-attendance-sheet-report.png
new file mode 100644
index 0000000..db5191d
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/monthly-attendance-sheet-report.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/monthly-salary-register-report.png b/erpnext/docs/assets/img/human-resources/monthly-salary-register-report.png
new file mode 100644
index 0000000..7d2b032
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/monthly-salary-register-report.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/offer-letter-print.png b/erpnext/docs/assets/img/human-resources/offer-letter-print.png
new file mode 100644
index 0000000..5d63750
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/offer-letter-print.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/offer-letter.png b/erpnext/docs/assets/img/human-resources/offer-letter.png
new file mode 100644
index 0000000..e3d5671
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/offer-letter.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/process-payroll.png b/erpnext/docs/assets/img/human-resources/process-payroll.png
new file mode 100644
index 0000000..ebbd9ae
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/process-payroll.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/salary-slip.png b/erpnext/docs/assets/img/human-resources/salary-slip.png
new file mode 100644
index 0000000..d3f77cd
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/salary-slip.png
Binary files differ
diff --git a/erpnext/docs/assets/img/human-resources/salary-structure.png b/erpnext/docs/assets/img/human-resources/salary-structure.png
new file mode 100644
index 0000000..af850ee
--- /dev/null
+++ b/erpnext/docs/assets/img/human-resources/salary-structure.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-FG-update-qty.png b/erpnext/docs/assets/img/manufacturing/PO-FG-update-qty.png
new file mode 100644
index 0000000..1ee59ec
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-FG-update-qty.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-FG-update.png b/erpnext/docs/assets/img/manufacturing/PO-FG-update.png
new file mode 100644
index 0000000..b07a7cf
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-FG-update.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-SE-for-material-transfer.png b/erpnext/docs/assets/img/manufacturing/PO-SE-for-material-transfer.png
new file mode 100644
index 0000000..74e1f64
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-SE-for-material-transfer.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-TL-buttons.png b/erpnext/docs/assets/img/manufacturing/PO-TL-buttons.png
new file mode 100644
index 0000000..e9b8453
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-TL-buttons.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-material-transfer-qty.png b/erpnext/docs/assets/img/manufacturing/PO-material-transfer-qty.png
new file mode 100644
index 0000000..e8dea02
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-material-transfer-qty.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-material-transfer-updated.png b/erpnext/docs/assets/img/manufacturing/PO-material-transfer-updated.png
new file mode 100644
index 0000000..5c20ff8
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-material-transfer-updated.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-material-transfer.png b/erpnext/docs/assets/img/manufacturing/PO-material-transfer.png
new file mode 100644
index 0000000..dbdc303
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-material-transfer.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-operations-make-tl.png b/erpnext/docs/assets/img/manufacturing/PO-operations-make-tl.png
new file mode 100644
index 0000000..1bc2720
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-operations-make-tl.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-operations.png b/erpnext/docs/assets/img/manufacturing/PO-operations.png
new file mode 100644
index 0000000..6916891
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-operations.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-reassigning-operations.png b/erpnext/docs/assets/img/manufacturing/PO-reassigning-operations.png
new file mode 100644
index 0000000..0970a54
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-reassigning-operations.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-stop-confirm.png b/erpnext/docs/assets/img/manufacturing/PO-stop-confirm.png
new file mode 100644
index 0000000..ab8b7da
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-stop-confirm.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/PO-stop.png b/erpnext/docs/assets/img/manufacturing/PO-stop.png
new file mode 100644
index 0000000..c486a68
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/PO-stop.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom-costing.png b/erpnext/docs/assets/img/manufacturing/bom-costing.png
new file mode 100644
index 0000000..6cb6a3f
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom-costing.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom-exploded.png b/erpnext/docs/assets/img/manufacturing/bom-exploded.png
new file mode 100644
index 0000000..c71e6d9
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom-exploded.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom-operations.png b/erpnext/docs/assets/img/manufacturing/bom-operations.png
new file mode 100644
index 0000000..04e8a12
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom-operations.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom-replace-tool.png b/erpnext/docs/assets/img/manufacturing/bom-replace-tool.png
new file mode 100644
index 0000000..51ac993
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom-replace-tool.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom-update-cost.png b/erpnext/docs/assets/img/manufacturing/bom-update-cost.png
new file mode 100644
index 0000000..6d467d0
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom-update-cost.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/bom.png b/erpnext/docs/assets/img/manufacturing/bom.png
new file mode 100644
index 0000000..0adf255
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/bom.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/manufacturing-settings.png b/erpnext/docs/assets/img/manufacturing/manufacturing-settings.png
new file mode 100644
index 0000000..18b28dd
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/manufacturing-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/manufacturing.png b/erpnext/docs/assets/img/manufacturing/manufacturing.png
new file mode 100644
index 0000000..75d7d3c
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/manufacturing.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/operation.png b/erpnext/docs/assets/img/manufacturing/operation.png
new file mode 100644
index 0000000..4cd045c
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/operation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/ppt-create-material-request.png b/erpnext/docs/assets/img/manufacturing/ppt-create-material-request.png
new file mode 100644
index 0000000..35fba3a
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/ppt-create-material-request.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/ppt-create-production-order.png b/erpnext/docs/assets/img/manufacturing/ppt-create-production-order.png
new file mode 100644
index 0000000..26185ac
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/ppt-create-production-order.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/ppt-get-item.png b/erpnext/docs/assets/img/manufacturing/ppt-get-item.png
new file mode 100644
index 0000000..e89efea
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/ppt-get-item.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/ppt-get-sales-orders.png b/erpnext/docs/assets/img/manufacturing/ppt-get-sales-orders.png
new file mode 100644
index 0000000..379e007
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/ppt-get-sales-orders.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/ppt.png b/erpnext/docs/assets/img/manufacturing/ppt.png
new file mode 100644
index 0000000..f5018b7
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/ppt.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/production-order.png b/erpnext/docs/assets/img/manufacturing/production-order.png
new file mode 100644
index 0000000..d1e7966
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/production-order.png
Binary files differ
diff --git a/erpnext/docs/assets/img/manufacturing/workstation.png b/erpnext/docs/assets/img/manufacturing/workstation.png
new file mode 100644
index 0000000..df6486b
--- /dev/null
+++ b/erpnext/docs/assets/img/manufacturing/workstation.png
Binary files differ
diff --git a/erpnext/docs/assets/img/pos-setting/pos-setting.png b/erpnext/docs/assets/img/pos-setting/pos-setting.png
new file mode 100644
index 0000000..6061199
--- /dev/null
+++ b/erpnext/docs/assets/img/pos-setting/pos-setting.png
Binary files differ
diff --git a/erpnext/docs/assets/img/price-list/price-list.png b/erpnext/docs/assets/img/price-list/price-list.png
new file mode 100644
index 0000000..93a0183
--- /dev/null
+++ b/erpnext/docs/assets/img/price-list/price-list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/activity_cost.png b/erpnext/docs/assets/img/project/activity_cost.png
new file mode 100644
index 0000000..d7468a0
--- /dev/null
+++ b/erpnext/docs/assets/img/project/activity_cost.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/activity_type.png b/erpnext/docs/assets/img/project/activity_type.png
new file mode 100644
index 0000000..e10cce1
--- /dev/null
+++ b/erpnext/docs/assets/img/project/activity_type.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project.png b/erpnext/docs/assets/img/project/project.png
new file mode 100644
index 0000000..c6bcd92
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_cost_center.png b/erpnext/docs/assets/img/project/project_cost_center.png
new file mode 100644
index 0000000..09bd557
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_cost_center.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_costing.png b/erpnext/docs/assets/img/project/project_costing.png
new file mode 100644
index 0000000..997e613
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_costing.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_expense_claim_link.png b/erpnext/docs/assets/img/project/project_expense_claim_link.png
new file mode 100644
index 0000000..077cea1
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_expense_claim_link.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_gantt_chart.png b/erpnext/docs/assets/img/project/project_gantt_chart.png
new file mode 100644
index 0000000..3eba443
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_gantt_chart.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_sales_order.png b/erpnext/docs/assets/img/project/project_sales_order.png
new file mode 100644
index 0000000..ff4030d
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_sales_order.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_task.png b/erpnext/docs/assets/img/project/project_task.png
new file mode 100644
index 0000000..88f1e68
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_task.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_task_grid.png b/erpnext/docs/assets/img/project/project_task_grid.png
new file mode 100644
index 0000000..935fba6
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_task_grid.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_task_list.png b/erpnext/docs/assets/img/project/project_task_list.png
new file mode 100644
index 0000000..2a59caf
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_task_list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_time_log_link.png b/erpnext/docs/assets/img/project/project_time_log_link.png
new file mode 100644
index 0000000..08ac36c
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_time_log_link.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_time_log_list.png b/erpnext/docs/assets/img/project/project_time_log_list.png
new file mode 100644
index 0000000..3b3724b
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_time_log_list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_total_expense_claim.png b/erpnext/docs/assets/img/project/project_total_expense_claim.png
new file mode 100644
index 0000000..cbd3c01
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_total_expense_claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_view_expense_claim.png b/erpnext/docs/assets/img/project/project_view_expense_claim.png
new file mode 100644
index 0000000..32056ca
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_view_expense_claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_view_gantt_chart.png b/erpnext/docs/assets/img/project/project_view_gantt_chart.png
new file mode 100644
index 0000000..7039a45
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_view_gantt_chart.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_view_task.png b/erpnext/docs/assets/img/project/project_view_task.png
new file mode 100644
index 0000000..dfdff8b
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_view_task.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/project_view_time_log.png b/erpnext/docs/assets/img/project/project_view_time_log.png
new file mode 100644
index 0000000..dbf184e
--- /dev/null
+++ b/erpnext/docs/assets/img/project/project_view_time_log.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task.png b/erpnext/docs/assets/img/project/task.png
new file mode 100644
index 0000000..6fe239d
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_depends_on.png b/erpnext/docs/assets/img/project/task_depends_on.png
new file mode 100644
index 0000000..2bbc393
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_depends_on.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_expense_claim_link.png b/erpnext/docs/assets/img/project/task_expense_claim_link.png
new file mode 100644
index 0000000..8583a74
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_expense_claim_link.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_status.png b/erpnext/docs/assets/img/project/task_status.png
new file mode 100644
index 0000000..c3424cb
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_status.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_time_log_link.png b/erpnext/docs/assets/img/project/task_time_log_link.png
new file mode 100644
index 0000000..d713b98
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_time_log_link.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_time_log_list.png b/erpnext/docs/assets/img/project/task_time_log_list.png
new file mode 100644
index 0000000..97218c1
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_time_log_list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_total_expense_claim.png b/erpnext/docs/assets/img/project/task_total_expense_claim.png
new file mode 100644
index 0000000..29fa6f9
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_total_expense_claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_view_expense_claim.png b/erpnext/docs/assets/img/project/task_view_expense_claim.png
new file mode 100644
index 0000000..efcb87f
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_view_expense_claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/task_view_time_log.png b/erpnext/docs/assets/img/project/task_view_time_log.png
new file mode 100644
index 0000000..4104842
--- /dev/null
+++ b/erpnext/docs/assets/img/project/task_view_time_log.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log.png b/erpnext/docs/assets/img/project/time_log.png
new file mode 100644
index 0000000..4d92a6c
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_batch.gif b/erpnext/docs/assets/img/project/time_log_batch.gif
new file mode 100644
index 0000000..35ff14d
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_batch.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_batch_make_invoice.png b/erpnext/docs/assets/img/project/time_log_batch_make_invoice.png
new file mode 100644
index 0000000..2ac4475
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_batch_make_invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_batch_sales_invoice.png b/erpnext/docs/assets/img/project/time_log_batch_sales_invoice.png
new file mode 100644
index 0000000..4fef5f2
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_batch_sales_invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_calendar_day.gif b/erpnext/docs/assets/img/project/time_log_calendar_day.gif
new file mode 100644
index 0000000..11deb23
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_calendar_day.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_calendar_week.gif b/erpnext/docs/assets/img/project/time_log_calendar_week.gif
new file mode 100644
index 0000000..8d81083
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_calendar_week.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_costing.png b/erpnext/docs/assets/img/project/time_log_costing.png
new file mode 100644
index 0000000..dda98f8
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_costing.png
Binary files differ
diff --git a/erpnext/docs/assets/img/project/time_log_view_calendar.png b/erpnext/docs/assets/img/project/time_log_view_calendar.png
new file mode 100644
index 0000000..0118dfb
--- /dev/null
+++ b/erpnext/docs/assets/img/project/time_log_view_calendar.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/make-SO-from-quote.png b/erpnext/docs/assets/img/selling/make-SO-from-quote.png
new file mode 100644
index 0000000..c3c6b38
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/make-SO-from-quote.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/make-quotation.gif b/erpnext/docs/assets/img/selling/make-quotation.gif
new file mode 100644
index 0000000..c707a70
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/make-quotation.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/make-quote-from-opp.png b/erpnext/docs/assets/img/selling/make-quote-from-opp.png
new file mode 100644
index 0000000..3acfa9a
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/make-quote-from-opp.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/make-so.gif b/erpnext/docs/assets/img/selling/make-so.gif
new file mode 100644
index 0000000..5edd19b
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/make-so.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/product-bundle.gif b/erpnext/docs/assets/img/selling/product-bundle.gif
new file mode 100644
index 0000000..a488e5d
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/product-bundle.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/product-bundle.png b/erpnext/docs/assets/img/selling/product-bundle.png
new file mode 100644
index 0000000..0264518
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/product-bundle.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/recurring-sales-order.png b/erpnext/docs/assets/img/selling/recurring-sales-order.png
new file mode 100644
index 0000000..c509333
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/recurring-sales-order.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/sales-partner-website.png b/erpnext/docs/assets/img/selling/sales-partner-website.png
new file mode 100644
index 0000000..3d84b10
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/sales-partner-website.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/sales-partner.png b/erpnext/docs/assets/img/selling/sales-partner.png
new file mode 100644
index 0000000..2c14edc
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/sales-partner.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/selling-settings.png b/erpnext/docs/assets/img/selling/selling-settings.png
new file mode 100644
index 0000000..345735b
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/selling-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/selling/shipping-rule.png b/erpnext/docs/assets/img/selling/shipping-rule.png
new file mode 100644
index 0000000..7cd9b46
--- /dev/null
+++ b/erpnext/docs/assets/img/selling/shipping-rule.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-1.png b/erpnext/docs/assets/img/setup-wizard/step-1.png
new file mode 100644
index 0000000..0a3c230
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-10.png b/erpnext/docs/assets/img/setup-wizard/step-10.png
new file mode 100644
index 0000000..4687999
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-10.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-2.png b/erpnext/docs/assets/img/setup-wizard/step-2.png
new file mode 100644
index 0000000..7330004
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-3.png b/erpnext/docs/assets/img/setup-wizard/step-3.png
new file mode 100644
index 0000000..7aac64a
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-4.png b/erpnext/docs/assets/img/setup-wizard/step-4.png
new file mode 100644
index 0000000..cee29fc
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-4.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-5.png b/erpnext/docs/assets/img/setup-wizard/step-5.png
new file mode 100644
index 0000000..a770f3e
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-5.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-6.png b/erpnext/docs/assets/img/setup-wizard/step-6.png
new file mode 100644
index 0000000..db2bf38
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-6.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-7.png b/erpnext/docs/assets/img/setup-wizard/step-7.png
new file mode 100644
index 0000000..02c6da6
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-7.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-8.png b/erpnext/docs/assets/img/setup-wizard/step-8.png
new file mode 100644
index 0000000..18f8d88
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-8.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup-wizard/step-9.png b/erpnext/docs/assets/img/setup-wizard/step-9.png
new file mode 100644
index 0000000..dced6e0
--- /dev/null
+++ b/erpnext/docs/assets/img/setup-wizard/step-9.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/auth-rule.png b/erpnext/docs/assets/img/setup/auth-rule.png
new file mode 100644
index 0000000..f6999cd
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/auth-rule.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/barcode-1.png b/erpnext/docs/assets/img/setup/barcode-1.png
new file mode 100644
index 0000000..c200a13
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/barcode-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/barcode-2.png b/erpnext/docs/assets/img/setup/barcode-2.png
new file mode 100644
index 0000000..6ea4529
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/barcode-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-adding-field.png b/erpnext/docs/assets/img/setup/customize/Doctype-adding-field.png
new file mode 100644
index 0000000..245ac5e
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-adding-field.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-all-fields.png b/erpnext/docs/assets/img/setup/customize/Doctype-all-fields.png
new file mode 100644
index 0000000..3a08267
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-all-fields.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-book-added.png b/erpnext/docs/assets/img/setup/customize/Doctype-book-added.png
new file mode 100644
index 0000000..1b5f643
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-book-added.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-list-view.png b/erpnext/docs/assets/img/setup/customize/Doctype-list-view.png
new file mode 100644
index 0000000..5edb604
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-list-view.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-naming.png b/erpnext/docs/assets/img/setup/customize/Doctype-naming.png
new file mode 100644
index 0000000..91ccf23
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-naming.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-other-options.png b/erpnext/docs/assets/img/setup/customize/Doctype-other-options.png
new file mode 100644
index 0000000..894b6b5
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-other-options.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-permissions.png b/erpnext/docs/assets/img/setup/customize/Doctype-permissions.png
new file mode 100644
index 0000000..9f9bfcc
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/Doctype-save.png b/erpnext/docs/assets/img/setup/customize/Doctype-save.png
new file mode 100644
index 0000000..5d11650
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/Doctype-save.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/doctype-basics.png b/erpnext/docs/assets/img/setup/customize/doctype-basics.png
new file mode 100644
index 0000000..2fbede1
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/doctype-basics.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/customize/doctype-field-naming.png b/erpnext/docs/assets/img/setup/customize/doctype-field-naming.png
new file mode 100644
index 0000000..7f91637
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/customize/doctype-field-naming.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/data-import/data-import-1.png b/erpnext/docs/assets/img/setup/data-import/data-import-1.png
new file mode 100644
index 0000000..96d7bb4
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/data-import/data-import-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/data-import/data-import-2.png b/erpnext/docs/assets/img/setup/data-import/data-import-2.png
new file mode 100644
index 0000000..90d0449
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/data-import/data-import-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/data-import/data-import-3.png b/erpnext/docs/assets/img/setup/data-import/data-import-3.png
new file mode 100644
index 0000000..971fff5
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/data-import/data-import-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/data/rename.png b/erpnext/docs/assets/img/setup/data/rename.png
new file mode 100644
index 0000000..0a922e1
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/data/rename.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-account-incoming.png b/erpnext/docs/assets/img/setup/email/email-account-incoming.png
new file mode 100644
index 0000000..8ef4f28
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-account-incoming.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-account-list.png b/erpnext/docs/assets/img/setup/email/email-account-list.png
new file mode 100644
index 0000000..10ba12c
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-account-list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-account-sending.png b/erpnext/docs/assets/img/setup/email/email-account-sending.png
new file mode 100644
index 0000000..81bb73d
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-account-sending.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-account-unreplied.png b/erpnext/docs/assets/img/setup/email/email-account-unreplied.png
new file mode 100644
index 0000000..bb105ad
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-account-unreplied.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-alert-1.png b/erpnext/docs/assets/img/setup/email/email-alert-1.png
new file mode 100644
index 0000000..4af172d
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-alert-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-alert-2.png b/erpnext/docs/assets/img/setup/email/email-alert-2.png
new file mode 100644
index 0000000..3856f89
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-alert-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-digest.png b/erpnext/docs/assets/img/setup/email/email-digest.png
new file mode 100644
index 0000000..4197ed8
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-digest.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/email-list.png b/erpnext/docs/assets/img/setup/email/email-list.png
new file mode 100644
index 0000000..9567e11
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/email-list.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/send-email.gif b/erpnext/docs/assets/img/setup/email/send-email.gif
new file mode 100644
index 0000000..cdd3079
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/send-email.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/email/standard-reply.png b/erpnext/docs/assets/img/setup/email/standard-reply.png
new file mode 100644
index 0000000..e661885
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/email/standard-reply.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/address-format.png b/erpnext/docs/assets/img/setup/print/address-format.png
new file mode 100644
index 0000000..f63108a
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/address-format.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/letter-head-1.png b/erpnext/docs/assets/img/setup/print/letter-head-1.png
new file mode 100644
index 0000000..8be8ce2
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/letter-head-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/letter-head.png b/erpnext/docs/assets/img/setup/print/letter-head.png
new file mode 100644
index 0000000..d316aae
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/letter-head.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-format-builder-1.gif b/erpnext/docs/assets/img/setup/print/print-format-builder-1.gif
new file mode 100644
index 0000000..a788470
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-format-builder-1.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-format-builder-2.gif b/erpnext/docs/assets/img/setup/print/print-format-builder-2.gif
new file mode 100644
index 0000000..cb78725
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-format-builder-2.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-format-builder-3.gif b/erpnext/docs/assets/img/setup/print/print-format-builder-3.gif
new file mode 100644
index 0000000..8502b1a
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-format-builder-3.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-format-builder-4.gif b/erpnext/docs/assets/img/setup/print/print-format-builder-4.gif
new file mode 100644
index 0000000..b1b241c
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-format-builder-4.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-heading-1.png b/erpnext/docs/assets/img/setup/print/print-heading-1.png
new file mode 100644
index 0000000..292ad52
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-heading-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-heading.png b/erpnext/docs/assets/img/setup/print/print-heading.png
new file mode 100644
index 0000000..a2a4010
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-heading.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/print-settings.png b/erpnext/docs/assets/img/setup/print/print-settings.png
new file mode 100644
index 0000000..9c43dce
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/print-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/terms-1.png b/erpnext/docs/assets/img/setup/print/terms-1.png
new file mode 100644
index 0000000..235e2af
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/terms-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/terms-2.png b/erpnext/docs/assets/img/setup/print/terms-2.png
new file mode 100644
index 0000000..7b715be
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/terms-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/terms-3.png b/erpnext/docs/assets/img/setup/print/terms-3.png
new file mode 100644
index 0000000..51c1017
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/terms-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/print/test.gif b/erpnext/docs/assets/img/setup/print/test.gif
new file mode 100644
index 0000000..364a9aa
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/print/test.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/settings/global-defaults.png b/erpnext/docs/assets/img/setup/settings/global-defaults.png
new file mode 100644
index 0000000..1db693e
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/settings/global-defaults.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/settings/naming-series.gif b/erpnext/docs/assets/img/setup/settings/naming-series.gif
new file mode 100644
index 0000000..211f93b
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/settings/naming-series.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/settings/show-hide-modules.png b/erpnext/docs/assets/img/setup/settings/show-hide-modules.png
new file mode 100644
index 0000000..3b86680
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/settings/show-hide-modules.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/settings/system-settings.png b/erpnext/docs/assets/img/setup/settings/system-settings.png
new file mode 100644
index 0000000..7bab5de
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/settings/system-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/stock-recon-1.png b/erpnext/docs/assets/img/setup/stock-recon-1.png
new file mode 100644
index 0000000..7990531
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/stock-recon-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/stock-recon-2.png b/erpnext/docs/assets/img/setup/stock-recon-2.png
new file mode 100644
index 0000000..42ea3e6
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/stock-recon-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/permission-1.png b/erpnext/docs/assets/img/setup/users/permission-1.png
new file mode 100644
index 0000000..5cad001
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/permission-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/permission-2.png b/erpnext/docs/assets/img/setup/users/permission-2.png
new file mode 100644
index 0000000..4261bdb
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/permission-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/permission-3.png b/erpnext/docs/assets/img/setup/users/permission-3.png
new file mode 100644
index 0000000..3d2dbb3
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/permission-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/permission-4.png b/erpnext/docs/assets/img/setup/users/permission-4.png
new file mode 100644
index 0000000..80bc117
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/permission-4.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/role-1.png b/erpnext/docs/assets/img/setup/users/role-1.png
new file mode 100644
index 0000000..15864ac
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/role-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/share.gif b/erpnext/docs/assets/img/setup/users/share.gif
new file mode 100644
index 0000000..f32aeea
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/share.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/user-1.png b/erpnext/docs/assets/img/setup/users/user-1.png
new file mode 100644
index 0000000..5529109
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/user-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/user-2.png b/erpnext/docs/assets/img/setup/users/user-2.png
new file mode 100644
index 0000000..b2c4969
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/user-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/user-3.png b/erpnext/docs/assets/img/setup/users/user-3.png
new file mode 100644
index 0000000..0e2af91
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/user-3.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/users/user-4.png b/erpnext/docs/assets/img/setup/users/user-4.png
new file mode 100644
index 0000000..807a05c
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/users/user-4.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/workflow-1.png b/erpnext/docs/assets/img/setup/workflow-1.png
new file mode 100644
index 0000000..632e1fb
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/workflow-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/setup/workflow-2.png b/erpnext/docs/assets/img/setup/workflow-2.png
new file mode 100644
index 0000000..2041860
--- /dev/null
+++ b/erpnext/docs/assets/img/setup/workflow-2.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/additional-costs-general-ledger.png b/erpnext/docs/assets/img/stock/additional-costs-general-ledger.png
new file mode 100644
index 0000000..edad86f
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/additional-costs-general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/additional-costs-table.png b/erpnext/docs/assets/img/stock/additional-costs-table.png
new file mode 100644
index 0000000..ae53973
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/additional-costs-table.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/batch.png b/erpnext/docs/assets/img/stock/batch.png
new file mode 100644
index 0000000..406acbd
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/batch.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/delivery-note.png b/erpnext/docs/assets/img/stock/delivery-note.png
new file mode 100644
index 0000000..9356495
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/delivery-note.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/installation-note.png b/erpnext/docs/assets/img/stock/installation-note.png
new file mode 100644
index 0000000..fe6100e
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/installation-note.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-1.png b/erpnext/docs/assets/img/stock/item-1.png
new file mode 100644
index 0000000..2bd7a81
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-attribute-non-numeric.png b/erpnext/docs/assets/img/stock/item-attribute-non-numeric.png
new file mode 100644
index 0000000..bf986fb
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-attribute-non-numeric.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-attribute-numeric.png b/erpnext/docs/assets/img/stock/item-attribute-numeric.png
new file mode 100644
index 0000000..b06dbd1
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-attribute-numeric.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-attribute.png b/erpnext/docs/assets/img/stock/item-attribute.png
new file mode 100644
index 0000000..8e8b3c1
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-attribute.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-attributes.png b/erpnext/docs/assets/img/stock/item-attributes.png
new file mode 100644
index 0000000..a78b76e
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-attributes.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-group-del.gif b/erpnext/docs/assets/img/stock/item-group-del.gif
new file mode 100644
index 0000000..94513e8
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-group-del.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-group-new.gif b/erpnext/docs/assets/img/stock/item-group-new.gif
new file mode 100644
index 0000000..6a042b1
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-group-new.gif
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-group-tree.png b/erpnext/docs/assets/img/stock/item-group-tree.png
new file mode 100644
index 0000000..23a6d45
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-group-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/item-has-variants.png b/erpnext/docs/assets/img/stock/item-has-variants.png
new file mode 100644
index 0000000..903a63c
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/item-has-variants.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/landed-cost.png b/erpnext/docs/assets/img/stock/landed-cost.png
new file mode 100644
index 0000000..acaebb1
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/landed-cost.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/make-variant-1.png b/erpnext/docs/assets/img/stock/make-variant-1.png
new file mode 100644
index 0000000..5b9f2d5
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/make-variant-1.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/make-variant.png b/erpnext/docs/assets/img/stock/make-variant.png
new file mode 100644
index 0000000..787e842
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/make-variant.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/manage-variants.png b/erpnext/docs/assets/img/stock/manage-variants.png
new file mode 100644
index 0000000..342a12f
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/manage-variants.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/packing-slip.png b/erpnext/docs/assets/img/stock/packing-slip.png
new file mode 100644
index 0000000..df2fa5f
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/packing-slip.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/purchase-receipt.png b/erpnext/docs/assets/img/stock/purchase-receipt.png
new file mode 100644
index 0000000..496a3b5
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/purchase-receipt.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/purchase-return-against-purchase-receipt.png b/erpnext/docs/assets/img/stock/purchase-return-against-purchase-receipt.png
new file mode 100644
index 0000000..e75d0e7
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/purchase-return-against-purchase-receipt.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/purchase-return-general-ledger.png b/erpnext/docs/assets/img/stock/purchase-return-general-ledger.png
new file mode 100644
index 0000000..2444209
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/purchase-return-general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/purchase-return-original-purchase-receipt.png b/erpnext/docs/assets/img/stock/purchase-return-original-purchase-receipt.png
new file mode 100644
index 0000000..7519007
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/purchase-return-original-purchase-receipt.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/purchase-return-stock-ledger.png b/erpnext/docs/assets/img/stock/purchase-return-stock-ledger.png
new file mode 100644
index 0000000..24020be
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/purchase-return-stock-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/quality-inspection.png b/erpnext/docs/assets/img/stock/quality-inspection.png
new file mode 100644
index 0000000..3707155
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/quality-inspection.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/sales-return-against-delivery-note.png b/erpnext/docs/assets/img/stock/sales-return-against-delivery-note.png
new file mode 100644
index 0000000..dcca634
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/sales-return-against-delivery-note.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/sales-return-against-sales-invoice.png b/erpnext/docs/assets/img/stock/sales-return-against-sales-invoice.png
new file mode 100644
index 0000000..96ec8b4
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/sales-return-against-sales-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/sales-return-general-ledger.png b/erpnext/docs/assets/img/stock/sales-return-general-ledger.png
new file mode 100644
index 0000000..127ad37
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/sales-return-general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/sales-return-original-delivery-note.png b/erpnext/docs/assets/img/stock/sales-return-original-delivery-note.png
new file mode 100644
index 0000000..82755cb
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/sales-return-original-delivery-note.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/sales-return-stock-ledger.png b/erpnext/docs/assets/img/stock/sales-return-stock-ledger.png
new file mode 100644
index 0000000..d9ed144
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/sales-return-stock-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/serial-no.png b/erpnext/docs/assets/img/stock/serial-no.png
new file mode 100644
index 0000000..3738433
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/serial-no.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/stock-entry-item-valuation-rate.png b/erpnext/docs/assets/img/stock/stock-entry-item-valuation-rate.png
new file mode 100644
index 0000000..58c36dd
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/stock-entry-item-valuation-rate.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/stock-entry.png b/erpnext/docs/assets/img/stock/stock-entry.png
new file mode 100644
index 0000000..30941b9
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/stock-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/stock-settings.png b/erpnext/docs/assets/img/stock/stock-settings.png
new file mode 100644
index 0000000..0065a92
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/stock-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/uom-replace.png b/erpnext/docs/assets/img/stock/uom-replace.png
new file mode 100644
index 0000000..2817e61
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/uom-replace.png
Binary files differ
diff --git a/erpnext/docs/assets/img/stock/warehouse.png b/erpnext/docs/assets/img/stock/warehouse.png
new file mode 100644
index 0000000..6b968d3
--- /dev/null
+++ b/erpnext/docs/assets/img/stock/warehouse.png
Binary files differ
diff --git a/erpnext/docs/assets/img/support/issue.png b/erpnext/docs/assets/img/support/issue.png
new file mode 100644
index 0000000..b28579b
--- /dev/null
+++ b/erpnext/docs/assets/img/support/issue.png
Binary files differ
diff --git a/erpnext/docs/assets/img/support/maintenance-schedule.png b/erpnext/docs/assets/img/support/maintenance-schedule.png
new file mode 100644
index 0000000..8af0cbe
--- /dev/null
+++ b/erpnext/docs/assets/img/support/maintenance-schedule.png
Binary files differ
diff --git a/erpnext/docs/assets/img/support/maintenance-visit.png b/erpnext/docs/assets/img/support/maintenance-visit.png
new file mode 100644
index 0000000..6212860
--- /dev/null
+++ b/erpnext/docs/assets/img/support/maintenance-visit.png
Binary files differ
diff --git a/erpnext/docs/assets/img/support/warranty-claim.png b/erpnext/docs/assets/img/support/warranty-claim.png
new file mode 100644
index 0000000..39cfb5f
--- /dev/null
+++ b/erpnext/docs/assets/img/support/warranty-claim.png
Binary files differ
diff --git a/erpnext/docs/assets/img/taxes/inclusive-tax.png b/erpnext/docs/assets/img/taxes/inclusive-tax.png
new file mode 100644
index 0000000..9bd76e1
--- /dev/null
+++ b/erpnext/docs/assets/img/taxes/inclusive-tax.png
Binary files differ
diff --git a/erpnext/docs/assets/img/taxes/item-tax.png b/erpnext/docs/assets/img/taxes/item-tax.png
new file mode 100644
index 0000000..6b70ef5
--- /dev/null
+++ b/erpnext/docs/assets/img/taxes/item-tax.png
Binary files differ
diff --git a/erpnext/docs/assets/img/taxes/sales-tax-master.png b/erpnext/docs/assets/img/taxes/sales-tax-master.png
new file mode 100644
index 0000000..f832454
--- /dev/null
+++ b/erpnext/docs/assets/img/taxes/sales-tax-master.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-employee-role.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-employee-role.png
new file mode 100644
index 0000000..4fb5a8f
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-employee-role.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-manager-role.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-manager-role.png
new file mode 100644
index 0000000..2a260c1
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-manager-role.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-user-role.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-user-role.png
new file mode 100644
index 0000000..eab8d57
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-hr-user-role.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application-form.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application-form.png
new file mode 100644
index 0000000..032707a
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application-form.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application.png
new file mode 100644
index 0000000..cd4e38f
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-application.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-approver-role.png b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-approver-role.png
new file mode 100644
index 0000000..b7b6770
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/setting-up-permissions-leave-approver-role.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permission-user-limited-by-company.png b/erpnext/docs/assets/img/users-and-permissions/user-permission-user-limited-by-company.png
new file mode 100644
index 0000000..e23f122
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permission-user-limited-by-company.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-role-all.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-role-all.png
new file mode 100644
index 0000000..0aececd
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-role-all.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-wind-power-llc.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-wind-power-llc.png
new file mode 100644
index 0000000..6d78e5d
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company-wind-power-llc.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-company.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company.png
new file mode 100644
index 0000000..e091a61
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-company.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-ignore-user-permissions.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-ignore-user-permissions.png
new file mode 100644
index 0000000..5f55e37
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-ignore-user-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-lead-role-permissions.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-lead-role-permissions.png
new file mode 100644
index 0000000..23564fa
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-lead-role-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/img/users-and-permissions/user-permissions-quotation-sales-user.png b/erpnext/docs/assets/img/users-and-permissions/user-permissions-quotation-sales-user.png
new file mode 100644
index 0000000..dd9ed49
--- /dev/null
+++ b/erpnext/docs/assets/img/users-and-permissions/user-permissions-quotation-sales-user.png
Binary files differ
diff --git a/erpnext/docs/assets/img/videos/conf-2014.jpg b/erpnext/docs/assets/img/videos/conf-2014.jpg
new file mode 100644
index 0000000..50e2ae9
--- /dev/null
+++ b/erpnext/docs/assets/img/videos/conf-2014.jpg
Binary files differ
diff --git a/erpnext/docs/assets/img/videos/learn.jpg b/erpnext/docs/assets/img/videos/learn.jpg
new file mode 100644
index 0000000..45e48e2
--- /dev/null
+++ b/erpnext/docs/assets/img/videos/learn.jpg
Binary files differ
diff --git a/erpnext/docs/assets/img/website/banner.png b/erpnext/docs/assets/img/website/banner.png
new file mode 100644
index 0000000..600cdd0
--- /dev/null
+++ b/erpnext/docs/assets/img/website/banner.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/blog-post.png b/erpnext/docs/assets/img/website/blog-post.png
new file mode 100644
index 0000000..69d0d48
--- /dev/null
+++ b/erpnext/docs/assets/img/website/blog-post.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/blog-sample.png b/erpnext/docs/assets/img/website/blog-sample.png
new file mode 100644
index 0000000..1fff0bb
--- /dev/null
+++ b/erpnext/docs/assets/img/website/blog-sample.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/blogger.png b/erpnext/docs/assets/img/website/blogger.png
new file mode 100644
index 0000000..cb1d08f
--- /dev/null
+++ b/erpnext/docs/assets/img/website/blogger.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/integrations.png b/erpnext/docs/assets/img/website/integrations.png
new file mode 100644
index 0000000..992ddd2
--- /dev/null
+++ b/erpnext/docs/assets/img/website/integrations.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/top-bar.png b/erpnext/docs/assets/img/website/top-bar.png
new file mode 100644
index 0000000..8200167
--- /dev/null
+++ b/erpnext/docs/assets/img/website/top-bar.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/web-form-view.png b/erpnext/docs/assets/img/website/web-form-view.png
new file mode 100644
index 0000000..935e4e8
--- /dev/null
+++ b/erpnext/docs/assets/img/website/web-form-view.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/web-form.png b/erpnext/docs/assets/img/website/web-form.png
new file mode 100644
index 0000000..69178fa
--- /dev/null
+++ b/erpnext/docs/assets/img/website/web-form.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/web-page.png b/erpnext/docs/assets/img/website/web-page.png
new file mode 100644
index 0000000..e8343a9
--- /dev/null
+++ b/erpnext/docs/assets/img/website/web-page.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/website-settings.png b/erpnext/docs/assets/img/website/website-settings.png
new file mode 100644
index 0000000..7ec9d33
--- /dev/null
+++ b/erpnext/docs/assets/img/website/website-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/img/website/website-theme.png b/erpnext/docs/assets/img/website/website-theme.png
new file mode 100644
index 0000000..fa85791
--- /dev/null
+++ b/erpnext/docs/assets/img/website/website-theme.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/erpnext-conf-14.png b/erpnext/docs/assets/old_images/conf/erpnext-conf-14.png
new file mode 100644
index 0000000..30786ba
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/erpnext-conf-14.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/matunga-1.jpg b/erpnext/docs/assets/old_images/conf/matunga-1.jpg
new file mode 100644
index 0000000..9b678df
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/matunga-1.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/matunga-2.jpg b/erpnext/docs/assets/old_images/conf/matunga-2.jpg
new file mode 100644
index 0000000..43b36b0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/matunga-2.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/matunga-3.jpg b/erpnext/docs/assets/old_images/conf/matunga-3.jpg
new file mode 100644
index 0000000..b28baa0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/matunga-3.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/matunga-4.jpg b/erpnext/docs/assets/old_images/conf/matunga-4.jpg
new file mode 100644
index 0000000..d4e63a6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/matunga-4.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/matunga-5.jpg b/erpnext/docs/assets/old_images/conf/matunga-5.jpg
new file mode 100644
index 0000000..9b7a100
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/matunga-5.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/aditya-duggal.jpg b/erpnext/docs/assets/old_images/conf/videos/aditya-duggal.jpg
new file mode 100644
index 0000000..30bc6f1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/aditya-duggal.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/anand-doshi.jpg b/erpnext/docs/assets/old_images/conf/videos/anand-doshi.jpg
new file mode 100644
index 0000000..e8832f1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/anand-doshi.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/deepak-gupta.jpg b/erpnext/docs/assets/old_images/conf/videos/deepak-gupta.jpg
new file mode 100644
index 0000000..6d9eb7f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/deepak-gupta.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/global-community.jpg b/erpnext/docs/assets/old_images/conf/videos/global-community.jpg
new file mode 100644
index 0000000..9a48d38
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/global-community.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/mahesh-malani.jpg b/erpnext/docs/assets/old_images/conf/videos/mahesh-malani.jpg
new file mode 100644
index 0000000..d244d0b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/mahesh-malani.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/nabin-hait.jpg b/erpnext/docs/assets/old_images/conf/videos/nabin-hait.jpg
new file mode 100644
index 0000000..732de4e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/nabin-hait.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/prashant-thakkar.jpg b/erpnext/docs/assets/old_images/conf/videos/prashant-thakkar.jpg
new file mode 100644
index 0000000..0f2c662
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/prashant-thakkar.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/rushabh-mehta.jpg b/erpnext/docs/assets/old_images/conf/videos/rushabh-mehta.jpg
new file mode 100644
index 0000000..50e2ae9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/rushabh-mehta.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/sonal-ramnathkar.jpg b/erpnext/docs/assets/old_images/conf/videos/sonal-ramnathkar.jpg
new file mode 100644
index 0000000..26ab4ea
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/sonal-ramnathkar.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/tarun-gupta.jpg b/erpnext/docs/assets/old_images/conf/videos/tarun-gupta.jpg
new file mode 100644
index 0000000..ed13a29
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/tarun-gupta.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/conf/videos/umair-sayyed.jpg b/erpnext/docs/assets/old_images/conf/videos/umair-sayyed.jpg
new file mode 100644
index 0000000..915482c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/conf/videos/umair-sayyed.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/coverdesk.png b/erpnext/docs/assets/old_images/coverdesk.png
new file mode 100644
index 0000000..6ff2e15
--- /dev/null
+++ b/erpnext/docs/assets/old_images/coverdesk.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/engineering.jpg b/erpnext/docs/assets/old_images/engineering.jpg
new file mode 100644
index 0000000..62c92e8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/engineering.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext-logo.png b/erpnext/docs/assets/old_images/erpnext-logo.png
new file mode 100644
index 0000000..9fc2066
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext-logo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/BOM-Replace-Tool.png b/erpnext/docs/assets/old_images/erpnext/BOM-Replace-Tool.png
new file mode 100644
index 0000000..14e879e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/BOM-Replace-Tool.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/Customer-group-add.png b/erpnext/docs/assets/old_images/erpnext/Customer-group-add.png
new file mode 100644
index 0000000..322b6dd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/Customer-group-add.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/Customer-group-form.png b/erpnext/docs/assets/old_images/erpnext/Customer-group-form.png
new file mode 100644
index 0000000..266ddc1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/Customer-group-form.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/Customer-group-new.png b/erpnext/docs/assets/old_images/erpnext/Customer-group-new.png
new file mode 100644
index 0000000..5e42a0d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/Customer-group-new.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/Make-to-order.png b/erpnext/docs/assets/old_images/erpnext/Make-to-order.png
new file mode 100644
index 0000000..cd3c890
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/Make-to-order.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-1.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-1.png
new file mode 100644
index 0000000..462c3f1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-10.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-10.png
new file mode 100644
index 0000000..eea5d73
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-10.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-11.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-11.png
new file mode 100644
index 0000000..a29c0e5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-11.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-12.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-12.png
new file mode 100644
index 0000000..9143371
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-12.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-13.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-13.png
new file mode 100644
index 0000000..a250fd0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-13.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-14.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-14.png
new file mode 100644
index 0000000..5ce57e8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-14.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-15.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-15.png
new file mode 100644
index 0000000..28d4970
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-15.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-16.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-16.png
new file mode 100644
index 0000000..dbd0cf2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-16.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-17.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-17.png
new file mode 100644
index 0000000..3d3edf2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-17.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-18.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-18.png
new file mode 100644
index 0000000..e006bf0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-18.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-2.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-2.png
new file mode 100644
index 0000000..f194360
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-3.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-3.png
new file mode 100644
index 0000000..c6e336f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-4.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-4.png
new file mode 100644
index 0000000..9370e86
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-5.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-5.png
new file mode 100644
index 0000000..cbe25e7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-6.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-6.png
new file mode 100644
index 0000000..3050931
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-6.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-7.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-7.png
new file mode 100644
index 0000000..dbe669e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-7.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-8.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-8.png
new file mode 100644
index 0000000..bfa9516
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-8.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-9.png b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-9.png
new file mode 100644
index 0000000..4f3fa7e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/accounting-for-stock-9.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/appraisal-1.png b/erpnext/docs/assets/old_images/erpnext/appraisal-1.png
new file mode 100644
index 0000000..4227490
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/appraisal-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/appraisal-2.png b/erpnext/docs/assets/old_images/erpnext/appraisal-2.png
new file mode 100644
index 0000000..30f865e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/appraisal-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assets-1.png b/erpnext/docs/assets/old_images/erpnext/assets-1.png
new file mode 100644
index 0000000..19b3328
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assets-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assets-2.png b/erpnext/docs/assets/old_images/erpnext/assets-2.png
new file mode 100644
index 0000000..f0b0262
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assets-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assets-3.png b/erpnext/docs/assets/old_images/erpnext/assets-3.png
new file mode 100644
index 0000000..fd0a9a5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assets-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assets-4.png b/erpnext/docs/assets/old_images/erpnext/assets-4.png
new file mode 100644
index 0000000..4727484
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assets-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assets-5.png b/erpnext/docs/assets/old_images/erpnext/assets-5.png
new file mode 100644
index 0000000..8beaa57
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assets-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assign-remove.png b/erpnext/docs/assets/old_images/erpnext/assign-remove.png
new file mode 100644
index 0000000..2973ec0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assign-remove.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assign-todo.png b/erpnext/docs/assets/old_images/erpnext/assign-todo.png
new file mode 100644
index 0000000..c63b943
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assign-todo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assign-user.png b/erpnext/docs/assets/old_images/erpnext/assign-user.png
new file mode 100644
index 0000000..4a34fe8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assign-user.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assigned-to-icon.png b/erpnext/docs/assets/old_images/erpnext/assigned-to-icon.png
new file mode 100644
index 0000000..9604a02
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assigned-to-icon.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assigned-to.png b/erpnext/docs/assets/old_images/erpnext/assigned-to.png
new file mode 100644
index 0000000..01a3875
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assigned-to.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/assignment.png b/erpnext/docs/assets/old_images/erpnext/assignment.png
new file mode 100644
index 0000000..c2213b3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/assignment.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/attendance.png b/erpnext/docs/assets/old_images/erpnext/attendance.png
new file mode 100644
index 0000000..e878c1a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/attendance.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-applicable.png b/erpnext/docs/assets/old_images/erpnext/auth-applicable.png
new file mode 100644
index 0000000..7694e45
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-applicable.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-approver.png b/erpnext/docs/assets/old_images/erpnext/auth-approver.png
new file mode 100644
index 0000000..42ff623
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-approver.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-based-on.png b/erpnext/docs/assets/old_images/erpnext/auth-based-on.png
new file mode 100644
index 0000000..f8d3d97
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-based-on.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-transaction.png b/erpnext/docs/assets/old_images/erpnext/auth-transaction.png
new file mode 100644
index 0000000..0165679
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-transaction.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-validation.png b/erpnext/docs/assets/old_images/erpnext/auth-validation.png
new file mode 100644
index 0000000..3902e36
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-validation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auth-value.png b/erpnext/docs/assets/old_images/erpnext/auth-value.png
new file mode 100644
index 0000000..57d6eb9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auth-value.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/authorization-rule-1.png b/erpnext/docs/assets/old_images/erpnext/authorization-rule-1.png
new file mode 100644
index 0000000..41ac7d9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/authorization-rule-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/authorization-rule-2.png b/erpnext/docs/assets/old_images/erpnext/authorization-rule-2.png
new file mode 100644
index 0000000..77f493d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/authorization-rule-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/authorization-rule.png b/erpnext/docs/assets/old_images/erpnext/authorization-rule.png
new file mode 100644
index 0000000..529a396
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/authorization-rule.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/auto-notification.png b/erpnext/docs/assets/old_images/erpnext/auto-notification.png
new file mode 100644
index 0000000..1331a72
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/auto-notification.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/backup-manager.png b/erpnext/docs/assets/old_images/erpnext/backup-manager.png
new file mode 100644
index 0000000..3483a1f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/backup-manager.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-1.png b/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-1.png
new file mode 100644
index 0000000..7135ab6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-2.png b/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-2.png
new file mode 100644
index 0000000..2fec1e6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/bank-reconciliation-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/barcode-1.png b/erpnext/docs/assets/old_images/erpnext/barcode-1.png
new file mode 100644
index 0000000..8912a01
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/barcode-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/barcode-2.png b/erpnext/docs/assets/old_images/erpnext/barcode-2.png
new file mode 100644
index 0000000..f66344f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/barcode-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-delivery.png b/erpnext/docs/assets/old_images/erpnext/batch-delivery.png
new file mode 100644
index 0000000..efac451
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-delivery.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-details.png b/erpnext/docs/assets/old_images/erpnext/batch-details.png
new file mode 100644
index 0000000..b0d143a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-details.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-id.png b/erpnext/docs/assets/old_images/erpnext/batch-id.png
new file mode 100644
index 0000000..89929fc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-id.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-item.png b/erpnext/docs/assets/old_images/erpnext/batch-item.png
new file mode 100644
index 0000000..dd39583
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-receipt.png b/erpnext/docs/assets/old_images/erpnext/batch-receipt.png
new file mode 100644
index 0000000..de64bdb
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-receipt.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/batch-report.png b/erpnext/docs/assets/old_images/erpnext/batch-report.png
new file mode 100644
index 0000000..4b68082
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/batch-report.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/blog-look.png b/erpnext/docs/assets/old_images/erpnext/blog-look.png
new file mode 100644
index 0000000..6bca9e8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/blog-look.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/blog.png b/erpnext/docs/assets/old_images/erpnext/blog.png
new file mode 100644
index 0000000..fc4fdb4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/blog.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/bom-wind-turbine.png b/erpnext/docs/assets/old_images/erpnext/bom-wind-turbine.png
new file mode 100644
index 0000000..a929ab3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/bom-wind-turbine.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/bom.png b/erpnext/docs/assets/old_images/erpnext/bom.png
new file mode 100644
index 0000000..b24e7fc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/bom.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/book-keeping-sp.png b/erpnext/docs/assets/old_images/erpnext/book-keeping-sp.png
new file mode 100644
index 0000000..7ce66d8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/book-keeping-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting-1.png b/erpnext/docs/assets/old_images/erpnext/budgeting-1.png
new file mode 100644
index 0000000..29038a0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting-2-1.png b/erpnext/docs/assets/old_images/erpnext/budgeting-2-1.png
new file mode 100644
index 0000000..7cd431e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting-2-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting-3.png b/erpnext/docs/assets/old_images/erpnext/budgeting-3.png
new file mode 100644
index 0000000..29037c7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting-4-1.png b/erpnext/docs/assets/old_images/erpnext/budgeting-4-1.png
new file mode 100644
index 0000000..6348f1e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting-4-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting-4.png b/erpnext/docs/assets/old_images/erpnext/budgeting-4.png
new file mode 100644
index 0000000..17683e3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/budgeting.png b/erpnext/docs/assets/old_images/erpnext/budgeting.png
new file mode 100644
index 0000000..809d6d1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/budgeting.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/bulb.jpg b/erpnext/docs/assets/old_images/erpnext/bulb.jpg
new file mode 100644
index 0000000..6412f50
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/bulb.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/butterfly-print.jpg b/erpnext/docs/assets/old_images/erpnext/butterfly-print.jpg
new file mode 100644
index 0000000..e503d77
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/butterfly-print.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-email-digest.png b/erpnext/docs/assets/old_images/erpnext/calender-email-digest.png
new file mode 100644
index 0000000..4d7a6cb
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-email-digest.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-event-lead.png b/erpnext/docs/assets/old_images/erpnext/calender-event-lead.png
new file mode 100644
index 0000000..ff04fb4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-event-lead.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-event-manually.png b/erpnext/docs/assets/old_images/erpnext/calender-event-manually.png
new file mode 100644
index 0000000..0174f52
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-event-manually.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-event-notification.png b/erpnext/docs/assets/old_images/erpnext/calender-event-notification.png
new file mode 100644
index 0000000..c86c5f5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-event-notification.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-event-permission.png b/erpnext/docs/assets/old_images/erpnext/calender-event-permission.png
new file mode 100644
index 0000000..f5b21f1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-event-permission.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/calender-event-recurring.png b/erpnext/docs/assets/old_images/erpnext/calender-event-recurring.png
new file mode 100644
index 0000000..174f154
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/calender-event-recurring.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/campaign.png b/erpnext/docs/assets/old_images/erpnext/campaign.png
new file mode 100644
index 0000000..0e1d521
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/campaign.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/celebrate-1.jpg b/erpnext/docs/assets/old_images/erpnext/celebrate-1.jpg
new file mode 100644
index 0000000..0966785
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/celebrate-1.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-1.png b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-1.png
new file mode 100644
index 0000000..67c764b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-2.png b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-2.png
new file mode 100644
index 0000000..6dd8b22
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/chart-of-accounts.png b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts.png
new file mode 100644
index 0000000..399adbe
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/chart-of-accounts.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/chart-of-cost-centers.png b/erpnext/docs/assets/old_images/erpnext/chart-of-cost-centers.png
new file mode 100644
index 0000000..ff14072
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/chart-of-cost-centers.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/company.png b/erpnext/docs/assets/old_images/erpnext/company.png
new file mode 100644
index 0000000..2a76eb8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/company.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/contact.png b/erpnext/docs/assets/old_images/erpnext/contact.png
new file mode 100644
index 0000000..f664bb4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/contact.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/credit-controller.png b/erpnext/docs/assets/old_images/erpnext/credit-controller.png
new file mode 100644
index 0000000..da108ac
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/credit-controller.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/credit-limit-1.png b/erpnext/docs/assets/old_images/erpnext/credit-limit-1.png
new file mode 100644
index 0000000..d1e725e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/credit-limit-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-document.png b/erpnext/docs/assets/old_images/erpnext/custom-field-document.png
new file mode 100644
index 0000000..6791d32
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-document.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-insert.png b/erpnext/docs/assets/old_images/erpnext/custom-field-insert.png
new file mode 100644
index 0000000..6eacdf1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-insert.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-label.png b/erpnext/docs/assets/old_images/erpnext/custom-field-label.png
new file mode 100644
index 0000000..948b705
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-label.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-link.png b/erpnext/docs/assets/old_images/erpnext/custom-field-link.png
new file mode 100644
index 0000000..d2ee056
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-link.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-option.png b/erpnext/docs/assets/old_images/erpnext/custom-field-option.png
new file mode 100644
index 0000000..712cf27
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-option.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-properties.png b/erpnext/docs/assets/old_images/erpnext/custom-field-properties.png
new file mode 100644
index 0000000..0c0554d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-properties.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field-type.png b/erpnext/docs/assets/old_images/erpnext/custom-field-type.png
new file mode 100644
index 0000000..f642b1c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field-type.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-field.png b/erpnext/docs/assets/old_images/erpnext/custom-field.png
new file mode 100644
index 0000000..309030b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-field.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/custom-script.png b/erpnext/docs/assets/old_images/erpnext/custom-script.png
new file mode 100644
index 0000000..f8612b0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/custom-script.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-1.png b/erpnext/docs/assets/old_images/erpnext/customer-1.png
new file mode 100644
index 0000000..afb99ef
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-issue.png b/erpnext/docs/assets/old_images/erpnext/customer-issue.png
new file mode 100644
index 0000000..2c5ec7b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-issue.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-portal-login.png b/erpnext/docs/assets/old_images/erpnext/customer-portal-login.png
new file mode 100644
index 0000000..459d503
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-portal-login.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-portal-orders-1.png b/erpnext/docs/assets/old_images/erpnext/customer-portal-orders-1.png
new file mode 100644
index 0000000..5cb95bd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-portal-orders-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-1.png b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-1.png
new file mode 100644
index 0000000..f7ff81b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-2.png b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-2.png
new file mode 100644
index 0000000..7693877
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-3.png b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-3.png
new file mode 100644
index 0000000..771de78
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer-portal-sign-up-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customer.png b/erpnext/docs/assets/old_images/erpnext/customer.png
new file mode 100644
index 0000000..37b8450
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customer.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-1.png b/erpnext/docs/assets/old_images/erpnext/customize-form-1.png
new file mode 100644
index 0000000..2d70df6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-2.png b/erpnext/docs/assets/old_images/erpnext/customize-form-2.png
new file mode 100644
index 0000000..204d46a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-custom-field.png b/erpnext/docs/assets/old_images/erpnext/customize-form-custom-field.png
new file mode 100644
index 0000000..d3e1143
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-custom-field.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-document.png b/erpnext/docs/assets/old_images/erpnext/customize-form-document.png
new file mode 100644
index 0000000..e6773d5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-document.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-list-view.png b/erpnext/docs/assets/old_images/erpnext/customize-form-list-view.png
new file mode 100644
index 0000000..fd42fd5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-list-view.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-mandatory.png b/erpnext/docs/assets/old_images/erpnext/customize-form-mandatory.png
new file mode 100644
index 0000000..1da1811
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-mandatory.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize-form-update.png b/erpnext/docs/assets/old_images/erpnext/customize-form-update.png
new file mode 100644
index 0000000..64431a5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize-form-update.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize/print-format.png b/erpnext/docs/assets/old_images/erpnext/customize/print-format.png
new file mode 100644
index 0000000..a1e0ede
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize/print-format.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/customize/print-settings.png b/erpnext/docs/assets/old_images/erpnext/customize/print-settings.png
new file mode 100644
index 0000000..635afc3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/customize/print-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/delivery-note.png b/erpnext/docs/assets/old_images/erpnext/delivery-note.png
new file mode 100644
index 0000000..93edc4e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/delivery-note.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/dog-bow.gif b/erpnext/docs/assets/old_images/erpnext/dog-bow.gif
new file mode 100644
index 0000000..0edad37
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/dog-bow.gif
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/dogs-3.jpg b/erpnext/docs/assets/old_images/erpnext/dogs-3.jpg
new file mode 100644
index 0000000..684af92
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/dogs-3.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/dropbox-access.png b/erpnext/docs/assets/old_images/erpnext/dropbox-access.png
new file mode 100644
index 0000000..7aa6cec
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/dropbox-access.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/email-digest.png b/erpnext/docs/assets/old_images/erpnext/email-digest.png
new file mode 100644
index 0000000..ac26e94
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/email-digest.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/email-settings1.png b/erpnext/docs/assets/old_images/erpnext/email-settings1.png
new file mode 100644
index 0000000..8052a38
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/email-settings1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/email-settings2.png b/erpnext/docs/assets/old_images/erpnext/email-settings2.png
new file mode 100644
index 0000000..3f84c71
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/email-settings2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/employee-1.png b/erpnext/docs/assets/old_images/erpnext/employee-1.png
new file mode 100644
index 0000000..e14a97a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/employee-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/employee-master-1.png b/erpnext/docs/assets/old_images/erpnext/employee-master-1.png
new file mode 100644
index 0000000..f41fd9f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/employee-master-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/employee-master-2.png b/erpnext/docs/assets/old_images/erpnext/employee-master-2.png
new file mode 100644
index 0000000..c22b3bb
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/employee-master-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/employee-master-3.png b/erpnext/docs/assets/old_images/erpnext/employee-master-3.png
new file mode 100644
index 0000000..abe035a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/employee-master-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/erpnext-introduction.png b/erpnext/docs/assets/old_images/erpnext/erpnext-introduction.png
new file mode 100644
index 0000000..9dcf4df
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/erpnext-introduction.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/event-1.png b/erpnext/docs/assets/old_images/erpnext/event-1.png
new file mode 100644
index 0000000..9f0bfd6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/event-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/event-2.png b/erpnext/docs/assets/old_images/erpnext/event-2.png
new file mode 100644
index 0000000..5ce4584
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/event-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/expense-claim.png b/erpnext/docs/assets/old_images/erpnext/expense-claim.png
new file mode 100644
index 0000000..cc3d920
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/expense-claim.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-allowance-percent.png b/erpnext/docs/assets/old_images/erpnext/faq-allowance-percent.png
new file mode 100644
index 0000000..b8ff9c9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-allowance-percent.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-branch.png b/erpnext/docs/assets/old_images/erpnext/faq-branch.png
new file mode 100644
index 0000000..7663eae
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-branch.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-employment-type.png b/erpnext/docs/assets/old_images/erpnext/faq-employment-type.png
new file mode 100644
index 0000000..17924a6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-employment-type.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-eol.png b/erpnext/docs/assets/old_images/erpnext/faq-eol.png
new file mode 100644
index 0000000..d0bbea5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-eol.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-is-sales-item.png b/erpnext/docs/assets/old_images/erpnext/faq-is-sales-item.png
new file mode 100644
index 0000000..4d0d9eb
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-is-sales-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-is-service-item.png b/erpnext/docs/assets/old_images/erpnext/faq-is-service-item.png
new file mode 100644
index 0000000..fa6a34c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-is-service-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-lead-time.png b/erpnext/docs/assets/old_images/erpnext/faq-lead-time.png
new file mode 100644
index 0000000..d50c4fb
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-lead-time.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-leave-allocation.png b/erpnext/docs/assets/old_images/erpnext/faq-leave-allocation.png
new file mode 100644
index 0000000..f71ad4c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-leave-allocation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-leave-application.png b/erpnext/docs/assets/old_images/erpnext/faq-leave-application.png
new file mode 100644
index 0000000..11ef581
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-leave-application.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-leave-without-pay.png b/erpnext/docs/assets/old_images/erpnext/faq-leave-without-pay.png
new file mode 100644
index 0000000..55ff93e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-leave-without-pay.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-manufacturer-part-no.png b/erpnext/docs/assets/old_images/erpnext/faq-manufacturer-part-no.png
new file mode 100644
index 0000000..e43667b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-manufacturer-part-no.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-min-ord-qty.png b/erpnext/docs/assets/old_images/erpnext/faq-min-ord-qty.png
new file mode 100644
index 0000000..22a2b6e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-min-ord-qty.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-process-payroll.png b/erpnext/docs/assets/old_images/erpnext/faq-process-payroll.png
new file mode 100644
index 0000000..81e9686
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-process-payroll.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-purchase-item-yes.png b/erpnext/docs/assets/old_images/erpnext/faq-purchase-item-yes.png
new file mode 100644
index 0000000..ce39087
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-purchase-item-yes.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-reorder-level.png b/erpnext/docs/assets/old_images/erpnext/faq-reorder-level.png
new file mode 100644
index 0000000..8e3e8c5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-reorder-level.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-reorder-qty.png b/erpnext/docs/assets/old_images/erpnext/faq-reorder-qty.png
new file mode 100644
index 0000000..7b1e312
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-reorder-qty.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-sales-partner-commissions.png b/erpnext/docs/assets/old_images/erpnext/faq-sales-partner-commissions.png
new file mode 100644
index 0000000..19d9f9b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-sales-partner-commissions.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-sales-partner.png b/erpnext/docs/assets/old_images/erpnext/faq-sales-partner.png
new file mode 100644
index 0000000..19d9f9b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-sales-partner.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-sales-person-1.png b/erpnext/docs/assets/old_images/erpnext/faq-sales-person-1.png
new file mode 100644
index 0000000..09271fe
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-sales-person-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-standard-rate.png b/erpnext/docs/assets/old_images/erpnext/faq-standard-rate.png
new file mode 100644
index 0000000..e2d9d7c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-standard-rate.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-status.png b/erpnext/docs/assets/old_images/erpnext/faq-status.png
new file mode 100644
index 0000000..01bd517
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-status.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-stock-item-yes.png b/erpnext/docs/assets/old_images/erpnext/faq-stock-item-yes.png
new file mode 100644
index 0000000..61e3b7a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-stock-item-yes.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-sub-contract.png b/erpnext/docs/assets/old_images/erpnext/faq-sub-contract.png
new file mode 100644
index 0000000..3cd665c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-sub-contract.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-user-id.png b/erpnext/docs/assets/old_images/erpnext/faq-user-id.png
new file mode 100644
index 0000000..6d63c1e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-user-id.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-warranty-period.png b/erpnext/docs/assets/old_images/erpnext/faq-warranty-period.png
new file mode 100644
index 0000000..0571fe7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-warranty-period.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/faq-warranty.png b/erpnext/docs/assets/old_images/erpnext/faq-warranty.png
new file mode 100644
index 0000000..93903a1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/faq-warranty.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/fifo.png b/erpnext/docs/assets/old_images/erpnext/fifo.png
new file mode 100644
index 0000000..6b62aec
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/fifo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/fifthdaysetup-tasks.png b/erpnext/docs/assets/old_images/erpnext/fifthdaysetup-tasks.png
new file mode 100644
index 0000000..e387560
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/fifthdaysetup-tasks.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/financial-analytic-bs.png b/erpnext/docs/assets/old_images/erpnext/financial-analytic-bs.png
new file mode 100644
index 0000000..a927878
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/financial-analytic-bs.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/financial-analytic-pl.png b/erpnext/docs/assets/old_images/erpnext/financial-analytic-pl.png
new file mode 100644
index 0000000..00630b2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/financial-analytic-pl.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/forms.png b/erpnext/docs/assets/old_images/erpnext/forms.png
new file mode 100644
index 0000000..0c4af1a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/forms.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/general-ledger.png b/erpnext/docs/assets/old_images/erpnext/general-ledger.png
new file mode 100644
index 0000000..1e6e274
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/general-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/global-defaults.png b/erpnext/docs/assets/old_images/erpnext/global-defaults.png
new file mode 100644
index 0000000..037a06d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/global-defaults.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/hide-features.png b/erpnext/docs/assets/old_images/erpnext/hide-features.png
new file mode 100644
index 0000000..3f86470
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/hide-features.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/hide-module.png b/erpnext/docs/assets/old_images/erpnext/hide-module.png
new file mode 100644
index 0000000..f3f26a4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/hide-module.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/holiday-list-1.png b/erpnext/docs/assets/old_images/erpnext/holiday-list-1.png
new file mode 100644
index 0000000..579c6dd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/holiday-list-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/holiday-list-2.png b/erpnext/docs/assets/old_images/erpnext/holiday-list-2.png
new file mode 100644
index 0000000..5717971
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/holiday-list-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/human-resources-sp.png b/erpnext/docs/assets/old_images/erpnext/human-resources-sp.png
new file mode 100644
index 0000000..cf7b259
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/human-resources-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/image-temp-opening.png b/erpnext/docs/assets/old_images/erpnext/image-temp-opening.png
new file mode 100644
index 0000000..52d0d5a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/image-temp-opening.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/implementation-image.png b/erpnext/docs/assets/old_images/erpnext/implementation-image.png
new file mode 100644
index 0000000..4edcf31
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/implementation-image.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/import-1.png b/erpnext/docs/assets/old_images/erpnext/import-1.png
new file mode 100644
index 0000000..b3aaa65
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/import-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/import-2.png b/erpnext/docs/assets/old_images/erpnext/import-2.png
new file mode 100644
index 0000000..49ac98a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/import-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/import-3.png b/erpnext/docs/assets/old_images/erpnext/import-3.png
new file mode 100644
index 0000000..9387dd5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/import-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/import-4.png b/erpnext/docs/assets/old_images/erpnext/import-4.png
new file mode 100644
index 0000000..fce1f51
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/import-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/import-5.png b/erpnext/docs/assets/old_images/erpnext/import-5.png
new file mode 100644
index 0000000..68a8b85
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/import-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/inclusive-tax.png b/erpnext/docs/assets/old_images/erpnext/inclusive-tax.png
new file mode 100644
index 0000000..d9f1082
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/inclusive-tax.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-1.png b/erpnext/docs/assets/old_images/erpnext/item-1.png
new file mode 100644
index 0000000..85fe1ed
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-add-image.png b/erpnext/docs/assets/old_images/erpnext/item-add-image.png
new file mode 100644
index 0000000..8901ee9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-add-image.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-distributor.png b/erpnext/docs/assets/old_images/erpnext/item-distributor.png
new file mode 100644
index 0000000..c30e18a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-distributor.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-group-tree.png b/erpnext/docs/assets/old_images/erpnext/item-group-tree.png
new file mode 100644
index 0000000..4d512e3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-group-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-manufacturing-website.png b/erpnext/docs/assets/old_images/erpnext/item-manufacturing-website.png
new file mode 100644
index 0000000..65d78b9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-manufacturing-website.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-price-1.png b/erpnext/docs/assets/old_images/erpnext/item-price-1.png
new file mode 100644
index 0000000..b97308e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-price-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-price-item.png b/erpnext/docs/assets/old_images/erpnext/item-price-item.png
new file mode 100644
index 0000000..90acbf1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-price-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-price-list.png b/erpnext/docs/assets/old_images/erpnext/item-price-list.png
new file mode 100644
index 0000000..60591f0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-price-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-price-rate.png b/erpnext/docs/assets/old_images/erpnext/item-price-rate.png
new file mode 100644
index 0000000..05dbef0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-price-rate.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-properties.png b/erpnext/docs/assets/old_images/erpnext/item-properties.png
new file mode 100644
index 0000000..4c0f021
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-properties.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-purchase.png b/erpnext/docs/assets/old_images/erpnext/item-purchase.png
new file mode 100644
index 0000000..04940b9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-purchase.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-sales.png b/erpnext/docs/assets/old_images/erpnext/item-sales.png
new file mode 100644
index 0000000..4579249
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-sales.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-serial-no-series.png b/erpnext/docs/assets/old_images/erpnext/item-serial-no-series.png
new file mode 100644
index 0000000..09ee8cf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-serial-no-series.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-tax-1.png b/erpnext/docs/assets/old_images/erpnext/item-tax-1.png
new file mode 100644
index 0000000..9942b7c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-tax-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-webimage-1.png b/erpnext/docs/assets/old_images/erpnext/item-webimage-1.png
new file mode 100644
index 0000000..a2dfe7f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-webimage-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-webimage-2.png b/erpnext/docs/assets/old_images/erpnext/item-webimage-2.png
new file mode 100644
index 0000000..473a3ff
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-webimage-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-webimage.png b/erpnext/docs/assets/old_images/erpnext/item-webimage.png
new file mode 100644
index 0000000..af46e3c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-webimage.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-wise-tax-calc.png b/erpnext/docs/assets/old_images/erpnext/item-wise-tax-calc.png
new file mode 100644
index 0000000..cd3a08f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-wise-tax-calc.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-wise-tax-master.png b/erpnext/docs/assets/old_images/erpnext/item-wise-tax-master.png
new file mode 100644
index 0000000..95983c5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-wise-tax-master.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/item-wise-tax.png b/erpnext/docs/assets/old_images/erpnext/item-wise-tax.png
new file mode 100644
index 0000000..374fab6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/item-wise-tax.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/itemgroup-webimage-bags.png b/erpnext/docs/assets/old_images/erpnext/itemgroup-webimage-bags.png
new file mode 100644
index 0000000..9c3a400
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/itemgroup-webimage-bags.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/itemgroup-websettings.png b/erpnext/docs/assets/old_images/erpnext/itemgroup-websettings.png
new file mode 100644
index 0000000..dcb8641
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/itemgroup-websettings.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/itemgroup-website-settings.png b/erpnext/docs/assets/old_images/erpnext/itemgroup-website-settings.png
new file mode 100644
index 0000000..1b4039c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/itemgroup-website-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/journal-voucher.png b/erpnext/docs/assets/old_images/erpnext/journal-voucher.png
new file mode 100644
index 0000000..e51586f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/journal-voucher.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/key-workflows.002.jpg b/erpnext/docs/assets/old_images/erpnext/key-workflows.002.jpg
new file mode 100644
index 0000000..0fc575e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/key-workflows.002.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/landed_cost_voucher.png b/erpnext/docs/assets/old_images/erpnext/landed_cost_voucher.png
new file mode 100644
index 0000000..e1199ae
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/landed_cost_voucher.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/laurence.jpg b/erpnext/docs/assets/old_images/erpnext/laurence.jpg
new file mode 100644
index 0000000..0d32939
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/laurence.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/lead.png b/erpnext/docs/assets/old_images/erpnext/lead.png
new file mode 100644
index 0000000..7aa159e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/lead.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/leave-allocation.png b/erpnext/docs/assets/old_images/erpnext/leave-allocation.png
new file mode 100644
index 0000000..434197d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/leave-allocation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ledgers.png b/erpnext/docs/assets/old_images/erpnext/ledgers.png
new file mode 100644
index 0000000..04609e2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ledgers.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/letter-head1.png b/erpnext/docs/assets/old_images/erpnext/letter-head1.png
new file mode 100644
index 0000000..5427cb5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/letter-head1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/letter-head2.png b/erpnext/docs/assets/old_images/erpnext/letter-head2.png
new file mode 100644
index 0000000..4f5b86a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/letter-head2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/letter-head4.png b/erpnext/docs/assets/old_images/erpnext/letter-head4.png
new file mode 100644
index 0000000..5427cb5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/letter-head4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/letterhead.png b/erpnext/docs/assets/old_images/erpnext/letterhead.png
new file mode 100644
index 0000000..0ec5daf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/letterhead.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/logo-robert.gif b/erpnext/docs/assets/old_images/erpnext/logo-robert.gif
new file mode 100644
index 0000000..24ba5d2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/logo-robert.gif
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-1.png b/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-1.png
new file mode 100644
index 0000000..62295ff
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-2.png b/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-2.png
new file mode 100644
index 0000000..eccd83d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/maintenance-schedule-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/maintenance-visit.png b/erpnext/docs/assets/old_images/erpnext/maintenance-visit.png
new file mode 100644
index 0000000..54478fd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/maintenance-visit.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/make-to-stock.png b/erpnext/docs/assets/old_images/erpnext/make-to-stock.png
new file mode 100644
index 0000000..192dae6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/make-to-stock.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-issue.png b/erpnext/docs/assets/old_images/erpnext/material-issue.png
new file mode 100644
index 0000000..89cd181
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-issue.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-request-1.png b/erpnext/docs/assets/old_images/erpnext/material-request-1.png
new file mode 100644
index 0000000..fad4a1a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-request-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-request-2.png b/erpnext/docs/assets/old_images/erpnext/material-request-2.png
new file mode 100644
index 0000000..2543f94
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-request-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-request-flowchart-image.png b/erpnext/docs/assets/old_images/erpnext/material-request-flowchart-image.png
new file mode 100644
index 0000000..d5e112f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-request-flowchart-image.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-request-workflow.jpg b/erpnext/docs/assets/old_images/erpnext/material-request-workflow.jpg
new file mode 100644
index 0000000..6846fa5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-request-workflow.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/material-transfer-1.png b/erpnext/docs/assets/old_images/erpnext/material-transfer-1.png
new file mode 100644
index 0000000..fedd247
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/material-transfer-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/merging-documents-1.png b/erpnext/docs/assets/old_images/erpnext/merging-documents-1.png
new file mode 100644
index 0000000..ea1d432
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/merging-documents-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/merging-documents-2.png b/erpnext/docs/assets/old_images/erpnext/merging-documents-2.png
new file mode 100644
index 0000000..01c375f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/merging-documents-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/merging-documents-3.png b/erpnext/docs/assets/old_images/erpnext/merging-documents-3.png
new file mode 100644
index 0000000..9714cbc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/merging-documents-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/merging-documents.png b/erpnext/docs/assets/old_images/erpnext/merging-documents.png
new file mode 100644
index 0000000..60b95d8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/merging-documents.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/message-list.png b/erpnext/docs/assets/old_images/erpnext/message-list.png
new file mode 100644
index 0000000..e5034a5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/message-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/message-to.png b/erpnext/docs/assets/old_images/erpnext/message-to.png
new file mode 100644
index 0000000..ecd75b4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/message-to.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mfg-bom-3.png b/erpnext/docs/assets/old_images/erpnext/mfg-bom-3.png
new file mode 100644
index 0000000..f99ad0c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mfg-bom-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp-1.1.png b/erpnext/docs/assets/old_images/erpnext/mrp-1.1.png
new file mode 100644
index 0000000..2fab108
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp-1.1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp-1.png b/erpnext/docs/assets/old_images/erpnext/mrp-1.png
new file mode 100644
index 0000000..b17adbe
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp-2.png b/erpnext/docs/assets/old_images/erpnext/mrp-2.png
new file mode 100644
index 0000000..62c6d96
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp-3.png b/erpnext/docs/assets/old_images/erpnext/mrp-3.png
new file mode 100644
index 0000000..42f6f4b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp-4.png b/erpnext/docs/assets/old_images/erpnext/mrp-4.png
new file mode 100644
index 0000000..6acb888
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/mrp.png b/erpnext/docs/assets/old_images/erpnext/mrp.png
new file mode 100644
index 0000000..4a86dec
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/mrp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/naming-series-1.png b/erpnext/docs/assets/old_images/erpnext/naming-series-1.png
new file mode 100644
index 0000000..9733229
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/naming-series-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/naming-series.png b/erpnext/docs/assets/old_images/erpnext/naming-series.png
new file mode 100644
index 0000000..b0f673b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/naming-series.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/new-email-digest.png b/erpnext/docs/assets/old_images/erpnext/new-email-digest.png
new file mode 100644
index 0000000..0f99991
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/new-email-digest.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/new-leave-application.png b/erpnext/docs/assets/old_images/erpnext/new-leave-application.png
new file mode 100644
index 0000000..2a97f7d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/new-leave-application.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/new-price-list-1.png b/erpnext/docs/assets/old_images/erpnext/new-price-list-1.png
new file mode 100644
index 0000000..a7d3d1f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/new-price-list-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/newsletter.png b/erpnext/docs/assets/old_images/erpnext/newsletter.png
new file mode 100644
index 0000000..3bb555f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/newsletter.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/note-permission.png b/erpnext/docs/assets/old_images/erpnext/note-permission.png
new file mode 100644
index 0000000..a3cbc25
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/note-permission.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/note.png b/erpnext/docs/assets/old_images/erpnext/note.png
new file mode 100644
index 0000000..58bc180
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/note.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/notes-1.png b/erpnext/docs/assets/old_images/erpnext/notes-1.png
new file mode 100644
index 0000000..896e7d0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/notes-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/notes.png b/erpnext/docs/assets/old_images/erpnext/notes.png
new file mode 100644
index 0000000..3bba0d4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/notes.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opening-accounts image.png b/erpnext/docs/assets/old_images/erpnext/opening-accounts image.png
new file mode 100644
index 0000000..324f8f3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opening-accounts image.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opening-entry-1.png b/erpnext/docs/assets/old_images/erpnext/opening-entry-1.png
new file mode 100644
index 0000000..42fbe57
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opening-entry-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opening-entry-2.png b/erpnext/docs/assets/old_images/erpnext/opening-entry-2.png
new file mode 100644
index 0000000..57e0fb3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opening-entry-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opening-entry.png b/erpnext/docs/assets/old_images/erpnext/opening-entry.png
new file mode 100644
index 0000000..5c7ab4f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opening-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opportunity-1.png b/erpnext/docs/assets/old_images/erpnext/opportunity-1.png
new file mode 100644
index 0000000..c212064
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opportunity-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/opportunity.png b/erpnext/docs/assets/old_images/erpnext/opportunity.png
new file mode 100644
index 0000000..4a74025
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/opportunity.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/overview.png b/erpnext/docs/assets/old_images/erpnext/overview.png
new file mode 100644
index 0000000..b62b09e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/overview.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/payment-entry.png b/erpnext/docs/assets/old_images/erpnext/payment-entry.png
new file mode 100644
index 0000000..35c1cc3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/payment-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/payment-reconciliation-1.png b/erpnext/docs/assets/old_images/erpnext/payment-reconciliation-1.png
new file mode 100644
index 0000000..c61ea52
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/payment-reconciliation-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/payment_tool_enter_pay.png b/erpnext/docs/assets/old_images/erpnext/payment_tool_enter_pay.png
new file mode 100644
index 0000000..2e8ace9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/payment_tool_enter_pay.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/payment_tool_get_voucher.png b/erpnext/docs/assets/old_images/erpnext/payment_tool_get_voucher.png
new file mode 100644
index 0000000..c97fbc5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/payment_tool_get_voucher.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/payment_tool_make_jv.png b/erpnext/docs/assets/old_images/erpnext/payment_tool_make_jv.png
new file mode 100644
index 0000000..fd19a7b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/payment_tool_make_jv.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pen-stand.jpg b/erpnext/docs/assets/old_images/erpnext/pen-stand.jpg
new file mode 100644
index 0000000..1c13c6e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pen-stand.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/period-closing-dates.png b/erpnext/docs/assets/old_images/erpnext/period-closing-dates.png
new file mode 100644
index 0000000..f7325cf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/period-closing-dates.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/period-closing-voucher.png b/erpnext/docs/assets/old_images/erpnext/period-closing-voucher.png
new file mode 100644
index 0000000..9105556
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/period-closing-voucher.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/period-closing.png b/erpnext/docs/assets/old_images/erpnext/period-closing.png
new file mode 100644
index 0000000..41de105
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/period-closing.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager-1.png b/erpnext/docs/assets/old_images/erpnext/permission-manager-1.png
new file mode 100644
index 0000000..4cc8e3f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager-2.png b/erpnext/docs/assets/old_images/erpnext/permission-manager-2.png
new file mode 100644
index 0000000..4a5c34c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager-3.png b/erpnext/docs/assets/old_images/erpnext/permission-manager-3.png
new file mode 100644
index 0000000..41eefb6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager-4.png b/erpnext/docs/assets/old_images/erpnext/permission-manager-4.png
new file mode 100644
index 0000000..f1e6cc1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager-5.png b/erpnext/docs/assets/old_images/erpnext/permission-manager-5.png
new file mode 100644
index 0000000..42c3941
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/permission-manager.png b/erpnext/docs/assets/old_images/erpnext/permission-manager.png
new file mode 100644
index 0000000..ed82dd8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/permission-manager.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-invoice-paid.png b/erpnext/docs/assets/old_images/erpnext/portal-invoice-paid.png
new file mode 100644
index 0000000..0993cb5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-invoice-paid.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-menu.png b/erpnext/docs/assets/old_images/erpnext/portal-menu.png
new file mode 100644
index 0000000..0f9ea82
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-menu.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-new-ticket.png b/erpnext/docs/assets/old_images/erpnext/portal-new-ticket.png
new file mode 100644
index 0000000..6130ded
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-new-ticket.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-order-billed.png b/erpnext/docs/assets/old_images/erpnext/portal-order-billed.png
new file mode 100644
index 0000000..e92e8dc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-order-billed.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-ticket-1.png b/erpnext/docs/assets/old_images/erpnext/portal-ticket-1.png
new file mode 100644
index 0000000..175eca7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-ticket-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-ticket-list-empty.png b/erpnext/docs/assets/old_images/erpnext/portal-ticket-list-empty.png
new file mode 100644
index 0000000..fd5875c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-ticket-list-empty.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/portal-ticket-reply.png b/erpnext/docs/assets/old_images/erpnext/portal-ticket-reply.png
new file mode 100644
index 0000000..f03f673
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/portal-ticket-reply.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pos-add-item.png b/erpnext/docs/assets/old_images/erpnext/pos-add-item.png
new file mode 100644
index 0000000..96e64d4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pos-add-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pos-features-setup.png b/erpnext/docs/assets/old_images/erpnext/pos-features-setup.png
new file mode 100644
index 0000000..c41ff60
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pos-features-setup.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pos-make-payment.png b/erpnext/docs/assets/old_images/erpnext/pos-make-payment.png
new file mode 100644
index 0000000..c4ef00f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pos-make-payment.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pos-remove-item.png b/erpnext/docs/assets/old_images/erpnext/pos-remove-item.png
new file mode 100644
index 0000000..46ffc2b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pos-remove-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pos-setting.png b/erpnext/docs/assets/old_images/erpnext/pos-setting.png
new file mode 100644
index 0000000..909c324
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pos-setting.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/pr_landed_cost_voucher_amount.png b/erpnext/docs/assets/old_images/erpnext/pr_landed_cost_voucher_amount.png
new file mode 100644
index 0000000..065e345
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/pr_landed_cost_voucher_amount.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/price-list-currency.png b/erpnext/docs/assets/old_images/erpnext/price-list-currency.png
new file mode 100644
index 0000000..17fbd70
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/price-list-currency.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/price-list-for.png b/erpnext/docs/assets/old_images/erpnext/price-list-for.png
new file mode 100644
index 0000000..dc058b7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/price-list-for.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/price-list-name.png b/erpnext/docs/assets/old_images/erpnext/price-list-name.png
new file mode 100644
index 0000000..27e1d89
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/price-list-name.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/price-list-territory.png b/erpnext/docs/assets/old_images/erpnext/price-list-territory.png
new file mode 100644
index 0000000..2ea3ecf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/price-list-territory.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/print-heading1.png b/erpnext/docs/assets/old_images/erpnext/print-heading1.png
new file mode 100644
index 0000000..32de28c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/print-heading1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/print-heading2.png b/erpnext/docs/assets/old_images/erpnext/print-heading2.png
new file mode 100644
index 0000000..a3f86f0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/print-heading2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/production-order-2.png b/erpnext/docs/assets/old_images/erpnext/production-order-2.png
new file mode 100644
index 0000000..4e493d1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/production-order-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/production-order.png b/erpnext/docs/assets/old_images/erpnext/production-order.png
new file mode 100644
index 0000000..4d5c386
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/production-order.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/projected-quantity-stock-report.png b/erpnext/docs/assets/old_images/erpnext/projected-quantity-stock-report.png
new file mode 100644
index 0000000..b7d0a90
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/projected-quantity-stock-report.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/projects-sp.png b/erpnext/docs/assets/old_images/erpnext/projects-sp.png
new file mode 100644
index 0000000..342515e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/projects-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/projects.png b/erpnext/docs/assets/old_images/erpnext/projects.png
new file mode 100644
index 0000000..aff4f86
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/projects.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-invoice-2.png b/erpnext/docs/assets/old_images/erpnext/purchase-invoice-2.png
new file mode 100644
index 0000000..575d4af
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-invoice-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-invoice.png b/erpnext/docs/assets/old_images/erpnext/purchase-invoice.png
new file mode 100644
index 0000000..df65a1d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-order-f.jpg b/erpnext/docs/assets/old_images/erpnext/purchase-order-f.jpg
new file mode 100644
index 0000000..0ff3ed0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-order-f.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-order-uom-change.png b/erpnext/docs/assets/old_images/erpnext/purchase-order-uom-change.png
new file mode 100644
index 0000000..e651a4d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-order-uom-change.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-order.png b/erpnext/docs/assets/old_images/erpnext/purchase-order.png
new file mode 100644
index 0000000..49fbf72
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-order.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-receipt.png b/erpnext/docs/assets/old_images/erpnext/purchase-receipt.png
new file mode 100644
index 0000000..8ad956b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-receipt.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase-taxes.png b/erpnext/docs/assets/old_images/erpnext/purchase-taxes.png
new file mode 100644
index 0000000..508bf4e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase-taxes.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase_receipt_gl_entries.png b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_gl_entries.png
new file mode 100644
index 0000000..9629bfe
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_gl_entries.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase_receipt_stock_ledger_entries.png b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_stock_ledger_entries.png
new file mode 100644
index 0000000..964e15e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_stock_ledger_entries.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/purchase_receipt_taxes_and_charges.png b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_taxes_and_charges.png
new file mode 100644
index 0000000..eb3be11
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/purchase_receipt_taxes_and_charges.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quality-inspection-2.png b/erpnext/docs/assets/old_images/erpnext/quality-inspection-2.png
new file mode 100644
index 0000000..17ebed7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quality-inspection-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quality-inspection-3.png b/erpnext/docs/assets/old_images/erpnext/quality-inspection-3.png
new file mode 100644
index 0000000..c4da2e5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quality-inspection-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quality-inspection.png b/erpnext/docs/assets/old_images/erpnext/quality-inspection.png
new file mode 100644
index 0000000..27c90e8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quality-inspection.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/query-report-accounts-payable.png b/erpnext/docs/assets/old_images/erpnext/query-report-accounts-payable.png
new file mode 100644
index 0000000..3a9e645
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/query-report-accounts-payable.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/query-report-sales-register.png b/erpnext/docs/assets/old_images/erpnext/query-report-sales-register.png
new file mode 100644
index 0000000..0e23430
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/query-report-sales-register.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quotation-1.png b/erpnext/docs/assets/old_images/erpnext/quotation-1.png
new file mode 100644
index 0000000..cf05760
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quotation-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quotation-2.png b/erpnext/docs/assets/old_images/erpnext/quotation-2.png
new file mode 100644
index 0000000..cb705ab
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quotation-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/quotation.png b/erpnext/docs/assets/old_images/erpnext/quotation.png
new file mode 100644
index 0000000..6e2cdbf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/quotation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/reconciliation-data.png b/erpnext/docs/assets/old_images/erpnext/reconciliation-data.png
new file mode 100644
index 0000000..52319d6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/reconciliation-data.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-general.png b/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-general.png
new file mode 100644
index 0000000..d871e35
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-general.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-sog.png b/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-sog.png
new file mode 100644
index 0000000..b2b0c23
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/rename-jute-bag-sog.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/rename-output.png b/erpnext/docs/assets/old_images/erpnext/rename-output.png
new file mode 100644
index 0000000..0d9ae3f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/rename-output.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/repack-1.png b/erpnext/docs/assets/old_images/erpnext/repack-1.png
new file mode 100644
index 0000000..447eb9c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/repack-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/repack-2.png b/erpnext/docs/assets/old_images/erpnext/repack-2.png
new file mode 100644
index 0000000..bf6c9b2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/repack-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/salary-manager.png b/erpnext/docs/assets/old_images/erpnext/salary-manager.png
new file mode 100644
index 0000000..0f62b33
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/salary-manager.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/salary-slip-1.png b/erpnext/docs/assets/old_images/erpnext/salary-slip-1.png
new file mode 100644
index 0000000..9ed66a5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/salary-slip-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/salary-structure.png b/erpnext/docs/assets/old_images/erpnext/salary-structure.png
new file mode 100644
index 0000000..8e7e6b3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/salary-structure.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-analytics-customer.png b/erpnext/docs/assets/old_images/erpnext/sales-analytics-customer.png
new file mode 100644
index 0000000..bb51d60
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-analytics-customer.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-bom-.png b/erpnext/docs/assets/old_images/erpnext/sales-bom-.png
new file mode 100644
index 0000000..b05b0a6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-bom-.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-bom-usein-so.png b/erpnext/docs/assets/old_images/erpnext/sales-bom-usein-so.png
new file mode 100644
index 0000000..95b0225
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-bom-usein-so.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-invoice.png b/erpnext/docs/assets/old_images/erpnext/sales-invoice.png
new file mode 100644
index 0000000..54f6311
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-invoice.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-order-f.jpg b/erpnext/docs/assets/old_images/erpnext/sales-order-f.jpg
new file mode 100644
index 0000000..084b651
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-order-f.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-order-list-distributor.png b/erpnext/docs/assets/old_images/erpnext/sales-order-list-distributor.png
new file mode 100644
index 0000000..b5379b6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-order-list-distributor.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-order-recurring.png b/erpnext/docs/assets/old_images/erpnext/sales-order-recurring.png
new file mode 100644
index 0000000..bcb8416
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-order-recurring.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-order.png b/erpnext/docs/assets/old_images/erpnext/sales-order.png
new file mode 100644
index 0000000..6cef259
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-order.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-address.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-address.png
new file mode 100644
index 0000000..9896705
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-address.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-listing.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-listing.png
new file mode 100644
index 0000000..944a7da
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-listing.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-name.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-name.png
new file mode 100644
index 0000000..7eba7a2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-name.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-published.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-published.png
new file mode 100644
index 0000000..631ca31
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-published.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-target.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-target.png
new file mode 100644
index 0000000..467b132
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-target.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-partner-website.png b/erpnext/docs/assets/old_images/erpnext/sales-partner-website.png
new file mode 100644
index 0000000..8cf839c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-partner-website.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-1.png b/erpnext/docs/assets/old_images/erpnext/sales-person-1.png
new file mode 100644
index 0000000..a907d73
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-2.png b/erpnext/docs/assets/old_images/erpnext/sales-person-2.png
new file mode 100644
index 0000000..2b4991d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-add.png b/erpnext/docs/assets/old_images/erpnext/sales-person-add.png
new file mode 100644
index 0000000..0c8ead3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-add.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-employee.png b/erpnext/docs/assets/old_images/erpnext/sales-person-employee.png
new file mode 100644
index 0000000..ca460e5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-employee.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-item-group-report.png b/erpnext/docs/assets/old_images/erpnext/sales-person-item-group-report.png
new file mode 100644
index 0000000..de1c6b8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-item-group-report.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-new.png b/erpnext/docs/assets/old_images/erpnext/sales-person-new.png
new file mode 100644
index 0000000..7824e6d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-new.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-target-distribution.png b/erpnext/docs/assets/old_images/erpnext/sales-person-target-distribution.png
new file mode 100644
index 0000000..d10da04
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-target-distribution.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-target-item-group.png b/erpnext/docs/assets/old_images/erpnext/sales-person-target-item-group.png
new file mode 100644
index 0000000..e1a2eb5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-target-item-group.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-territory-manager.png b/erpnext/docs/assets/old_images/erpnext/sales-person-territory-manager.png
new file mode 100644
index 0000000..51f470b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-territory-manager.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-person-territory-report.png b/erpnext/docs/assets/old_images/erpnext/sales-person-territory-report.png
new file mode 100644
index 0000000..154a73d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-person-territory-report.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales-tax-master.png b/erpnext/docs/assets/old_images/erpnext/sales-tax-master.png
new file mode 100644
index 0000000..8a1127d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales-tax-master.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales_bom_child_in_transaction.png b/erpnext/docs/assets/old_images/erpnext/sales_bom_child_in_transaction.png
new file mode 100644
index 0000000..187192f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales_bom_child_in_transaction.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales_bom_item.png b/erpnext/docs/assets/old_images/erpnext/sales_bom_item.png
new file mode 100644
index 0000000..3d05240
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales_bom_item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales_bom_main_in_transaction.png b/erpnext/docs/assets/old_images/erpnext/sales_bom_main_in_transaction.png
new file mode 100644
index 0000000..8066ac8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales_bom_main_in_transaction.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sales_bom_packed_items.png b/erpnext/docs/assets/old_images/erpnext/sales_bom_packed_items.png
new file mode 100644
index 0000000..3158844
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sales_bom_packed_items.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts-jv.png b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts-jv.png
new file mode 100644
index 0000000..2192b00
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts-jv.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts.png b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts.png
new file mode 100644
index 0000000..ce9a3f9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-accounts.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/seconddaysetup-hr.png b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-hr.png
new file mode 100644
index 0000000..ac754a2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-hr.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/seconddaysetup-stock-opening.png b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-stock-opening.png
new file mode 100644
index 0000000..3968eda
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-stock-opening.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/seconddaysetup-tree.png b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-tree.png
new file mode 100644
index 0000000..e030f3c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/seconddaysetup-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/selling-setup.png b/erpnext/docs/assets/old_images/erpnext/selling-setup.png
new file mode 100644
index 0000000..d0de2df
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/selling-setup.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/serial-no-auto-1.png b/erpnext/docs/assets/old_images/erpnext/serial-no-auto-1.png
new file mode 100644
index 0000000..60555d0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/serial-no-auto-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/serial-no-auto-2.png b/erpnext/docs/assets/old_images/erpnext/serial-no-auto-2.png
new file mode 100644
index 0000000..a5dd54b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/serial-no-auto-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/serial-no-entry.png b/erpnext/docs/assets/old_images/erpnext/serial-no-entry.png
new file mode 100644
index 0000000..581fb47
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/serial-no-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/service-provider-desktop.png b/erpnext/docs/assets/old_images/erpnext/service-provider-desktop.png
new file mode 100644
index 0000000..e7114d8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/service-provider-desktop.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/service-provider-item.png b/erpnext/docs/assets/old_images/erpnext/service-provider-item.png
new file mode 100644
index 0000000..8641580
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/service-provider-item.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/service-provider-quotation.png b/erpnext/docs/assets/old_images/erpnext/service-provider-quotation.png
new file mode 100644
index 0000000..d827628
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/service-provider-quotation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-role.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-role.png
new file mode 100644
index 0000000..e2a2bd6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-role.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-user-permissions.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-user-permissions.png
new file mode 100644
index 0000000..80ce1e1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-employee-user-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-manager-role.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-manager-role.png
new file mode 100644
index 0000000..d3f268e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-manager-role.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-user-role.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-user-role.png
new file mode 100644
index 0000000..36220e2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-hr-user-role.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application-form.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application-form.png
new file mode 100644
index 0000000..3da67c4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application-form.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application.png
new file mode 100644
index 0000000..21bf7ac
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-application.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-approver-role.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-approver-role.png
new file mode 100644
index 0000000..5174fd8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-leave-approver-role.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-level-1.png b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-level-1.png
new file mode 100644
index 0000000..ffa0d07
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setting-up-permissions-level-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setup/email-alert-1.png b/erpnext/docs/assets/old_images/erpnext/setup/email-alert-1.png
new file mode 100644
index 0000000..d1a7f02
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setup/email-alert-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/setup/email-alert-2.png b/erpnext/docs/assets/old_images/erpnext/setup/email-alert-2.png
new file mode 100644
index 0000000..25dc8d3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/setup/email-alert-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/shopping-cart-1.png b/erpnext/docs/assets/old_images/erpnext/shopping-cart-1.png
new file mode 100644
index 0000000..2611ce4
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/shopping-cart-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/shopping-cart-2.png b/erpnext/docs/assets/old_images/erpnext/shopping-cart-2.png
new file mode 100644
index 0000000..868c170
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/shopping-cart-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-1.png b/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-1.png
new file mode 100644
index 0000000..d9ab164
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-amount.png b/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-amount.png
new file mode 100644
index 0000000..6fd5f000
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/shopping-cart-display-amount.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sms-setting2.jpg b/erpnext/docs/assets/old_images/erpnext/sms-setting2.jpg
new file mode 100644
index 0000000..4b1e8f3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sms-setting2.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sms-settings1.png b/erpnext/docs/assets/old_images/erpnext/sms-settings1.png
new file mode 100644
index 0000000..64678d0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sms-settings1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/sog-spoon-stand.jpg b/erpnext/docs/assets/old_images/erpnext/sog-spoon-stand.jpg
new file mode 100644
index 0000000..dde1b43
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/sog-spoon-stand.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-campaign-naming-by.png b/erpnext/docs/assets/old_images/erpnext/ss-campaign-naming-by.png
new file mode 100644
index 0000000..fd14cde
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-campaign-naming-by.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-customer-group-error.png b/erpnext/docs/assets/old_images/erpnext/ss-customer-group-error.png
new file mode 100644
index 0000000..0b32d06
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-customer-group-error.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-customer-naming-by.png b/erpnext/docs/assets/old_images/erpnext/ss-customer-naming-by.png
new file mode 100644
index 0000000..0b565d5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-customer-naming-by.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-default-customer-group.png b/erpnext/docs/assets/old_images/erpnext/ss-default-customer-group.png
new file mode 100644
index 0000000..885c978
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-default-customer-group.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-default-price-list.png b/erpnext/docs/assets/old_images/erpnext/ss-default-price-list.png
new file mode 100644
index 0000000..0678cde
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-default-price-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-default-territory.png b/erpnext/docs/assets/old_images/erpnext/ss-default-territory.png
new file mode 100644
index 0000000..f2ce83c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-default-territory.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-delivery-note-required.png b/erpnext/docs/assets/old_images/erpnext/ss-delivery-note-required.png
new file mode 100644
index 0000000..9b447b3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-delivery-note-required.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-edit-price-list-rate.png b/erpnext/docs/assets/old_images/erpnext/ss-edit-price-list-rate.png
new file mode 100644
index 0000000..5bc5b10
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-edit-price-list-rate.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-sales-order-required.png b/erpnext/docs/assets/old_images/erpnext/ss-sales-order-required.png
new file mode 100644
index 0000000..9174957
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-sales-order-required.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/ss-same-rate-throughout.png b/erpnext/docs/assets/old_images/erpnext/ss-same-rate-throughout.png
new file mode 100644
index 0000000..38c23a8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/ss-same-rate-throughout.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-balance-report-jps-1.png b/erpnext/docs/assets/old_images/erpnext/stock-balance-report-jps-1.png
new file mode 100644
index 0000000..3533cc9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-balance-report-jps-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-entry-repack.png b/erpnext/docs/assets/old_images/erpnext/stock-entry-repack.png
new file mode 100644
index 0000000..d78e717
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-entry-repack.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-entry.png b/erpnext/docs/assets/old_images/erpnext/stock-entry.png
new file mode 100644
index 0000000..b0198bf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-entry.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-inventory.png b/erpnext/docs/assets/old_images/erpnext/stock-inventory.png
new file mode 100644
index 0000000..26bb7dc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-inventory.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-ledger-report-sr000001.png b/erpnext/docs/assets/old_images/erpnext/stock-ledger-report-sr000001.png
new file mode 100644
index 0000000..92bfe3d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-ledger-report-sr000001.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reco-browse.png b/erpnext/docs/assets/old_images/erpnext/stock-reco-browse.png
new file mode 100644
index 0000000..6113043
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reco-browse.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reco-data.png b/erpnext/docs/assets/old_images/erpnext/stock-reco-data.png
new file mode 100644
index 0000000..50c027e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reco-data.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reco-ledger.png b/erpnext/docs/assets/old_images/erpnext/stock-reco-ledger.png
new file mode 100644
index 0000000..811689f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reco-ledger.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reco-template.png b/erpnext/docs/assets/old_images/erpnext/stock-reco-template.png
new file mode 100644
index 0000000..7b1bb6d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reco-template.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reco-upload.png b/erpnext/docs/assets/old_images/erpnext/stock-reco-upload.png
new file mode 100644
index 0000000..1c6d7d0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reco-upload.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-recociliation-upload.png b/erpnext/docs/assets/old_images/erpnext/stock-recociliation-upload.png
new file mode 100644
index 0000000..4b8b082
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-recociliation-upload.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-4.png b/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-4.png
new file mode 100644
index 0000000..8b8d450
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-with-data.png b/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-with-data.png
new file mode 100644
index 0000000..f6ff914
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/stock-reconciliation-with-data.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/subcontract.png b/erpnext/docs/assets/old_images/erpnext/subcontract.png
new file mode 100644
index 0000000..a199314
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/subcontract.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier-1.png b/erpnext/docs/assets/old_images/erpnext/supplier-1.png
new file mode 100644
index 0000000..88971be
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier-quotation-f.jpg b/erpnext/docs/assets/old_images/erpnext/supplier-quotation-f.jpg
new file mode 100644
index 0000000..03c50de
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier-quotation-f.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier-quotation-list-distributor.png b/erpnext/docs/assets/old_images/erpnext/supplier-quotation-list-distributor.png
new file mode 100644
index 0000000..9ccdeda
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier-quotation-list-distributor.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier-quotation.png b/erpnext/docs/assets/old_images/erpnext/supplier-quotation.png
new file mode 100644
index 0000000..25ab739
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier-quotation.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier-type.png b/erpnext/docs/assets/old_images/erpnext/supplier-type.png
new file mode 100644
index 0000000..5cfa18f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier-type.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/supplier.png b/erpnext/docs/assets/old_images/erpnext/supplier.png
new file mode 100644
index 0000000..447ef76
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/supplier.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/support-sp.png b/erpnext/docs/assets/old_images/erpnext/support-sp.png
new file mode 100644
index 0000000..d94c45f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/support-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/support-ticket.png b/erpnext/docs/assets/old_images/erpnext/support-ticket.png
new file mode 100644
index 0000000..e1e078e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/support-ticket.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/tags-in-list.png b/erpnext/docs/assets/old_images/erpnext/tags-in-list.png
new file mode 100644
index 0000000..257ab5f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/tags-in-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/tags.png b/erpnext/docs/assets/old_images/erpnext/tags.png
new file mode 100644
index 0000000..3211f52
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/tags.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/target-distribution.png b/erpnext/docs/assets/old_images/erpnext/target-distribution.png
new file mode 100644
index 0000000..7e451cd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/target-distribution.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/tasks.png b/erpnext/docs/assets/old_images/erpnext/tasks.png
new file mode 100644
index 0000000..9f89994
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/tasks.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/taxes-master-sp.png b/erpnext/docs/assets/old_images/erpnext/taxes-master-sp.png
new file mode 100644
index 0000000..7e301b5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/taxes-master-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/terms-and-condition-data.png b/erpnext/docs/assets/old_images/erpnext/terms-and-condition-data.png
new file mode 100644
index 0000000..9446887
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/terms-and-condition-data.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/terms-and-condition-transactions.png b/erpnext/docs/assets/old_images/erpnext/terms-and-condition-transactions.png
new file mode 100644
index 0000000..b568fa1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/terms-and-condition-transactions.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/terms-edit-in-html.png b/erpnext/docs/assets/old_images/erpnext/terms-edit-in-html.png
new file mode 100644
index 0000000..e60edb6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/terms-edit-in-html.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/terms-in-html.png b/erpnext/docs/assets/old_images/erpnext/terms-in-html.png
new file mode 100644
index 0000000..b510d84
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/terms-in-html.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/terms.png b/erpnext/docs/assets/old_images/erpnext/terms.png
new file mode 100644
index 0000000..d65934f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/terms.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/territory-1.png b/erpnext/docs/assets/old_images/erpnext/territory-1.png
new file mode 100644
index 0000000..159b465
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/territory-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/territory-2.png b/erpnext/docs/assets/old_images/erpnext/territory-2.png
new file mode 100644
index 0000000..371ec78
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/territory-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/territory-tree-1.png b/erpnext/docs/assets/old_images/erpnext/territory-tree-1.png
new file mode 100644
index 0000000..10f9c7c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/territory-tree-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/territory-tree.png b/erpnext/docs/assets/old_images/erpnext/territory-tree.png
new file mode 100644
index 0000000..1535657
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/territory-tree.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/third-party-backups.png b/erpnext/docs/assets/old_images/erpnext/third-party-backups.png
new file mode 100644
index 0000000..3bd10c8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/third-party-backups.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/time-log.png b/erpnext/docs/assets/old_images/erpnext/time-log.png
new file mode 100644
index 0000000..600ebdd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/time-log.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog1.jpg b/erpnext/docs/assets/old_images/erpnext/timelog1.jpg
new file mode 100644
index 0000000..2d23ef6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog1.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog2.jpg b/erpnext/docs/assets/old_images/erpnext/timelog2.jpg
new file mode 100644
index 0000000..424739c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog2.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog3.jpg b/erpnext/docs/assets/old_images/erpnext/timelog3.jpg
new file mode 100644
index 0000000..dd1c11e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog3.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog4.jpg b/erpnext/docs/assets/old_images/erpnext/timelog4.jpg
new file mode 100644
index 0000000..2b74e1c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog4.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog5.jpg b/erpnext/docs/assets/old_images/erpnext/timelog5.jpg
new file mode 100644
index 0000000..492f9c0
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog5.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog6.jpg b/erpnext/docs/assets/old_images/erpnext/timelog6.jpg
new file mode 100644
index 0000000..070ef60
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog6.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/timelog7.jpg b/erpnext/docs/assets/old_images/erpnext/timelog7.jpg
new file mode 100644
index 0000000..1d1d2ca
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/timelog7.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/to-do.png b/erpnext/docs/assets/old_images/erpnext/to-do.png
new file mode 100644
index 0000000..c6504d3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/to-do.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/todo-close.png b/erpnext/docs/assets/old_images/erpnext/todo-close.png
new file mode 100644
index 0000000..5ef0b2a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/todo-close.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/todo-list.png b/erpnext/docs/assets/old_images/erpnext/todo-list.png
new file mode 100644
index 0000000..fc65ced
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/todo-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/transfer-raw-material.png b/erpnext/docs/assets/old_images/erpnext/transfer-raw-material.png
new file mode 100644
index 0000000..14bf8ef
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/transfer-raw-material.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/trial-balance-1.png b/erpnext/docs/assets/old_images/erpnext/trial-balance-1.png
new file mode 100644
index 0000000..a4322e9
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/trial-balance-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/trial-balance.png b/erpnext/docs/assets/old_images/erpnext/trial-balance.png
new file mode 100644
index 0000000..46d217f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/trial-balance.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/triangle-button-company.png b/erpnext/docs/assets/old_images/erpnext/triangle-button-company.png
new file mode 100644
index 0000000..6e2273b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/triangle-button-company.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/unionglobal-coffeemaker.jpg b/erpnext/docs/assets/old_images/erpnext/unionglobal-coffeemaker.jpg
new file mode 100644
index 0000000..9b9fdd7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/unionglobal-coffeemaker.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/unionglobal-ricecooker.jpg b/erpnext/docs/assets/old_images/erpnext/unionglobal-ricecooker.jpg
new file mode 100644
index 0000000..ee05a8a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/unionglobal-ricecooker.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/unionglobal-tumbledryer.jpg b/erpnext/docs/assets/old_images/erpnext/unionglobal-tumbledryer.jpg
new file mode 100644
index 0000000..c4d6400
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/unionglobal-tumbledryer.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/upload-attendance.png b/erpnext/docs/assets/old_images/erpnext/upload-attendance.png
new file mode 100644
index 0000000..8dcb741
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/upload-attendance.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permission-user-limited-by-company.png b/erpnext/docs/assets/old_images/erpnext/user-permission-user-limited-by-company.png
new file mode 100644
index 0000000..717cf84
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permission-user-limited-by-company.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-company-role-all.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-company-role-all.png
new file mode 100644
index 0000000..3fac69a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-company-role-all.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-company-wind-power-llc.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-company-wind-power-llc.png
new file mode 100644
index 0000000..bd57719
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-company-wind-power-llc.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-company.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-company.png
new file mode 100644
index 0000000..f0c5ba5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-company.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-ignore-user-permissions.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-ignore-user-permissions.png
new file mode 100644
index 0000000..84cea52
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-ignore-user-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-based-on-territory.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-based-on-territory.png
new file mode 100644
index 0000000..e0b2373
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-based-on-territory.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-role-permissions.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-role-permissions.png
new file mode 100644
index 0000000..6ec0fcf
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-lead-role-permissions.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-list.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-list.png
new file mode 100644
index 0000000..8a7e9c6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-list.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-sales-user.png b/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-sales-user.png
new file mode 100644
index 0000000..7f382c8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user-permissions-quotation-sales-user.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user1.png b/erpnext/docs/assets/old_images/erpnext/user1.png
new file mode 100644
index 0000000..4c30c26
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user2.png b/erpnext/docs/assets/old_images/erpnext/user2.png
new file mode 100644
index 0000000..a16c627
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user3.png b/erpnext/docs/assets/old_images/erpnext/user3.png
new file mode 100644
index 0000000..490305b
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/user4.png b/erpnext/docs/assets/old_images/erpnext/user4.png
new file mode 100644
index 0000000..c3686dc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/user4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/warehouse.png b/erpnext/docs/assets/old_images/erpnext/warehouse.png
new file mode 100644
index 0000000..406c5a8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/warehouse.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/webpage-itemgroup-display.png b/erpnext/docs/assets/old_images/erpnext/webpage-itemgroup-display.png
new file mode 100644
index 0000000..7981e4f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/webpage-itemgroup-display.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/webpage-labels.png b/erpnext/docs/assets/old_images/erpnext/webpage-labels.png
new file mode 100644
index 0000000..3182ab7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/webpage-labels.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/webpage.png b/erpnext/docs/assets/old_images/erpnext/webpage.png
new file mode 100644
index 0000000..08b5d63
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/webpage.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-settings-1.png b/erpnext/docs/assets/old_images/erpnext/website-settings-1.png
new file mode 100644
index 0000000..03b1e3a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-settings-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-settings-2.png b/erpnext/docs/assets/old_images/erpnext/website-settings-2.png
new file mode 100644
index 0000000..2ec234d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-settings-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-settings-3.png b/erpnext/docs/assets/old_images/erpnext/website-settings-3.png
new file mode 100644
index 0000000..c6d3bf7
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-settings-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-settings-4.png b/erpnext/docs/assets/old_images/erpnext/website-settings-4.png
new file mode 100644
index 0000000..c8abb42
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-settings-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-settings.png b/erpnext/docs/assets/old_images/erpnext/website-settings.png
new file mode 100644
index 0000000..9455c15
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-settings.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website-sp.png b/erpnext/docs/assets/old_images/erpnext/website-sp.png
new file mode 100644
index 0000000..2e3a1c2
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website-sp.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/Customer-group-add.png b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-add.png
new file mode 100644
index 0000000..322b6dd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-add.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/Customer-group-form.png b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-form.png
new file mode 100644
index 0000000..266ddc1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-form.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/Customer-group-new.png b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-new.png
new file mode 100644
index 0000000..5e42a0d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/Customer-group-new.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/make-web-form.gif b/erpnext/docs/assets/old_images/erpnext/website/make-web-form.gif
new file mode 100644
index 0000000..783d10c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/make-web-form.gif
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/view-web-form.gif b/erpnext/docs/assets/old_images/erpnext/website/view-web-form.gif
new file mode 100644
index 0000000..def4359
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/view-web-form.gif
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/website/web-form-event.png b/erpnext/docs/assets/old_images/erpnext/website/web-form-event.png
new file mode 100644
index 0000000..3c90103
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/website/web-form-event.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-employee-la.png b/erpnext/docs/assets/old_images/erpnext/workflow-employee-la.png
new file mode 100644
index 0000000..e0878a3
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-employee-la.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-hr-user-la.png b/erpnext/docs/assets/old_images/erpnext/workflow-hr-user-la.png
new file mode 100644
index 0000000..80f3ecc
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-hr-user-la.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-leave-approver-la.png b/erpnext/docs/assets/old_images/erpnext/workflow-leave-approver-la.png
new file mode 100644
index 0000000..26ff3e6
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-leave-approver-la.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-leave-fl.jpg b/erpnext/docs/assets/old_images/erpnext/workflow-leave-fl.jpg
new file mode 100644
index 0000000..3430974
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-leave-fl.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-leave1.png b/erpnext/docs/assets/old_images/erpnext/workflow-leave1.png
new file mode 100644
index 0000000..67a3d75
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-leave1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/erpnext/workflow-leave2.png b/erpnext/docs/assets/old_images/erpnext/workflow-leave2.png
new file mode 100644
index 0000000..7cdc676
--- /dev/null
+++ b/erpnext/docs/assets/old_images/erpnext/workflow-leave2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-1.png b/erpnext/docs/assets/old_images/features/feature-1.png
new file mode 100644
index 0000000..2809c14
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-10.png b/erpnext/docs/assets/old_images/features/feature-10.png
new file mode 100644
index 0000000..4945aab
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-10.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-11.png b/erpnext/docs/assets/old_images/features/feature-11.png
new file mode 100644
index 0000000..8b4ee81
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-11.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-2.png b/erpnext/docs/assets/old_images/features/feature-2.png
new file mode 100644
index 0000000..d986b33
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-3.png b/erpnext/docs/assets/old_images/features/feature-3.png
new file mode 100644
index 0000000..2785eab
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-4.png b/erpnext/docs/assets/old_images/features/feature-4.png
new file mode 100644
index 0000000..dedeb9c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-5.png b/erpnext/docs/assets/old_images/features/feature-5.png
new file mode 100644
index 0000000..207796d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-6.png b/erpnext/docs/assets/old_images/features/feature-6.png
new file mode 100644
index 0000000..86ada5a
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-6.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-7.png b/erpnext/docs/assets/old_images/features/feature-7.png
new file mode 100644
index 0000000..fde736d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-7.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-8.png b/erpnext/docs/assets/old_images/features/feature-8.png
new file mode 100644
index 0000000..60d59e1
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-8.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/features/feature-9.png b/erpnext/docs/assets/old_images/features/feature-9.png
new file mode 100644
index 0000000..acb7414
--- /dev/null
+++ b/erpnext/docs/assets/old_images/features/feature-9.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/person-6.jpg b/erpnext/docs/assets/old_images/person-6.jpg
new file mode 100644
index 0000000..d458e85
--- /dev/null
+++ b/erpnext/docs/assets/old_images/person-6.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/px_by_Gre3g.png b/erpnext/docs/assets/old_images/px_by_Gre3g.png
new file mode 100644
index 0000000..aad9ba5
--- /dev/null
+++ b/erpnext/docs/assets/old_images/px_by_Gre3g.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/repair-1.jpg b/erpnext/docs/assets/old_images/repair-1.jpg
new file mode 100644
index 0000000..d7a4355
--- /dev/null
+++ b/erpnext/docs/assets/old_images/repair-1.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/sharing.jpg b/erpnext/docs/assets/old_images/sharing.jpg
new file mode 100644
index 0000000..0e2a615
--- /dev/null
+++ b/erpnext/docs/assets/old_images/sharing.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/aditya-duggal.png b/erpnext/docs/assets/old_images/stories/aditya-duggal.png
new file mode 100644
index 0000000..34e3486
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/aditya-duggal.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/alcon-logo.png b/erpnext/docs/assets/old_images/stories/alcon-logo.png
new file mode 100644
index 0000000..f6dec2c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/alcon-logo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/becht.jpg b/erpnext/docs/assets/old_images/stories/becht.jpg
new file mode 100644
index 0000000..0bfd4cd
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/becht.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-1.png b/erpnext/docs/assets/old_images/stories/fritzing-1.png
new file mode 100644
index 0000000..7d8928c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-board.png b/erpnext/docs/assets/old_images/stories/fritzing-board.png
new file mode 100644
index 0000000..0696e4f
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-board.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-board2.png b/erpnext/docs/assets/old_images/stories/fritzing-board2.png
new file mode 100644
index 0000000..a2ad866
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-board2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-lab.png b/erpnext/docs/assets/old_images/stories/fritzing-lab.png
new file mode 100644
index 0000000..b666460
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-lab.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-logo.png b/erpnext/docs/assets/old_images/stories/fritzing-logo.png
new file mode 100644
index 0000000..687ee7e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-logo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/fritzing-ohs.png b/erpnext/docs/assets/old_images/stories/fritzing-ohs.png
new file mode 100644
index 0000000..e9f0af8
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/fritzing-ohs.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/hisham_farid.jpg b/erpnext/docs/assets/old_images/stories/hisham_farid.jpg
new file mode 100644
index 0000000..5dc4d2c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/hisham_farid.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/laurence.jpg b/erpnext/docs/assets/old_images/stories/laurence.jpg
new file mode 100644
index 0000000..0d32939
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/laurence.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/max_morais.jpg b/erpnext/docs/assets/old_images/stories/max_morais.jpg
new file mode 100644
index 0000000..b4ee6ca
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/max_morais.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/rigpl-logo.png b/erpnext/docs/assets/old_images/stories/rigpl-logo.png
new file mode 100644
index 0000000..f4938e9e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/rigpl-logo.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/rigpl-products.png b/erpnext/docs/assets/old_images/stories/rigpl-products.png
new file mode 100644
index 0000000..9251914
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/rigpl-products.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/tarun-gupta-neural.jpg b/erpnext/docs/assets/old_images/stories/tarun-gupta-neural.jpg
new file mode 100644
index 0000000..6200479
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/tarun-gupta-neural.jpg
Binary files differ
diff --git a/erpnext/docs/assets/old_images/stories/zel-ortiz.png b/erpnext/docs/assets/old_images/stories/zel-ortiz.png
new file mode 100644
index 0000000..e68941d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/stories/zel-ortiz.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-1.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-1.png
new file mode 100644
index 0000000..c420597
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-1.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-2.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-2.png
new file mode 100644
index 0000000..4c0bd14
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-2.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-3.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-3.png
new file mode 100644
index 0000000..11b184e
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-3.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-4.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-4.png
new file mode 100644
index 0000000..54dd15d
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-4.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-5.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-5.png
new file mode 100644
index 0000000..b879e11
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-5.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-6.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-6.png
new file mode 100644
index 0000000..e024005
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-6.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-7.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-7.png
new file mode 100644
index 0000000..13bdc4c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-7.png
Binary files differ
diff --git a/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-8.png b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-8.png
new file mode 100644
index 0000000..bdbe64c
--- /dev/null
+++ b/erpnext/docs/assets/old_images/user-guide/setup-wizard/setup-wizard-8.png
Binary files differ
diff --git a/erpnext/docs/current/api/accounts/erpnext.accounts.general_ledger.html b/erpnext/docs/current/api/accounts/erpnext.accounts.general_ledger.html
index 33fa85f..c04c2f9 100644
--- a/erpnext/docs/current/api/accounts/erpnext.accounts.general_ledger.html
+++ b/erpnext/docs/current/api/accounts/erpnext.accounts.general_ledger.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.general_ledger --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/general_ledger.py"
diff --git a/erpnext/docs/current/api/accounts/erpnext.accounts.html b/erpnext/docs/current/api/accounts/erpnext.accounts.html
index ccefaf5..6b43dba 100644
--- a/erpnext/docs/current/api/accounts/erpnext.accounts.html
+++ b/erpnext/docs/current/api/accounts/erpnext.accounts.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts.py"
diff --git a/erpnext/docs/current/api/accounts/erpnext.accounts.party.html b/erpnext/docs/current/api/accounts/erpnext.accounts.party.html
index 31caa9f..af32df0 100644
--- a/erpnext/docs/current/api/accounts/erpnext.accounts.party.html
+++ b/erpnext/docs/current/api/accounts/erpnext.accounts.party.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.party --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/party.py"
diff --git a/erpnext/docs/current/api/accounts/erpnext.accounts.utils.html b/erpnext/docs/current/api/accounts/erpnext.accounts.utils.html
index 3fe95fe..4935cd7 100644
--- a/erpnext/docs/current/api/accounts/erpnext.accounts.utils.html
+++ b/erpnext/docs/current/api/accounts/erpnext.accounts.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/utils.py"
diff --git a/erpnext/docs/current/api/accounts/index.html b/erpnext/docs/current/api/accounts/index.html
index 9f6ab14..1a64d9f 100644
--- a/erpnext/docs/current/api/accounts/index.html
+++ b/erpnext/docs/current/api/accounts/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/accounts"
diff --git a/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/erpnext.accounts.print_format.cheque_printing_format.html b/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/erpnext.accounts.print_format.cheque_printing_format.html
index e7b88ad..785bf0a 100644
--- a/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/erpnext.accounts.print_format.cheque_printing_format.html
+++ b/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/erpnext.accounts.print_format.cheque_printing_format.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.print_format.cheque_printing_format --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/print_format/cheque_printing_format.py"
diff --git a/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/index.html b/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/index.html
index 0354aef..acfbf42 100644
--- a/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/index.html
+++ b/erpnext/docs/current/api/accounts/print_format/cheque_printing_format/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/cheque_printing_format"
diff --git a/erpnext/docs/current/api/accounts/print_format/credit_note/erpnext.accounts.print_format.credit_note.html b/erpnext/docs/current/api/accounts/print_format/credit_note/erpnext.accounts.print_format.credit_note.html
index 5312a8e..3034ba4 100644
--- a/erpnext/docs/current/api/accounts/print_format/credit_note/erpnext.accounts.print_format.credit_note.html
+++ b/erpnext/docs/current/api/accounts/print_format/credit_note/erpnext.accounts.print_format.credit_note.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.print_format.credit_note --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/print_format/credit_note.py"
diff --git a/erpnext/docs/current/api/accounts/print_format/credit_note/index.html b/erpnext/docs/current/api/accounts/print_format/credit_note/index.html
index b68c743..2c6948a 100644
--- a/erpnext/docs/current/api/accounts/print_format/credit_note/index.html
+++ b/erpnext/docs/current/api/accounts/print_format/credit_note/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/credit_note"
diff --git a/erpnext/docs/current/api/accounts/print_format/erpnext.accounts.print_format.html b/erpnext/docs/current/api/accounts/print_format/erpnext.accounts.print_format.html
index 6640ee7..73ca9d8 100644
--- a/erpnext/docs/current/api/accounts/print_format/erpnext.accounts.print_format.html
+++ b/erpnext/docs/current/api/accounts/print_format/erpnext.accounts.print_format.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.print_format --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/print_format.py"
diff --git a/erpnext/docs/current/api/accounts/print_format/index.html b/erpnext/docs/current/api/accounts/print_format/index.html
index 07f7381..49a7deb 100644
--- a/erpnext/docs/current/api/accounts/print_format/index.html
+++ b/erpnext/docs/current/api/accounts/print_format/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/print_format"
diff --git a/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/erpnext.accounts.print_format.payment_receipt_voucher.html b/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/erpnext.accounts.print_format.payment_receipt_voucher.html
index b525cb0..72a8746 100644
--- a/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/erpnext.accounts.print_format.payment_receipt_voucher.html
+++ b/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/erpnext.accounts.print_format.payment_receipt_voucher.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.print_format.payment_receipt_voucher --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/print_format/payment_receipt_voucher.py"
diff --git a/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/index.html b/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/index.html
index 7ab73b6..47a3055 100644
--- a/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/index.html
+++ b/erpnext/docs/current/api/accounts/print_format/payment_receipt_voucher/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/payment_receipt_voucher"
diff --git a/erpnext/docs/current/api/accounts/print_format/pos_invoice/erpnext.accounts.print_format.pos_invoice.html b/erpnext/docs/current/api/accounts/print_format/pos_invoice/erpnext.accounts.print_format.pos_invoice.html
index 6c7fcdf..41e3299 100644
--- a/erpnext/docs/current/api/accounts/print_format/pos_invoice/erpnext.accounts.print_format.pos_invoice.html
+++ b/erpnext/docs/current/api/accounts/print_format/pos_invoice/erpnext.accounts.print_format.pos_invoice.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.accounts.print_format.pos_invoice --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/print_format/pos_invoice.py"
diff --git a/erpnext/docs/current/api/accounts/print_format/pos_invoice/index.html b/erpnext/docs/current/api/accounts/print_format/pos_invoice/index.html
index cda5b3b..c379bbf 100644
--- a/erpnext/docs/current/api/accounts/print_format/pos_invoice/index.html
+++ b/erpnext/docs/current/api/accounts/print_format/pos_invoice/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/pos_invoice"
diff --git a/erpnext/docs/current/api/buying/erpnext.buying.html b/erpnext/docs/current/api/buying/erpnext.buying.html
index 46eb03f..67df84b 100644
--- a/erpnext/docs/current/api/buying/erpnext.buying.html
+++ b/erpnext/docs/current/api/buying/erpnext.buying.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.buying --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/buying.py"
diff --git a/erpnext/docs/current/api/buying/index.html b/erpnext/docs/current/api/buying/index.html
index 4a6a2f1..df8d169 100644
--- a/erpnext/docs/current/api/buying/index.html
+++ b/erpnext/docs/current/api/buying/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/buying"
diff --git a/erpnext/docs/current/api/buying/print_format/drop_shipping/erpnext.buying.print_format.drop_shipping.html b/erpnext/docs/current/api/buying/print_format/drop_shipping/erpnext.buying.print_format.drop_shipping.html
index cdd8641..a90102a 100644
--- a/erpnext/docs/current/api/buying/print_format/drop_shipping/erpnext.buying.print_format.drop_shipping.html
+++ b/erpnext/docs/current/api/buying/print_format/drop_shipping/erpnext.buying.print_format.drop_shipping.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.buying.print_format.drop_shipping --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/buying/print_format/drop_shipping.py"
diff --git a/erpnext/docs/current/api/buying/print_format/drop_shipping/index.html b/erpnext/docs/current/api/buying/print_format/drop_shipping/index.html
index 0f2f9f4..258a053 100644
--- a/erpnext/docs/current/api/buying/print_format/drop_shipping/index.html
+++ b/erpnext/docs/current/api/buying/print_format/drop_shipping/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/drop_shipping"
diff --git a/erpnext/docs/current/api/buying/print_format/erpnext.buying.print_format.html b/erpnext/docs/current/api/buying/print_format/erpnext.buying.print_format.html
index de7a42c..01f9401 100644
--- a/erpnext/docs/current/api/buying/print_format/erpnext.buying.print_format.html
+++ b/erpnext/docs/current/api/buying/print_format/erpnext.buying.print_format.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.buying.print_format --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/buying/print_format.py"
diff --git a/erpnext/docs/current/api/buying/print_format/index.html b/erpnext/docs/current/api/buying/print_format/index.html
index 07f7381..49a7deb 100644
--- a/erpnext/docs/current/api/buying/print_format/index.html
+++ b/erpnext/docs/current/api/buying/print_format/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/print_format"
diff --git a/erpnext/docs/current/api/config/erpnext.config.accounts.html b/erpnext/docs/current/api/config/erpnext.config.accounts.html
index 1ea68f3..b04b565 100644
--- a/erpnext/docs/current/api/config/erpnext.config.accounts.html
+++ b/erpnext/docs/current/api/config/erpnext.config.accounts.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.accounts --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/accounts.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.buying.html b/erpnext/docs/current/api/config/erpnext.config.buying.html
index 0065c85..84b4453 100644
--- a/erpnext/docs/current/api/config/erpnext.config.buying.html
+++ b/erpnext/docs/current/api/config/erpnext.config.buying.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.buying --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/buying.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.crm.html b/erpnext/docs/current/api/config/erpnext.config.crm.html
index a189f0f..7ed5e62 100644
--- a/erpnext/docs/current/api/config/erpnext.config.crm.html
+++ b/erpnext/docs/current/api/config/erpnext.config.crm.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.crm --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/crm.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.desktop.html b/erpnext/docs/current/api/config/erpnext.config.desktop.html
index 9374056..408964d 100644
--- a/erpnext/docs/current/api/config/erpnext.config.desktop.html
+++ b/erpnext/docs/current/api/config/erpnext.config.desktop.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.desktop --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/desktop.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.docs.html b/erpnext/docs/current/api/config/erpnext.config.docs.html
index ac7601d..2756e56 100644
--- a/erpnext/docs/current/api/config/erpnext.config.docs.html
+++ b/erpnext/docs/current/api/config/erpnext.config.docs.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.docs --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/docs.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.hr.html b/erpnext/docs/current/api/config/erpnext.config.hr.html
index 37120f6..d13e762 100644
--- a/erpnext/docs/current/api/config/erpnext.config.hr.html
+++ b/erpnext/docs/current/api/config/erpnext.config.hr.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.hr --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/hr.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.html b/erpnext/docs/current/api/config/erpnext.config.html
index 051729d..2380ee8 100644
--- a/erpnext/docs/current/api/config/erpnext.config.html
+++ b/erpnext/docs/current/api/config/erpnext.config.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.learn.html b/erpnext/docs/current/api/config/erpnext.config.learn.html
index d3e04dc..4cc1cf1 100644
--- a/erpnext/docs/current/api/config/erpnext.config.learn.html
+++ b/erpnext/docs/current/api/config/erpnext.config.learn.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.learn --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/learn.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.manufacturing.html b/erpnext/docs/current/api/config/erpnext.config.manufacturing.html
index d60bebb..a1748ee 100644
--- a/erpnext/docs/current/api/config/erpnext.config.manufacturing.html
+++ b/erpnext/docs/current/api/config/erpnext.config.manufacturing.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.manufacturing --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/manufacturing.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.projects.html b/erpnext/docs/current/api/config/erpnext.config.projects.html
index 88ef05c..f0b873c 100644
--- a/erpnext/docs/current/api/config/erpnext.config.projects.html
+++ b/erpnext/docs/current/api/config/erpnext.config.projects.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.projects --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/projects.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.selling.html b/erpnext/docs/current/api/config/erpnext.config.selling.html
index 02040b7..fafca93 100644
--- a/erpnext/docs/current/api/config/erpnext.config.selling.html
+++ b/erpnext/docs/current/api/config/erpnext.config.selling.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.selling --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/selling.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.setup.html b/erpnext/docs/current/api/config/erpnext.config.setup.html
index 34d767a..21db2a8 100644
--- a/erpnext/docs/current/api/config/erpnext.config.setup.html
+++ b/erpnext/docs/current/api/config/erpnext.config.setup.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.setup --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/setup.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.stock.html b/erpnext/docs/current/api/config/erpnext.config.stock.html
index d913152..1886de1 100644
--- a/erpnext/docs/current/api/config/erpnext.config.stock.html
+++ b/erpnext/docs/current/api/config/erpnext.config.stock.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.stock --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/stock.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.support.html b/erpnext/docs/current/api/config/erpnext.config.support.html
index 4bec149..6feb58d 100644
--- a/erpnext/docs/current/api/config/erpnext.config.support.html
+++ b/erpnext/docs/current/api/config/erpnext.config.support.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.support --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/support.py"
diff --git a/erpnext/docs/current/api/config/erpnext.config.website.html b/erpnext/docs/current/api/config/erpnext.config.website.html
index f7452e6..b3672e0 100644
--- a/erpnext/docs/current/api/config/erpnext.config.website.html
+++ b/erpnext/docs/current/api/config/erpnext.config.website.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.config.website --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/config/website.py"
diff --git a/erpnext/docs/current/api/config/index.html b/erpnext/docs/current/api/config/index.html
index 8a2937e..9a768fa 100644
--- a/erpnext/docs/current/api/config/index.html
+++ b/erpnext/docs/current/api/config/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/config"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.accounts_controller.html b/erpnext/docs/current/api/controllers/erpnext.controllers.accounts_controller.html
index 6b12563..d08e008 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.accounts_controller.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.accounts_controller.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.accounts_controller --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/accounts_controller.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.buying_controller.html b/erpnext/docs/current/api/controllers/erpnext.controllers.buying_controller.html
index b7c5a96..f981794 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.buying_controller.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.buying_controller.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.buying_controller --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/buying_controller.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.html b/erpnext/docs/current/api/controllers/erpnext.controllers.html
index 61b2fc6..4c1caf2 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.item_variant.html b/erpnext/docs/current/api/controllers/erpnext.controllers.item_variant.html
index 86e87e9..105405f 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.item_variant.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.item_variant.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.item_variant --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/item_variant.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.print_settings.html b/erpnext/docs/current/api/controllers/erpnext.controllers.print_settings.html
index b9dba69..dd42e0b 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.print_settings.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.print_settings.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.print_settings --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/print_settings.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.queries.html b/erpnext/docs/current/api/controllers/erpnext.controllers.queries.html
index 9ad7252c..c0e2124 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.queries.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.queries.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.queries --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/queries.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.recurring_document.html b/erpnext/docs/current/api/controllers/erpnext.controllers.recurring_document.html
index 3331337..f9ad12d 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.recurring_document.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.recurring_document.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.recurring_document --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/recurring_document.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.sales_and_purchase_return.html b/erpnext/docs/current/api/controllers/erpnext.controllers.sales_and_purchase_return.html
index 6f2e059..ef44ac0 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.sales_and_purchase_return.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.sales_and_purchase_return.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.sales_and_purchase_return --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/sales_and_purchase_return.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.selling_controller.html b/erpnext/docs/current/api/controllers/erpnext.controllers.selling_controller.html
index fd665f6..278fd8f 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.selling_controller.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.selling_controller.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.selling_controller --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/selling_controller.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.status_updater.html b/erpnext/docs/current/api/controllers/erpnext.controllers.status_updater.html
index 8398226..2aed24a 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.status_updater.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.status_updater.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.status_updater --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/status_updater.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.stock_controller.html b/erpnext/docs/current/api/controllers/erpnext.controllers.stock_controller.html
index 31d1747..067ef3b 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.stock_controller.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.stock_controller.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.stock_controller --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/stock_controller.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.taxes_and_totals.html b/erpnext/docs/current/api/controllers/erpnext.controllers.taxes_and_totals.html
index 432b1dc..3a378bf 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.taxes_and_totals.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.taxes_and_totals.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.taxes_and_totals --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/taxes_and_totals.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.trends.html b/erpnext/docs/current/api/controllers/erpnext.controllers.trends.html
index b2864c2..bee83e1 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.trends.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.trends.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.trends --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/trends.py"
diff --git a/erpnext/docs/current/api/controllers/erpnext.controllers.website_list_for_contact.html b/erpnext/docs/current/api/controllers/erpnext.controllers.website_list_for_contact.html
index 8f30794..54597d9 100644
--- a/erpnext/docs/current/api/controllers/erpnext.controllers.website_list_for_contact.html
+++ b/erpnext/docs/current/api/controllers/erpnext.controllers.website_list_for_contact.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.controllers.website_list_for_contact --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/controllers/website_list_for_contact.py"
diff --git a/erpnext/docs/current/api/controllers/index.html b/erpnext/docs/current/api/controllers/index.html
index 248aced..58fa252 100644
--- a/erpnext/docs/current/api/controllers/index.html
+++ b/erpnext/docs/current/api/controllers/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/controllers"
diff --git a/erpnext/docs/current/api/crm/erpnext.crm.html b/erpnext/docs/current/api/crm/erpnext.crm.html
index 8437c30..1580e25 100644
--- a/erpnext/docs/current/api/crm/erpnext.crm.html
+++ b/erpnext/docs/current/api/crm/erpnext.crm.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.crm --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/crm.py"
diff --git a/erpnext/docs/current/api/crm/index.html b/erpnext/docs/current/api/crm/index.html
index 6724f58..7558eb8 100644
--- a/erpnext/docs/current/api/crm/index.html
+++ b/erpnext/docs/current/api/crm/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/crm"
diff --git a/erpnext/docs/current/api/erpnext.__init__.html b/erpnext/docs/current/api/erpnext.__init__.html
index ee4696e..2637128 100644
--- a/erpnext/docs/current/api/erpnext.__init__.html
+++ b/erpnext/docs/current/api/erpnext.__init__.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.__init__ --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/__init__.py"
diff --git a/erpnext/docs/current/api/erpnext.__version__.html b/erpnext/docs/current/api/erpnext.__version__.html
index 40caef2..70f1c0c 100644
--- a/erpnext/docs/current/api/erpnext.__version__.html
+++ b/erpnext/docs/current/api/erpnext.__version__.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.__version__ --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/__version__.py"
diff --git a/erpnext/docs/current/api/erpnext.exceptions.html b/erpnext/docs/current/api/erpnext.exceptions.html
index 7eaf194..385538e 100644
--- a/erpnext/docs/current/api/erpnext.exceptions.html
+++ b/erpnext/docs/current/api/erpnext.exceptions.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.exceptions --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/exceptions.py"
diff --git a/erpnext/docs/current/api/erpnext.hooks.html b/erpnext/docs/current/api/erpnext.hooks.html
index daaf877..6170b28 100644
--- a/erpnext/docs/current/api/erpnext.hooks.html
+++ b/erpnext/docs/current/api/erpnext.hooks.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hooks --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hooks.py"
diff --git a/erpnext/docs/current/api/erpnext.tasks.html b/erpnext/docs/current/api/erpnext.tasks.html
index 06ed177..2774695 100644
--- a/erpnext/docs/current/api/erpnext.tasks.html
+++ b/erpnext/docs/current/api/erpnext.tasks.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.tasks --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/tasks.py"
diff --git a/erpnext/docs/current/api/hr/erpnext.hr.html b/erpnext/docs/current/api/hr/erpnext.hr.html
index ccb3305..e785718 100644
--- a/erpnext/docs/current/api/hr/erpnext.hr.html
+++ b/erpnext/docs/current/api/hr/erpnext.hr.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hr --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hr.py"
diff --git a/erpnext/docs/current/api/hr/erpnext.hr.utils.html b/erpnext/docs/current/api/hr/erpnext.hr.utils.html
index 1091aa6..d31c5c3 100644
--- a/erpnext/docs/current/api/hr/erpnext.hr.utils.html
+++ b/erpnext/docs/current/api/hr/erpnext.hr.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hr.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hr/utils.py"
diff --git a/erpnext/docs/current/api/hr/index.html b/erpnext/docs/current/api/hr/index.html
index 17f1281..3de85ef 100644
--- a/erpnext/docs/current/api/hr/index.html
+++ b/erpnext/docs/current/api/hr/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/hr"
diff --git a/erpnext/docs/current/api/hr/print_format/erpnext.hr.print_format.html b/erpnext/docs/current/api/hr/print_format/erpnext.hr.print_format.html
index 0fd9108..7525a7d 100644
--- a/erpnext/docs/current/api/hr/print_format/erpnext.hr.print_format.html
+++ b/erpnext/docs/current/api/hr/print_format/erpnext.hr.print_format.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hr.print_format --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hr/print_format.py"
diff --git a/erpnext/docs/current/api/hr/print_format/index.html b/erpnext/docs/current/api/hr/print_format/index.html
index 07f7381..49a7deb 100644
--- a/erpnext/docs/current/api/hr/print_format/index.html
+++ b/erpnext/docs/current/api/hr/print_format/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/print_format"
diff --git a/erpnext/docs/current/api/hr/print_format/offer_letter/erpnext.hr.print_format.offer_letter.html b/erpnext/docs/current/api/hr/print_format/offer_letter/erpnext.hr.print_format.offer_letter.html
index f5c23d7..bcd5638 100644
--- a/erpnext/docs/current/api/hr/print_format/offer_letter/erpnext.hr.print_format.offer_letter.html
+++ b/erpnext/docs/current/api/hr/print_format/offer_letter/erpnext.hr.print_format.offer_letter.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hr.print_format.offer_letter --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hr/print_format/offer_letter.py"
diff --git a/erpnext/docs/current/api/hr/print_format/offer_letter/index.html b/erpnext/docs/current/api/hr/print_format/offer_letter/index.html
index 392354c..182687c 100644
--- a/erpnext/docs/current/api/hr/print_format/offer_letter/index.html
+++ b/erpnext/docs/current/api/hr/print_format/offer_letter/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/offer_letter"
diff --git a/erpnext/docs/current/api/hub_node/erpnext.hub_node.html b/erpnext/docs/current/api/hub_node/erpnext.hub_node.html
index 32673f1..16ca632 100644
--- a/erpnext/docs/current/api/hub_node/erpnext.hub_node.html
+++ b/erpnext/docs/current/api/hub_node/erpnext.hub_node.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.hub_node --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/hub_node.py"
diff --git a/erpnext/docs/current/api/hub_node/index.html b/erpnext/docs/current/api/hub_node/index.html
index 6e2e60f..e7acf49 100644
--- a/erpnext/docs/current/api/hub_node/index.html
+++ b/erpnext/docs/current/api/hub_node/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/hub_node"
diff --git a/erpnext/docs/current/api/index.html b/erpnext/docs/current/api/index.html
index 7fc2386..74bb16e 100644
--- a/erpnext/docs/current/api/index.html
+++ b/erpnext/docs/current/api/index.html
@@ -5,7 +5,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext"
diff --git a/erpnext/docs/current/api/manufacturing/erpnext.manufacturing.html b/erpnext/docs/current/api/manufacturing/erpnext.manufacturing.html
index c1a091b..b59fe14 100644
--- a/erpnext/docs/current/api/manufacturing/erpnext.manufacturing.html
+++ b/erpnext/docs/current/api/manufacturing/erpnext.manufacturing.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.manufacturing --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/manufacturing.py"
diff --git a/erpnext/docs/current/api/manufacturing/index.html b/erpnext/docs/current/api/manufacturing/index.html
index f0fbcfa..a71cae7 100644
--- a/erpnext/docs/current/api/manufacturing/index.html
+++ b/erpnext/docs/current/api/manufacturing/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/manufacturing"
diff --git a/erpnext/docs/current/api/projects/erpnext.projects.html b/erpnext/docs/current/api/projects/erpnext.projects.html
index 8e3d53f..d7c40b3 100644
--- a/erpnext/docs/current/api/projects/erpnext.projects.html
+++ b/erpnext/docs/current/api/projects/erpnext.projects.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.projects --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/projects.py"
diff --git a/erpnext/docs/current/api/projects/erpnext.projects.utils.html b/erpnext/docs/current/api/projects/erpnext.projects.utils.html
index 34394a2..3bbd553 100644
--- a/erpnext/docs/current/api/projects/erpnext.projects.utils.html
+++ b/erpnext/docs/current/api/projects/erpnext.projects.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.projects.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/projects/utils.py"
diff --git a/erpnext/docs/current/api/projects/index.html b/erpnext/docs/current/api/projects/index.html
index 2c98558..4b39a96 100644
--- a/erpnext/docs/current/api/projects/index.html
+++ b/erpnext/docs/current/api/projects/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/projects"
diff --git a/erpnext/docs/current/api/selling/erpnext.selling.html b/erpnext/docs/current/api/selling/erpnext.selling.html
index 0bf2133..e8d2e9f 100644
--- a/erpnext/docs/current/api/selling/erpnext.selling.html
+++ b/erpnext/docs/current/api/selling/erpnext.selling.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.selling --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/selling.py"
diff --git a/erpnext/docs/current/api/selling/index.html b/erpnext/docs/current/api/selling/index.html
index 30cb218..8b9f3be 100644
--- a/erpnext/docs/current/api/selling/index.html
+++ b/erpnext/docs/current/api/selling/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/selling"
diff --git a/erpnext/docs/current/api/setup/erpnext.setup.html b/erpnext/docs/current/api/setup/erpnext.setup.html
index 414eaa7..232e600 100644
--- a/erpnext/docs/current/api/setup/erpnext.setup.html
+++ b/erpnext/docs/current/api/setup/erpnext.setup.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.setup --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/setup.py"
diff --git a/erpnext/docs/current/api/setup/erpnext.setup.install.html b/erpnext/docs/current/api/setup/erpnext.setup.install.html
index 70308fa..34ef1ae 100644
--- a/erpnext/docs/current/api/setup/erpnext.setup.install.html
+++ b/erpnext/docs/current/api/setup/erpnext.setup.install.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.setup.install --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/setup/install.py"
diff --git a/erpnext/docs/current/api/setup/erpnext.setup.utils.html b/erpnext/docs/current/api/setup/erpnext.setup.utils.html
index 72c8a1f..8b534d4 100644
--- a/erpnext/docs/current/api/setup/erpnext.setup.utils.html
+++ b/erpnext/docs/current/api/setup/erpnext.setup.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.setup.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/setup/utils.py"
diff --git a/erpnext/docs/current/api/setup/index.html b/erpnext/docs/current/api/setup/index.html
index 5933c42..2235df6 100644
--- a/erpnext/docs/current/api/setup/index.html
+++ b/erpnext/docs/current/api/setup/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/setup"
diff --git a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.cart.html b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.cart.html
index d6f51fe..943314f 100644
--- a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.cart.html
+++ b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.cart.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.shopping_cart.cart --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/shopping_cart/cart.py"
diff --git a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.html b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.html
index 3ba425b..5ad7cac 100644
--- a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.html
+++ b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.shopping_cart --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/shopping_cart.py"
diff --git a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.product.html b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.product.html
index 421e3d0..3cc5e7c 100644
--- a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.product.html
+++ b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.product.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.shopping_cart.product --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/shopping_cart/product.py"
diff --git a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.test_shopping_cart.html b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.test_shopping_cart.html
index e37030e..6a8025e 100644
--- a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.test_shopping_cart.html
+++ b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.test_shopping_cart.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.shopping_cart.test_shopping_cart --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/shopping_cart/test_shopping_cart.py"
diff --git a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.utils.html b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.utils.html
index 542125d..59c9cfa 100644
--- a/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.utils.html
+++ b/erpnext/docs/current/api/shopping_cart/erpnext.shopping_cart.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.shopping_cart.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/shopping_cart/utils.py"
diff --git a/erpnext/docs/current/api/shopping_cart/index.html b/erpnext/docs/current/api/shopping_cart/index.html
index cb03ff0..a13e821 100644
--- a/erpnext/docs/current/api/shopping_cart/index.html
+++ b/erpnext/docs/current/api/shopping_cart/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/shopping_cart"
diff --git a/erpnext/docs/current/api/startup/erpnext.startup.boot.html b/erpnext/docs/current/api/startup/erpnext.startup.boot.html
index 4e19559..8ec8ff5 100644
--- a/erpnext/docs/current/api/startup/erpnext.startup.boot.html
+++ b/erpnext/docs/current/api/startup/erpnext.startup.boot.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.startup.boot --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/startup/boot.py"
diff --git a/erpnext/docs/current/api/startup/erpnext.startup.html b/erpnext/docs/current/api/startup/erpnext.startup.html
index 70850f9..af93687 100644
--- a/erpnext/docs/current/api/startup/erpnext.startup.html
+++ b/erpnext/docs/current/api/startup/erpnext.startup.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.startup --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/startup.py"
diff --git a/erpnext/docs/current/api/startup/erpnext.startup.notifications.html b/erpnext/docs/current/api/startup/erpnext.startup.notifications.html
index 8890f3d..ad6697a 100644
--- a/erpnext/docs/current/api/startup/erpnext.startup.notifications.html
+++ b/erpnext/docs/current/api/startup/erpnext.startup.notifications.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.startup.notifications --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/startup/notifications.py"
diff --git a/erpnext/docs/current/api/startup/erpnext.startup.report_data_map.html b/erpnext/docs/current/api/startup/erpnext.startup.report_data_map.html
index 21798b2..4f5023f 100644
--- a/erpnext/docs/current/api/startup/erpnext.startup.report_data_map.html
+++ b/erpnext/docs/current/api/startup/erpnext.startup.report_data_map.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.startup.report_data_map --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/startup/report_data_map.py"
diff --git a/erpnext/docs/current/api/startup/index.html b/erpnext/docs/current/api/startup/index.html
index b58226a..e258152 100644
--- a/erpnext/docs/current/api/startup/index.html
+++ b/erpnext/docs/current/api/startup/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/startup"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.get_item_details.html b/erpnext/docs/current/api/stock/erpnext.stock.get_item_details.html
index 8a52940..5eafa84 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.get_item_details.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.get_item_details.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock.get_item_details --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock/get_item_details.py"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.html b/erpnext/docs/current/api/stock/erpnext.stock.html
index 7ab952b..ca25b6b 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock.py"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.reorder_item.html b/erpnext/docs/current/api/stock/erpnext.stock.reorder_item.html
index 139eb3f..3755104 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.reorder_item.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.reorder_item.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock.reorder_item --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock/reorder_item.py"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.stock_balance.html b/erpnext/docs/current/api/stock/erpnext.stock.stock_balance.html
index fc6a2e8..6e415aa 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.stock_balance.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.stock_balance.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock.stock_balance --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock/stock_balance.py"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.stock_ledger.html b/erpnext/docs/current/api/stock/erpnext.stock.stock_ledger.html
index 5e97d89..5d481d1 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.stock_ledger.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.stock_ledger.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock.stock_ledger --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock/stock_ledger.py"
diff --git a/erpnext/docs/current/api/stock/erpnext.stock.utils.html b/erpnext/docs/current/api/stock/erpnext.stock.utils.html
index 31c52e0..1579352 100644
--- a/erpnext/docs/current/api/stock/erpnext.stock.utils.html
+++ b/erpnext/docs/current/api/stock/erpnext.stock.utils.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.stock.utils --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/stock/utils.py"
diff --git a/erpnext/docs/current/api/stock/index.html b/erpnext/docs/current/api/stock/index.html
index 381d792..c928269 100644
--- a/erpnext/docs/current/api/stock/index.html
+++ b/erpnext/docs/current/api/stock/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/stock"
diff --git a/erpnext/docs/current/api/support/erpnext.support.html b/erpnext/docs/current/api/support/erpnext.support.html
index c672bfa..886cbf9 100644
--- a/erpnext/docs/current/api/support/erpnext.support.html
+++ b/erpnext/docs/current/api/support/erpnext.support.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.support --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/support.py"
diff --git a/erpnext/docs/current/api/support/index.html b/erpnext/docs/current/api/support/index.html
index 916af27..adb0625 100644
--- a/erpnext/docs/current/api/support/index.html
+++ b/erpnext/docs/current/api/support/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/support"
diff --git a/erpnext/docs/current/api/utilities/erpnext.utilities.address_and_contact.html b/erpnext/docs/current/api/utilities/erpnext.utilities.address_and_contact.html
index c8be620..f2d194a 100644
--- a/erpnext/docs/current/api/utilities/erpnext.utilities.address_and_contact.html
+++ b/erpnext/docs/current/api/utilities/erpnext.utilities.address_and_contact.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.utilities.address_and_contact --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/utilities/address_and_contact.py"
diff --git a/erpnext/docs/current/api/utilities/erpnext.utilities.html b/erpnext/docs/current/api/utilities/erpnext.utilities.html
index f198b5b..05deb2c 100644
--- a/erpnext/docs/current/api/utilities/erpnext.utilities.html
+++ b/erpnext/docs/current/api/utilities/erpnext.utilities.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.utilities --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/utilities.py"
diff --git a/erpnext/docs/current/api/utilities/erpnext.utilities.transaction_base.html b/erpnext/docs/current/api/utilities/erpnext.utilities.transaction_base.html
index dcb8bf5..6283243 100644
--- a/erpnext/docs/current/api/utilities/erpnext.utilities.transaction_base.html
+++ b/erpnext/docs/current/api/utilities/erpnext.utilities.transaction_base.html
@@ -1,7 +1,7 @@
 <!-- title: erpnext.utilities.transaction_base --><div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/blob/develop/erpnext/utilities/transaction_base.py"
diff --git a/erpnext/docs/current/api/utilities/index.html b/erpnext/docs/current/api/utilities/index.html
index 061031f..55f622f 100644
--- a/erpnext/docs/current/api/utilities/index.html
+++ b/erpnext/docs/current/api/utilities/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/utilities"
diff --git a/erpnext/docs/current/index.html b/erpnext/docs/current/index.html
index 08adab9..458097d 100644
--- a/erpnext/docs/current/index.html
+++ b/erpnext/docs/current/index.html
@@ -5,7 +5,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext"
@@ -35,7 +35,7 @@
 			Version
 		</td>
 		<td>
-			<code>6.7.1</code>
+			<code>6.7.3</code>
 		</td>
 	</tr>
 </table>
diff --git a/erpnext/docs/current/models/accounts/account.html b/erpnext/docs/current/models/accounts/account.html
index e99d761..d8793ae 100644
--- a/erpnext/docs/current/models/accounts/account.html
+++ b/erpnext/docs/current/models/accounts/account.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/account"
diff --git a/erpnext/docs/current/models/accounts/accounts_settings.html b/erpnext/docs/current/models/accounts/accounts_settings.html
index 20e4620..e1c944b 100644
--- a/erpnext/docs/current/models/accounts/accounts_settings.html
+++ b/erpnext/docs/current/models/accounts/accounts_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/accounts_settings"
diff --git a/erpnext/docs/current/models/accounts/bank_reconciliation.html b/erpnext/docs/current/models/accounts/bank_reconciliation.html
index cd50167..551fb85 100644
--- a/erpnext/docs/current/models/accounts/bank_reconciliation.html
+++ b/erpnext/docs/current/models/accounts/bank_reconciliation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/bank_reconciliation"
diff --git a/erpnext/docs/current/models/accounts/bank_reconciliation_detail.html b/erpnext/docs/current/models/accounts/bank_reconciliation_detail.html
index 7f3c2a0..61bbc2e 100644
--- a/erpnext/docs/current/models/accounts/bank_reconciliation_detail.html
+++ b/erpnext/docs/current/models/accounts/bank_reconciliation_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/bank_reconciliation_detail"
diff --git a/erpnext/docs/current/models/accounts/budget_detail.html b/erpnext/docs/current/models/accounts/budget_detail.html
index f22e25c..0275ef8 100644
--- a/erpnext/docs/current/models/accounts/budget_detail.html
+++ b/erpnext/docs/current/models/accounts/budget_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/budget_detail"
diff --git a/erpnext/docs/current/models/accounts/c_form.html b/erpnext/docs/current/models/accounts/c_form.html
index 6d5e9c7..23b2d27 100644
--- a/erpnext/docs/current/models/accounts/c_form.html
+++ b/erpnext/docs/current/models/accounts/c_form.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/c_form"
diff --git a/erpnext/docs/current/models/accounts/c_form_invoice_detail.html b/erpnext/docs/current/models/accounts/c_form_invoice_detail.html
index d65bacc..ce976da 100644
--- a/erpnext/docs/current/models/accounts/c_form_invoice_detail.html
+++ b/erpnext/docs/current/models/accounts/c_form_invoice_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/c_form_invoice_detail"
diff --git a/erpnext/docs/current/models/accounts/cost_center.html b/erpnext/docs/current/models/accounts/cost_center.html
index 9d7b8fc..556c7ca 100644
--- a/erpnext/docs/current/models/accounts/cost_center.html
+++ b/erpnext/docs/current/models/accounts/cost_center.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/cost_center"
diff --git a/erpnext/docs/current/models/accounts/fiscal_year.html b/erpnext/docs/current/models/accounts/fiscal_year.html
index 4d9df39..237894b 100644
--- a/erpnext/docs/current/models/accounts/fiscal_year.html
+++ b/erpnext/docs/current/models/accounts/fiscal_year.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/fiscal_year"
diff --git a/erpnext/docs/current/models/accounts/fiscal_year_company.html b/erpnext/docs/current/models/accounts/fiscal_year_company.html
index 48bcb9e..1ef8c6f 100644
--- a/erpnext/docs/current/models/accounts/fiscal_year_company.html
+++ b/erpnext/docs/current/models/accounts/fiscal_year_company.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/fiscal_year_company"
diff --git a/erpnext/docs/current/models/accounts/gl_entry.html b/erpnext/docs/current/models/accounts/gl_entry.html
index 52b0ea2..d836b6c 100644
--- a/erpnext/docs/current/models/accounts/gl_entry.html
+++ b/erpnext/docs/current/models/accounts/gl_entry.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/gl_entry"
diff --git a/erpnext/docs/current/models/accounts/index.html b/erpnext/docs/current/models/accounts/index.html
index c7506b5..05d913c 100644
--- a/erpnext/docs/current/models/accounts/index.html
+++ b/erpnext/docs/current/models/accounts/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts"
diff --git a/erpnext/docs/current/models/accounts/journal_entry.html b/erpnext/docs/current/models/accounts/journal_entry.html
index 7835391..1141c79 100644
--- a/erpnext/docs/current/models/accounts/journal_entry.html
+++ b/erpnext/docs/current/models/accounts/journal_entry.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/journal_entry"
diff --git a/erpnext/docs/current/models/accounts/journal_entry_account.html b/erpnext/docs/current/models/accounts/journal_entry_account.html
index d4fa991..84465d1 100644
--- a/erpnext/docs/current/models/accounts/journal_entry_account.html
+++ b/erpnext/docs/current/models/accounts/journal_entry_account.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/journal_entry_account"
diff --git a/erpnext/docs/current/models/accounts/mode_of_payment.html b/erpnext/docs/current/models/accounts/mode_of_payment.html
index 3887a90..d7e7625 100644
--- a/erpnext/docs/current/models/accounts/mode_of_payment.html
+++ b/erpnext/docs/current/models/accounts/mode_of_payment.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/mode_of_payment"
diff --git a/erpnext/docs/current/models/accounts/mode_of_payment_account.html b/erpnext/docs/current/models/accounts/mode_of_payment_account.html
index 10d5425..2166039 100644
--- a/erpnext/docs/current/models/accounts/mode_of_payment_account.html
+++ b/erpnext/docs/current/models/accounts/mode_of_payment_account.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/mode_of_payment_account"
diff --git a/erpnext/docs/current/models/accounts/monthly_distribution.html b/erpnext/docs/current/models/accounts/monthly_distribution.html
index 272bb64..056296a 100644
--- a/erpnext/docs/current/models/accounts/monthly_distribution.html
+++ b/erpnext/docs/current/models/accounts/monthly_distribution.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/monthly_distribution"
diff --git a/erpnext/docs/current/models/accounts/monthly_distribution_percentage.html b/erpnext/docs/current/models/accounts/monthly_distribution_percentage.html
index da44dd1..d2873cd 100644
--- a/erpnext/docs/current/models/accounts/monthly_distribution_percentage.html
+++ b/erpnext/docs/current/models/accounts/monthly_distribution_percentage.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/monthly_distribution_percentage"
diff --git a/erpnext/docs/current/models/accounts/party_account.html b/erpnext/docs/current/models/accounts/party_account.html
index 9fdb862..9174b1b 100644
--- a/erpnext/docs/current/models/accounts/party_account.html
+++ b/erpnext/docs/current/models/accounts/party_account.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/party_account"
diff --git a/erpnext/docs/current/models/accounts/payment_reconciliation.html b/erpnext/docs/current/models/accounts/payment_reconciliation.html
index a71d628..d51e148 100644
--- a/erpnext/docs/current/models/accounts/payment_reconciliation.html
+++ b/erpnext/docs/current/models/accounts/payment_reconciliation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/payment_reconciliation"
diff --git a/erpnext/docs/current/models/accounts/payment_reconciliation_invoice.html b/erpnext/docs/current/models/accounts/payment_reconciliation_invoice.html
index c4a6bd6..1a2cba2 100644
--- a/erpnext/docs/current/models/accounts/payment_reconciliation_invoice.html
+++ b/erpnext/docs/current/models/accounts/payment_reconciliation_invoice.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/payment_reconciliation_invoice"
diff --git a/erpnext/docs/current/models/accounts/payment_reconciliation_payment.html b/erpnext/docs/current/models/accounts/payment_reconciliation_payment.html
index eed9870..49e33af 100644
--- a/erpnext/docs/current/models/accounts/payment_reconciliation_payment.html
+++ b/erpnext/docs/current/models/accounts/payment_reconciliation_payment.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/payment_reconciliation_payment"
diff --git a/erpnext/docs/current/models/accounts/payment_tool.html b/erpnext/docs/current/models/accounts/payment_tool.html
index 8e3f0e9..1b3abc4 100644
--- a/erpnext/docs/current/models/accounts/payment_tool.html
+++ b/erpnext/docs/current/models/accounts/payment_tool.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/payment_tool"
diff --git a/erpnext/docs/current/models/accounts/payment_tool_detail.html b/erpnext/docs/current/models/accounts/payment_tool_detail.html
index 621dcc8..d024c47 100644
--- a/erpnext/docs/current/models/accounts/payment_tool_detail.html
+++ b/erpnext/docs/current/models/accounts/payment_tool_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/payment_tool_detail"
diff --git a/erpnext/docs/current/models/accounts/period_closing_voucher.html b/erpnext/docs/current/models/accounts/period_closing_voucher.html
index 55186d2..18b5e2f 100644
--- a/erpnext/docs/current/models/accounts/period_closing_voucher.html
+++ b/erpnext/docs/current/models/accounts/period_closing_voucher.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/period_closing_voucher"
diff --git a/erpnext/docs/current/models/accounts/pos_profile.html b/erpnext/docs/current/models/accounts/pos_profile.html
index 8417812..0eb260d 100644
--- a/erpnext/docs/current/models/accounts/pos_profile.html
+++ b/erpnext/docs/current/models/accounts/pos_profile.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/pos_profile"
diff --git a/erpnext/docs/current/models/accounts/pricing_rule.html b/erpnext/docs/current/models/accounts/pricing_rule.html
index e581335..9441c68 100644
--- a/erpnext/docs/current/models/accounts/pricing_rule.html
+++ b/erpnext/docs/current/models/accounts/pricing_rule.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/pricing_rule"
diff --git a/erpnext/docs/current/models/accounts/purchase_invoice.html b/erpnext/docs/current/models/accounts/purchase_invoice.html
index 91112df..bb41254 100644
--- a/erpnext/docs/current/models/accounts/purchase_invoice.html
+++ b/erpnext/docs/current/models/accounts/purchase_invoice.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/purchase_invoice"
diff --git a/erpnext/docs/current/models/accounts/purchase_invoice_advance.html b/erpnext/docs/current/models/accounts/purchase_invoice_advance.html
index d995db8..e3afef4 100644
--- a/erpnext/docs/current/models/accounts/purchase_invoice_advance.html
+++ b/erpnext/docs/current/models/accounts/purchase_invoice_advance.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/purchase_invoice_advance"
diff --git a/erpnext/docs/current/models/accounts/purchase_invoice_item.html b/erpnext/docs/current/models/accounts/purchase_invoice_item.html
index 7003e16..c7a5b3b 100644
--- a/erpnext/docs/current/models/accounts/purchase_invoice_item.html
+++ b/erpnext/docs/current/models/accounts/purchase_invoice_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/purchase_invoice_item"
diff --git a/erpnext/docs/current/models/accounts/purchase_taxes_and_charges.html b/erpnext/docs/current/models/accounts/purchase_taxes_and_charges.html
index b98cd16..7cda2d6 100644
--- a/erpnext/docs/current/models/accounts/purchase_taxes_and_charges.html
+++ b/erpnext/docs/current/models/accounts/purchase_taxes_and_charges.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/purchase_taxes_and_charges"
diff --git a/erpnext/docs/current/models/accounts/purchase_taxes_and_charges_template.html b/erpnext/docs/current/models/accounts/purchase_taxes_and_charges_template.html
index 8bde570..78ab885 100644
--- a/erpnext/docs/current/models/accounts/purchase_taxes_and_charges_template.html
+++ b/erpnext/docs/current/models/accounts/purchase_taxes_and_charges_template.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/purchase_taxes_and_charges_template"
diff --git a/erpnext/docs/current/models/accounts/sales_invoice.html b/erpnext/docs/current/models/accounts/sales_invoice.html
index 7096a08..e33dcc2 100644
--- a/erpnext/docs/current/models/accounts/sales_invoice.html
+++ b/erpnext/docs/current/models/accounts/sales_invoice.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/sales_invoice"
diff --git a/erpnext/docs/current/models/accounts/sales_invoice_advance.html b/erpnext/docs/current/models/accounts/sales_invoice_advance.html
index 4e407f9..d22dee7 100644
--- a/erpnext/docs/current/models/accounts/sales_invoice_advance.html
+++ b/erpnext/docs/current/models/accounts/sales_invoice_advance.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/sales_invoice_advance"
diff --git a/erpnext/docs/current/models/accounts/sales_invoice_item.html b/erpnext/docs/current/models/accounts/sales_invoice_item.html
index 94a8ea8..5f481ed 100644
--- a/erpnext/docs/current/models/accounts/sales_invoice_item.html
+++ b/erpnext/docs/current/models/accounts/sales_invoice_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/sales_invoice_item"
diff --git a/erpnext/docs/current/models/accounts/sales_taxes_and_charges.html b/erpnext/docs/current/models/accounts/sales_taxes_and_charges.html
index 5948320..6a7b0c6 100644
--- a/erpnext/docs/current/models/accounts/sales_taxes_and_charges.html
+++ b/erpnext/docs/current/models/accounts/sales_taxes_and_charges.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/sales_taxes_and_charges"
diff --git a/erpnext/docs/current/models/accounts/sales_taxes_and_charges_template.html b/erpnext/docs/current/models/accounts/sales_taxes_and_charges_template.html
index eaeffee..8701de1 100644
--- a/erpnext/docs/current/models/accounts/sales_taxes_and_charges_template.html
+++ b/erpnext/docs/current/models/accounts/sales_taxes_and_charges_template.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/sales_taxes_and_charges_template"
diff --git a/erpnext/docs/current/models/accounts/shipping_rule.html b/erpnext/docs/current/models/accounts/shipping_rule.html
index ab2ff4a..55f0c1e 100644
--- a/erpnext/docs/current/models/accounts/shipping_rule.html
+++ b/erpnext/docs/current/models/accounts/shipping_rule.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/shipping_rule"
diff --git a/erpnext/docs/current/models/accounts/shipping_rule_condition.html b/erpnext/docs/current/models/accounts/shipping_rule_condition.html
index 7cb37e4..e5d2f78 100644
--- a/erpnext/docs/current/models/accounts/shipping_rule_condition.html
+++ b/erpnext/docs/current/models/accounts/shipping_rule_condition.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/shipping_rule_condition"
diff --git a/erpnext/docs/current/models/accounts/shipping_rule_country.html b/erpnext/docs/current/models/accounts/shipping_rule_country.html
index b428cb2..8864d5c 100644
--- a/erpnext/docs/current/models/accounts/shipping_rule_country.html
+++ b/erpnext/docs/current/models/accounts/shipping_rule_country.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/shipping_rule_country"
diff --git a/erpnext/docs/current/models/accounts/tax_rule.html b/erpnext/docs/current/models/accounts/tax_rule.html
index 8c40c5b..5803531 100644
--- a/erpnext/docs/current/models/accounts/tax_rule.html
+++ b/erpnext/docs/current/models/accounts/tax_rule.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/accounts/doctype/tax_rule"
diff --git a/erpnext/docs/current/models/buying/buying_settings.html b/erpnext/docs/current/models/buying/buying_settings.html
index 3fe5e2a..ecc66c0 100644
--- a/erpnext/docs/current/models/buying/buying_settings.html
+++ b/erpnext/docs/current/models/buying/buying_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/buying_settings"
diff --git a/erpnext/docs/current/models/buying/index.html b/erpnext/docs/current/models/buying/index.html
index 9d7d3e4..97217e6 100644
--- a/erpnext/docs/current/models/buying/index.html
+++ b/erpnext/docs/current/models/buying/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying"
diff --git a/erpnext/docs/current/models/buying/purchase_common.html b/erpnext/docs/current/models/buying/purchase_common.html
index 1bd8606..6f9197e 100644
--- a/erpnext/docs/current/models/buying/purchase_common.html
+++ b/erpnext/docs/current/models/buying/purchase_common.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/purchase_common"
diff --git a/erpnext/docs/current/models/buying/purchase_order.html b/erpnext/docs/current/models/buying/purchase_order.html
index 8c79a78..7d57b3e 100644
--- a/erpnext/docs/current/models/buying/purchase_order.html
+++ b/erpnext/docs/current/models/buying/purchase_order.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/purchase_order"
diff --git a/erpnext/docs/current/models/buying/purchase_order_item.html b/erpnext/docs/current/models/buying/purchase_order_item.html
index 0826527..eb2e3c6 100644
--- a/erpnext/docs/current/models/buying/purchase_order_item.html
+++ b/erpnext/docs/current/models/buying/purchase_order_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/purchase_order_item"
diff --git a/erpnext/docs/current/models/buying/purchase_order_item_supplied.html b/erpnext/docs/current/models/buying/purchase_order_item_supplied.html
index 7e4fd01..774b7e1 100644
--- a/erpnext/docs/current/models/buying/purchase_order_item_supplied.html
+++ b/erpnext/docs/current/models/buying/purchase_order_item_supplied.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/purchase_order_item_supplied"
diff --git a/erpnext/docs/current/models/buying/purchase_receipt_item_supplied.html b/erpnext/docs/current/models/buying/purchase_receipt_item_supplied.html
index 6ce77ae..efe9b85 100644
--- a/erpnext/docs/current/models/buying/purchase_receipt_item_supplied.html
+++ b/erpnext/docs/current/models/buying/purchase_receipt_item_supplied.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/purchase_receipt_item_supplied"
diff --git a/erpnext/docs/current/models/buying/quality_inspection.html b/erpnext/docs/current/models/buying/quality_inspection.html
index e1c1d75..ea38d96 100644
--- a/erpnext/docs/current/models/buying/quality_inspection.html
+++ b/erpnext/docs/current/models/buying/quality_inspection.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/quality_inspection"
diff --git a/erpnext/docs/current/models/buying/quality_inspection_reading.html b/erpnext/docs/current/models/buying/quality_inspection_reading.html
index 19888b9..e42ad86 100644
--- a/erpnext/docs/current/models/buying/quality_inspection_reading.html
+++ b/erpnext/docs/current/models/buying/quality_inspection_reading.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/quality_inspection_reading"
diff --git a/erpnext/docs/current/models/buying/supplier.html b/erpnext/docs/current/models/buying/supplier.html
index 36cd297..02c01fd 100644
--- a/erpnext/docs/current/models/buying/supplier.html
+++ b/erpnext/docs/current/models/buying/supplier.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/supplier"
diff --git a/erpnext/docs/current/models/buying/supplier_quotation.html b/erpnext/docs/current/models/buying/supplier_quotation.html
index a9b2676..d353ac4 100644
--- a/erpnext/docs/current/models/buying/supplier_quotation.html
+++ b/erpnext/docs/current/models/buying/supplier_quotation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/supplier_quotation"
diff --git a/erpnext/docs/current/models/buying/supplier_quotation_item.html b/erpnext/docs/current/models/buying/supplier_quotation_item.html
index c29c333..8e656a2 100644
--- a/erpnext/docs/current/models/buying/supplier_quotation_item.html
+++ b/erpnext/docs/current/models/buying/supplier_quotation_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/buying/doctype/supplier_quotation_item"
diff --git a/erpnext/docs/current/models/contacts/index.html b/erpnext/docs/current/models/contacts/index.html
index 6cb1714..7790895 100644
--- a/erpnext/docs/current/models/contacts/index.html
+++ b/erpnext/docs/current/models/contacts/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/contacts"
diff --git a/erpnext/docs/current/models/crm/index.html b/erpnext/docs/current/models/crm/index.html
index fa2c424..6a9044c 100644
--- a/erpnext/docs/current/models/crm/index.html
+++ b/erpnext/docs/current/models/crm/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm"
diff --git a/erpnext/docs/current/models/crm/lead.html b/erpnext/docs/current/models/crm/lead.html
index 5f128a9..5eae8a2 100644
--- a/erpnext/docs/current/models/crm/lead.html
+++ b/erpnext/docs/current/models/crm/lead.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/lead"
diff --git a/erpnext/docs/current/models/crm/newsletter.html b/erpnext/docs/current/models/crm/newsletter.html
index 4797092..e3467fa 100644
--- a/erpnext/docs/current/models/crm/newsletter.html
+++ b/erpnext/docs/current/models/crm/newsletter.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/newsletter"
diff --git a/erpnext/docs/current/models/crm/newsletter_list.html b/erpnext/docs/current/models/crm/newsletter_list.html
index c755e0f..10b928b 100644
--- a/erpnext/docs/current/models/crm/newsletter_list.html
+++ b/erpnext/docs/current/models/crm/newsletter_list.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/newsletter_list"
diff --git a/erpnext/docs/current/models/crm/newsletter_list_subscriber.html b/erpnext/docs/current/models/crm/newsletter_list_subscriber.html
index d08192b..aae3b4e 100644
--- a/erpnext/docs/current/models/crm/newsletter_list_subscriber.html
+++ b/erpnext/docs/current/models/crm/newsletter_list_subscriber.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/newsletter_list_subscriber"
diff --git a/erpnext/docs/current/models/crm/opportunity.html b/erpnext/docs/current/models/crm/opportunity.html
index 9ae33be..a2b8b9e 100644
--- a/erpnext/docs/current/models/crm/opportunity.html
+++ b/erpnext/docs/current/models/crm/opportunity.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/opportunity"
diff --git a/erpnext/docs/current/models/crm/opportunity_item.html b/erpnext/docs/current/models/crm/opportunity_item.html
index 5c1ad10..039c354 100644
--- a/erpnext/docs/current/models/crm/opportunity_item.html
+++ b/erpnext/docs/current/models/crm/opportunity_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/crm/doctype/opportunity_item"
diff --git a/erpnext/docs/current/models/hr/appraisal.html b/erpnext/docs/current/models/hr/appraisal.html
index 94c11c8..0565bd7 100644
--- a/erpnext/docs/current/models/hr/appraisal.html
+++ b/erpnext/docs/current/models/hr/appraisal.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/appraisal"
diff --git a/erpnext/docs/current/models/hr/appraisal_goal.html b/erpnext/docs/current/models/hr/appraisal_goal.html
index 9803773..27fef00 100644
--- a/erpnext/docs/current/models/hr/appraisal_goal.html
+++ b/erpnext/docs/current/models/hr/appraisal_goal.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/appraisal_goal"
diff --git a/erpnext/docs/current/models/hr/appraisal_template.html b/erpnext/docs/current/models/hr/appraisal_template.html
index 5bb6d5b..297fc76 100644
--- a/erpnext/docs/current/models/hr/appraisal_template.html
+++ b/erpnext/docs/current/models/hr/appraisal_template.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/appraisal_template"
diff --git a/erpnext/docs/current/models/hr/appraisal_template_goal.html b/erpnext/docs/current/models/hr/appraisal_template_goal.html
index 4320132..a89b9ee 100644
--- a/erpnext/docs/current/models/hr/appraisal_template_goal.html
+++ b/erpnext/docs/current/models/hr/appraisal_template_goal.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/appraisal_template_goal"
diff --git a/erpnext/docs/current/models/hr/attendance.html b/erpnext/docs/current/models/hr/attendance.html
index 5e9924b..d2a040c 100644
--- a/erpnext/docs/current/models/hr/attendance.html
+++ b/erpnext/docs/current/models/hr/attendance.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/attendance"
diff --git a/erpnext/docs/current/models/hr/branch.html b/erpnext/docs/current/models/hr/branch.html
index ef623ee..e713714 100644
--- a/erpnext/docs/current/models/hr/branch.html
+++ b/erpnext/docs/current/models/hr/branch.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/branch"
diff --git a/erpnext/docs/current/models/hr/deduction_type.html b/erpnext/docs/current/models/hr/deduction_type.html
index f040d37..a29a1d2 100644
--- a/erpnext/docs/current/models/hr/deduction_type.html
+++ b/erpnext/docs/current/models/hr/deduction_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/deduction_type"
diff --git a/erpnext/docs/current/models/hr/department.html b/erpnext/docs/current/models/hr/department.html
index df02796..cf1e7c4 100644
--- a/erpnext/docs/current/models/hr/department.html
+++ b/erpnext/docs/current/models/hr/department.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/department"
diff --git a/erpnext/docs/current/models/hr/designation.html b/erpnext/docs/current/models/hr/designation.html
index ee160c3..3c1ae3e 100644
--- a/erpnext/docs/current/models/hr/designation.html
+++ b/erpnext/docs/current/models/hr/designation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/designation"
diff --git a/erpnext/docs/current/models/hr/earning_type.html b/erpnext/docs/current/models/hr/earning_type.html
index 43ea4aa..c9279bb 100644
--- a/erpnext/docs/current/models/hr/earning_type.html
+++ b/erpnext/docs/current/models/hr/earning_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/earning_type"
diff --git a/erpnext/docs/current/models/hr/employee.html b/erpnext/docs/current/models/hr/employee.html
index 6815b27..176591e 100644
--- a/erpnext/docs/current/models/hr/employee.html
+++ b/erpnext/docs/current/models/hr/employee.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee"
diff --git a/erpnext/docs/current/models/hr/employee_education.html b/erpnext/docs/current/models/hr/employee_education.html
index df660a4..d3e0560 100644
--- a/erpnext/docs/current/models/hr/employee_education.html
+++ b/erpnext/docs/current/models/hr/employee_education.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee_education"
diff --git a/erpnext/docs/current/models/hr/employee_external_work_history.html b/erpnext/docs/current/models/hr/employee_external_work_history.html
index 3fddaa7..35373b0 100644
--- a/erpnext/docs/current/models/hr/employee_external_work_history.html
+++ b/erpnext/docs/current/models/hr/employee_external_work_history.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee_external_work_history"
diff --git a/erpnext/docs/current/models/hr/employee_internal_work_history.html b/erpnext/docs/current/models/hr/employee_internal_work_history.html
index 5f9ed1e..198e5f8 100644
--- a/erpnext/docs/current/models/hr/employee_internal_work_history.html
+++ b/erpnext/docs/current/models/hr/employee_internal_work_history.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee_internal_work_history"
diff --git a/erpnext/docs/current/models/hr/employee_leave_approver.html b/erpnext/docs/current/models/hr/employee_leave_approver.html
index 422417f..6683601 100644
--- a/erpnext/docs/current/models/hr/employee_leave_approver.html
+++ b/erpnext/docs/current/models/hr/employee_leave_approver.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employee_leave_approver"
diff --git a/erpnext/docs/current/models/hr/employment_type.html b/erpnext/docs/current/models/hr/employment_type.html
index 84cbb5a..baa6a81 100644
--- a/erpnext/docs/current/models/hr/employment_type.html
+++ b/erpnext/docs/current/models/hr/employment_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/employment_type"
diff --git a/erpnext/docs/current/models/hr/expense_claim.html b/erpnext/docs/current/models/hr/expense_claim.html
index dbcc6ad..aa1e63c 100644
--- a/erpnext/docs/current/models/hr/expense_claim.html
+++ b/erpnext/docs/current/models/hr/expense_claim.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/expense_claim"
diff --git a/erpnext/docs/current/models/hr/expense_claim_detail.html b/erpnext/docs/current/models/hr/expense_claim_detail.html
index ff3920f..e77401a 100644
--- a/erpnext/docs/current/models/hr/expense_claim_detail.html
+++ b/erpnext/docs/current/models/hr/expense_claim_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/expense_claim_detail"
diff --git a/erpnext/docs/current/models/hr/expense_claim_type.html b/erpnext/docs/current/models/hr/expense_claim_type.html
index 53b2f31..c99fb79 100644
--- a/erpnext/docs/current/models/hr/expense_claim_type.html
+++ b/erpnext/docs/current/models/hr/expense_claim_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/expense_claim_type"
diff --git a/erpnext/docs/current/models/hr/holiday.html b/erpnext/docs/current/models/hr/holiday.html
index e1256b3..eac822c 100644
--- a/erpnext/docs/current/models/hr/holiday.html
+++ b/erpnext/docs/current/models/hr/holiday.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/holiday"
diff --git a/erpnext/docs/current/models/hr/holiday_list.html b/erpnext/docs/current/models/hr/holiday_list.html
index 07ed720..0eb963c 100644
--- a/erpnext/docs/current/models/hr/holiday_list.html
+++ b/erpnext/docs/current/models/hr/holiday_list.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/holiday_list"
diff --git a/erpnext/docs/current/models/hr/hr_settings.html b/erpnext/docs/current/models/hr/hr_settings.html
index 76848ac..b629cd8 100644
--- a/erpnext/docs/current/models/hr/hr_settings.html
+++ b/erpnext/docs/current/models/hr/hr_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/hr_settings"
diff --git a/erpnext/docs/current/models/hr/index.html b/erpnext/docs/current/models/hr/index.html
index c7d4242..309555b 100644
--- a/erpnext/docs/current/models/hr/index.html
+++ b/erpnext/docs/current/models/hr/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr"
diff --git a/erpnext/docs/current/models/hr/job_applicant.html b/erpnext/docs/current/models/hr/job_applicant.html
index 1acbfdf..db55837 100644
--- a/erpnext/docs/current/models/hr/job_applicant.html
+++ b/erpnext/docs/current/models/hr/job_applicant.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/job_applicant"
diff --git a/erpnext/docs/current/models/hr/job_opening.html b/erpnext/docs/current/models/hr/job_opening.html
index 900df46..3323ff9 100644
--- a/erpnext/docs/current/models/hr/job_opening.html
+++ b/erpnext/docs/current/models/hr/job_opening.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/job_opening"
diff --git a/erpnext/docs/current/models/hr/leave_allocation.html b/erpnext/docs/current/models/hr/leave_allocation.html
index c21ed14..8b0fb35 100644
--- a/erpnext/docs/current/models/hr/leave_allocation.html
+++ b/erpnext/docs/current/models/hr/leave_allocation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_allocation"
diff --git a/erpnext/docs/current/models/hr/leave_application.html b/erpnext/docs/current/models/hr/leave_application.html
index 09eb227..cb2a236 100644
--- a/erpnext/docs/current/models/hr/leave_application.html
+++ b/erpnext/docs/current/models/hr/leave_application.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_application"
diff --git a/erpnext/docs/current/models/hr/leave_block_list.html b/erpnext/docs/current/models/hr/leave_block_list.html
index 7648d0b..a269400 100644
--- a/erpnext/docs/current/models/hr/leave_block_list.html
+++ b/erpnext/docs/current/models/hr/leave_block_list.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_block_list"
diff --git a/erpnext/docs/current/models/hr/leave_block_list_allow.html b/erpnext/docs/current/models/hr/leave_block_list_allow.html
index 54ed219..f28d311 100644
--- a/erpnext/docs/current/models/hr/leave_block_list_allow.html
+++ b/erpnext/docs/current/models/hr/leave_block_list_allow.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_block_list_allow"
diff --git a/erpnext/docs/current/models/hr/leave_block_list_date.html b/erpnext/docs/current/models/hr/leave_block_list_date.html
index 96bb019..f3eb2cf 100644
--- a/erpnext/docs/current/models/hr/leave_block_list_date.html
+++ b/erpnext/docs/current/models/hr/leave_block_list_date.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_block_list_date"
diff --git a/erpnext/docs/current/models/hr/leave_control_panel.html b/erpnext/docs/current/models/hr/leave_control_panel.html
index 4ecb86f..20e811c 100644
--- a/erpnext/docs/current/models/hr/leave_control_panel.html
+++ b/erpnext/docs/current/models/hr/leave_control_panel.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_control_panel"
diff --git a/erpnext/docs/current/models/hr/leave_type.html b/erpnext/docs/current/models/hr/leave_type.html
index 8b0d1f0..1e8475a 100644
--- a/erpnext/docs/current/models/hr/leave_type.html
+++ b/erpnext/docs/current/models/hr/leave_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/leave_type"
diff --git a/erpnext/docs/current/models/hr/offer_letter.html b/erpnext/docs/current/models/hr/offer_letter.html
index b24246b..ce85985 100644
--- a/erpnext/docs/current/models/hr/offer_letter.html
+++ b/erpnext/docs/current/models/hr/offer_letter.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/offer_letter"
diff --git a/erpnext/docs/current/models/hr/offer_letter_term.html b/erpnext/docs/current/models/hr/offer_letter_term.html
index 3f2bec0..ff6cc1a 100644
--- a/erpnext/docs/current/models/hr/offer_letter_term.html
+++ b/erpnext/docs/current/models/hr/offer_letter_term.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/offer_letter_term"
diff --git a/erpnext/docs/current/models/hr/offer_term.html b/erpnext/docs/current/models/hr/offer_term.html
index f7d6011..8b9dc38 100644
--- a/erpnext/docs/current/models/hr/offer_term.html
+++ b/erpnext/docs/current/models/hr/offer_term.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/offer_term"
diff --git a/erpnext/docs/current/models/hr/process_payroll.html b/erpnext/docs/current/models/hr/process_payroll.html
index 973d25b..49c2582 100644
--- a/erpnext/docs/current/models/hr/process_payroll.html
+++ b/erpnext/docs/current/models/hr/process_payroll.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/process_payroll"
diff --git a/erpnext/docs/current/models/hr/salary_slip.html b/erpnext/docs/current/models/hr/salary_slip.html
index 2372002..8f6b795 100644
--- a/erpnext/docs/current/models/hr/salary_slip.html
+++ b/erpnext/docs/current/models/hr/salary_slip.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_slip"
diff --git a/erpnext/docs/current/models/hr/salary_slip_deduction.html b/erpnext/docs/current/models/hr/salary_slip_deduction.html
index a8b7ce0..08a70e9 100644
--- a/erpnext/docs/current/models/hr/salary_slip_deduction.html
+++ b/erpnext/docs/current/models/hr/salary_slip_deduction.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_slip_deduction"
diff --git a/erpnext/docs/current/models/hr/salary_slip_earning.html b/erpnext/docs/current/models/hr/salary_slip_earning.html
index 0daec07..69dfd58 100644
--- a/erpnext/docs/current/models/hr/salary_slip_earning.html
+++ b/erpnext/docs/current/models/hr/salary_slip_earning.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_slip_earning"
diff --git a/erpnext/docs/current/models/hr/salary_structure.html b/erpnext/docs/current/models/hr/salary_structure.html
index 963207c..8a10f9b 100644
--- a/erpnext/docs/current/models/hr/salary_structure.html
+++ b/erpnext/docs/current/models/hr/salary_structure.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_structure"
diff --git a/erpnext/docs/current/models/hr/salary_structure_deduction.html b/erpnext/docs/current/models/hr/salary_structure_deduction.html
index 0ddda82..feb6a02 100644
--- a/erpnext/docs/current/models/hr/salary_structure_deduction.html
+++ b/erpnext/docs/current/models/hr/salary_structure_deduction.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_structure_deduction"
diff --git a/erpnext/docs/current/models/hr/salary_structure_earning.html b/erpnext/docs/current/models/hr/salary_structure_earning.html
index 9de98f6..a61ec1b 100644
--- a/erpnext/docs/current/models/hr/salary_structure_earning.html
+++ b/erpnext/docs/current/models/hr/salary_structure_earning.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/salary_structure_earning"
diff --git a/erpnext/docs/current/models/hr/upload_attendance.html b/erpnext/docs/current/models/hr/upload_attendance.html
index 245b2df..03e4994 100644
--- a/erpnext/docs/current/models/hr/upload_attendance.html
+++ b/erpnext/docs/current/models/hr/upload_attendance.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hr/doctype/upload_attendance"
diff --git a/erpnext/docs/current/models/hub_node/hub_settings.html b/erpnext/docs/current/models/hub_node/hub_settings.html
index 6520223..8e74353 100644
--- a/erpnext/docs/current/models/hub_node/hub_settings.html
+++ b/erpnext/docs/current/models/hub_node/hub_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hub_node/doctype/hub_settings"
diff --git a/erpnext/docs/current/models/hub_node/index.html b/erpnext/docs/current/models/hub_node/index.html
index 6806701..dc096b2 100644
--- a/erpnext/docs/current/models/hub_node/index.html
+++ b/erpnext/docs/current/models/hub_node/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/hub_node"
diff --git a/erpnext/docs/current/models/index.html b/erpnext/docs/current/models/index.html
index d3f3514..d2c6a09 100644
--- a/erpnext/docs/current/models/index.html
+++ b/erpnext/docs/current/models/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext"
diff --git a/erpnext/docs/current/models/manufacturing/bom.html b/erpnext/docs/current/models/manufacturing/bom.html
index 1f945c3..f7489c9 100644
--- a/erpnext/docs/current/models/manufacturing/bom.html
+++ b/erpnext/docs/current/models/manufacturing/bom.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/bom"
diff --git a/erpnext/docs/current/models/manufacturing/bom_explosion_item.html b/erpnext/docs/current/models/manufacturing/bom_explosion_item.html
index 6a872f4..7dfbcba9 100644
--- a/erpnext/docs/current/models/manufacturing/bom_explosion_item.html
+++ b/erpnext/docs/current/models/manufacturing/bom_explosion_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/bom_explosion_item"
diff --git a/erpnext/docs/current/models/manufacturing/bom_item.html b/erpnext/docs/current/models/manufacturing/bom_item.html
index 3d62c36..9aa3f98 100644
--- a/erpnext/docs/current/models/manufacturing/bom_item.html
+++ b/erpnext/docs/current/models/manufacturing/bom_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/bom_item"
diff --git a/erpnext/docs/current/models/manufacturing/bom_operation.html b/erpnext/docs/current/models/manufacturing/bom_operation.html
index d220cc8..e2f82fb 100644
--- a/erpnext/docs/current/models/manufacturing/bom_operation.html
+++ b/erpnext/docs/current/models/manufacturing/bom_operation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/bom_operation"
diff --git a/erpnext/docs/current/models/manufacturing/bom_replace_tool.html b/erpnext/docs/current/models/manufacturing/bom_replace_tool.html
index d11103c..ea8bce2 100644
--- a/erpnext/docs/current/models/manufacturing/bom_replace_tool.html
+++ b/erpnext/docs/current/models/manufacturing/bom_replace_tool.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/bom_replace_tool"
diff --git a/erpnext/docs/current/models/manufacturing/index.html b/erpnext/docs/current/models/manufacturing/index.html
index 53e2ceb..33301d4 100644
--- a/erpnext/docs/current/models/manufacturing/index.html
+++ b/erpnext/docs/current/models/manufacturing/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing"
diff --git a/erpnext/docs/current/models/manufacturing/manufacturing_settings.html b/erpnext/docs/current/models/manufacturing/manufacturing_settings.html
index 8bf517f..6b4cef4 100644
--- a/erpnext/docs/current/models/manufacturing/manufacturing_settings.html
+++ b/erpnext/docs/current/models/manufacturing/manufacturing_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/manufacturing_settings"
diff --git a/erpnext/docs/current/models/manufacturing/operation.html b/erpnext/docs/current/models/manufacturing/operation.html
index 58727f5..bca02d9 100644
--- a/erpnext/docs/current/models/manufacturing/operation.html
+++ b/erpnext/docs/current/models/manufacturing/operation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/operation"
diff --git a/erpnext/docs/current/models/manufacturing/production_order.html b/erpnext/docs/current/models/manufacturing/production_order.html
index 58f4aea..a58e571 100644
--- a/erpnext/docs/current/models/manufacturing/production_order.html
+++ b/erpnext/docs/current/models/manufacturing/production_order.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/production_order"
diff --git a/erpnext/docs/current/models/manufacturing/production_order_operation.html b/erpnext/docs/current/models/manufacturing/production_order_operation.html
index 0478281..90a906c 100644
--- a/erpnext/docs/current/models/manufacturing/production_order_operation.html
+++ b/erpnext/docs/current/models/manufacturing/production_order_operation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/production_order_operation"
diff --git a/erpnext/docs/current/models/manufacturing/production_plan_item.html b/erpnext/docs/current/models/manufacturing/production_plan_item.html
index 90f3a14..dc88746 100644
--- a/erpnext/docs/current/models/manufacturing/production_plan_item.html
+++ b/erpnext/docs/current/models/manufacturing/production_plan_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/production_plan_item"
diff --git a/erpnext/docs/current/models/manufacturing/production_plan_sales_order.html b/erpnext/docs/current/models/manufacturing/production_plan_sales_order.html
index d97f80c..ebdfeee 100644
--- a/erpnext/docs/current/models/manufacturing/production_plan_sales_order.html
+++ b/erpnext/docs/current/models/manufacturing/production_plan_sales_order.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/production_plan_sales_order"
diff --git a/erpnext/docs/current/models/manufacturing/production_planning_tool.html b/erpnext/docs/current/models/manufacturing/production_planning_tool.html
index 303f03f..09d5c3d 100644
--- a/erpnext/docs/current/models/manufacturing/production_planning_tool.html
+++ b/erpnext/docs/current/models/manufacturing/production_planning_tool.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/production_planning_tool"
diff --git a/erpnext/docs/current/models/manufacturing/workstation.html b/erpnext/docs/current/models/manufacturing/workstation.html
index a9c76e6..4c585e7 100644
--- a/erpnext/docs/current/models/manufacturing/workstation.html
+++ b/erpnext/docs/current/models/manufacturing/workstation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/workstation"
diff --git a/erpnext/docs/current/models/manufacturing/workstation_working_hour.html b/erpnext/docs/current/models/manufacturing/workstation_working_hour.html
index a2afee5..414c0de 100644
--- a/erpnext/docs/current/models/manufacturing/workstation_working_hour.html
+++ b/erpnext/docs/current/models/manufacturing/workstation_working_hour.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/manufacturing/doctype/workstation_working_hour"
diff --git a/erpnext/docs/current/models/projects/activity_cost.html b/erpnext/docs/current/models/projects/activity_cost.html
index 38888a2..5ba3c54 100644
--- a/erpnext/docs/current/models/projects/activity_cost.html
+++ b/erpnext/docs/current/models/projects/activity_cost.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/activity_cost"
diff --git a/erpnext/docs/current/models/projects/activity_type.html b/erpnext/docs/current/models/projects/activity_type.html
index 4cf9eb2..a3c44d1 100644
--- a/erpnext/docs/current/models/projects/activity_type.html
+++ b/erpnext/docs/current/models/projects/activity_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/activity_type"
diff --git a/erpnext/docs/current/models/projects/dependent_task.html b/erpnext/docs/current/models/projects/dependent_task.html
index fefcbcc..cd4521e 100644
--- a/erpnext/docs/current/models/projects/dependent_task.html
+++ b/erpnext/docs/current/models/projects/dependent_task.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/dependent_task"
diff --git a/erpnext/docs/current/models/projects/index.html b/erpnext/docs/current/models/projects/index.html
index 78b4d63..2318648 100644
--- a/erpnext/docs/current/models/projects/index.html
+++ b/erpnext/docs/current/models/projects/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects"
diff --git a/erpnext/docs/current/models/projects/project.html b/erpnext/docs/current/models/projects/project.html
index 524ef94..01dfdec 100644
--- a/erpnext/docs/current/models/projects/project.html
+++ b/erpnext/docs/current/models/projects/project.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/project"
diff --git a/erpnext/docs/current/models/projects/project_task.html b/erpnext/docs/current/models/projects/project_task.html
index 202c29e..473558d 100644
--- a/erpnext/docs/current/models/projects/project_task.html
+++ b/erpnext/docs/current/models/projects/project_task.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/project_task"
diff --git a/erpnext/docs/current/models/projects/task.html b/erpnext/docs/current/models/projects/task.html
index 066054f..94d439e 100644
--- a/erpnext/docs/current/models/projects/task.html
+++ b/erpnext/docs/current/models/projects/task.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/task"
diff --git a/erpnext/docs/current/models/projects/task_depends_on.html b/erpnext/docs/current/models/projects/task_depends_on.html
index 68c2ac7..c7ebff9 100644
--- a/erpnext/docs/current/models/projects/task_depends_on.html
+++ b/erpnext/docs/current/models/projects/task_depends_on.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/task_depends_on"
diff --git a/erpnext/docs/current/models/projects/time_log.html b/erpnext/docs/current/models/projects/time_log.html
index 58bcf99..c91862d 100644
--- a/erpnext/docs/current/models/projects/time_log.html
+++ b/erpnext/docs/current/models/projects/time_log.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/time_log"
diff --git a/erpnext/docs/current/models/projects/time_log_batch.html b/erpnext/docs/current/models/projects/time_log_batch.html
index b241f5d..7ae395d 100644
--- a/erpnext/docs/current/models/projects/time_log_batch.html
+++ b/erpnext/docs/current/models/projects/time_log_batch.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/time_log_batch"
diff --git a/erpnext/docs/current/models/projects/time_log_batch_detail.html b/erpnext/docs/current/models/projects/time_log_batch_detail.html
index f543442..36655eb 100644
--- a/erpnext/docs/current/models/projects/time_log_batch_detail.html
+++ b/erpnext/docs/current/models/projects/time_log_batch_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/projects/doctype/time_log_batch_detail"
diff --git a/erpnext/docs/current/models/selling/campaign.html b/erpnext/docs/current/models/selling/campaign.html
index 664d29a..020e0d5 100644
--- a/erpnext/docs/current/models/selling/campaign.html
+++ b/erpnext/docs/current/models/selling/campaign.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/campaign"
diff --git a/erpnext/docs/current/models/selling/customer.html b/erpnext/docs/current/models/selling/customer.html
index f541399..e61492f 100644
--- a/erpnext/docs/current/models/selling/customer.html
+++ b/erpnext/docs/current/models/selling/customer.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/customer"
diff --git a/erpnext/docs/current/models/selling/index.html b/erpnext/docs/current/models/selling/index.html
index 564c6c1..24540ba 100644
--- a/erpnext/docs/current/models/selling/index.html
+++ b/erpnext/docs/current/models/selling/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling"
diff --git a/erpnext/docs/current/models/selling/industry_type.html b/erpnext/docs/current/models/selling/industry_type.html
index c04fd51..e9c5862 100644
--- a/erpnext/docs/current/models/selling/industry_type.html
+++ b/erpnext/docs/current/models/selling/industry_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/industry_type"
diff --git a/erpnext/docs/current/models/selling/installation_note.html b/erpnext/docs/current/models/selling/installation_note.html
index 2cde04e..a2ff5b0 100644
--- a/erpnext/docs/current/models/selling/installation_note.html
+++ b/erpnext/docs/current/models/selling/installation_note.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/installation_note"
diff --git a/erpnext/docs/current/models/selling/installation_note_item.html b/erpnext/docs/current/models/selling/installation_note_item.html
index a768b7a..c339abb 100644
--- a/erpnext/docs/current/models/selling/installation_note_item.html
+++ b/erpnext/docs/current/models/selling/installation_note_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/installation_note_item"
diff --git a/erpnext/docs/current/models/selling/product_bundle.html b/erpnext/docs/current/models/selling/product_bundle.html
index 16605f7..0e5087c 100644
--- a/erpnext/docs/current/models/selling/product_bundle.html
+++ b/erpnext/docs/current/models/selling/product_bundle.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/product_bundle"
diff --git a/erpnext/docs/current/models/selling/product_bundle_item.html b/erpnext/docs/current/models/selling/product_bundle_item.html
index 53d32d1..6826b66 100644
--- a/erpnext/docs/current/models/selling/product_bundle_item.html
+++ b/erpnext/docs/current/models/selling/product_bundle_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/product_bundle_item"
diff --git a/erpnext/docs/current/models/selling/quotation.html b/erpnext/docs/current/models/selling/quotation.html
index 4b77705..5cdea46 100644
--- a/erpnext/docs/current/models/selling/quotation.html
+++ b/erpnext/docs/current/models/selling/quotation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/quotation"
diff --git a/erpnext/docs/current/models/selling/quotation_item.html b/erpnext/docs/current/models/selling/quotation_item.html
index 279db0d..ef6e99b 100644
--- a/erpnext/docs/current/models/selling/quotation_item.html
+++ b/erpnext/docs/current/models/selling/quotation_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/quotation_item"
diff --git a/erpnext/docs/current/models/selling/sales_order.html b/erpnext/docs/current/models/selling/sales_order.html
index bf12d74..94cc36c 100644
--- a/erpnext/docs/current/models/selling/sales_order.html
+++ b/erpnext/docs/current/models/selling/sales_order.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/sales_order"
diff --git a/erpnext/docs/current/models/selling/sales_order_item.html b/erpnext/docs/current/models/selling/sales_order_item.html
index b0300a7..5ee737f 100644
--- a/erpnext/docs/current/models/selling/sales_order_item.html
+++ b/erpnext/docs/current/models/selling/sales_order_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/sales_order_item"
diff --git a/erpnext/docs/current/models/selling/sales_team.html b/erpnext/docs/current/models/selling/sales_team.html
index 255efb4..ec77cd6 100644
--- a/erpnext/docs/current/models/selling/sales_team.html
+++ b/erpnext/docs/current/models/selling/sales_team.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/sales_team"
diff --git a/erpnext/docs/current/models/selling/selling_settings.html b/erpnext/docs/current/models/selling/selling_settings.html
index c62c3d3..ede404c 100644
--- a/erpnext/docs/current/models/selling/selling_settings.html
+++ b/erpnext/docs/current/models/selling/selling_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/selling_settings"
diff --git a/erpnext/docs/current/models/selling/sms_center.html b/erpnext/docs/current/models/selling/sms_center.html
index 8dca5a0..d5a05c6 100644
--- a/erpnext/docs/current/models/selling/sms_center.html
+++ b/erpnext/docs/current/models/selling/sms_center.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/selling/doctype/sms_center"
diff --git a/erpnext/docs/current/models/setup/authorization_control.html b/erpnext/docs/current/models/setup/authorization_control.html
index 2db8310..ad90022 100644
--- a/erpnext/docs/current/models/setup/authorization_control.html
+++ b/erpnext/docs/current/models/setup/authorization_control.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/authorization_control"
diff --git a/erpnext/docs/current/models/setup/authorization_rule.html b/erpnext/docs/current/models/setup/authorization_rule.html
index 59d7694..a511c71 100644
--- a/erpnext/docs/current/models/setup/authorization_rule.html
+++ b/erpnext/docs/current/models/setup/authorization_rule.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/authorization_rule"
diff --git a/erpnext/docs/current/models/setup/brand.html b/erpnext/docs/current/models/setup/brand.html
index 0e94cdc..b75b49c 100644
--- a/erpnext/docs/current/models/setup/brand.html
+++ b/erpnext/docs/current/models/setup/brand.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/brand"
diff --git a/erpnext/docs/current/models/setup/company.html b/erpnext/docs/current/models/setup/company.html
index 7fb4607..9e0e04b 100644
--- a/erpnext/docs/current/models/setup/company.html
+++ b/erpnext/docs/current/models/setup/company.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/company"
diff --git a/erpnext/docs/current/models/setup/currency_exchange.html b/erpnext/docs/current/models/setup/currency_exchange.html
index 52b41e3..5c074ab 100644
--- a/erpnext/docs/current/models/setup/currency_exchange.html
+++ b/erpnext/docs/current/models/setup/currency_exchange.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/currency_exchange"
diff --git a/erpnext/docs/current/models/setup/customer_group.html b/erpnext/docs/current/models/setup/customer_group.html
index db0ea1d..5fd5633 100644
--- a/erpnext/docs/current/models/setup/customer_group.html
+++ b/erpnext/docs/current/models/setup/customer_group.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/customer_group"
diff --git a/erpnext/docs/current/models/setup/email_digest.html b/erpnext/docs/current/models/setup/email_digest.html
index 6d5608c..a89f580 100644
--- a/erpnext/docs/current/models/setup/email_digest.html
+++ b/erpnext/docs/current/models/setup/email_digest.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/email_digest"
diff --git a/erpnext/docs/current/models/setup/features_setup.html b/erpnext/docs/current/models/setup/features_setup.html
index 647faab..90e6a9b 100644
--- a/erpnext/docs/current/models/setup/features_setup.html
+++ b/erpnext/docs/current/models/setup/features_setup.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/features_setup"
diff --git a/erpnext/docs/current/models/setup/global_defaults.html b/erpnext/docs/current/models/setup/global_defaults.html
index 199b62a..5d33532 100644
--- a/erpnext/docs/current/models/setup/global_defaults.html
+++ b/erpnext/docs/current/models/setup/global_defaults.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/global_defaults"
diff --git a/erpnext/docs/current/models/setup/index.html b/erpnext/docs/current/models/setup/index.html
index 0093aa4..f377e41 100644
--- a/erpnext/docs/current/models/setup/index.html
+++ b/erpnext/docs/current/models/setup/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup"
diff --git a/erpnext/docs/current/models/setup/item_group.html b/erpnext/docs/current/models/setup/item_group.html
index 8ea9d1e..f6364fe 100644
--- a/erpnext/docs/current/models/setup/item_group.html
+++ b/erpnext/docs/current/models/setup/item_group.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/item_group"
diff --git a/erpnext/docs/current/models/setup/naming_series.html b/erpnext/docs/current/models/setup/naming_series.html
index 4c22ba0..2449299 100644
--- a/erpnext/docs/current/models/setup/naming_series.html
+++ b/erpnext/docs/current/models/setup/naming_series.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/naming_series"
diff --git a/erpnext/docs/current/models/setup/notification_control.html b/erpnext/docs/current/models/setup/notification_control.html
index f4c9c26..2e0cab8 100644
--- a/erpnext/docs/current/models/setup/notification_control.html
+++ b/erpnext/docs/current/models/setup/notification_control.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/notification_control"
diff --git a/erpnext/docs/current/models/setup/print_heading.html b/erpnext/docs/current/models/setup/print_heading.html
index 3a3b6f4..5a2b6fa 100644
--- a/erpnext/docs/current/models/setup/print_heading.html
+++ b/erpnext/docs/current/models/setup/print_heading.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/print_heading"
diff --git a/erpnext/docs/current/models/setup/quotation_lost_reason.html b/erpnext/docs/current/models/setup/quotation_lost_reason.html
index bca8c0c..12107ee 100644
--- a/erpnext/docs/current/models/setup/quotation_lost_reason.html
+++ b/erpnext/docs/current/models/setup/quotation_lost_reason.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/quotation_lost_reason"
diff --git a/erpnext/docs/current/models/setup/sales_partner.html b/erpnext/docs/current/models/setup/sales_partner.html
index 242ef93..43460ec 100644
--- a/erpnext/docs/current/models/setup/sales_partner.html
+++ b/erpnext/docs/current/models/setup/sales_partner.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/sales_partner"
diff --git a/erpnext/docs/current/models/setup/sales_person.html b/erpnext/docs/current/models/setup/sales_person.html
index c82612d..c745d7b 100644
--- a/erpnext/docs/current/models/setup/sales_person.html
+++ b/erpnext/docs/current/models/setup/sales_person.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/sales_person"
diff --git a/erpnext/docs/current/models/setup/sms_parameter.html b/erpnext/docs/current/models/setup/sms_parameter.html
index a53f7fd..8bfa9b1 100644
--- a/erpnext/docs/current/models/setup/sms_parameter.html
+++ b/erpnext/docs/current/models/setup/sms_parameter.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/sms_parameter"
diff --git a/erpnext/docs/current/models/setup/sms_settings.html b/erpnext/docs/current/models/setup/sms_settings.html
index e9e0b86..3a727de 100644
--- a/erpnext/docs/current/models/setup/sms_settings.html
+++ b/erpnext/docs/current/models/setup/sms_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/sms_settings"
diff --git a/erpnext/docs/current/models/setup/supplier_type.html b/erpnext/docs/current/models/setup/supplier_type.html
index 03d46fd..4ed93fb 100644
--- a/erpnext/docs/current/models/setup/supplier_type.html
+++ b/erpnext/docs/current/models/setup/supplier_type.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/supplier_type"
diff --git a/erpnext/docs/current/models/setup/target_detail.html b/erpnext/docs/current/models/setup/target_detail.html
index 1f5b7cd..89611db 100644
--- a/erpnext/docs/current/models/setup/target_detail.html
+++ b/erpnext/docs/current/models/setup/target_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/target_detail"
diff --git a/erpnext/docs/current/models/setup/terms_and_conditions.html b/erpnext/docs/current/models/setup/terms_and_conditions.html
index 92f897d..df60883 100644
--- a/erpnext/docs/current/models/setup/terms_and_conditions.html
+++ b/erpnext/docs/current/models/setup/terms_and_conditions.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/terms_and_conditions"
diff --git a/erpnext/docs/current/models/setup/territory.html b/erpnext/docs/current/models/setup/territory.html
index f4db49b..6db6071 100644
--- a/erpnext/docs/current/models/setup/territory.html
+++ b/erpnext/docs/current/models/setup/territory.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/territory"
diff --git a/erpnext/docs/current/models/setup/uom.html b/erpnext/docs/current/models/setup/uom.html
index 3a25fe0..3ffb3c5 100644
--- a/erpnext/docs/current/models/setup/uom.html
+++ b/erpnext/docs/current/models/setup/uom.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/uom"
diff --git a/erpnext/docs/current/models/setup/website_item_group.html b/erpnext/docs/current/models/setup/website_item_group.html
index 33eef75..40dfade 100644
--- a/erpnext/docs/current/models/setup/website_item_group.html
+++ b/erpnext/docs/current/models/setup/website_item_group.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/setup/doctype/website_item_group"
diff --git a/erpnext/docs/current/models/shopping_cart/index.html b/erpnext/docs/current/models/shopping_cart/index.html
index 6f20bd8..3c635ea 100644
--- a/erpnext/docs/current/models/shopping_cart/index.html
+++ b/erpnext/docs/current/models/shopping_cart/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/shopping_cart"
diff --git a/erpnext/docs/current/models/shopping_cart/shopping_cart_settings.html b/erpnext/docs/current/models/shopping_cart/shopping_cart_settings.html
index 8e8bf5f..70ae1ce 100644
--- a/erpnext/docs/current/models/shopping_cart/shopping_cart_settings.html
+++ b/erpnext/docs/current/models/shopping_cart/shopping_cart_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/shopping_cart/doctype/shopping_cart_settings"
diff --git a/erpnext/docs/current/models/stock/batch.html b/erpnext/docs/current/models/stock/batch.html
index cf1803d..e0ef78f 100644
--- a/erpnext/docs/current/models/stock/batch.html
+++ b/erpnext/docs/current/models/stock/batch.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/batch"
diff --git a/erpnext/docs/current/models/stock/bin.html b/erpnext/docs/current/models/stock/bin.html
index 55e5a44..19837d8 100644
--- a/erpnext/docs/current/models/stock/bin.html
+++ b/erpnext/docs/current/models/stock/bin.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/bin"
diff --git a/erpnext/docs/current/models/stock/delivery_note.html b/erpnext/docs/current/models/stock/delivery_note.html
index b22d091..6a815b7 100644
--- a/erpnext/docs/current/models/stock/delivery_note.html
+++ b/erpnext/docs/current/models/stock/delivery_note.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/delivery_note"
diff --git a/erpnext/docs/current/models/stock/delivery_note_item.html b/erpnext/docs/current/models/stock/delivery_note_item.html
index 51292cd..bd841b4 100644
--- a/erpnext/docs/current/models/stock/delivery_note_item.html
+++ b/erpnext/docs/current/models/stock/delivery_note_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/delivery_note_item"
diff --git a/erpnext/docs/current/models/stock/index.html b/erpnext/docs/current/models/stock/index.html
index 9a15543..e0fcdf2 100644
--- a/erpnext/docs/current/models/stock/index.html
+++ b/erpnext/docs/current/models/stock/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock"
diff --git a/erpnext/docs/current/models/stock/item.html b/erpnext/docs/current/models/stock/item.html
index 5264016..6f06b64 100644
--- a/erpnext/docs/current/models/stock/item.html
+++ b/erpnext/docs/current/models/stock/item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item"
diff --git a/erpnext/docs/current/models/stock/item_attribute.html b/erpnext/docs/current/models/stock/item_attribute.html
index 4234ab6..677484a 100644
--- a/erpnext/docs/current/models/stock/item_attribute.html
+++ b/erpnext/docs/current/models/stock/item_attribute.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_attribute"
diff --git a/erpnext/docs/current/models/stock/item_attribute_value.html b/erpnext/docs/current/models/stock/item_attribute_value.html
index 0f0364c..3a8da9d 100644
--- a/erpnext/docs/current/models/stock/item_attribute_value.html
+++ b/erpnext/docs/current/models/stock/item_attribute_value.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_attribute_value"
diff --git a/erpnext/docs/current/models/stock/item_customer_detail.html b/erpnext/docs/current/models/stock/item_customer_detail.html
index 2139055..fadf66c 100644
--- a/erpnext/docs/current/models/stock/item_customer_detail.html
+++ b/erpnext/docs/current/models/stock/item_customer_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_customer_detail"
diff --git a/erpnext/docs/current/models/stock/item_price.html b/erpnext/docs/current/models/stock/item_price.html
index 34fa80d..f453932 100644
--- a/erpnext/docs/current/models/stock/item_price.html
+++ b/erpnext/docs/current/models/stock/item_price.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_price"
diff --git a/erpnext/docs/current/models/stock/item_quality_inspection_parameter.html b/erpnext/docs/current/models/stock/item_quality_inspection_parameter.html
index e545063..5338036 100644
--- a/erpnext/docs/current/models/stock/item_quality_inspection_parameter.html
+++ b/erpnext/docs/current/models/stock/item_quality_inspection_parameter.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_quality_inspection_parameter"
diff --git a/erpnext/docs/current/models/stock/item_reorder.html b/erpnext/docs/current/models/stock/item_reorder.html
index e388d9d..fe26560 100644
--- a/erpnext/docs/current/models/stock/item_reorder.html
+++ b/erpnext/docs/current/models/stock/item_reorder.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_reorder"
diff --git a/erpnext/docs/current/models/stock/item_supplier.html b/erpnext/docs/current/models/stock/item_supplier.html
index b1347b4..f06b666 100644
--- a/erpnext/docs/current/models/stock/item_supplier.html
+++ b/erpnext/docs/current/models/stock/item_supplier.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_supplier"
diff --git a/erpnext/docs/current/models/stock/item_tax.html b/erpnext/docs/current/models/stock/item_tax.html
index ab2e565..5f10c2d 100644
--- a/erpnext/docs/current/models/stock/item_tax.html
+++ b/erpnext/docs/current/models/stock/item_tax.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_tax"
diff --git a/erpnext/docs/current/models/stock/item_variant.html b/erpnext/docs/current/models/stock/item_variant.html
index 4653068..8042f78 100644
--- a/erpnext/docs/current/models/stock/item_variant.html
+++ b/erpnext/docs/current/models/stock/item_variant.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_variant"
diff --git a/erpnext/docs/current/models/stock/item_variant_attribute.html b/erpnext/docs/current/models/stock/item_variant_attribute.html
index 527421f..52572e0 100644
--- a/erpnext/docs/current/models/stock/item_variant_attribute.html
+++ b/erpnext/docs/current/models/stock/item_variant_attribute.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_variant_attribute"
diff --git a/erpnext/docs/current/models/stock/item_website_specification.html b/erpnext/docs/current/models/stock/item_website_specification.html
index b5ec6e0..d802bd3 100644
--- a/erpnext/docs/current/models/stock/item_website_specification.html
+++ b/erpnext/docs/current/models/stock/item_website_specification.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/item_website_specification"
diff --git a/erpnext/docs/current/models/stock/landed_cost_item.html b/erpnext/docs/current/models/stock/landed_cost_item.html
index 3f865ae..f47321d 100644
--- a/erpnext/docs/current/models/stock/landed_cost_item.html
+++ b/erpnext/docs/current/models/stock/landed_cost_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/landed_cost_item"
diff --git a/erpnext/docs/current/models/stock/landed_cost_purchase_receipt.html b/erpnext/docs/current/models/stock/landed_cost_purchase_receipt.html
index d4623c6..4de7a8a 100644
--- a/erpnext/docs/current/models/stock/landed_cost_purchase_receipt.html
+++ b/erpnext/docs/current/models/stock/landed_cost_purchase_receipt.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/landed_cost_purchase_receipt"
diff --git a/erpnext/docs/current/models/stock/landed_cost_taxes_and_charges.html b/erpnext/docs/current/models/stock/landed_cost_taxes_and_charges.html
index 45f8aa6..dc9ca17 100644
--- a/erpnext/docs/current/models/stock/landed_cost_taxes_and_charges.html
+++ b/erpnext/docs/current/models/stock/landed_cost_taxes_and_charges.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/landed_cost_taxes_and_charges"
diff --git a/erpnext/docs/current/models/stock/landed_cost_voucher.html b/erpnext/docs/current/models/stock/landed_cost_voucher.html
index 5258d50..ca83d5d 100644
--- a/erpnext/docs/current/models/stock/landed_cost_voucher.html
+++ b/erpnext/docs/current/models/stock/landed_cost_voucher.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/landed_cost_voucher"
diff --git a/erpnext/docs/current/models/stock/material_request.html b/erpnext/docs/current/models/stock/material_request.html
index c028a18..e115724 100644
--- a/erpnext/docs/current/models/stock/material_request.html
+++ b/erpnext/docs/current/models/stock/material_request.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/material_request"
diff --git a/erpnext/docs/current/models/stock/material_request_item.html b/erpnext/docs/current/models/stock/material_request_item.html
index 2c08c80..f19b961 100644
--- a/erpnext/docs/current/models/stock/material_request_item.html
+++ b/erpnext/docs/current/models/stock/material_request_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/material_request_item"
diff --git a/erpnext/docs/current/models/stock/packed_item.html b/erpnext/docs/current/models/stock/packed_item.html
index 6e6bf6f..1e7865f 100644
--- a/erpnext/docs/current/models/stock/packed_item.html
+++ b/erpnext/docs/current/models/stock/packed_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/packed_item"
diff --git a/erpnext/docs/current/models/stock/packing_slip.html b/erpnext/docs/current/models/stock/packing_slip.html
index ae1e5d5..0c2fd39 100644
--- a/erpnext/docs/current/models/stock/packing_slip.html
+++ b/erpnext/docs/current/models/stock/packing_slip.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/packing_slip"
diff --git a/erpnext/docs/current/models/stock/packing_slip_item.html b/erpnext/docs/current/models/stock/packing_slip_item.html
index f3d88d2..c123bf9 100644
--- a/erpnext/docs/current/models/stock/packing_slip_item.html
+++ b/erpnext/docs/current/models/stock/packing_slip_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/packing_slip_item"
diff --git a/erpnext/docs/current/models/stock/price_list.html b/erpnext/docs/current/models/stock/price_list.html
index 1a73fe9..0b92dc4 100644
--- a/erpnext/docs/current/models/stock/price_list.html
+++ b/erpnext/docs/current/models/stock/price_list.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/price_list"
diff --git a/erpnext/docs/current/models/stock/price_list_country.html b/erpnext/docs/current/models/stock/price_list_country.html
index 117ab29..18e1e68 100644
--- a/erpnext/docs/current/models/stock/price_list_country.html
+++ b/erpnext/docs/current/models/stock/price_list_country.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/price_list_country"
diff --git a/erpnext/docs/current/models/stock/purchase_receipt.html b/erpnext/docs/current/models/stock/purchase_receipt.html
index 8e66351..e52fcbc 100644
--- a/erpnext/docs/current/models/stock/purchase_receipt.html
+++ b/erpnext/docs/current/models/stock/purchase_receipt.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/purchase_receipt"
diff --git a/erpnext/docs/current/models/stock/purchase_receipt_item.html b/erpnext/docs/current/models/stock/purchase_receipt_item.html
index 419b83b..d002e8d 100644
--- a/erpnext/docs/current/models/stock/purchase_receipt_item.html
+++ b/erpnext/docs/current/models/stock/purchase_receipt_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/purchase_receipt_item"
diff --git a/erpnext/docs/current/models/stock/serial_no.html b/erpnext/docs/current/models/stock/serial_no.html
index 6f690f0..95f2889 100644
--- a/erpnext/docs/current/models/stock/serial_no.html
+++ b/erpnext/docs/current/models/stock/serial_no.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/serial_no"
diff --git a/erpnext/docs/current/models/stock/stock_entry.html b/erpnext/docs/current/models/stock/stock_entry.html
index 9b7b443..51499a0 100644
--- a/erpnext/docs/current/models/stock/stock_entry.html
+++ b/erpnext/docs/current/models/stock/stock_entry.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_entry"
diff --git a/erpnext/docs/current/models/stock/stock_entry_detail.html b/erpnext/docs/current/models/stock/stock_entry_detail.html
index d054e14..a057315 100644
--- a/erpnext/docs/current/models/stock/stock_entry_detail.html
+++ b/erpnext/docs/current/models/stock/stock_entry_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_entry_detail"
diff --git a/erpnext/docs/current/models/stock/stock_ledger_entry.html b/erpnext/docs/current/models/stock/stock_ledger_entry.html
index ebfc462..551abd2 100644
--- a/erpnext/docs/current/models/stock/stock_ledger_entry.html
+++ b/erpnext/docs/current/models/stock/stock_ledger_entry.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_ledger_entry"
diff --git a/erpnext/docs/current/models/stock/stock_reconciliation.html b/erpnext/docs/current/models/stock/stock_reconciliation.html
index 4b6998f..b4033e9 100644
--- a/erpnext/docs/current/models/stock/stock_reconciliation.html
+++ b/erpnext/docs/current/models/stock/stock_reconciliation.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_reconciliation"
diff --git a/erpnext/docs/current/models/stock/stock_reconciliation_item.html b/erpnext/docs/current/models/stock/stock_reconciliation_item.html
index 1d607e5..d925eb9 100644
--- a/erpnext/docs/current/models/stock/stock_reconciliation_item.html
+++ b/erpnext/docs/current/models/stock/stock_reconciliation_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_reconciliation_item"
diff --git a/erpnext/docs/current/models/stock/stock_settings.html b/erpnext/docs/current/models/stock/stock_settings.html
index 86149b9..6b18111 100644
--- a/erpnext/docs/current/models/stock/stock_settings.html
+++ b/erpnext/docs/current/models/stock/stock_settings.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_settings"
diff --git a/erpnext/docs/current/models/stock/stock_uom_replace_utility.html b/erpnext/docs/current/models/stock/stock_uom_replace_utility.html
index ad998cb..971b396 100644
--- a/erpnext/docs/current/models/stock/stock_uom_replace_utility.html
+++ b/erpnext/docs/current/models/stock/stock_uom_replace_utility.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/stock_uom_replace_utility"
diff --git a/erpnext/docs/current/models/stock/uom_conversion_detail.html b/erpnext/docs/current/models/stock/uom_conversion_detail.html
index ea28a62..345bd20 100644
--- a/erpnext/docs/current/models/stock/uom_conversion_detail.html
+++ b/erpnext/docs/current/models/stock/uom_conversion_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/uom_conversion_detail"
diff --git a/erpnext/docs/current/models/stock/warehouse.html b/erpnext/docs/current/models/stock/warehouse.html
index 596af83..1bf3e60 100644
--- a/erpnext/docs/current/models/stock/warehouse.html
+++ b/erpnext/docs/current/models/stock/warehouse.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/stock/doctype/warehouse"
diff --git a/erpnext/docs/current/models/support/index.html b/erpnext/docs/current/models/support/index.html
index eb86d87..033e746 100644
--- a/erpnext/docs/current/models/support/index.html
+++ b/erpnext/docs/current/models/support/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support"
diff --git a/erpnext/docs/current/models/support/issue.html b/erpnext/docs/current/models/support/issue.html
index 044c562..69849a0 100644
--- a/erpnext/docs/current/models/support/issue.html
+++ b/erpnext/docs/current/models/support/issue.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/issue"
diff --git a/erpnext/docs/current/models/support/maintenance_schedule.html b/erpnext/docs/current/models/support/maintenance_schedule.html
index 1ab6927..cacc96c 100644
--- a/erpnext/docs/current/models/support/maintenance_schedule.html
+++ b/erpnext/docs/current/models/support/maintenance_schedule.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/maintenance_schedule"
diff --git a/erpnext/docs/current/models/support/maintenance_schedule_detail.html b/erpnext/docs/current/models/support/maintenance_schedule_detail.html
index ba53cd4..433d513 100644
--- a/erpnext/docs/current/models/support/maintenance_schedule_detail.html
+++ b/erpnext/docs/current/models/support/maintenance_schedule_detail.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/maintenance_schedule_detail"
diff --git a/erpnext/docs/current/models/support/maintenance_schedule_item.html b/erpnext/docs/current/models/support/maintenance_schedule_item.html
index b46852d..0d1c46e 100644
--- a/erpnext/docs/current/models/support/maintenance_schedule_item.html
+++ b/erpnext/docs/current/models/support/maintenance_schedule_item.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/maintenance_schedule_item"
diff --git a/erpnext/docs/current/models/support/maintenance_visit.html b/erpnext/docs/current/models/support/maintenance_visit.html
index ad254e4..ecedadf 100644
--- a/erpnext/docs/current/models/support/maintenance_visit.html
+++ b/erpnext/docs/current/models/support/maintenance_visit.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/maintenance_visit"
diff --git a/erpnext/docs/current/models/support/maintenance_visit_purpose.html b/erpnext/docs/current/models/support/maintenance_visit_purpose.html
index a8c8cda..0cf08e0 100644
--- a/erpnext/docs/current/models/support/maintenance_visit_purpose.html
+++ b/erpnext/docs/current/models/support/maintenance_visit_purpose.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/maintenance_visit_purpose"
diff --git a/erpnext/docs/current/models/support/warranty_claim.html b/erpnext/docs/current/models/support/warranty_claim.html
index f325b2a..1a8f674 100644
--- a/erpnext/docs/current/models/support/warranty_claim.html
+++ b/erpnext/docs/current/models/support/warranty_claim.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/support/doctype/warranty_claim"
diff --git a/erpnext/docs/current/models/utilities/address.html b/erpnext/docs/current/models/utilities/address.html
index cf81690..38f9ed7 100644
--- a/erpnext/docs/current/models/utilities/address.html
+++ b/erpnext/docs/current/models/utilities/address.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities/doctype/address"
diff --git a/erpnext/docs/current/models/utilities/address_template.html b/erpnext/docs/current/models/utilities/address_template.html
index 743ae5b..9dcc4d8 100644
--- a/erpnext/docs/current/models/utilities/address_template.html
+++ b/erpnext/docs/current/models/utilities/address_template.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities/doctype/address_template"
diff --git a/erpnext/docs/current/models/utilities/contact.html b/erpnext/docs/current/models/utilities/contact.html
index 64d7eef..9a9dee1 100644
--- a/erpnext/docs/current/models/utilities/contact.html
+++ b/erpnext/docs/current/models/utilities/contact.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities/doctype/contact"
diff --git a/erpnext/docs/current/models/utilities/index.html b/erpnext/docs/current/models/utilities/index.html
index aa8c485..25b033c 100644
--- a/erpnext/docs/current/models/utilities/index.html
+++ b/erpnext/docs/current/models/utilities/index.html
@@ -4,7 +4,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities"
diff --git a/erpnext/docs/current/models/utilities/rename_tool.html b/erpnext/docs/current/models/utilities/rename_tool.html
index 96cc0de..cec2ddd 100644
--- a/erpnext/docs/current/models/utilities/rename_tool.html
+++ b/erpnext/docs/current/models/utilities/rename_tool.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities/doctype/rename_tool"
diff --git a/erpnext/docs/current/models/utilities/sms_log.html b/erpnext/docs/current/models/utilities/sms_log.html
index 73ca9cc..1066141 100644
--- a/erpnext/docs/current/models/utilities/sms_log.html
+++ b/erpnext/docs/current/models/utilities/sms_log.html
@@ -7,7 +7,7 @@
 <div class="dev-header">
 
 <a class="btn btn-default btn-sm" disabled style="margin-bottom: 10px;">
-	Version 6.7.1</a>
+	Version 6.7.3</a>
 
 
 	<a class="btn btn-default btn-sm" href="https://github.com/frappe/erpnext/tree/develop/erpnext/utilities/doctype/sms_log"
diff --git a/erpnext/docs/index.txt b/erpnext/docs/index.txt
index 8e3d277..a98dc96 100644
--- a/erpnext/docs/index.txt
+++ b/erpnext/docs/index.txt
@@ -1,6 +1,6 @@
+user
 assets
 contents
 current
 install
-license
-user
\ No newline at end of file
+license
\ No newline at end of file
diff --git a/erpnext/docs/user/CRM/contact.md b/erpnext/docs/user/CRM/contact.md
deleted file mode 100644
index b985a31..0000000
--- a/erpnext/docs/user/CRM/contact.md
+++ /dev/null
@@ -1,19 +0,0 @@
-Contacts and Addresses in ERPNext are stored separately so that you can
-attach multiple Contacts or Addresses to Customers and Suppliers.
-
-To create a new Contact go to ,
-
-> CRM > Contact > New
-
-<img class="screenshot" alt="Contact" src="/assets/manual_erpnext_com/img/crm/contact.png">
-
-Or you can add a Contact or Address directly from the Customer record, click on “New
-Contact” or “New Address”.
-
-<img class="screenshot" alt="Contact" src="/assets/manual_erpnext_com/img/crm/contact-from-cust.png">
-
-> Tip: When you select a Customer in any transaction, one Contact and Address
-gets pre-selected. This is the “Default Contact or Address”.
-
-To Import multiple Contacts and Addresses from a spreadsheet, use the Data
-Import Tool.
\ No newline at end of file
diff --git a/erpnext/docs/user/CRM/customer.md b/erpnext/docs/user/CRM/customer.md
deleted file mode 100644
index 664e516..0000000
--- a/erpnext/docs/user/CRM/customer.md
+++ /dev/null
@@ -1,68 +0,0 @@
-A customer, who is sometimes known as a client, buyer, or purchaser is the one
-who receives goods, services, products, or ideas, from a seller for a monetary
-consideration. A customer can also receive goods or services from a vendor or
-a supplier for other valuable considerations.
-
-You can either directly create your Customers via
-
-> Selling > Customer
-
-or upload it via the Data Import Tool.
-
-<img class="screenshot" alt="Customer" src="/assets/manual_erpnext_com/img/crm/customer.png">
-
-> Note: Customers are separate from Contacts and Addresses. A Customer can
-have multiple Contacts and Addresses.
-
-### Contacts and Addresses
-
-Contacts and Addresses in ERPNext are stored separately so that you can
-attach multiple Contacts or Addresses to Customers and Suppliers.
-
-Read [Contact](/contents/crm/contact) to know more.
-
-### Integration with Accounts
-
-In ERPNext, there is a separate Account record for each Customer, for each
-Company.
-
-When you create a new Customer, ERPNext will automatically create an Account
-Ledger for the Customer under “Accounts Receivable” in the Company set in the
-Customer record.
-
-> Advanced Tip: If you want to change the Account Group under which the
-Customer Account is created, you can set it in the Company master.
-
-If you want to create an Account in another Company, just change the Company
-value and “Save” the Customer again.
-
-### Customer Settings
-
-You can link a Price List to a Customer (select “Default Price List”), so that
-when you select that Customer, the Price List will be automatically selected.
-
-You can set “Credit Days”, so that it is automatically set due date in the Sales
-Invoices made against this Customer. Credit Days can be defined as fixed days or last day of the next month based on invoice date.
-
-You can set how much credit you want to allow for a Customer by adding the
-“Credit Limit”. You can also set a global “Credit Limit” in the Company
-master. Classifying Customers
-
-ERPNext allows you to group your Customers using [Customer Group](/contents/crm/setup/customer-group) 
-and also divide them into [Territories](/contents/crm/setup/territory)
-Grouping will help you get better analysis of your data and
-identify which Customers are profitable and which are not. Territories will
-help you set sales targets for the respective territories.
-You can also mention [Sales Person](/contents/crm/setup/sales-person) against a customer.
-
-### Sales Partner
-
-A Sales Partner is a third party distributor / dealer / commission agent /
-affiliate / reseller who sells the companies products, for a commission. This
-is useful if you make the end sale to the Customer, involving your Sales
-Partner.
-
-If you sell to your Sales Partner who in-turn sells it to the Customer, then
-you must make a Customer instead.
-
-{next}
diff --git a/erpnext/docs/user/CRM/lead.md b/erpnext/docs/user/CRM/lead.md
deleted file mode 100644
index cb06eee..0000000
--- a/erpnext/docs/user/CRM/lead.md
+++ /dev/null
@@ -1,46 +0,0 @@
-To get the customer through the door, you may be doing all or any of the
-following:
-
-  * Listing your product on directories.
-  * Maintaining an updated and searchable website.
-  * Meeting people at trade events.
-  * Advertising your product or services.
-
-When you send out the word that you are around and have something valuable to
-offer, people will come in to check out your product. These are your Leads.
-
-They are called Leads because they may lead you to a sale. Sales people
-usually work on leads by calling them, building a relationship and sending
-information about their products or services. It is important to track all
-this conversation to enable another person who may have to follow-up on that
-contact. The new person is then able to know the history of that particular
-Lead.
-
-To create a Lead, go to:
-
-> Selling > Lead > New Lead
-
-<img class="screenshot" alt="Lead" src="/assets/manual_erpnext_com/img/crm/lead.png">
-
-ERPNext gives you a lot of options you may want to store about your Leads. For
-example what is the source, how likely are they to give you business etc. If
-you have a healthy number of leads, this information will help you prioritize
-who you want to work with.
-
-> **Tip:** ERPNext makes it easy to follow-up on leads by updating the “Next
-Contact” details. This will add a new event in the Calendar for the User who
-has to contact the lead next.
-
-### Difference between Lead, Contact and Customer
-
-The difference is that a Lead is a potential Customer, someone who can give
-you business. A Customer is an organization or individual who has given you
-business before (and has an Account in your system). A Contact is a person who
-belongs to the Customer.
-
-A Lead can be converted to a Customer by clicking on the “Create Customer”
-button. Once the Customer is created, the Lead becomes “Converted” and any
-further Opportunities from the same source can be created against the
-Customer.
-
-{next}
diff --git a/erpnext/docs/user/CRM/newsletter.md b/erpnext/docs/user/CRM/newsletter.md
deleted file mode 100644
index d32efb0..0000000
--- a/erpnext/docs/user/CRM/newsletter.md
+++ /dev/null
@@ -1,19 +0,0 @@
-A newsletter is a short written report that tells about the recent activities
-of an organization. It is generally sent to members of the organization,
-potential clients customers or potential leads.
-
-In ERPNext, you can use this UI to send any type of communication to a large
-number of audience. The process of sending bulk email to a target audience is
-very simple and easy.
-
-Select the list that you want to send the email to. Fill in your content in
-the message box, and send your newsletter.If you wish to test your email, to
-see how it looks to the recepient, you can use the test function. Save the
-document before testing. A test email will be sent to your email id. You can
-send the email to all the intended receipients by clicking on the send button.
-
-<img class="screenshot" alt="Newsletter - New" src="/assets/manual_erpnext_com/img/crm/newsletter-new.png">
-
-<img class="screenshot" alt="Newsletter - Test" src="/assets/manual_erpnext_com/img/crm/newsletter-test.png">
-
-{next}
diff --git a/erpnext/docs/user/CRM/opportunity.md b/erpnext/docs/user/CRM/opportunity.md
deleted file mode 100644
index fc533bb..0000000
--- a/erpnext/docs/user/CRM/opportunity.md
+++ /dev/null
@@ -1,30 +0,0 @@
-When you know a Lead is looking for some products or services to buy, you can
-track that as an Opportunity.
-
-You can create an Opportunity from:
-
-> Selling > Opportunity > New Opportunity
-
-or open a “Open” Lead and click on “Create Opportunity” button.
-
-#### Figure 1: Create Opportunity 
-
-<img class="screenshot" alt="Opportunity" src="/assets/manual_erpnext_com/img/crm/opportunity.png">
-
-You can also open a “Open” Lead and click on “Create Opportunity” button.
-
-#### Figure 2: Create Opportunity from an open Lead
-
-<img class="screenshot" alt="Opportunity" src="/assets/manual_erpnext_com/img/crm/lead-to-opportunity.png">
-
-An Opportunity can also come from an existing Customer. You can create
-multiple Opportunities against the same Lead. In Opportunity, apart from the
-Communication, you can also add the Items for which the Lead or Contact is
-looking for.
-
-> Best Practice: Leads and Opportunities are often referred as your “Sales
-Pipeline” this is what you need to track if you want to be able to predict how
-much business you are going to get in the future. Its always a good idea to be
-able to track what is coming in order to adjust your resources.
-
-{next}
diff --git a/erpnext/docs/user/CRM/setup/campaign.md b/erpnext/docs/user/CRM/setup/campaign.md
deleted file mode 100644
index 801beb0..0000000
--- a/erpnext/docs/user/CRM/setup/campaign.md
+++ /dev/null
@@ -1,20 +0,0 @@
-A Campaign is a full-scale implementation of a sales strategy to promote a
-product or a service. This is done in a market segment of a particular
-geographical area, to achieve specified objectives.
-
-<img class="screenshot" alt="Campaign" src="/assets/manual_erpnext_com/img/crm/campaign.png">
-
-You can track [Lead](/contents/crm/lead), [Opportunity](/contents/crm/opportunity), [Quotation](/contents/selling/quotation) against a campaign.
-
-###Track Leads against Campaign
-
-* To track a 'Lead' against a campaign select 'View Leads'.
-
-<img class="screenshot" alt="Campaign - View Leads" src="/assets/manual_erpnext_com/img/crm/campaign-view-leads.png">
-
-* You shall get a filtered list of all leads made against that campaign.
-* You can also create new leads by clicking 'New'
-
-<img class="screenshot" alt="Campaign - New Lead" src="/assets/manual_erpnext_com/img/crm/campaign-new-lead.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/CRM/setup/customer-group.md b/erpnext/docs/user/CRM/setup/customer-group.md
deleted file mode 100644
index 4a023bf..0000000
--- a/erpnext/docs/user/CRM/setup/customer-group.md
+++ /dev/null
@@ -1,14 +0,0 @@
-Customer groups allow you to organize your customers. You can also have discounts based on customer groups.
-You can also get trend analysis for each
-group. Typically Customers are grouped by market segment (that is usually
-based on your domain).
-
-<img class="screenshot" alt="Customer Group Tree" src="/assets/manual_erpnext_com/img/crm/customer-group-tree.png">
-
-> Tip: If you think all this is too much effort, you can leave it at “Default
-Customer Group”. But all this effort, will pay off when you start getting
-reports. An example of a sample report is given below:
-
-![Sales Analytics](/assets/manual_erpnext_com/old_images/erpnext/sales-analytics-customer.png)
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/CRM/setup/sales-person.md b/erpnext/docs/user/CRM/setup/sales-person.md
deleted file mode 100644
index aca6975..0000000
--- a/erpnext/docs/user/CRM/setup/sales-person.md
+++ /dev/null
@@ -1,14 +0,0 @@
-Sales Persons behave exactly like Territories. You can create an organization
-chart of Sales Persons where each Sales Person’s target can be set
-individually. Again as in Territory, the target has to be set against Item
-Group.
-
-<img class="screenshot" alt="Sales Person Tree" src="/assets/manual_erpnext_com/img/crm/sales-person-tree.png">
-
-####Sales Person in Transactions
-
-You can use this Sales Person in Customer and sales transactions like Sales Order, Delivery Note and Sales Invoice.
-Click [here](https://erpnext.com/kb/selling/managing-sales-persons-in-sales-transactions) to learn more 
-about how Sales Persons are used in the transactions of Sales Cycle.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/accounts/accounting-entries.md b/erpnext/docs/user/accounts/accounting-entries.md
deleted file mode 100644
index 4615d4b..0000000
--- a/erpnext/docs/user/accounts/accounting-entries.md
+++ /dev/null
@@ -1,58 +0,0 @@
-The concept of accounting is explained with an example given below: We will
-take a "Tea Stall" as a company and see how to book accounting entries for the
-business.
-
-  * Mama (The Tea-stall owner) invests Rs 25000 to start the business.
-
-![A&L](/assets/manual_erpnext_com/old_images/erpnext/assets-1.png)
-
-__Analysis:__ Mama invested 25000 in company, hoping to get some profit. In other
-words, company is liable to pay 25000 to Mama in the future. So, account
-"Mama" is a liability account and it is credited. Company's cash balance will
-be increased due to the investment, "Cash" is an asset to the company and it
-will debited.
-
-  * The company needs equipments (Stove, teapot, cups etc) and raw materials (tea, sugar, milk etc) immediately. He decides to buy from the nearest general store "Super Bazaar" who is a friend so that he gets some credit. Equipments cost him 2800 and raw materials worth of 2200. He pays 2000 out of total cost 5000.
-
-![A&L](/assets/manual_erpnext_com/old_images/erpnext/assets-2.png)
-
-__Analysis:__ Equipments are "Fixed Assets" (because they have a long life) of the
-company and raw materials "Current Assets" (since they are used for day-to-day
-business), of the company. So, "Equipments" and "Stock in Hand" accounts have
-been debited to increase the value. He pays 2000, so "Cash" account will be
-reduced by that amount, hence credited and he is liable to pay 3000 to "Super
-Bazaar" later, so Super Bazaar will be credited by 3000.
-
-  * Mama (who takes care of all entries) decides to book sales at the end of the every day, so that he can analyze daily sales. At the end of the very first day, the tea stall sells 325 cups of tea, which gives net sales of Rs. 1575. The owner happily books his first day sales.
-
-![A&L](/assets/manual_erpnext_com/old_images/erpnext/assets-3.png)
-
-__Analysis:__ Income has been booked in "Sales of Tea" account which has been
-credited to increase the value and the same amount will be debited to "Cash"
-account. Lets say, to make 325 cups of tea, it costs Rs. 800, so "Stock in
-Hand" will be reduced (Cr) by 800 and expense will be booked in "Cost of goods
-sold" account by same amount.
-
-At the end of the month, the company paid the rent amount of stall (5000) and
-salary of one employee (8000), who joined from the very first day.
-
-![A&L](/assets/manual_erpnext_com/old_images/erpnext/assets-4.png)
-
-### Booking Profit
-
-As month progress, company purchased more raw materials for the business.
-After a month he books profit to balance the "Balance Sheet" and "Profit and
-Loss Statements" statements. Profit belongs to Mama and not the company hence
-its a liability for the company (it has to pay it to Mama). When the Balance
-Sheet is not balanced i.e. Debit is not equal to Credit, the profit has not
-yet been booked. To book profit, the following entry has to be made:
-
-![A&L](/assets/manual_erpnext_com/old_images/erpnext/assets-5.png)
-
-Explanation: Company's net sales and expenses are 40000 and 20000
-respectively. So, company made a profit of 20000. To make the profit booking
-entry, "Profit or Loss" account has been debited and "Capital Account" has
-been credited. Company's net cash balance is 44000 and there is some raw
-materials available worth 1000 rupees.
-
-{next}
diff --git a/erpnext/docs/user/accounts/accounting-reports.md b/erpnext/docs/user/accounts/accounting-reports.md
deleted file mode 100644
index d8557b9..0000000
--- a/erpnext/docs/user/accounts/accounting-reports.md
+++ /dev/null
@@ -1,43 +0,0 @@
-Some of the major accounting reports are:
-
-### General Ledger
-
-General Ledger is based on the table GL Entry and can be filtered by Account
-and between a period. This will help you to get a full update for all entries
-done in that period for that Account.
-
-<img alt="General Ledger" class="screenshot"
-    src="/assets/manual_erpnext_com/img/accounts/general-ledger.png">
-
-### Trial Balance
-
-Trial Balance is the list of Account balances for all your Accounts
-(“Ledger” and “Group”) on a particular date. For each Account it will give you
-the:
-
-  * Opening
-  * Debits
-  * Credits
-  * Closing
-
-<img alt="Trial Balance" class="screenshot" src="/assets/manual_erpnext_com/img/accounts/trial-balance.png">
-
-The sum of all closing balances in a Trial Balance must be zero.
-
-### Accounts Payable and Accounts Receivable (AP / AR)
-
-These reports help you to track the outstanding invoices sent to Customer and
-Suppliers. In this report, you will get your outstanding amounts period wise.
-i.e. between 0-30 days, 30-60 days and so on.
-
-<img alt="Accounts Receivable" class="screenshot" src="/assets/manual_erpnext_com/img/accounts/accounts-receivable.png">
-
-### Sales and Purchase Register
-
-In this report, each tax Account is transposed in columns. For each Invoice and
-invoice Item, you will get the amount of individual tax that has been paid,
-based on the Taxes and Charges table.
-
-<img alt="Sales Register" class="screenshot" src="/assets/manual_erpnext_com/img/accounts/sales-register.png">
-
-{next}
diff --git a/erpnext/docs/user/accounts/advance-payment-entry.md b/erpnext/docs/user/accounts/advance-payment-entry.md
deleted file mode 100644
index 1506be7..0000000
--- a/erpnext/docs/user/accounts/advance-payment-entry.md
+++ /dev/null
@@ -1,62 +0,0 @@
-Payment done by the customer before accepting delivery of the product is an
-Advance Payment. For Orders of high value, the business houses expect to
-receive advance.
-
-  
-__For Example:__ Consider a customer- Jane D'souza placing an order for a double
-bed costing $10000 She is asked to give some advance before the furniture
-house begins work on her order. She gives them $5000 in cash.
-
-  
-Go to Accounts and open a new Journal Entry to make the advance entry.
-
-> Accounts > Documents > Journal Entry > New Journal Entry  
-
-Mention the voucher type as cash voucher. This differs for different
-customers. If somebody pays by cheque the voucher type will be Bank Voucher.
-Then select the customer account and make the respective debit and credit
-entries.  
-
-Since the customer has given $5000 as cash advance,it will be recorded as a
-credit entry against the customer. To balance it with the debit entry [Double
-accounting Entry] enter $5000 as debit against the company's cash account. In
-the row "Is Advance" click 'Yes'.
-
-#### Figure 1 : Journal Entry -Advance Entry  
-
-<img class="screenshot" alt="Advace Payment" src="/assets/manual_erpnext_com/img/accounts/advance-payment-1.png">
-
-### Double Entry Accounting  
-
-Double entry bookkeeping is a system of accounting in which every transaction
-has a corresponding positive and negative entry : debits and credits. Every
-transaction involves a [debit entry
-](http://www.e-conomic.co.uk/accountingsystem/glossary/debit)in one account
-and a [credit
-entry](http://www.e-conomic.co.uk/accountingsystem/glossary/credit) in another
-account. This means that every transaction must be recorded in two accounts;
-one account will be debited because it receives value and the other account
-will be credited because it has given value.
-
-  
-#### Figure 2: Transaction and Difference Entry
-
-<img class="screenshot" alt="Advace Payment" src="/assets/manual_erpnext_com/img/accounts/advance-payment-2.png">
-
-Save and submit the JV. If this document is not saved it will not be pulled in
-other accounting documents.
-
-When you make a new Sales Invoice for the same customer, mention the advance
-in the Sales Invoice Form.
-
-To link the Sales Invoice to the Journal Entry which mentions the advance
-payment entry, click on ‘Get Advances Received’.  Allocate the amount of
-advance in the advances table. The accounting will be adjusted accordingly.
-
-#### Figure 3: Receive Advance 
-
-<img class="screenshot" alt="Advace Payment" src="/assets/manual_erpnext_com/img/accounts/advance-payment-3.png">
-
-Save and submit the Sales Invoice.
-
-{next}
diff --git a/erpnext/docs/user/accounts/budgeting.md b/erpnext/docs/user/accounts/budgeting.md
deleted file mode 100644
index e38ec9c..0000000
--- a/erpnext/docs/user/accounts/budgeting.md
+++ /dev/null
@@ -1,58 +0,0 @@
-ERPNext will help you set and manage budgets on your Cost Centers. This is
-useful when, for example, you are doing online sales. You have a budget for
-search ads, and you want ERPNext to stop or warn you from over spending, based
-on that budget.
-
-Budgets are also great for planning purposes. When you are making plans for
-the next financial year, you would typically target a revenue based on which
-you would set your expenses. Setting a budget will ensure that your expenses
-do not get out of hand, at any point, as per your plans.
-
-You can define it in the Cost Center. If you have seasonal sales you can also
-define a budget distribution that the budget will follow.
-
-In order to allocate budget, go to Accounts > Setup > Chart of Cost Centers and click on Chart of Cost Center.
-Select a Cost Center and click on Open.
-
-#### Step 1: Click on Edit.
-
-![](/assets/manual_erpnext_com/old_images/erpnext/budgeting-1.png)  
-
-<img alt="Accounts Receivable" class="screenshot" src="/assets/manual_erpnext_com/img/accounts/accounts-receivable.png">
-
-#### Step 2: Enter Monthly Distribution.
-
-![](/assets/manual_erpnext_com/old_images/erpnext/budgeting-2-1.png)
-
-
-If you leave the** **distribution ID blank, ERPNext will calculate on a yearly
-basis or in equal proportion for every month.
-
-#### Step 3:Add New Row and select budget account.  
-
-
-
-![](/assets/manual_erpnext_com/old_images/erpnext/budgeting-3.png)  
-
-
-
-### To Create New Distribution ID
-
-ERPNext allows you to take a few budget actions. It signifies whether to stop
-, warn or Ignore  if you exceed budgets.  
-
-![](/assets/manual_erpnext_com/old_images/erpnext/budgeting-4.png)
-
-
-
-These can be defined from the Company record.
-
-![](/assets/manual_erpnext_com/old_images/erpnext/budgeting-4-1.png)  
-
-
-
-Even if you choose to “ignore” budget overruns, you will get a wealth of
-information from the “Budget vs Actual” variance report. This report shows
-month wise actual expenses as compared to the budgeted expenses.
-
-{next}
diff --git a/erpnext/docs/user/accounts/chart-of-accounts.md b/erpnext/docs/user/accounts/chart-of-accounts.md
deleted file mode 100644
index 644d329..0000000
--- a/erpnext/docs/user/accounts/chart-of-accounts.md
+++ /dev/null
@@ -1,128 +0,0 @@
-The Chart of Accounts forms the blueprint of your organization. The overall
-structure of your Chart of Accounts is based on a system of double entry
-accounting that has become a standard all over the world to quantify how a
-company is doing financially.
-
-The Chart of Accounts helps you to answer:
-
-  * What is your organisation worth?
-  * How much debt have you taken?
-  * How much profit are you making (and hence paying tax)?
-  * How much are you selling?
-  * What is your expense break-up
-
-You may note that as a business manager, it is very valuable to see how well
-your business is doing.
-
-> Tip: If you can’t read a Balance Sheet (It took me a long time to
-figure this out) it's a good opportunity to start learning about this. It will
-be worth the effort. You can also take the help of your accountant to setup
-your Chart of Accounts.
-
-Financial statement of your company is easily viewable in ERPNext. An Example
-of a financial statement is given below:
-
-<img class="screenshot" alt="Financial Analytics Balance Sheet" src="/assets/manual_erpnext_com/img/accounts/financial-analytics-bl.png">
-
-To edit your Chart of Accounts in ERPNext go to:
-
->  Accounts > Setup > Chart of Accounts
-
-Chart of Accounts is a tree view of the names of the Accounts (Ledgers and
-Groups) that a Company requires to manage its books of accounts. ERPNext sets
-up a simple chart of accounts for each Company you create, but you have to
-modify it according to your needs and legal requirements. For each company,
-Chart of Accounts signifies the way to classify the accounting entries, mostly
-based on statutory (tax, compliance to government regulations) requirements.
-
-Let us understand the main groups of the Chart of Accounts.
-
-<img class="screenshot" alt="Chart of Accounts" src="/assets/manual_erpnext_com/img/accounts/chart-of-accounts-1.png">
-
-### Balance Sheet Accounts
-
-The Balance Sheet has Application of Funds (/assets) and Sources of Funds
-(Liabilities) that signify the net-worth of your company at any given time.
-When you begin or end a financial period, all the Assets are equal to the
-Liabilities.
-
-> Accounting: If you are new to accounting, you might be wondering, how can
-Assets be equal to Liabilities? That would mean the company has nothing of its
-own. Thats right. All the “investment” made in the company to buy assets (like
-land, furniture, machines) is made by the owners and is a liability to the
-company. If the company would want to shut down, it would need to sell all the
-assets and pay back all the liabilities (including profits) to the owners,
-leaving itself with nothing.
-
-All the accounts under this represent an asset owned by the company like "Bank
-Account", "Land and Property", "Furniture" or a liability (funds that the
-company owes to others) like "Owners funds", "Debt" etc.
-
-Two special accounts to note here are Accounts Receivable (money you have to
-collect from your customers) and Accounts Payable (money you have to pay to
-your suppliers) under Assets and Liabilities respectively.
-
-### Profit and Loss Accounts
-
-Profit and Loss is the group of Income and Expense accounts that represent
-your accounting transactions over a period.
-
-Unlike Balance sheet accounts, Profit and Loss accounts (or PL accounts) do
-not represent net worth (/assets), but rather represent the amount of money
-spent and collected in servicing customers during the period. Hence at the
-beginning and end of your Fiscal Year, they become zero.
-
-In ERPNext it is easy to create a Profit and Loss analysis chart. An example
-of a Profit and Loss analysis chart is given below:
-
-<img class="screenshot" alt="Financial Analytics Profit and Loss Statement" src="/assets/manual_erpnext_com/img/accounts/financial-analytics-pl.png">
-
-(On the first day of the year you have not made any profit or loss, but you
-still have assets, hence balance sheet accounts never become zero at the
-beginning or end of a period)
-
-### Groups and Ledgers
-
-There are two main kinds of Accounts in ERPNext - Group and Ledger. Groups can
-have sub-groups and ledgers within them, whereas ledgers are the leaf nodes of
-your chart and cannot be further classified.
-
-Accounting Transactions can only be made against Ledger Accounts (not Groups)
-
-> Info: The term "Ledger" means a page in an accounting book where entries are
-made. There is usually one ledger for each account (like a Customer or a
-Supplier).
-
-> Note: An Account “Ledger” is also sometimes called as Account “Head”.
-
-<img class="screenshot" alt="Chart of Accounts" src="/assets/manual_erpnext_com/img/accounts/chart-of-accounts-2.png">
-
-### Other Account Types
-
-In ERPNext, you can also specify more information when you create a new
-Account, this is there to help you select that particular account in a
-scenario like Bank Account or a Tax Account and has no effect on the Chart
-itself.
-
-### Creating / Editing Accounts
-
-To create new Accounts, explore your Chart of Accounts and click on an Account
-group under which you want to create the new Account. On the right side, you
-will see an option to “Open” or “Add Child” a new Account.
-
-<img class="screenshot" alt="Chart of Accounts" src="/assets/manual_erpnext_com/img/accounts/chart-of-accounts-3.png">
-
-Option to create will only appear if you click on a Group (folder) type
-Account.
-
-ERPNext creates a standard structure for you when the Company is created but
-it is up to you to modify or add or remove accounts.
-
-Typically, you might want to create Accounts for
-
-  * Types of Expenses (travel, salaries, telephone etc) under Expenses.
-  * Taxes (VAT, Sales Tax etc based on your country) under Current Liabilities.
-  * Types of Sales (for example, Product Sales, Service Sales etc.) under Income.
-  * Types of Assets (building, machinery, furniture etc.) under Fixed Assets.
-
-{next}
diff --git a/erpnext/docs/user/accounts/credit-limit.md b/erpnext/docs/user/accounts/credit-limit.md
deleted file mode 100644
index 292c12b..0000000
--- a/erpnext/docs/user/accounts/credit-limit.md
+++ /dev/null
@@ -1,34 +0,0 @@
-  
-
-A credit limit is the maximum amount of credit that a financial institution or
-other lender will extend to a debtor for a particular line of credit. From an
-organisation's perspective, it is the maximum amount of credit which a
-customer gets on goods purchased.  
-
-To set credit limit go to Customer - Master
-
-> Selling > Document > Customer 
-
-  
-#### Figure 1: Credit Limit
-
-<img class="screenshot" alt="Credit Limit" src="/assets/manual_erpnext_com/img/accounts/credit-limit-1.png">
-
-Go to the 'More Info section' and enter the amount in the field Credit Limit.
-
-In case a need arises to allow more credit to the customer as a good-will, the
-Credit Controller has access to submit order even if credit limit is crossed.
-
-To allow any other role to submit transactions by customers whose credit limit
-has expired, go to accounting settings and make changes.
-
-In the field Credit Controller, select the role who would be authorized to
-accept orders or raise credit limits of customers.
-  
-#### Figure 2: Credit Controller
-
-<img class="screenshot" alt="Credit Limit" src="/assets/manual_erpnext_com/img/accounts/credit-limit-2.png">
-
-Save the changes.
-
-{next}
diff --git a/erpnext/docs/user/accounts/item-wise-tax.md b/erpnext/docs/user/accounts/item-wise-tax.md
deleted file mode 100644
index 5bba9c7..0000000
--- a/erpnext/docs/user/accounts/item-wise-tax.md
+++ /dev/null
@@ -1,30 +0,0 @@
-
-Taxes selected in the Tax and Other Charges in transactions are applied on all the items. If you need different taxes applied on items selected in the same transaction, you should setup you item and tax master as explained in the steps below.
-
-####Step 1: Mention Tax Applicable in the Item master
-
-Item master has tax table where you can list taxes which will be applied on it.
-
-![Item wise Tax](/assets/manual_erpnext_com/old_images/erpnext/item-wise-tax.png)
-
-Tax rate mentioned in the item master gets preference over tax rate entered in the transactions. 
-
-For example, if you provide tax rate for VAT as 10% for item ABC, where for same VAT ledger 12% rate is entered in the Sales Order/Invoice, for item ABC, tax rate applied would be 10%, as mentioned in the item master.
-
-####Step 2: Setup Taxes and Other Charges
-
-In Taxes and Other Charges master, you should select all the applicable taxes which could be applicable on item.
-
-For example, if few items has VAT 5 applied on them, other has Service Tax applied, and some other has Excise Duty applicable, then you tax master should have all these taxes selected.
-
-![item wise tax master](/assets/manual_erpnext_com/old_images/erpnext/item-wise-tax-master.png)
-
-####Step 3: Set Tax Rate as Zero in Taxes and Charges Template
-
-In the Taxes and Other Charges master, tax rate will be updated as ZERO. It means, tax rate applicable on items will be pulled from the respective Item master. While for other items, 0% tax will be applied, means no other taxes will be applied on that item.
-
-Based on the above setting, you will have taxes applied on items as mentioned in the respective item master. Check following for an instance.
-
-![item wise tax calculation](/assets/manual_erpnext_com/old_images/erpnext/item-wise-tax-calc.png)
-
-{next}
diff --git a/erpnext/docs/user/accounts/journal-entry.md b/erpnext/docs/user/accounts/journal-entry.md
deleted file mode 100644
index 7e1aee7..0000000
--- a/erpnext/docs/user/accounts/journal-entry.md
+++ /dev/null
@@ -1,71 +0,0 @@
-All types of accounting entries other than **Sales Invoice** and **Purchase
-Invoice** are made using the **Journal Entry**. A **Journal Entry** 
-is a standard accounting transaction that affects
-multiple Accounts and the sum of debits is equal to the sum of credits.
-
-To create a Journal Entry go to:
-
-> Accounts > Documents > Journal Entry > New
-
-<img class="screenshot" alt="Journal Entry" src="/assets/manual_erpnext_com/img/accounts/journal-entry.png">
-
-In a Journal Entry, you must select.
-
-  * Type of Voucher from the drop down.
-  * Add rows for the individual accounting entries. In each row, you must specify: 
-    * The Account that will be affected
-    * The amount to Debit or Credit
-    * The Cost Center (if it is an Income or Expense)
-    * Against Voucher: Link it to a voucher or invoice if it affects the “outstanding” amount of that invoice.
-    * Is Advance: Select “Yes” if you want to make it selectable in an Invoice. Other information in case it is a Bank Payment or a bill.
-
-#### Difference
-
-The “Difference” field is the difference between the Debit and Credit amounts.
-This should be zero if the Journal Entry is to be “Submitted”. If this
-number is not zero, you can click on “Make Difference Entry” to add a new row
-with the amount required to make the total as zero.
-
-* * *
-
-## Common Entries
-
-A look at some of the common accounting entries that can be done via Journal
-Voucher.
-
-#### Expenses (non accruing)
-
-Many times it may not be necessary to accrue an expense, but it can be
-directly booked against an expense Account on payment. For example a travel
-allowance or a telephone bill. You can directly debit Telephone Expense
-(instead of your telephone company) and credit your Bank on payment.
-
-  * Debit: Expense Account (like Telephone expense)
-  * Credit: Bank or Cash Account
-
-#### Bad Debts or Write Offs
-
-If you are writing off an Invoice as a bad debt, you can create a Journal
-Voucher similar to a Payment, except instead of debiting your Bank, you can
-debit an Expense Account called Bad Debts.
-
-  * Debit: Bad Debts Written Off
-  * Credit: Customer
-
-> Note: There may be regulations in your country before you can write off bad
-debts.
-
-#### Depreciation
-
-Depreciation is when you write off certain value of your assets as an expense.
-For example if you have a computer that you will use for say 5 years, you can
-distribute its expense over the period and pass a Journal Entry at the end
-of each year reducing its value by a certain percentage.
-
-  * Debit: Depreciation (Expense)
-  * Credit: Asset (the Account under which you had booked the asset to be depreciated)
-
-> Note: There may be regulations in your country that define by how much
-amount you can depreciate a class of Assets.
-
-{next}
diff --git a/erpnext/docs/user/accounts/making-payments.md b/erpnext/docs/user/accounts/making-payments.md
deleted file mode 100644
index 763f422..0000000
--- a/erpnext/docs/user/accounts/making-payments.md
+++ /dev/null
@@ -1,98 +0,0 @@
-Payments made against Sales Invoices or Purchase Invoices can be made by
-clicking on “Make Payment Entry” button on “Submitted” invoices.
-
-  1. Update the “Bank Account” (you can also set the default account in the Company master).
-  2. Update posting date.
-  3. Enter the cheque number, cheque date.
-  4. Save and Submit.
-
-<img class="screenshot" alt="Manking Payment" src="/assets/manual_erpnext_com/img/accounts/make-payment.png">
-
-Payments can also be made independent of invoices by creating a new Journal
-Voucher and selecting the type of payment.
-
-#### Incoming Payment
-
-For payments from Customers,
-
-  * Debit: Bank or Cash Account
-  * Credit: Customer
-
-> Note: Remember to add “Against Sales Invoice” or “Is Advance” as applicable.
-
-#### Outgoing Payment
-
-For payments to Suppliers,
-
-  * Debit: Supplier
-  * Credit: Bank or Cash Account
-
-### Example Payment Journal Entry
-
-<img class="screenshot" alt="Manking Payment" src="/assets/manual_erpnext_com/img/accounts/new-bank-entry.png">
-
-* * *
-
-### Reconciling Cheque Payments
-
-If you are receiving payments or making payments via cheques, the bank
-statements will not accurately match the dates of your entry, this is because
-the bank usually takes time to “clear” these payments. Also you may have
-mailed a cheque to your Supplier and it may be a few days before it is
-received and deposited by the Supplier. In ERPNext you can synchronize your
-bank statements and your Journal Entrys using the “Bank Reconciliation”
-tool.
-
-To use this, go to:
-
-> Accounts > Tools > Bank Reconciliation
-
-Select your “Bank” Account and enter the dates of your statement. Here you
-will get all the “Bank Voucher” type entries. In each of the entry on the
-right most column, update the “Clearance Date” and click on “Update”.
-
-By doing this you will be able to sync your bank statements and entries into
-the system.
-
-* * *
-
-## Managing Outstanding Payments
-
-In most cases, apart from retail sales, billing and payments are separate
-activities. There are several combinations in which these payments are done.
-These cases apply to both sales and purchases.
-
-  * They can be upfront (100% in advance).
-  * Post shipment. Either on delivery or within a few days of delivery.
-  * Part in advance and part on or post delivery.
-  * Payments can be made together for a bunch of invoices.
-  * Advances can be given together for a bunch of invoices (and can be split across invoices).
-
-ERPNext allows you to manage all these scenarios. All accounting entries (GL
-Entry) can be made against a Sales Invoice, Purchase Invoice or Journal
-Vouchers (in special cases, an invoice can be made via a Sales Invoice too).
-
-The total outstanding amount against an invoice is the sum of all the
-accounting entries that are made “against” (or are linked to) that invoice.
-This way you can combine or split payments in Journal Entrys to manage the
-scenarios.
-
-### Matching Payments to Invoices
-
-In complex scenarios, especially in the capital goods industry, sometimes
-there is no direct link between payments and invoices. You send invoices to
-your Customers and your Customer sends you block payments or payments based on
-some schedule that is not linked to your invoices.
-
-In such cases, you can use the Payment to Invoice Matching Tool.
-
-> Accounts > Tools > Payment Reconciliation
-
-In this tool, you can select an account (your Customer’s account) and click on
-“Pull Payment Entries” and it will select all un-linked Journal Entrys and
-Sales Invoices from that Customer.
-
-To cancel off some payments and invoices, select the Invoices and Journal
-Vouchers and click on “Reconcile”.
-
-{next}
diff --git a/erpnext/docs/user/accounts/multi-currency-accounting.md b/erpnext/docs/user/accounts/multi-currency-accounting.md
deleted file mode 100644
index 7a43b5b..0000000
--- a/erpnext/docs/user/accounts/multi-currency-accounting.md
+++ /dev/null
@@ -1,119 +0,0 @@
-In ERPNext, you can make accounting entries in multiple currency. For example, if you have a bank account in foreign currency, you can make transactions in that currency and system will show bank balance in that specific currency only.
-
-## Setup
-
-To get started with multi-currency accounting, you need to assign accounting currency in Account record. You can define Currency from Chart of Accounts while creating Account.
-
-<img class="screenshot" alt="Set Currency from Chart of Accounts"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/chart-of-accounts.png">
-
-You can also assign / modify the currency by opening specific Account record for existing Accounts.
-
-<img class="screenshot" alt="Modify Account Currency"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/account.png">
-
-For Customer / Supplier (Party), you can also define it's accounting currency in the Party record. If the Party's accounting currency is different from Company Currency, you have to mention Default Receivable / Payable Account in that currency.
-
-<img class="screenshot" alt="Customer Accounting Currency"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/customer.png">
-
-
-Once you defined Accounting Currency in Party / Account record, you are ready to make transactions against them. If Party's accounting currency is different from Company Currency, system will restrict to make transaction for that party with that currency only. If accounting currency is same as Company Currency, you can make transactions for that Party in any currency. But accounting entries (GL Entries) will always be in Party's Accounting Currency. In any case, currency of Receivable Account will always be same as accounting currency of the Party.
-
-You can change accounting currency in Party / Account record, until making any transactions against them. After making accounting entries, system will not allow to change the accounting currency for both Party / Account record.
-
-In case of multi-company setup, accounting currency of Party must be same for all the companies.
-
-## Transactions
-
-### Sales Invoice
-
-In Sales Invoice, transaction currency must be same as accounting currency of Customer if Customer's accounting currency is other than Company Currency. Otherwise, you can select any currency in Invoice. On selection of Customer, system will fetch Receivable account from Customer / Company. The currency of receivable account must be same as Customer's accounting currency.
-
-Now, in POS, Paid Amount will be enetered in transaction currency, instead of earlier Company Currency. Write Off Amount will also be entered in transaction currency.
-
-Outstanding Amount and Advance Amount will always be calculated and shown in Customer's Account Currency.
-
-<img class="screenshot" alt="Sales Invoice Outstanding"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/sales-invoice.png">
-
-### Purchase Invoice
-
-Similarly, in Purchase Invoice, accounting entries will be made based on Supplier's accounting currency. Outstanding Amount and Advance Amount will also be shown in the supplier's accounting currency. Write Off Amount will now be entered in transaction currency.
-
-### Journal Entry
-
-In Journal Entry, you can make transactions in different currencies. There is a checkbox "Multi Currency", to enable multi-currency entries. If "Multi Currency" option selected, you will be able to select accounts with different currencies.
-
-<img class="screenshot" alt="Journal Entry Exchange Rate"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/journal-entry-multi-currency.png">
-
- 
-In Accounts table, on selection of foreign currency account, system will show Currency section and fetch Account Currency and Exchange Rate automatically. You can change / modify the Exchange Rate later manually.
-
-In a single Journal Entry, you can select accounts with only one alternate currency, apart from accounts in Company Currency. Debit / Credit amount should be entered in Account Currency, system will calculate and show the Debit / Credit amount in Company Currency automatically.
-
-<img class="screenshot" alt="Journal Entry in multi currency"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/journal-entry-row.png">
-
-#### Example 1: Payment Entry  Against Customer With Alternate Currency
-
-Suppose, default currency of the company is INR and customer's accounting currency is USD. Customer made full payment against an outstanding invoice of USD 100. Exchange Rate (USD -> INR) in Sales Invoice was 60.
-
-Exchange Rate in the payment entry should always be same as invoice (60), even if exchange rate on the payment date is 62. The bank account will be credited by the amount considering exchange rate as 62. Hence, Exchnage Gain / Loss will be booked based on exchange rate difference.
-
-<img class="screenshot" alt="Payment Entry"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/payment-entry.png">
-
-#### Example 2: Inter-bank Transfer (USD -> INR)
-
-Suppose, default currency of the company is INR. You have an Paypal account for which Currency is USD. You receive payments in the paypal account and lets say, paypal transfers amount once in a week to your other bank account which is managed in INR. 
-
-Paypal account gets debited on different date with different exchange rate, but on transfer date the exchange rate can be different. Hence, there is generally Exchange Loss / Gain on the transfer entry.
-In the bank transfer entry, system sets exchange rate based on the average incoming exchange rate Paypal account. You need to calculate and enter Exchange Loss / Gain based on the average exchange rate and the exchange rate on the transfer date.
-
-Lets say, Paypal account debited by following amounts over the week, which has not been transferred to your other bank account.
-
-<table class="table table-bordered">
-	<thead>
-		<tr>
-			<td>Date</td>
-			<td>Account</td>
-			<td>Debit (USD)</td>
-			<td>Exchange Rate</td>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>2015-09-02</td>
-			<td>Paypal</td>
-			<td>100</td>
-			<td>60</td>
-		</tr>
-		<tr>
-			<td>2015-09-02</td>
-			<td>Paypal</td>
-			<td>100</td>
-			<td>61</td>
-		</tr>
-		<tr>
-			<td>2015-09-02</td>
-			<td>Paypal</td>
-			<td>100</td>
-			<td>64</td>
-		</tr>
-	</tbody>
-</table>
-
-
-Suppose, Exchange Rate on the payment date is 62 and Bank Transfer Entry will be look like below:
-
-<img class="screenshot" alt="Inter Bank Transfer"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/bank-transfer.png">
-
-
-## Reports
-
-### General Ledger
-
-In General Ledger, system shows debit / credit amount in both currency if filtered by an Account and Account Currency is different from Company Currency.
-
-<img class="screenshot" alt="General Ledger Report"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/general-ledger.png">
-
-### Accounts Receivable / Payable
-
-In Accounts Receivable / Payable report, system shows all the amounts in Party / Account Currency.
-
-<img class="screenshot" alt="Accounts Receivable Report"  	src="/assets/manual_erpnext_com/img/accounts/multi-currency/accounts-receivable.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/accounts/opening-accounts.md b/erpnext/docs/user/accounts/opening-accounts.md
deleted file mode 100644
index a6c0c77..0000000
--- a/erpnext/docs/user/accounts/opening-accounts.md
+++ /dev/null
@@ -1,94 +0,0 @@
-Now that you have completed most of the setup, its time to start moving in!
-
-There are two important sets of data you need to enter before you start your
-operations.
-
-  * Opening Account balances.
-  * Opening Stock balances.
-
-To setup your accounts and stock correctly you will need accurate data to work
-with. Make sure you have the data setup for this.
-
-### Opening Accounts
-
-We usually recommend that you start using accounting in a new financial year,
-but you could start midway too. To setup your accounts, you will need the
-following for the “day” you start using accounting in ERPNext:
-
-Opening capital accounts - like your shareholder’s (or owner’) capital, loans,
-bank balances on that day. List of outstanding sales and purchase invoices
-(Payables and Receivables).
-
-Based on Voucher Type
-
-You can select accounts based on the voucher type. In such a scenario, your balance sheet should be balanced.
-
-<img class="screenshot" alt="Opening Account" src="/assets/manual_erpnext_com/img/accounts/opening-account-1.png">
-
- Also, note that if there are more than 300 ledgers, the system will crash. Thus to avoid such a situation, you can open accounts by using temporary accounts.
-
-#### Temporary Accounts
-
-A nice way to simplify opening is to use a temporary account
-just for opening. These accounts will become zero once all your old
-invoices and opening balances of bank, debt stock etc are entered.
-In the standard chart of accounts, a **Temperory Opening** account is created under
-assets
-
-#### The Opening Entry
-
-In ERPNext Opening Accounts are setup by submitting a special Journal Entries
-(Journal Entry).
-
-Note: Make sure to set “Is Opening” as “Yes” in the More Info section.
-
-> Setup > Opening Accounts and Stock > Opening Accounting Entries.
-
-Complete Journal Entries on the Debit and Credit side.
-
-![Opening Entry](/assets/manual_erpnext_com/old_images/erpnext/opening-entry-1.png)
-
- To update opening balance is to make Journal Entry for an individual/group of accounts.
-
-For example, if you want to update balance in three bank accounts, then make Journal Entrys in this manner.
-
-![Opening Temp Entry](/assets/manual_erpnext_com/old_images/erpnext/image-temp-opening.png)
-
-
-![Opening Entry](/assets/manual_erpnext_com/old_images/erpnext/opening-entry-2.png)
-
-Temporary Asset and Liability account is used for balancing purpose. When you update opening balance in Liability Account, you can use Temporary Asset Account for balancing.
-
-This way, you can update opening balance in Asset and Liability accounts.
-
-You can make two Opening Journal Entrys:
-
-  * For all assets (excluding Accounts Receivables): This entry will contain all your assets except the amounts you are expecting from your Customers against outstanding Sales Invoices. You will have to update your receivables by making an individual entry for each Invoice (this is because, the system will help you track the invoices which are yet to be paid). You can credit the sum of all these debits against the **Temperory Opening** account.
-  * For all liabilities: Similarly you need to pass a Journal Entry for your Opening Liabilities (except for the bills you have to pay) against **Temperory Opening** account.
-  * In this method you can update opening balance of specific balancesheet accounts and not for all.
-  * Opening entry is only for balance sheet accounts and not for expense or Income accounts.
-
-After completing the accounting entries, the trial balance report will look
-like the one given below:
-
-
-![Trial Balance](/assets/manual_erpnext_com/old_images/erpnext/trial-balance-1.png)
-
-#### Outstanding Invoices
-
-After your Opening Journal Entrys are made, you will need to enter each
-Sales Invoice and Purchase Invoice that is yet to be paid.
-
-Since you have already booked the income or expense on these invoices in the
-previous period, select the temp opening account **Temporary Opening** in the “Income” and
-“Expense” accounts.
-
-> Note: Make sure to set each invoice as “Is Opening”!
-
-If you don’t care what items are in that invoice, just make a dummy item entry
-in the Invoice. Item code in the Invoice is not necessary, so it should not be
-such a problem.
-
-Once all your invoices are entered, your **Temperory Opening** account will have a balance of zero!
-
-{next}
diff --git a/erpnext/docs/user/accounts/point-of-sale-pos-invoice.md b/erpnext/docs/user/accounts/point-of-sale-pos-invoice.md
deleted file mode 100644
index c95351c..0000000
--- a/erpnext/docs/user/accounts/point-of-sale-pos-invoice.md
+++ /dev/null
@@ -1,98 +0,0 @@
-# Point of Sale Invoice
-
-Point of Sale (POS) is the place where a retail transaction is completed. It
-is the point at which a customer makes a payment to the merchant in exchange
-for goods or services. For retail operations, the delivery of goods, accrual
-of sale and payment all happens in one event, that is usually called the
-“Point of Sale”.
-
-You can make a Sales Invoice of type POS by checking on “Is POS”. When you
-check this, you will notice that some fields get hidden and some new ones
-emerge.
-
-> Tip: In retail, you may not create a separate Customer record for each
-customer. You can create a general Customer called “Walk-in Customer” and make
-all your transactions against this Customer record.
-
-#### Setting Up POS
-
-In ERPNext all Sales and Purchase transactions, like Sales Invoice, Quotation, Sales Order, Purchase Order etc. can be edited via the POS. There two steps to Setup POS:
-
-1. Enable POS View via (Setup > Customize > Feature Setup)
-2. Create a [POS Setting](/contents/setting-up/pos-setting) record
-
-#### Switch to POS View
-
-Open any sales / purchase transaction. Click on the Computer <i class="icon-desktop"></i> Icon.
-
-#### Different sections of the POS
-
-  * Update Stock: If this is checked, Stock Ledger Entries will be made when you “Submit” this Sales Invoice thereby eliminating the need for a separate Delivery Note.
-  * In your Items table, update inventory information like Warehouse (saved as default), Serial Number, or Batch Number if applicable.
-  * Update Payment Details like your Bank / Cash Account, Paid amount etc.
-  * If you are writing off certain amount. For example when you receive extra cash as a result of not having exact denomination of change, check on ‘Write off Outstanding Amount’ and set the Account.
-
-### Adding an Item
-
-At the billing counter, the retailer needs to select Items which the consumer
-buys. In the POS interface you can select an Item by two methods. One, is by
-clicking on the Item image and the other, is through the Barcode / Serial No.
-
-**Select Item** \- To select a product click on the Item image and add it into the cart. A cart is an area that prepares a customer for checkout by allowing to edit product information, adjust taxes and add discounts.
-
-**Barcode / Serial No** \- A Barcode / Serial No is an optical machine-readable representation of data relating to the object to which it is attached. Enter Barcode / Serial No in the box as shown in the image below and pause for a second, the item will be automatically added to the cart.
-
-![POS](/assets/manual_erpnext_com/old_images/erpnext/pos-add-item.png)
-
-> Tip: To change the quantity of an Item, enter your desired quantity in the
-quantity box. These are mostly used if the same Item is purchased in bulk.
-
-If your product list is very long use the Search field, type the product name
-in Search box.
-
-### Removing an Item
-
-There are two ways to remove an Item.
-
-  * Select an Item by clicking on the row of that Item from Item cart. Then click on “Del” button. OR
-
-  * Enter 0(zero) quantity of any item to delete that item.
-
-To remove multiple Items together, select multiple rows & click on “Del”
-button.
-
-> Delete button appears only when Items are selected.
-
-![POS](/assets/manual_erpnext_com/old_images/erpnext/pos-remove-item.png)
-
-### Make Payment
-
-After all the Items and their quantities are added into the cart, you are
-ready to make the Payment. Payment process is divided into 3 steps -
-
-  1. Click on “Make Payment” to get the Payment window.
-  2. Select your “Mode of Payment”.
-  3. Click on “Pay” button to Save the document.
-
-![POS Payment](/assets/manual_erpnext_com/old_images/erpnext/pos-make-payment.png)
-
-Submit the document to finalise the record. After the document is submitted,
-you can either print or email it directly to the customer.
-
-#### Accounting entries (GL Entry) for a Point of Sale:
-
-Debits:
-
-  * Customer (grand total) 
-  * Bank / Cash (payment)
-
-Credits:
-
-  * Income (net total, minus taxes for each Item) 
-  * Taxes (liabilities to be paid to the government)
-  * Customer (payment)
-  * Write Off (optional)
-
-To see entries after “Submit”, click on “View Ledger”.
-
-{next}
diff --git a/erpnext/docs/user/accounts/purchase-invoice.md b/erpnext/docs/user/accounts/purchase-invoice.md
deleted file mode 100644
index ba7d270..0000000
--- a/erpnext/docs/user/accounts/purchase-invoice.md
+++ /dev/null
@@ -1,71 +0,0 @@
-Purchase Invoice is the exact opposite of your Sales Invoice. It is the bill
-that your Supplier sends you for products or services delivered. Here you
-accrue expenses to your Supplier. Making a Purchase Invoice is very similar to
-making a Purchase Order.
-
-To make a new Purchase Invoice, go to:
-
-> Accounts > Documents > Purchase Invoice > New Purchase Invoice
-
-or click on “Make Purchase Invoice” in Purchase Order or Purchase Receipt.
-
-<img class="screenshot" alt="Purchase Invoice" src="/assets/manual_erpnext_com/img/accounts/purchase-invoice.png">
-
-The concept of “Posting Date” is again same as Sales Invoice. “Bill No” and
-“Bill Date” helps to track the bill number as set by your Supplier for
-reference.
-
-#### Accounting Impact
-
-Like in Sales Invoice, you have to enter an Expense or an Asset account for
-each row in your Items table. This helps to indicate if the Item is an Asset
-or an Expense. You must also enter a Cost Center. These can also be set in the
-Item master.
-
-The Purchase Invoice will affect your accounts as follows:
-
-Accounting entries (GL Entry) for a typical double entry “purchase”:
-
-Debits:
-
-  * Expense or Asset (net totals, excluding taxes)
-  * Taxes (/assets if VAT-type or expense again).
-
-Credits:
-
-  * Supplier
-
-To see entries in your Purchase Invoice after you “Submit”, click on “View
-Ledger”.
-
-* * *
-
-#### Is purchase an “Expense” or an “Asset”?
-
-If the Item is consumed immediately on purchase, or if it is a service, then
-the purchase becomes an “Expense”. For example, a telephone bill or travel
-bill is an “Expense” - it is already consumed.
-
-For inventory Items, that have a value, these purchases are not yet “Expense”,
-because they still have a value while they remain in your stock. They are
-“Assets”. If they are raw-materials (used in a process), they will become
-“Expense” the moment they are consumed in the process. If they are to be sold
-to a Customer, they become “Expense” when you ship them to the Customer.
-
-* * *
-
-#### Deducting Taxes at Source
-
-In many countries, the law may require you to deduct taxes, while paying your
-suppliers. These taxes could be based on a standard rate. Under these type of
-schemes, typically if a Supplier crosses a certain threshold of payment, and
-if the type of product is taxable, you may have to deduct some tax (which you
-pay back to your government, on your Supplier’s behalf).
-
-To do this, you will have to make a new Tax Account under “Tax Liabilities” or
-similar and credit this Account by the percent you are bound to deduct for
-every transaction.
-
-For more help, please contact your Accountant!
-
-{next}
diff --git a/erpnext/docs/user/accounts/sales-invoice.md b/erpnext/docs/user/accounts/sales-invoice.md
deleted file mode 100644
index 4b6c70a..0000000
--- a/erpnext/docs/user/accounts/sales-invoice.md
+++ /dev/null
@@ -1,74 +0,0 @@
-A Sales Invoice is a bill that you send to your customers, against which the customer processes the payment. Sales Invoice is an accounting transaction. On submission of Sales Invoice,  the system updates the receivable and books income against a Customer Account.
-
-You can create a Sales Invoice directly from
-
-> Accounting > Documents > Sales Invoice > New Sales Invoice
-
-or Click on Make Invoice at the right hand corner of the Delivery Note.
-
-<img class="screenshot" alt="Sales Invoice" src="/assets/manual_erpnext_com/img/accounts/sales-invoice.png">
-
-#### Accounting Impact
-
-All Sales must be booked against an “Income Account”. This refers to an
-Account in the “Income” section of your Chart of Accounts. It is a good
-practice to classify your income by type (like product income, service income
-etc). The Income Account must be set for each row of the Items table.
-
-> Tip: To set default Income Accounts for Items, you can set it in the Item or
-Item Group.
-
-The other account that is affected is the Account of the Customer. That is
-automatically set from “Debit To” in the heading section.
-
-You must also mention the Cost Centers in which your Income must be booked.
-Remember that your Cost Centers tell you the profitability of the different
-lines of business or product. You can also set a default Cost Center in the
-Item master.
-
-#### Accounting entries (GL Entry) for a typical double entry “Sale”:
-
-When booking a sale (accrual):
-
-**Debit:** Customer (grand total) **Credit:** Income (net total, minus taxes for each Item) **Credit:** Taxes (liabilities to be paid to the government)
-
-> To see entries in your Sales Invoice after you “Submit”, click on “View
-Ledger”.
-
-#### Dates
-
-Posting Date: The date on which the Sales Invoice will affect your books of
-accounts i.e. your General Ledger. This will affect all your balances in that
-accounting period.
-
-Due Date: The date on which the payment is due (if you have sold on credit).
-This can be automatically set from the Customer master.
-
-#### Recurring Invoices
-
-If you have a contract with a Customer where you bill the Customer on a
-monthly, quarterly, half-yearly or annual basis, you can check the “Recurring
-Invoice” box. Here you can fill in the details of how frequently you want to
-bill this Invoice and the period for which the contract is valid.
-
-ERPNext will automatically create new Invoices and mail it to the email ids
-you set.
-
-* * *
-
-#### "Pro Forma" Invoice
-
-If you want to give an Invoice to a Customer to make a payment before you
-deliver, i.e. you operate on a payment first basis, you should create a
-Quotation and title it as a “Pro-forma Invoice” (or something similar) using
-the Print Heading feature.
-
-“Pro Forma” means for formality. Why do this? Because if you book a Sales
-Invoice it will show up in your “Accounts Receivable” and “Income”. This is
-not ideal as your Customer may or may not decide to pay up. But since your
-Customer wants an “Invoice”, you could give the Customer a Quotation (in
-ERPNext) titled as “Pro Forma Invoice”. This way everyone is happy.
-
-This is a fairly common practice. We follow this at Frappe too.
-
-{next}
diff --git a/erpnext/docs/user/accounts/setup/accounts-settings.md b/erpnext/docs/user/accounts/setup/accounts-settings.md
deleted file mode 100644
index e1f0d11..0000000
--- a/erpnext/docs/user/accounts/setup/accounts-settings.md
+++ /dev/null
@@ -1,10 +0,0 @@
-
-<img class="screenshot" alt="Account Settings" src="/assets/manual_erpnext_com/img/accounts/account-settings.png">
-
-* Accounts Frozen Upto: Freeze accounting transactions upto specified date, nobody can make / modify entry except specified role.
-
-* Role Allowed to Set Frozen Accounts & Edit Frozen Entries: Users with this role are allowed to set frozen accounts and create / modify accounting entries against frozen accounts.
-
-* Credit Controller: Role that is allowed to submit transactions that exceed credit limits set.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/accounts/setup/cost-center.md b/erpnext/docs/user/accounts/setup/cost-center.md
deleted file mode 100644
index d433fe4..0000000
--- a/erpnext/docs/user/accounts/setup/cost-center.md
+++ /dev/null
@@ -1,78 +0,0 @@
-Your Chart of Accounts is mainly designed to provide reports to the government
-and tax authorities. Most businesses have multiple activities like different
-product lines, market segments, areas of business, etc that share some common
-overheads. They should ideally have their own structure to report, whether they
-are profitable or not. For this purpose, there is an alternate structure,
-called the Chart of Cost Centers.
-
-### Cost Center
-
-You can create a tree of Cost Centers to represent your business better. Each
-Income / Expense entry is also tagged against a Cost Center.
-
-For example, if you have two types of sales:
-
-  * Walk-in Sales
-  * Online Sales
-
-You may not have shipping expenses for your walk-in customers, and no shop-
-rent for your online customers. If you want to get the profitability of each
-of these separately, you should create the two as Cost Centers and mark all
-sales as either "Walk-in" or "Online". Mark your all your purchases in the
-same way.
-
-Thus when you do your analysis you get a better understanding as to which side
-of your business is doing better. Since ERPNext has an option to add multiple
-Companies, you can create Cost Centers for each Company and manage it
-separately.
-
-Chart of Cost Centers
-
-To setup your Chart of Cost Centers go to:
-
-> Accounts > Setup > Chart of Cost Centers
-
-![Chart of Cost Center](/assets/manual_erpnext_com/old_images/erpnext/chart-of-cost-centers.png)
-
-Cost centers help you in one more activity, budgeting.
-
-### Budgeting
-
-ERPNext will help you set and manage budgets on your Cost Centers. This is
-useful when, for example, you are doing online sales. You have a budget for
-search ads, and you want ERPNext to stop or warn you from over spending, based
-on that budget.
-
-Budgets are also great for planning purposes. When you are making plans for
-the next financial year, you would typically target a revenue based on which
-you would set your expenses. Setting a budget will ensure that your expenses
-do not get out of hand, at any point, as per your plans.
-
-You can define it in the Cost Center. If you have seasonal sales you can also
-define a budget distribution that the budget will follow.
-
-> Accounts > Setup > Budget Distribution > New Budget Distribution
-
-![Budget Distribution](/assets/manual_erpnext_com/old_images/erpnext/budgeting.png)
-
-#### Budget Actions
-
-ERPNext allows you to either:
-
-  * Stop.
-  * Warn or, 
-  * Ignore 
-
-if you exceed budgets.
-
-These can be defined from the Company record.
-
-Even if you choose to “ignore” budget overruns, you will get a wealth of
-information from the “Budget vs Actual” variance report.
-
-> Note: When you set a budget, it has to be set as per Account under the Cost
-Center. For example if you have a Cost Center “Online Sales”, you can restrict
-“Advertising Budget” by creating a row with that Account and defining the
-amount.
-
-{next}
diff --git a/erpnext/docs/user/accounts/setup/fiscal-year.md b/erpnext/docs/user/accounts/setup/fiscal-year.md
deleted file mode 100644
index b8cf34b..0000000
--- a/erpnext/docs/user/accounts/setup/fiscal-year.md
+++ /dev/null
@@ -1,23 +0,0 @@
-A fiscal year is also known as a financial year or a budget year. It is used
-for calculating financial statements in businesses and other organisations.
-The fiscal year may or may not be the same as a calendar year. For tax
-purposes, companies can choose to be calendar-year taxpayers or fiscal-year
-taxpayers. In many jurisdictions, regulatory laws regarding accounting and
-taxation require such reports once per twelve months. However, it is not
-mandatory that the period should be a calendar year (that is, 1 January to 31
-December).
-
-A fiscal year usually starts at the beginning of a quarter, such as April 1,
-July 1 or October 1. However, most companies' fiscal year also coincides with
-the calendar year, which starts January 1. For the most part, it is simpler
-and easier that way. For some organizations, there are advantages in starting
-the fiscal year at a different time. For example, businesses that are seasonal
-might start their fiscal year on July 1 or October 1. A business that has most
-of its income in the fall and most of its expenses in the spring might also
-choose to start its fiscal year on October 1. That way, they know what their
-income will be for that year, and can adjust their expenses to maintain their
-desired profit margins.
-
-<img class="screenshot" alt="Fiscal Year" src="/assets/manual_erpnext_com/img/accounts/fiscal-year.png">
-
-{next}
diff --git a/erpnext/docs/user/accounts/setup/tax-rule.md b/erpnext/docs/user/accounts/setup/tax-rule.md
deleted file mode 100644
index b183717..0000000
--- a/erpnext/docs/user/accounts/setup/tax-rule.md
+++ /dev/null
@@ -1,21 +0,0 @@
-You can define which [Tax Template](/contents/setting-up/setting-up-taxes) must be applied on a Sales / Purchase transaction using Tax Rule.
-
-<img class="screenshot" alt="Tax Rule" src="/assets/manual_erpnext_com/img/accounts/tax-rule.png">
-
-You can define Tax Rules for Sales or Purchase Taxes. 
-While making a Transaction the system will select and apply tax template based on the tax rule defined.
-The system selects Tax Rule with maximum matching Filters.
-
-Let us consider a senario to understand Tax Rule Better.
-
-Suppose we define 2 Tax Rules as below.
-
-<img class="screenshot" alt="Tax Rule" src="/assets/manual_erpnext_com/img/accounts/tax-rule-1.png">
-
-<img class="screenshot" alt="Tax Rule" src="/assets/manual_erpnext_com/img/accounts/tax-rule-2.png">
-
-Here Tax Rule 1 has Billing Country as India and Tax Rule 2 has Billing Country as United Kingdom
-
-Now supposed we try to create a Sales Order for a customer whose default Billing Country is India, system shall select Tax Rule 1.
-In case the customers Billing Country was United Kingdom, the system would have selected Tax Rule 2.
-
diff --git a/erpnext/docs/user/accounts/tools/bank-reconciliation.md b/erpnext/docs/user/accounts/tools/bank-reconciliation.md
deleted file mode 100644
index 81c5e24..0000000
--- a/erpnext/docs/user/accounts/tools/bank-reconciliation.md
+++ /dev/null
@@ -1,52 +0,0 @@
-### Bank Reconciliation Statement
-
-A Bank Reconciliation is a process that explains the difference between the
-bank balance shown in an organisation's bank statement, as supplied by the
-bank, and the corresponding amount shown in the organisation's own accounting
-records at a particular point in time.  
-
-Such differences may occur, for example, because a cheque or a list of cheques
-issued by the organisation has not been presented to the bank, a banking
-transaction, such as a credit received, or a charge made by the bank, has not
-yet been recorded in the organisations books, or either the bank or the
-organisation itself has made an error.
-
-The Bank Reconciliation statement in ERPNext comes in the form of a report.
-
-#### Figure 1: Bank Reconciliation Statement
-
-![](/assets/manual_erpnext_com/old_images/erpnext/bank-reconciliation-2.png)  
-
-  
-
-When you get the report, check whether the field 'Balance as per bank' matches
-the Bank Account Statement. If there is a match then all the clearance dates
-are updated. If there is a mismatch then check clearance dates and journal
-entries.
-
-To add clearance entries go to Accounts > Tools > Bank Reconciliation
-
-### Bank Reconciliation Tool
-
-The Bank Reconciliation tool in ERPNext, helps add clearance dates to the
-account statements. To Reconcile cheque payments go to Accounts and click on
-Bank Reconciliation.  
-
-__Step 1:__ Select the Bank Account against which you intend to reconcile. For
-example; HDFC Bank, ICICI Bank, or Citibank etc.
-
-__Step 2:__ Select the Date range that you wish to reconcile for.
-
-__Step 3:__ Click on 'Get Reconciled Entries'
-
-All the entries in the specified date range will be shown in a table below.
-
-__Step 4:__ Click on the JV from the table and update clearance date.
-
-#### Figure 2: Bank Reconciliation Tool
-
-<img class="screenshot" alt="Bank Reconciliation" src="/assets/manual_erpnext_com/img/accounts/bank-reconciliation.png">
-
-__Step 5:__ Click on the button 'Update Clearance Date'.
- 
-{next}
diff --git a/erpnext/docs/user/accounts/tools/payment-reconciliation.md b/erpnext/docs/user/accounts/tools/payment-reconciliation.md
deleted file mode 100644
index 1508923..0000000
--- a/erpnext/docs/user/accounts/tools/payment-reconciliation.md
+++ /dev/null
@@ -1,31 +0,0 @@
-Reconciliation is an accounting process used to compare two sets of records to
-ensure the figures are in agreement and are accurate. It is the key process
-used to determine whether the money leaving an account matches the amount
-spent, ensuring the two values are balanced at the end of the recording
-period. In Payment Reconciliation, the invoices are matched against the
-payments made to the bank. Thus if you have many payments which are not
-reconciled with their respective invoices, you can use the payment
-reconciliation tool.
-
-To use Payment Reconciliation Tool go to,
-
-Accounts > Tools > Payment Reconciliation
-
-<img class="screenshot" alt="Payment Reconciliation" src="/assets/manual_erpnext_com/img/accounts/payment-reconcile-tool.png">
-
-__Step 1:__ Select the Account against whom the payments need to be reconciled.
-
-__Step 2:__ Mention the Voucher Type, whether it is Purchase Invoice, Sales
-Invoice or Journal Entry.
-
-__Step 3:__ Select the Voucher Number and click on 'Get Unreconcilled Entries'.  
-
-* All the payment entries will be pulled into a table below.
-
-__Step 4:__ Click on the entry row to allocate a particular amount.
-
-__Step 5:__ Click on the button 'Reconcile'
-
-* You will get a message that says 'Amount allocated successfully'
-
-{next}
diff --git a/erpnext/docs/user/accounts/tools/payment-tool.md b/erpnext/docs/user/accounts/tools/payment-tool.md
deleted file mode 100644
index 9a60e46..0000000
--- a/erpnext/docs/user/accounts/tools/payment-tool.md
+++ /dev/null
@@ -1,24 +0,0 @@
-###Payment Tool
-The Payment Tool Feature allows non-accounting personnel to generate Journal Entrys by populating relevant fields in the Journal Entry with account and payment details.
-
-To go to Payment Tool, click on Accounts > Tools > Payment Tool.
-
-1. Select the Company Name.
-2. Select the Party Type (Customer or Supplier) and the name of the customer or supplier against whom the payment has been made or received.
-3. Use the Received Or Paid field to specify 'Received' if payment is being received or 'Paid' if User is making the payment.
-4. Select the Mode of Payment and the Payment Account .
-5. Enter the Reference Number and Reference Date of the payment, for instance, the Cheque no. and Cheque date in case the payment is being made by cheque.
-6. Click on Get Outstanding Vouchers to fetch all the valid Vouchers, Invoices and Orders against which a payment can be made/received. These will appear in the Against Voucher section.
-	* __Note:__ In case User is paying a customer or receiving payment from a supplier, add the details regarding the relevant invoices and orders manually.
-
-<img class="screenshot" alt="Payment Tool" src="/assets/manual_erpnext_com/img/accounts/payment-tool-1.png">
-
-7. Once details have been fetched, click on the detail entry and enter the payment amount made against that Invoice/Order/Voucher
-
-<img class="screenshot" alt="Payment Tool" src="/assets/manual_erpnext_com/img/accounts/payment-tool-2.png">
-
-8. Click on 'Make Journal Entry' to generate a new Journal Entry with the relevant Party Details and Credit/Debit details filled in.
-
-<img class="screenshot" alt="Payment Tool" src="/assets/manual_erpnext_com/img/accounts/payment-tool-3.png">
-	
-{next}
diff --git a/erpnext/docs/user/accounts/tools/period-closing-voucher.md b/erpnext/docs/user/accounts/tools/period-closing-voucher.md
deleted file mode 100644
index 17e40c0..0000000
--- a/erpnext/docs/user/accounts/tools/period-closing-voucher.md
+++ /dev/null
@@ -1,30 +0,0 @@
-At the end of every year or (quarterly or maybe even monthly), after completing auditing, you can close your books of accounts. This means that you make all your special entries like:
-
-  * Depreciation
-  * Change in value of Assets
-  * Defer taxes and liabilities
-  * Update bad debts
-
-etc. and book your Profit or Loss.
-
-By doing this, your balance in your Income and Expense Accounts become zero. You start a new Fiscal Year (or period) with a balanced Balance Sheet and fresh Profit and Loss account.
-
-In ERPNext after making all the special entries via Journal Entry for the current fiscal year, you should set all your Income and Expense accounts to zero via:
-
-> Accounts > Tools > Period Closing Voucher
-
-**Posting Date** will be when this entry should be executed. If your Fiscal Year ends on 31st December, then that date should be selected as Posting Date in the Period Closing Voucher.
-
-**Transaction Date** will be Period Closing Voucher's creation date.
-
-**Closing Fiscal Year** will be an year for which you are closing your financial statement.
-
-<img class="screenshot" alt="Period Closing Voucher" src="/assets/manual_erpnext_com/img/accounts/period-closing-voucher.png">
-
-This voucher will transfer Profit or Loss (availed from P&L statment) to Closing Account Head. You should select a libility account like Reserves and Surplus, or Capital Fund account as Closing Account.
-
-The Period Closing Voucher will make accounting entries (GL Entry) making all your Income and Expense Accounts zero and transferring Profit/Loss balance to the Closing Account.
-
-<div class=well>If accounting entries are made in a closing fiscal year, even after Period Closing Voucher was created for that Fiscal Year, you should create another Period Closing Voucher. Later voucher will only transfer the pending P&L balance into Closing Account Head.</div>
-
-{next}
diff --git a/erpnext/docs/user/buying/purchase-order.md b/erpnext/docs/user/buying/purchase-order.md
deleted file mode 100644
index 29f6970..0000000
--- a/erpnext/docs/user/buying/purchase-order.md
+++ /dev/null
@@ -1,86 +0,0 @@
-A Purchase Order is analogous to a Sales Order. It is usually a binding
-contract with your Supplier that you promise to buy a set of Items under the
-given conditions.
-
-A Purchase Order can be automatically created from a Material Request or
-Supplier Quotation.
-
-#### Purchase Order Flow Chart
-
-![Purchase Order](/assets/manual_erpnext_com/old_images/erpnext/purchase-order-f.jpg)
-
-In ERPNext, you can also make a Purchase Order directly by going to:
-
-> Buying > Documents > Purchase Order > New Purchase Order
-
-#### Create Purchase Order
-
-<img class="screenshot" alt="Purchase Order" src="/assets/manual_erpnext_com/img/buying/purchase-order.png">
-
-Entering a Purchase Order is very similar to a Purchase Request, additionally
-you will have to set:
-
-  * Supplier.
-  * A “Required By” date on each Item: If you are expecting part delivery, your Supplier will know how much quantity to deliver at which date. This will help you from preventing over-supply. It will also help you to track how well your Supplier is doing on timeliness.
-
-### Taxes
-
-If your Supplier is going to charge you additional taxes or charge like a
-shipping or insurance charge, you can add it here. It will help you to
-accurately track your costs. Also, if some of these charges add to the value
-of the product you will have to mention them in the Taxes table. You can also
-use templates for your taxes. For more information on setting up your taxes
-see the Purchase Taxes and Charges Template.
-
-### Value Added Taxes (VAT)
-
-Many a times, the tax paid by you to a Supplier, for an Item, is the same tax
-which you collect from your Customer. In many regions, what you pay to your
-government is only the difference between what you collect from your Customer
-and what you pay to your Supplier. This is called Value Added Tax (VAT).
-
-For example you buy Items worth X and sell them for 1.3X. So your Customer
-pays 1.3 times the tax you pay your Supplier. Since you have already paid tax
-to your Supplier for X, what you owe your government is only the tax on 0.3X.
-
-This is very easy to track in ERPNext since each tax head is also an Account.
-Ideally you must create two Accounts for each type of VAT you pay and collect,
-“Purchase VAT-X” (asset) and “Sales VAT-X” (liability), or something to that
-effect. Please contact your accountant if you need more help or post a query
-on our forums!
-
-  
-
-#### Purchase UOM and Stock UOM Conversion
-
-You can change your UOM as per your stock requirements in the Purchase Order
-form.
-
-For example, If you have bought your raw material in large quantities with UOM
--boxes, and wish to stock them in UOM- Nos; you can do so while making your
-Purchase Order.
-
-__Step 1:__ Store UOM as Nos in the Item form.
-
-Note: The UOM in the Item form is the stock UOM.
-
-__Step 2:__ In the Purchase Order mention UOM as Box. (Since material arrives in
-Boxes)
-
-__Step 3:__ In the Warehouse and Reference section, the UOM will be pulled in as
-Nos (from the Item form)
-
-#### Figure 3: Conversion of Purchase UOM to stock UOM
-
-
-<img class="screenshot" alt="Purchase Order - UOM" src="/assets/manual_erpnext_com/img/buying/purchase-order-uom.png">
-
-__Step 4:__ Mention the UOM conversion factor. For example, (100);If one box has
-100 pieces.  
-
-__Step 5:__  Notice that the stock quantity will be updated accordingly.
-
-__Step 6:__ Save and Submit the Form.
-
-  
-{next}
diff --git a/erpnext/docs/user/buying/purchase-taxes.md b/erpnext/docs/user/buying/purchase-taxes.md
deleted file mode 100644
index e8b5de6..0000000
--- a/erpnext/docs/user/buying/purchase-taxes.md
+++ /dev/null
@@ -1,38 +0,0 @@
-For Tax Accounts that you want to use in the tax templates, you must mention
-them as type “Tax” in your Chart of Accounts.
-
-Similar to your Sales Taxes and Charges Template is the Purchase Taxes and
-Charges Master. This is the tax template that you can use in your Purchase
-Orders and Purchase Invoices.
-
-> Buying > Setup > Purchase Taxes and Charges Template > New Purchase Taxes and Charges
-Master
-
-![Purchase-Taxes](/assets/manual_erpnext_com/old_images/erpnext/purchase-taxes.png)
-
-  
-
-You can specify if the tax / charge is only for valuation (not a part of
-total) or only for total (does not add value to the item) or for both.
-
-If you select a particular tax as your Default tax, the system will apply this
-tax to all the purchase transactions by default. 
-
-### Calculation Type
-
-This can be on Net Total (that is the sum of basic amount). On Previous Row
-Total / Amount (for cumulative taxes or charges). If you select this option,
-the tax will be applied as a percentage of the previous row (in the tax table)
-amount or total. Actual (as mentioned).
-
-  * **Account Head:** The Account ledger under which this tax will be booked.
-  * **Cost Center:** If the tax / charge is an income (like shipping) or expense it needs to be booked against a Cost Center.
-  * **Description:** Description of the tax (that will be printed in invoices / quotes).
-  * **Rate:** Tax rate.
-  * **Amount:** Tax amount.
-  * **Total:** Cumulative total to this point.
-  * **Enter Row:** If based on "Previous Row Total" you can select the row number which will be taken as a base for this calculation (default is the previous row).
-  * **Consider Tax or Charge for:** In this section you can specify if the tax / charge is only for valuation (not a part of total) or only for total (does not add value to the item) or for both.
-  * **Add or Deduct:** Whether you want to add or deduct the tax.
-
-{next}
diff --git a/erpnext/docs/user/buying/setup/buying-settings.md b/erpnext/docs/user/buying/setup/buying-settings.md
deleted file mode 100644
index 22fd888..0000000
--- a/erpnext/docs/user/buying/setup/buying-settings.md
+++ /dev/null
@@ -1,39 +0,0 @@
-Buying Settings is where you can define properties which will be applied in the Buying module's transactions. 
-
-![Buying Settings](/assets/manual_erpnext_com/img/buying/buying-settings.png)
-
-Let us look at the various options that can be configured:
-
-### 1. Supplier Naming By
-
-When a Supplier is saved, system generates a unique identity or name for that Supplier which can be used to refer the Supplier in various Buying transactions.
-
-If not configured otherwise, ERPNext uses the Supplier's Name as the unique name. If you want to identify Suppliers using names like SUPP-00001, SUPP-00002, or such other patterned series, select the value of Supplier Naming By as "Naming Series".
-
-You can define or select the Naming Series pattern from:
-
-> Setup > Settings > Naming Series
-
-[Click here to know more about defining a Naming Series.](/contents/setting-up/settings/naming-series)
-
-### 2. Default Supplier Type
-
-Configure what should be the value of Supplier Type when a new Supplier is created.
-
-### 3. Default Buying Price List
-
-Configure what should be the value of Buying Price List when a new Buying transaction is created.
-
-### 4. Maintain Same Rate Throughout Purchase Cycle
-
-If this is checked, ERPNext will stop you if you change the Item's price in a Purchase Invoice or Purchase Receipt created based on a Purchase Order, i.e. it will maintain the same price throughout the purchase cycle. If there is a requirement where you need the Item's price to change, you should uncheck this option.
-
-### 5. Purchase Order Required
-
-If this option is configured "Yes", ERPNext will prevent you from creating a Purchase Invoice or a Purchase Receipt without first creating a Purchase Order.
-
-### 6. Purchase Receipt Required
-
-If this option is configured "Yes", ERPNext will prevent you from creating a Purchase Invoice without first creating a Purchase Receipt.
-
-{next}
diff --git a/erpnext/docs/user/buying/setup/supplier-type.md b/erpnext/docs/user/buying/setup/supplier-type.md
deleted file mode 100644
index 356d810..0000000
--- a/erpnext/docs/user/buying/setup/supplier-type.md
+++ /dev/null
@@ -1,28 +0,0 @@
-A supplier may be distinguished from a contractor or subcontractor, who
-commonly adds specialized input to deliverables. A supplier is also known as a
-vendor. There are different types of suppliers based on their goods and
-products.
-
-ERPNext allows you to create your own categories of suppliers. These
-categories are known as Supplier Type. For Example, if your suppliers are
-mainly pharmaceutical companies and FMCG distributors, You can create a new
-Type for them and name them accordingly.
-
-Based on what the suppliers supply, they are classified into different
-categories called Supplier Type. There can be different types of suppliers.
-You can create your own category of Supplier Type.
-
-> Buying > Setup > Supplier Type > New Supplier Type
-
-<img class="screenshot" alt="Supplier Type" src="/assets/manual_erpnext_com/img/buying/supplier-type.png">
-
-You can classify your suppliers from a range of choice available in ERPNext.
-Choose from a set of given options like Distributor, Electrical,Hardware,
-Local, Pharmaceutical, Raw material, Services etc.
-
-Classifying your supplier into different types facilitates accounting and
-payments.
-
-Type your new supplier category and Save.
-
-{next}
diff --git a/erpnext/docs/user/buying/supplier-quotation.md b/erpnext/docs/user/buying/supplier-quotation.md
deleted file mode 100644
index 8419e49..0000000
--- a/erpnext/docs/user/buying/supplier-quotation.md
+++ /dev/null
@@ -1,33 +0,0 @@
-A Supplier Quotation is a formal statement of promise by potential supplier to
-supply the goods or services required by a buyer, at specified prices, and
-within a specified period. A quotation may also contain terms of sale and
-payment, and warranties. Acceptance of quotation by the buyer constitutes an
-agreement binding on both parties.
-
-You can make a supplier quotation from a Material Request
-
-#### Supplier Quotation Flow-Chart
-
-![Supplier Quotation](/assets/manual_erpnext_com/old_images/erpnext/supplier-quotation-f.jpg)
-
-You can also make a Supplier Quotation directly from:
-
-> Buying > Documents > Supplier Quotation > New Supplier Quotation
-
-#### Create Supplier Quotation
-
-<img class="screenshot" alt="Supplier Quotation" src="/assets/manual_erpnext_com/img/buying/supplier-quotation.png">
-
-If you have multiple Suppliers who supply you with the same Item, you
-usually send out a message (Request for Quote) to various Suppliers. In
-many cases, especially if you have centralized buying, you may want to record
-all the quotes so that
-
-  * You can easily compare prices in the future 
-  * Audit whether all Suppliers were given the opportunity to quote.
-
-Supplier Quotations are not necessary for most small businesses. Always
-evaluate the cost of collecting information to the value it really provides!
-You could only do this for high value items.
-
-{next}
diff --git a/erpnext/docs/user/buying/supplier.md b/erpnext/docs/user/buying/supplier.md
deleted file mode 100644
index e31955f..0000000
--- a/erpnext/docs/user/buying/supplier.md
+++ /dev/null
@@ -1,37 +0,0 @@
-Suppliers are companies or individuals who provide you with products or
-services. They are treated in exactly the same manner as Customers in ERPNext.
-
-You can create a new Supplier via:
-
-> Buying > Documents > Supplier > New Supplier
-
-<img class="screenshot" alt="Supplier Master" src="/assets/manual_erpnext_com/img/buying/supplier-master.png">
-
-### Contacts and Addresses
-
-Contacts and Addresses in ERPNext are stored separately so that you can attach
-multiple Contacts or Addresses to Customers and Suppliers. To add a Contact or
-Address go to Buying and click on “New Contact” or “New Address”.
-
-> Tip: When you select a Supplier in any transaction, one Contact and Address
-gets pre-selected. This is the “Default Contact or Address”. So make sure you
-set your defaults correctly!
-
-### Integration with Accounts
-
-In ERPNext, there is a separate Account record for each Supplier, of Each
-company.
-
-When you create a new Supplier, ERPNext will automatically create an Account
-Ledger for the Supplier under “Accounts Payable” in the Company set in the
-Supplier record.
-
-> Advanced Tip: If you want to change the Account Group under which the
-Supplier Account is created, you can set it in the Company master.
-
-If you want to create an Account in another Company, just change the Company
-value and “Save” the Supplier again.
-
-> Tip: You can also import from the Data Import Tool
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/assignment.md b/erpnext/docs/user/collaboration-tools/assignment.md
deleted file mode 100644
index 51948ee..0000000
--- a/erpnext/docs/user/collaboration-tools/assignment.md
+++ /dev/null
@@ -1,40 +0,0 @@
-Assign To feature in ERPNext allows you to allocate particular document to specific user, whom needs to further work on that document.
-
-For example, if Sales Order needs to be approved/submitted by Sales Manager, first draft user can allocate that Sales Order to Sales Manager. On allocating document to Sales Manager, it will be added to that user's ToDo list. Same way, allocation can also be done to Material User and Account user who needs to create Delivery Note and Sales Invoice respectively against this Sales Note.
-
-<div class=well>Permissions restriction cannot be done based on Assigned To</div>
-
-Following are the steps to assign document to another user.
-
-#### Step 1: Click on the Assign To Button
-
-Assign to option is located at the footer of document. Clicking on Assignment Icon on the tool bar will fast-forward you to footer of same document.
-
-![Assigned To Icon](/assets/manual_erpnext_com/old_images/erpnext/assigned-to-icon.png)
-
-
-![Assigned To](/assets/manual_erpnext_com/old_images/erpnext/assigned-to.png)
-
-#### Step 2: Assign to User
-
-In the Assign To section, you will find option to select User to whom this document will be assigned to. You can assign one document to multiple people at a time.
-
-![Assign User](/assets/manual_erpnext_com/old_images/erpnext/assign-user.png)
-
-With assignment, you can also leave a comment for the review of asignee.
-
-####ToDo List of Assignee
-
-This transaction will appear in the To-do list of the ser in “Todo” section.
-
-![Assign Todo](/assets/manual_erpnext_com/old_images/erpnext/assign-todo.png)
-
-####Removing Assignment
-
-User will be able to remove assignment by clicking on "Assignment Completed" button in the document.
-
-![Assign Remove](/assets/manual_erpnext_com/old_images/erpnext/assign-remove.png)
-
-Once assignment is set as completed, Status of its ToDo record will be set as Closed.
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/calendar.md b/erpnext/docs/user/collaboration-tools/calendar.md
deleted file mode 100644
index 9874eb9..0000000
--- a/erpnext/docs/user/collaboration-tools/calendar.md
+++ /dev/null
@@ -1,63 +0,0 @@
-The Calendar is a tool where you can create and share Events and also see
-auto-generated events from the system.
-
-You can switch calender view based on Month, Week and Day.
-
-###Creating Events in Calender
-
-####Creating Event Manually
-
-To create event manually, you should first determine Calender View. If Event's start and end time will be within one day, then you should first switch to Day view.
-
-This view will 24 hours of a day broken in various slots. You should click on slot for Event Start Time, and drag it down till you reach event end time.
-
-![Calender Event Manually](/assets/manual_erpnext_com/old_images/erpnext/calender-event-manually.png)
-
-Based on the selection of time slot, Start Time and End Time will be updated in the Event master. Then you can set subject for an event, and save it.
-
-####Event Based on Lead
-
-In the Lead form, you will find a field called Next Contact By and Next Contact Date. Event will be auto created for date and person person specified in this field.
-
-![Calender Event Lead](/assets/manual_erpnext_com/old_images/erpnext/calender-event-lead.png)
-
-####Birthday Event
-
-Birthday Event is created based on Date of Birth specified in the Employee master.
-
-###Recurring Events
-
-You can set events as recurring in specific interval by Checking the "Repeat This
-Event".
-
-![Calender Event Recurring](/assets/manual_erpnext_com/old_images/erpnext/calender-event-recurring.png)
-
-###Permission for Event
-
-You can set Event as Private or Public. Private Events will be visible only to you, and if any other user selected in the participants table. Instead of User, you can also assign permission for event based on Role.
-
-Public Event, like Birthday will be visible to all.
-
-![Calender Event Permission](/assets/manual_erpnext_com/old_images/erpnext/calender-event-permission.png)
-
-###Event Reminders
-
-There are two ways you can receive email reminder for an event.
-
-####Enable Reminder in Event
-
-In the Event master, checking "Send an email reminder in the morning" will trigger notifcation email to all the participants for this event.
-
-![Calender Event Notification](/assets/manual_erpnext_com/old_images/erpnext/calender-event-notification.png)
-
-####Create Email Digest
-
-To get email reminders for event, you should set Email Digest for Calender Events.
-
-Email Digest can be set from:
-
-`Setup > Email > Email Digest`
-
-![Calender Email Digest](/assets/manual_erpnext_com/old_images/erpnext/calender-email-digest.png)
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/collaborating-around-forms.md b/erpnext/docs/user/collaboration-tools/collaborating-around-forms.md
deleted file mode 100644
index 103e3a2..0000000
--- a/erpnext/docs/user/collaboration-tools/collaborating-around-forms.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Assigned to
-
-You can email any transaction from the system by clicking on the “Assigned to”
-button in the right sidebar. A log of all your sent emails will be maintained
-in Communication.
-
-![Forms](/assets/manual_erpnext_com/old_images/erpnext/forms.png)
-
-### Comments
-
-Comments are a great way to add information about a transaction that is not a
-part of the transactions. Like some background information etc. Comments can
-be added in the right sidebar.
-
-### Tags
-
-[Read more about Tags](/contents/collaboration-tools/tags)  
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/messages.md b/erpnext/docs/user/collaboration-tools/messages.md
deleted file mode 100644
index 102f6c9..0000000
--- a/erpnext/docs/user/collaboration-tools/messages.md
+++ /dev/null
@@ -1,12 +0,0 @@
-You can send and receive messages from the system by using the Messages tool.
-If you send a message to a user, and the user is logged in, it will appear as
-a popup message and the unread messages counter in the top toolbar will be
-updated.
-
-![Message List](/assets/manual_erpnext_com/old_images/erpnext/message-list.png)
-
-You can choose to send message to all the users, or to specific user.
-
-![Messsage To](/assets/manual_erpnext_com/old_images/erpnext/message-to.png)
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/notes.md b/erpnext/docs/user/collaboration-tools/notes.md
deleted file mode 100644
index 5111cd1..0000000
--- a/erpnext/docs/user/collaboration-tools/notes.md
+++ /dev/null
@@ -1,21 +0,0 @@
-You can store your long notes under this section. It can contain your partner lists, frequently used passwords, terms and conditions, or any other document which needs to be shared. Following are the steps to create new Note.
-
-####Go to Note
-
-`Home > Note > New`
-
-####Notes Details
-
-Enter Title and Context.
-
-![Note](/assets/manual_erpnext_com/old_images/erpnext/note.png)
-
-####Set Permissions to select Users
-
-To make Note accessible for all, check "Public" under links section. If specific Note is to be made accessible to specific user, they shall be selected in the Share With table.
-
-![Note Permission](/assets/manual_erpnext_com/old_images/erpnext/note-permission.png)
-
-<div class=well>Notes can also be used as a knowledge base internally. You can also attach file in the Notes, and make it accessible to specific set of users only.</div>
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/tags.md b/erpnext/docs/user/collaboration-tools/tags.md
deleted file mode 100644
index 76adb4f..0000000
--- a/erpnext/docs/user/collaboration-tools/tags.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Like Assignments and Comments, you can also add your own tags to each type of transactions. These tags can help you search a document and also classify it. ERPNext will also show you all the important tags in the document list.
-
-![Tags](/assets/manual_erpnext_com/old_images/erpnext/tags-in-list.png)
-
-{next}
diff --git a/erpnext/docs/user/collaboration-tools/to-do.md b/erpnext/docs/user/collaboration-tools/to-do.md
deleted file mode 100644
index a816bd2..0000000
--- a/erpnext/docs/user/collaboration-tools/to-do.md
+++ /dev/null
@@ -1,10 +0,0 @@
-To Do is a simple tool where all the activities [assigned](https://erpnext.com/collaboration-tools/assignment) to you and assigned
-by you are listed. You can also add your own to-do items in the list.
-
-![Todo List](/assets/manual_erpnext_com/old_images/erpnext/todo-list.png)
-
-When task is completed, you should simply remove assignment from the assigned document. With this, task will be removed from your Todo list as well. For Todo which are not assigned via document, you can set their status as Closed from the Todo record itself.
-
-![Todo Close](/assets/manual_erpnext_com/old_images/erpnext/todo-close.png)
-
-{next}
diff --git a/erpnext/docs/user/customer-portal/customer-orders-invoices-and-shipping-status.md b/erpnext/docs/user/customer-portal/customer-orders-invoices-and-shipping-status.md
deleted file mode 100644
index 33020a8..0000000
--- a/erpnext/docs/user/customer-portal/customer-orders-invoices-and-shipping-status.md
+++ /dev/null
@@ -1,22 +0,0 @@
-ERPNext Web Portal gives your customers quick access to their Orders, Invoices
-and Shipments Customers can check the status of their orders, invoices, and
-shipping status by logging on to the web.
-
-![Portal Menu](/assets/manual_erpnext_com/old_images/erpnext/portal-menu.png)
-
-Once an order is raised, either using the Shopping Cart or from within
-ERPNext, your customer can view the order and keep an eye on the billing and
-shipment status. When the invoice and payment against these orders are
-submitted, the customer can see the updated status on the portal, at a glance.
-
-![Customer Portal](/assets/manual_erpnext_com/old_images/erpnext/customer-portal-orders-1.png)
-
-#### Invoice with paid status.
-
-![Invoice Paid](/assets/manual_erpnext_com/old_images/erpnext/portal-invoice-paid.png)
-
-#### Invoice with billed status.
-
-![Billed Invoice](/assets/manual_erpnext_com/old_images/erpnext/portal-order-billed.png)
-
-{next}
diff --git a/erpnext/docs/user/customer-portal/issues.md b/erpnext/docs/user/customer-portal/issues.md
deleted file mode 100644
index abf4662..0000000
--- a/erpnext/docs/user/customer-portal/issues.md
+++ /dev/null
@@ -1,22 +0,0 @@
-The customer portal makes it very easy for a customer to raise concerns. A
-simple and intuitive interface facilitates your customer to report their
-concerns as Issues. They can view the complete thread of their
-conversation.
-
-#### Empty Ticket List
-
-![Ticket List](/assets/manual_erpnext_com/old_images/erpnext/portal-ticket-list-empty.png)
-
-#### New Issue
-
-![New Ticket](/assets/manual_erpnext_com/old_images/erpnext/portal-new-ticket.png)
-
-#### Open Issue
-
-![Open Issue](/assets/manual_erpnext_com/old_images/erpnext/portal-ticket-1.png)
-
-#### Reply on Issue
-
-![Reply Issue](/assets/manual_erpnext_com/old_images/erpnext/portal-ticket-reply.png)
-
-{next}
diff --git a/erpnext/docs/user/customer-portal/portal-login.md b/erpnext/docs/user/customer-portal/portal-login.md
deleted file mode 100644
index a8aee26..0000000
--- a/erpnext/docs/user/customer-portal/portal-login.md
+++ /dev/null
@@ -1,6 +0,0 @@
-To login into the customer account, the customer has to use his email id and
-the password sent by ERPNext; generated through the sign-up process.
-
-![Login](/assets/manual_erpnext_com/old_images/erpnext/customer-portal-login.png)
-
-{next}
diff --git a/erpnext/docs/user/customer-portal/sign-up.md b/erpnext/docs/user/customer-portal/sign-up.md
deleted file mode 100644
index 4c54617..0000000
--- a/erpnext/docs/user/customer-portal/sign-up.md
+++ /dev/null
@@ -1,22 +0,0 @@
-Customers have to log-in to the Company Website, and sign-up as a customer.
-
-#### Step 1: Click on Login Icon
-
-![Sign Up](/assets/manual_erpnext_com/old_images/erpnext/customer-portal-sign-up-1.png)
-
-  
-
-#### Step 2: Click on Sign Up Icon
-
-![Sign Up](/assets/manual_erpnext_com/old_images/erpnext/customer-portal-sign-up-2.png)
-
-  
-
-#### Step 3: Enter Customer Name and ID
-
-![Sign Up](/assets/manual_erpnext_com/old_images/erpnext/customer-portal-sign-up-3.png)
-
-After the sign up process, a mail will be sent to the customers email id with
-the password details.
-
-{next}
diff --git a/erpnext/docs/user/customize-erpnext/custom-doctype.md b/erpnext/docs/user/customize-erpnext/custom-doctype.md
deleted file mode 100644
index bcfa4dd..0000000
--- a/erpnext/docs/user/customize-erpnext/custom-doctype.md
+++ /dev/null
@@ -1,74 +0,0 @@
-DocType or Document Type is a tool to insert form in ERPNext. The forms like Sales Order,
-Sales Invoices, Production Order are added as Doctype in the backend. Let's assume we are
-creating a Custom Doctype for a Book.
-
-Custom Doctype allows you to insert custom forms in ERPNext as per your requirement.
-
-To create a new **DocType**, go to:
-
-`Setup > Customize > Doctype > New`
-
-#### Doctype Detail
-
-1. Module: Select module in which this Doctype should be placed.
-1. Document Type: Specify if this Doctype will be to carry master data, or to track transactions. Doctype
-for book will be added as Master.
-1. Is Child table: If this Doctype is to be inserted as table into another Doctype, like Item table
-in the Sales Order Doctype, then you should check Is Child Table. Else no.
-1. Is Single: If checked, this Doctype will become a single form, like Selling Setting, which user will
-not be able to re-produce.
-1. Custom?: This field will be checked by default when adding Custom Doctype.
-
-![Doctype Basic](/assets/manual_erpnext_com/img/setup/customize/doctype-basics.png)
-
-#### Fields
-
-In the Fields Table, you can add the fields (properties) of the DocType (Article).
-
-Fields are much more than database columns, they can be:
-
-1. Columns in the database
-1. For Layout (section / column breaks)
-1. Child tables (Table type field)
-1. HTML
-1. Actions (button)
-1. Attachments or Images
-
-![Doctype fields](/assets/manual_erpnext_com/img/setup/customize/Doctype-all-fields.png)
-
-When you add fields, you need to enter the **Type**. **Label** is optional for Section Break and Column Break. **Name** (`fieldname`) is the name of the database table column.
-
-You can also set other properties of the field like whether it is mandatory, read only etc.
-
-#### Naming
-
-In this section, you can define criteria based on which document for this doctype will be named. There are multiple criterion based on which document can be named, like naming based on the value in the specific field, or based on Naming Series, or based on value provided by the user in the prompt, which will be shown when saving document. In the following example, we are doing naming based on the value in the field **book_name**.
-
-![Doctype Naming](/assets/manual_erpnext_com/img/setup/customize/doctype-field-naming.png)
-
-#### Permission
-
-In this table, you should select roles and define permission roles for them for this Doctype.
-
-![Doctype Permissions](/assets/manual_erpnext_com/img/setup/customize/Doctype-permissions.png)
-
-#### Save Doctype
-
-On saving doctype, you will get pop-up to provide name for this Doctype.
-
-![Doctype Save](/assets/manual_erpnext_com/img/setup/customize/Doctype-save.png)
-
-#### Doctype in System
-
-To check this Doctype, open Module defined for this doctype. Since we have added Books doctype in the
-Human Resource module, to access this doctype, go to:
-
-`Human Resource > Document > Book`
-
-![Doctype List](/assets/manual_erpnext_com/img/setup/customize/Doctype-list-view.png)
-
-#### Book master
-
-Using the fields entered, following is the master one book.
-
-![Doctype List](/assets/manual_erpnext_com/img/setup/customize/Doctype-book-added.png)
diff --git a/erpnext/docs/user/customize-erpnext/custom-field.md b/erpnext/docs/user/customize-erpnext/custom-field.md
deleted file mode 100644
index 3c6ef41..0000000
--- a/erpnext/docs/user/customize-erpnext/custom-field.md
+++ /dev/null
@@ -1,77 +0,0 @@
-Custom Field feature allows you to insert fields in the existing masters and transactions as per your requirement. While inseting custom field, you can define its properties like.
-
-* Field Name/Label
-* Field Type
-* Mandatory/Non-Mandatory
-* Insert After Field
-
-To add a Custom Field, go to:
-
-> Setup > Customize > Custom Field > New Custom Field
-
-You can also insert new Custom Field from [Customize Form](https://erpnext.com/customize-erpnext/customize-form) tool.
-
-In Customize Form, for each field, you will find plus (+) option. When click on it, new row will be inserted above that field. You can enter properties for your Custom Field in the newly added blank row.
-
-![Customize Form Custom Field](/assets/manual_erpnext_com/old_images/erpnext/customize-form-custom-field.png)
-
-Following are the steps to insert Custom Field in the existing form.
-
-####New Custom Field form / Row in Customize Form
-
-As mentioned above, you can insert Custom Field from Custom Field form, and also from Customize Form.
-
-####Select Document/Form
-
-You should select transaction or master in which you want to insert custom field. Let's assume you need to insert a custom link field in the Quotation form. In this case, Document will be "Quotation".
-
-![Custom Field Document](/assets/manual_erpnext_com/old_images/erpnext/custom-field-document.png)
-
-####Set Field Label
-
-Custom Field's name will be set based on its Label. If you want to create Custom Field with specific name, but with different label, then you should first set Label as you want Field Name to be set. After Custom Field is saved, you can edit the Field Label again.
-
-![Custom Field Label](/assets/manual_erpnext_com/old_images/erpnext/custom-field-label.png)
-
-####Select Insert After
-
-This field will have all the existing field of the form/doctype selected. Your Custom Field will be placed after field you select in the Insert After field.
-
-![Custom Field Insert](/assets/manual_erpnext_com/old_images/erpnext/custom-field-insert.png)
-
-####Select Field Type
-
-Click [here](https://erpnext.com/kb/customize/field-types) to learn more about types of field you can set for your Custom Field.
-
-![Custom Field Type](/assets/manual_erpnext_com/old_images/erpnext/custom-field-type.png)
-
-####Set Option
-
-If you are creating a Link field, then Doctype name with which this field will be linked to will be entered in the Option field. Click [here](https://erpnext.com/kb/customize/creating-custom-link-field) to learn more about creating custom link field.
-
-![Custom Field Link](/assets/manual_erpnext_com/old_images/erpnext/custom-field-link.png)
-
-If field type is set as Select (drop down field), then all he possible result for this field should be listed in the Options field. Each possible result should be separate by row.
-
-![Custom Field Option](/assets/manual_erpnext_com/old_images/erpnext/custom-field-option.png)
-
-For other field types, like Data, Date, Currency etc., Opton field will be left blank.
-
-####Set More Properties
-
-You can set properties as:
-
-1. Mandatory: Should this field be mandatory or non-mandatory.
-1. Print Hide: Should this field be visible in the print format or no.
-1. Field Description: It will be short field description which will appear just below that field.
-1. Default Value: Value entered in this field will be auto-updated in this field.
-1. Read Only: Checking this option will make custom field non-editable.
-1. Allow on Submit: Checking this option will allow editing value in the field when in submitted transaction.
-
-![Custom Field Properties](/assets/manual_erpnext_com/old_images/erpnext/custom-field-properties.png)
-
-####Deleting Custom Field
-
-Given a permission, user will be able to delete Custom Fields. Incase, it was deleted by default, if you add another Custom Field with same name. Then you shall see new field auto-mapped with old-deleted Custom Field.
-
-{next}
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/index.md b/erpnext/docs/user/customize-erpnext/custom-scripts/index.md
deleted file mode 100644
index 27d4560..0000000
--- a/erpnext/docs/user/customize-erpnext/custom-scripts/index.md
+++ /dev/null
@@ -1,11 +0,0 @@
-If you wish to change any ERPNext form formats, you can do so by using Custom
-Scripts. For example, if you wish to add a submit button after saving, to a
-Lead form, you can do so by creating your own script.
-
-> Setup > Customization > Custom Script
-
-![Custom Script](/assets/manual_erpnext_com/old_images/erpnext/custom-script.png)
-
-### Topics
-
-{index}
diff --git a/erpnext/docs/user/customize-erpnext/customize-form.md b/erpnext/docs/user/customize-erpnext/customize-form.md
deleted file mode 100644
index 62ffce3..0000000
--- a/erpnext/docs/user/customize-erpnext/customize-form.md
+++ /dev/null
@@ -1,107 +0,0 @@
-<!--markdown-->
-Before we venture to learn form customization tool, click [here](https://kb.frappe.io/kb/customization/form-architecture) to understand the architecture of forms in ERPNext. It shall help you in using Customize Form tool more efficiently.
-
-Customize Form is the tool which allows user to customize the property of standard fields as per the requirement. Let's assume we need to set Project Name field as mandatory in the Sales Order form. Following are the steps which shall be followed to achieve this.
-
-####Step 1: Go to Customize Form
-
-You can go to Customize Form from:
-
-> Setup >> Customize >> Customize Form
-
-System Manager will find Customize Form option in the Sales Order list (or any other form for that matter) view as well.
-
-![Customize Form List View](/assets/manual_erpnext_com/old_images/erpnext/customize-form-list-view.png)
-
-####Step 2: Select Docytpe/Document
-
-You should select Docytpe/Document which has field-to-be-customized located in it.
-
-![Customize Form Document](/assets/manual_erpnext_com/old_images/erpnext/customize-form-document.png)
-
-####Step 3:Edit Property
-
-On selecting Doctype/table, you will have all the fields of the table updated as rows in the Customize Form table. You should drill down to field you need to work on, Project Name in this case.
-
-On clicking Project Name row, fields to set various property for this field will be shown. To Customize the mandatory property for a field, there is a field called "Mandatory". Checking this field will set Project Name field as mandatory in the Quotation form.
-
-![Customize Form Mandatory](/assets/manual_erpnext_com/old_images/erpnext/customize-form-mandatory.png)
-
-Like this, you can customize following properties of the field.
-
-* Change field types (for e.g. you want to increase the number of decimal places, you can convert come fields from Float to Currency).
-* Change labels to suit your industry / language.
-* Make certain fields mandatory.
-* Hide certain fields.
-* Change layout (sequence of fields). To do this, select a field in the grid and click on“Up” or “Down” in the grid toolbar.
-* Add / edit “Select” Options. (for example, you can add more sources in Leads etc).
-
-####Step 4: Update
-
-![Customize Form Update](/assets/manual_erpnext_com/old_images/erpnext/customize-form-update.png)
-
-Before checking Sales Order form, you should clear cache and refresh browser tab for customization to take effect.
-
-For Customize Form, you can also allow attachments, set max number of attachments and set the default Print Format.
-
->Note: Though we want you to do everything you can to customize your ERP based on your business needs, we recommend that you do not make “wild” changes to the forms. This is because, these changes may affect certain operations and may mess up your forms. Make small changes and see its effect before doing some more.
-
-Following are the properties which you can customize for a specific field from Customize Form.
-<style>
-    td {
-    padding:5px 10px 5px 5px;
-    };
-    img {
-    align:center;
-    };
-table, th, td {
-    border: 1px solid black;
-    border-collapse: collapse;
-}
-</style>
-<table border="1" width="700px">
-  <tbody>
-    <tr>
-      <td style="text-align: center;"><b>Field property</b></td>
-      <td style="text-align: center;"><b>Purpose</b></td>
-    </tr>
-    <tr>
-      <td>Print hide</td>
-      <td>Checking it will hide field from Standard print format.</td>
-    </tr>
-    <tr>
-      <td>Hidden</td>
-      <td>Checking it field will hide field in the data entry form.</td>
-    </tr>
-    <tr>
-      <td>Mandatory</td>
-      <td>Checking it will set field as mandatory.</td>
-    </tr>
-    <tr>
-      <td>Field Type</td>
-      <td>Click <a href="https://erpnext.com/kb/customize/field-types">here</a> to learn about of fields types.</td>
-    </tr>
-    <tr>
-      <td>Options</td>
-      <td>Possible result for a drop down fields can be listed here. Also for a link field, relevant Doctype can be provided.</td>
-    </tr>
-    <tr>
-      <td>Allow on submit</td>
-      <td>Checking it will let user update value in field even in submitted form.</td>
-    </tr>
-    <tr>
-      <td>Default</td>
-      <td>Value defined in default will be pulled on new record creation.</td>
-    </tr>
-    <tr>
-      <td>Description</td>
-      <td>Gives field description for users understanding.</td>
-    </tr>
-    <tr>
-      <td>Label</td>
-      <td>Label is the field name which appears in form.</td>
-    </tr>
-  </tbody>
-</table>
-
-{next}
diff --git a/erpnext/docs/user/customize-erpnext/document-title.md b/erpnext/docs/user/customize-erpnext/document-title.md
deleted file mode 100644
index da2a6db..0000000
--- a/erpnext/docs/user/customize-erpnext/document-title.md
+++ /dev/null
@@ -1,33 +0,0 @@
-You can customize the title of documents based on properties so that you have meaningful information for the list views.
-
-For example the default title on **Quotation** is the customer name, but if you are dealing a few customers and sending lots of quotes to the same customer, you may want to customize.
-
-#### Setting Title Fields
-
-From ERPNext Version 6.0 onwards, all transactions have a `title` property. If there is not a title property, you can add a **Custom Field** as title and set the **Title Field** via **Customize Form**.
-
-You can set the default value of that property by using Python style string formatting in **Default** or **Options**
-
-To edit a default title, go to
-
-1. Setup > Customize > Customize Form
-2. Select your transaction
-3. Edit the **Default** field in your form
-
-#### Defining Titles
-
-You can define the title by setting document properties in braces `{}`. For example if your document has properties `customer_name` and `project` here is how you can set the default title:
-
-    {customer_name} for {project}
-
-<img class="screenshot" alt = "Customize Title"
-    src="/assets/manual_erpnext_com/img/customize/customize-title.gif">
-
-#### Fixed or Editable Titles
-
-If your title is generated as a default title, it can be edited by the user by clicking on the heading of the document.
-
-<img class="screenshot" alt = "Editable Title"
-    src="/assets/manual_erpnext_com/img/customize/editable-title.gif">
-
-If you want a fixed title, you can set the rule in the **Options** property. In this way, the title will be automatically updated everytime the document is updated.
diff --git a/erpnext/docs/user/customize-erpnext/hiding-modules-and-features.md b/erpnext/docs/user/customize-erpnext/hiding-modules-and-features.md
deleted file mode 100644
index 125a17a..0000000
--- a/erpnext/docs/user/customize-erpnext/hiding-modules-and-features.md
+++ /dev/null
@@ -1,30 +0,0 @@
-### Hiding Unused Features
-
-As you have seen from this manual that ERPNext contains tons of features which
-you may not use. We have observed that most users start with using 20% of the
-features, though a different 20%. To hide fields belonging to features you
-dont require, go to:
-
-> Setup > Tools > Hide/Unhide Features
-
-![Hide Features](/assets/manual_erpnext_com/old_images/erpnext/hide-features.png)
-
-Check / uncheck the features you want to use and refresh your page for the
-changes to take effect.
-
-* * *
-
-### Hiding Module Icons
-
-To hide modules (icons) from the home page, go to:
-
-Setup > Tools> Modules Setup
-
-![Hide/Unhide Modules](/assets/manual_erpnext_com/old_images/erpnext/hide-module.png)
-
-> Note: Modules are automatically hidden for users that have no permissions on
-the documents within that module. For example, if a user has no permissions on
-Purchase Order, Purchase Request, Supplier, the “Buying” module will
-automatically be hidden.
-
-{next}
diff --git a/erpnext/docs/user/customize-erpnext/print-format.md b/erpnext/docs/user/customize-erpnext/print-format.md
deleted file mode 100644
index 0cb9013..0000000
--- a/erpnext/docs/user/customize-erpnext/print-format.md
+++ /dev/null
@@ -1,106 +0,0 @@
-<!-- no-jinja -->
-
-Print Formats are the layouts that are generated when you want to Print or
-Email a transaction like a Sales Invoice. There are two types of Print
-Formats,
-
-  * The auto-generated “Standard” Print Format: This type of format follows the same layout as the form and is generated automatically by ERPNext.
-  * Based on the Print Format document. There are templates in HTML that will be rendered with data.
-
-ERPNext comes with a number of pre-defined templates in three styles: Modern,
-Classic and Standard.
-
-You can modify the templates or create your own. Editing
-ERPNext templates is not allowed because they may be over-written in an
-upcoming release.
-
-To create your own versions, open an existing template from:
-
-> Setup > Printing > Print Formats
-
-![Print Format](/assets/manual_erpnext_com/old_images/erpnext/customize/print-format.png)
-
-Select the type of Print Format you want to edit and click on the “Copy”
-button on the right column. A new Print Format will open up with “Is Standard”
-set as “No” and you can edit the Print Format.
-
-Editing a Print Format is a long discussion and you will have to know a bit of
-HTML, CSS, Python to learn this. For help, please post on our forum.
-
-Print Formats are rendered on the server side using the [Jinja Templating Language](http://jinja.pocoo.org/docs/templates/). All forms have access to the doc object which contains information about the document that is being formatted. You can also access common utilities via the frappe module.
-
-For styling, the [Boostrap CSS Framework](http://getbootstrap.com/) is provided and you can enjoy the full range of classes.
-
-> Note: Pre-printed stationary is usually not a good idea because your Prints
-will look incomplete (inconsistent) when you send them by mail.
-
-#### References
-
-1. [Jinja Tempalting Language: Reference](http://jinja.pocoo.org/docs/templates/)
-1. [Bootstrap CSS Framework](http://getbootstrap.com/)
-
-#### Print Settings
-
-To edit / update your print and PDF settings, go to:
-
-> Setup > Printing and Branding > Print Settings
-
-![Print Format](/assets/manual_erpnext_com/old_images/erpnext/customize/print-settings.png)
-
-#### Example
-
-{% set example = '''<h3>{{ doc.select_print_heading or "Invoice" }}</h3>
-	<div class="row">
-		<div class="col-md-3 text-right">Customer Name</div>
-		<div class="col-md-9">{{ doc.customer_name }}</div>
-	</div>
-	<div class="row">
-		<div class="col-md-3 text-right">Date</div>
-		<div class="col-md-9">{{ doc.get_formatted("invoice_date") }}</div>
-	</div>
-	<table class="table table-bordered">
-		<tbody>
-			<tr>
-				<th>Sr</th>
-				<th>Item Name</th>
-				<th>Description</th>
-				<th class="text-right">Qty</th>
-				<th class="text-right">Rate</th>
-				<th class="text-right">Amount</th>
-			</tr>
-			{%- for row in doc.items -%}
-			<tr>
-				<td style="width: 3%;">{{ row.idx }}</td>
-				<td style="width: 20%;">
-					{{ row.item_name }}
-					{% if row.item_code != row.item_name -%}
-					<br>Item Code: {{ row.item_code}}
-					{%- endif %}
-				</td>
-				<td style="width: 37%;">
-					<div style="border: 0px;">{{ row.description }}</div></td>
-				<td style="width: 10%; text-align: right;">{{ row.qty }} {{ row.uom or row.stock_uom }}</td>
-				<td style="width: 15%; text-align: right;">{{
-					row.get_formatted("rate", doc) }}</td>
-				<td style="width: 15%; text-align: right;">{{
-					row.get_formatted("amount", doc) }}</td>
-			</tr>
-			{%- endfor -%}
-		</tbody>
-	</table>''' %}
-
-    {{ example|e }}
-
-#### Notes
-
-1. To get date and currency formatted values use, `doc.get_formatted("fieldname")`
-1. For translatable strings, us `{{ _("This string is translated") }}`
-
-#### Footers
-
-Many times you may want to have a standard footer for your prints with your
-address and contact information. Unfortunately due to the limited print
-support in HTML pages, it is not possible unless you get it scripted. Either
-you can use pre-printed stationary or add this information in your header.
-
-{next}
diff --git a/erpnext/docs/user/CRM/.txt b/erpnext/docs/user/guides/CRM/.txt
similarity index 100%
rename from erpnext/docs/user/CRM/.txt
rename to erpnext/docs/user/guides/CRM/.txt
diff --git a/erpnext/docs/user/guides/CRM/contact.md b/erpnext/docs/user/guides/CRM/contact.md
new file mode 100644
index 0000000..0294431
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/contact.md
@@ -0,0 +1,19 @@
+Contacts and Addresses in ERPNext are stored separately so that you can
+attach multiple Contacts or Addresses to Customers and Suppliers.
+
+To create a new Contact go to ,
+
+> CRM > Contact > New
+
+<img class="screenshot" alt="Contact" src="assets/img/crm/contact.png">
+
+Or you can add a Contact or Address directly from the Customer record, click on “New
+Contact” or “New Address”.
+
+<img class="screenshot" alt="Contact" src="assets/img/crm/contact-from-cust.png">
+
+> Tip: When you select a Customer in any transaction, one Contact and Address
+gets pre-selected. This is the “Default Contact or Address”.
+
+To Import multiple Contacts and Addresses from a spreadsheet, use the Data
+Import Tool.
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/CRM/customer.md b/erpnext/docs/user/guides/CRM/customer.md
new file mode 100644
index 0000000..c45cfcf
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/customer.md
@@ -0,0 +1,68 @@
+A customer, who is sometimes known as a client, buyer, or purchaser is the one
+who receives goods, services, products, or ideas, from a seller for a monetary
+consideration. A customer can also receive goods or services from a vendor or
+a supplier for other valuable considerations.
+
+You can either directly create your Customers via
+
+> Selling > Customer
+
+or upload it via the Data Import Tool.
+
+<img class="screenshot" alt="Customer" src="assets/img/crm/customer.png">
+
+> Note: Customers are separate from Contacts and Addresses. A Customer can
+have multiple Contacts and Addresses.
+
+### Contacts and Addresses
+
+Contacts and Addresses in ERPNext are stored separately so that you can
+attach multiple Contacts or Addresses to Customers and Suppliers.
+
+Read [Contact](/contents/crm/contact) to know more.
+
+### Integration with Accounts
+
+In ERPNext, there is a separate Account record for each Customer, for each
+Company.
+
+When you create a new Customer, ERPNext will automatically create an Account
+Ledger for the Customer under “Accounts Receivable” in the Company set in the
+Customer record.
+
+> Advanced Tip: If you want to change the Account Group under which the
+Customer Account is created, you can set it in the Company master.
+
+If you want to create an Account in another Company, just change the Company
+value and “Save” the Customer again.
+
+### Customer Settings
+
+You can link a Price List to a Customer (select “Default Price List”), so that
+when you select that Customer, the Price List will be automatically selected.
+
+You can set “Credit Days”, so that it is automatically set due date in the Sales
+Invoices made against this Customer. Credit Days can be defined as fixed days or last day of the next month based on invoice date.
+
+You can set how much credit you want to allow for a Customer by adding the
+“Credit Limit”. You can also set a global “Credit Limit” in the Company
+master. Classifying Customers
+
+ERPNext allows you to group your Customers using [Customer Group](/contents/crm/setup/customer-group) 
+and also divide them into [Territories](/contents/crm/setup/territory)
+Grouping will help you get better analysis of your data and
+identify which Customers are profitable and which are not. Territories will
+help you set sales targets for the respective territories.
+You can also mention [Sales Person](/contents/crm/setup/sales-person) against a customer.
+
+### Sales Partner
+
+A Sales Partner is a third party distributor / dealer / commission agent /
+affiliate / reseller who sells the companies products, for a commission. This
+is useful if you make the end sale to the Customer, involving your Sales
+Partner.
+
+If you sell to your Sales Partner who in-turn sells it to the Customer, then
+you must make a Customer instead.
+
+{next}
diff --git a/erpnext/docs/user/CRM/index.md b/erpnext/docs/user/guides/CRM/index.md
similarity index 100%
rename from erpnext/docs/user/CRM/index.md
rename to erpnext/docs/user/guides/CRM/index.md
diff --git a/erpnext/docs/user/CRM/index.txt b/erpnext/docs/user/guides/CRM/index.txt
similarity index 100%
rename from erpnext/docs/user/CRM/index.txt
rename to erpnext/docs/user/guides/CRM/index.txt
diff --git a/erpnext/docs/user/guides/CRM/lead.md b/erpnext/docs/user/guides/CRM/lead.md
new file mode 100644
index 0000000..b545ca3
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/lead.md
@@ -0,0 +1,46 @@
+To get the customer through the door, you may be doing all or any of the
+following:
+
+  * Listing your product on directories.
+  * Maintaining an updated and searchable website.
+  * Meeting people at trade events.
+  * Advertising your product or services.
+
+When you send out the word that you are around and have something valuable to
+offer, people will come in to check out your product. These are your Leads.
+
+They are called Leads because they may lead you to a sale. Sales people
+usually work on leads by calling them, building a relationship and sending
+information about their products or services. It is important to track all
+this conversation to enable another person who may have to follow-up on that
+contact. The new person is then able to know the history of that particular
+Lead.
+
+To create a Lead, go to:
+
+> Selling > Lead > New Lead
+
+<img class="screenshot" alt="Lead" src="assets/img/crm/lead.png">
+
+ERPNext gives you a lot of options you may want to store about your Leads. For
+example what is the source, how likely are they to give you business etc. If
+you have a healthy number of leads, this information will help you prioritize
+who you want to work with.
+
+> **Tip:** ERPNext makes it easy to follow-up on leads by updating the “Next
+Contact” details. This will add a new event in the Calendar for the User who
+has to contact the lead next.
+
+### Difference between Lead, Contact and Customer
+
+The difference is that a Lead is a potential Customer, someone who can give
+you business. A Customer is an organization or individual who has given you
+business before (and has an Account in your system). A Contact is a person who
+belongs to the Customer.
+
+A Lead can be converted to a Customer by clicking on the “Create Customer”
+button. Once the Customer is created, the Lead becomes “Converted” and any
+further Opportunities from the same source can be created against the
+Customer.
+
+{next}
diff --git a/erpnext/docs/user/guides/CRM/newsletter.md b/erpnext/docs/user/guides/CRM/newsletter.md
new file mode 100644
index 0000000..c2c9718
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/newsletter.md
@@ -0,0 +1,19 @@
+A newsletter is a short written report that tells about the recent activities
+of an organization. It is generally sent to members of the organization,
+potential clients customers or potential leads.
+
+In ERPNext, you can use this UI to send any type of communication to a large
+number of audience. The process of sending bulk email to a target audience is
+very simple and easy.
+
+Select the list that you want to send the email to. Fill in your content in
+the message box, and send your newsletter.If you wish to test your email, to
+see how it looks to the recepient, you can use the test function. Save the
+document before testing. A test email will be sent to your email id. You can
+send the email to all the intended receipients by clicking on the send button.
+
+<img class="screenshot" alt="Newsletter - New" src="assets/img/crm/newsletter-new.png">
+
+<img class="screenshot" alt="Newsletter - Test" src="assets/img/crm/newsletter-test.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/CRM/opportunity.md b/erpnext/docs/user/guides/CRM/opportunity.md
new file mode 100644
index 0000000..4134168
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/opportunity.md
@@ -0,0 +1,30 @@
+When you know a Lead is looking for some products or services to buy, you can
+track that as an Opportunity.
+
+You can create an Opportunity from:
+
+> Selling > Opportunity > New Opportunity
+
+or open a “Open” Lead and click on “Create Opportunity” button.
+
+#### Figure 1: Create Opportunity 
+
+<img class="screenshot" alt="Opportunity" src="assets/img/crm/opportunity.png">
+
+You can also open a “Open” Lead and click on “Create Opportunity” button.
+
+#### Figure 2: Create Opportunity from an open Lead
+
+<img class="screenshot" alt="Opportunity" src="assets/img/crm/lead-to-opportunity.png">
+
+An Opportunity can also come from an existing Customer. You can create
+multiple Opportunities against the same Lead. In Opportunity, apart from the
+Communication, you can also add the Items for which the Lead or Contact is
+looking for.
+
+> Best Practice: Leads and Opportunities are often referred as your “Sales
+Pipeline” this is what you need to track if you want to be able to predict how
+much business you are going to get in the future. Its always a good idea to be
+able to track what is coming in order to adjust your resources.
+
+{next}
diff --git a/erpnext/docs/user/guides/CRM/setup/campaign.md b/erpnext/docs/user/guides/CRM/setup/campaign.md
new file mode 100644
index 0000000..6b45512
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/setup/campaign.md
@@ -0,0 +1,20 @@
+A Campaign is a full-scale implementation of a sales strategy to promote a
+product or a service. This is done in a market segment of a particular
+geographical area, to achieve specified objectives.
+
+<img class="screenshot" alt="Campaign" src="assets/img/crm/campaign.png">
+
+You can track [Lead](/contents/crm/lead), [Opportunity](/contents/crm/opportunity), [Quotation](/contents/selling/quotation) against a campaign.
+
+###Track Leads against Campaign
+
+* To track a 'Lead' against a campaign select 'View Leads'.
+
+<img class="screenshot" alt="Campaign - View Leads" src="assets/img/crm/campaign-view-leads.png">
+
+* You shall get a filtered list of all leads made against that campaign.
+* You can also create new leads by clicking 'New'
+
+<img class="screenshot" alt="Campaign - New Lead" src="assets/img/crm/campaign-new-lead.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/CRM/setup/customer-group.md b/erpnext/docs/user/guides/CRM/setup/customer-group.md
new file mode 100644
index 0000000..2bbc533
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/setup/customer-group.md
@@ -0,0 +1,14 @@
+Customer groups allow you to organize your customers. You can also have discounts based on customer groups.
+You can also get trend analysis for each
+group. Typically Customers are grouped by market segment (that is usually
+based on your domain).
+
+<img class="screenshot" alt="Customer Group Tree" src="assets/img/crm/customer-group-tree.png">
+
+> Tip: If you think all this is too much effort, you can leave it at “Default
+Customer Group”. But all this effort, will pay off when you start getting
+reports. An example of a sample report is given below:
+
+![Sales Analytics](assets/old_images/erpnext/sales-analytics-customer.png)
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/CRM/setup/index.md b/erpnext/docs/user/guides/CRM/setup/index.md
similarity index 100%
rename from erpnext/docs/user/CRM/setup/index.md
rename to erpnext/docs/user/guides/CRM/setup/index.md
diff --git a/erpnext/docs/user/CRM/setup/index.txt b/erpnext/docs/user/guides/CRM/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/CRM/setup/index.txt
rename to erpnext/docs/user/guides/CRM/setup/index.txt
diff --git a/erpnext/docs/user/guides/CRM/setup/sales-person.md b/erpnext/docs/user/guides/CRM/setup/sales-person.md
new file mode 100644
index 0000000..93dfb63
--- /dev/null
+++ b/erpnext/docs/user/guides/CRM/setup/sales-person.md
@@ -0,0 +1,14 @@
+Sales Persons behave exactly like Territories. You can create an organization
+chart of Sales Persons where each Sales Person’s target can be set
+individually. Again as in Territory, the target has to be set against Item
+Group.
+
+<img class="screenshot" alt="Sales Person Tree" src="assets/img/crm/sales-person-tree.png">
+
+####Sales Person in Transactions
+
+You can use this Sales Person in Customer and sales transactions like Sales Order, Delivery Note and Sales Invoice.
+Click [here](https://erpnext.com/kb/selling/managing-sales-persons-in-sales-transactions) to learn more 
+about how Sales Persons are used in the transactions of Sales Cycle.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/accounts/accounting-entries.md b/erpnext/docs/user/guides/accounts/accounting-entries.md
new file mode 100644
index 0000000..0514009
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/accounting-entries.md
@@ -0,0 +1,58 @@
+The concept of accounting is explained with an example given below: We will
+take a "Tea Stall" as a company and see how to book accounting entries for the
+business.
+
+  * Mama (The Tea-stall owner) invests Rs 25000 to start the business.
+
+![A&L](assets/old_images/erpnext/assets-1.png)
+
+__Analysis:__ Mama invested 25000 in company, hoping to get some profit. In other
+words, company is liable to pay 25000 to Mama in the future. So, account
+"Mama" is a liability account and it is credited. Company's cash balance will
+be increased due to the investment, "Cash" is an asset to the company and it
+will debited.
+
+  * The company needs equipments (Stove, teapot, cups etc) and raw materials (tea, sugar, milk etc) immediately. He decides to buy from the nearest general store "Super Bazaar" who is a friend so that he gets some credit. Equipments cost him 2800 and raw materials worth of 2200. He pays 2000 out of total cost 5000.
+
+![A&L](assets/old_images/erpnext/assets-2.png)
+
+__Analysis:__ Equipments are "Fixed Assets" (because they have a long life) of the
+company and raw materials "Current Assets" (since they are used for day-to-day
+business), of the company. So, "Equipments" and "Stock in Hand" accounts have
+been debited to increase the value. He pays 2000, so "Cash" account will be
+reduced by that amount, hence credited and he is liable to pay 3000 to "Super
+Bazaar" later, so Super Bazaar will be credited by 3000.
+
+  * Mama (who takes care of all entries) decides to book sales at the end of the every day, so that he can analyze daily sales. At the end of the very first day, the tea stall sells 325 cups of tea, which gives net sales of Rs. 1575. The owner happily books his first day sales.
+
+![A&L](assets/old_images/erpnext/assets-3.png)
+
+__Analysis:__ Income has been booked in "Sales of Tea" account which has been
+credited to increase the value and the same amount will be debited to "Cash"
+account. Lets say, to make 325 cups of tea, it costs Rs. 800, so "Stock in
+Hand" will be reduced (Cr) by 800 and expense will be booked in "Cost of goods
+sold" account by same amount.
+
+At the end of the month, the company paid the rent amount of stall (5000) and
+salary of one employee (8000), who joined from the very first day.
+
+![A&L](assets/old_images/erpnext/assets-4.png)
+
+### Booking Profit
+
+As month progress, company purchased more raw materials for the business.
+After a month he books profit to balance the "Balance Sheet" and "Profit and
+Loss Statements" statements. Profit belongs to Mama and not the company hence
+its a liability for the company (it has to pay it to Mama). When the Balance
+Sheet is not balanced i.e. Debit is not equal to Credit, the profit has not
+yet been booked. To book profit, the following entry has to be made:
+
+![A&L](assets/old_images/erpnext/assets-5.png)
+
+Explanation: Company's net sales and expenses are 40000 and 20000
+respectively. So, company made a profit of 20000. To make the profit booking
+entry, "Profit or Loss" account has been debited and "Capital Account" has
+been credited. Company's net cash balance is 44000 and there is some raw
+materials available worth 1000 rupees.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/accounting-reports.md b/erpnext/docs/user/guides/accounts/accounting-reports.md
new file mode 100644
index 0000000..a7e401a
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/accounting-reports.md
@@ -0,0 +1,43 @@
+Some of the major accounting reports are:
+
+### General Ledger
+
+General Ledger is based on the table GL Entry and can be filtered by Account
+and between a period. This will help you to get a full update for all entries
+done in that period for that Account.
+
+<img alt="General Ledger" class="screenshot"
+    src="assets/img/accounts/general-ledger.png">
+
+### Trial Balance
+
+Trial Balance is the list of Account balances for all your Accounts
+(“Ledger” and “Group”) on a particular date. For each Account it will give you
+the:
+
+  * Opening
+  * Debits
+  * Credits
+  * Closing
+
+<img alt="Trial Balance" class="screenshot" src="assets/img/accounts/trial-balance.png">
+
+The sum of all closing balances in a Trial Balance must be zero.
+
+### Accounts Payable and Accounts Receivable (AP / AR)
+
+These reports help you to track the outstanding invoices sent to Customer and
+Suppliers. In this report, you will get your outstanding amounts period wise.
+i.e. between 0-30 days, 30-60 days and so on.
+
+<img alt="Accounts Receivable" class="screenshot" src="assets/img/accounts/accounts-receivable.png">
+
+### Sales and Purchase Register
+
+In this report, each tax Account is transposed in columns. For each Invoice and
+invoice Item, you will get the amount of individual tax that has been paid,
+based on the Taxes and Charges table.
+
+<img alt="Sales Register" class="screenshot" src="assets/img/accounts/sales-register.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/advance-payment-entry.md b/erpnext/docs/user/guides/accounts/advance-payment-entry.md
new file mode 100644
index 0000000..72b7e5e
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/advance-payment-entry.md
@@ -0,0 +1,62 @@
+Payment done by the customer before accepting delivery of the product is an
+Advance Payment. For Orders of high value, the business houses expect to
+receive advance.
+
+  
+__For Example:__ Consider a customer- Jane D'souza placing an order for a double
+bed costing $10000 She is asked to give some advance before the furniture
+house begins work on her order. She gives them $5000 in cash.
+
+  
+Go to Accounts and open a new Journal Entry to make the advance entry.
+
+> Accounts > Documents > Journal Entry > New Journal Entry  
+
+Mention the voucher type as cash voucher. This differs for different
+customers. If somebody pays by cheque the voucher type will be Bank Voucher.
+Then select the customer account and make the respective debit and credit
+entries.  
+
+Since the customer has given $5000 as cash advance,it will be recorded as a
+credit entry against the customer. To balance it with the debit entry [Double
+accounting Entry] enter $5000 as debit against the company's cash account. In
+the row "Is Advance" click 'Yes'.
+
+#### Figure 1 : Journal Entry -Advance Entry  
+
+<img class="screenshot" alt="Advace Payment" src="assets/img/accounts/advance-payment-1.png">
+
+### Double Entry Accounting  
+
+Double entry bookkeeping is a system of accounting in which every transaction
+has a corresponding positive and negative entry : debits and credits. Every
+transaction involves a [debit entry
+](http://www.e-conomic.co.uk/accountingsystem/glossary/debit)in one account
+and a [credit
+entry](http://www.e-conomic.co.uk/accountingsystem/glossary/credit) in another
+account. This means that every transaction must be recorded in two accounts;
+one account will be debited because it receives value and the other account
+will be credited because it has given value.
+
+  
+#### Figure 2: Transaction and Difference Entry
+
+<img class="screenshot" alt="Advace Payment" src="assets/img/accounts/advance-payment-2.png">
+
+Save and submit the JV. If this document is not saved it will not be pulled in
+other accounting documents.
+
+When you make a new Sales Invoice for the same customer, mention the advance
+in the Sales Invoice Form.
+
+To link the Sales Invoice to the Journal Entry which mentions the advance
+payment entry, click on ‘Get Advances Received’.  Allocate the amount of
+advance in the advances table. The accounting will be adjusted accordingly.
+
+#### Figure 3: Receive Advance 
+
+<img class="screenshot" alt="Advace Payment" src="assets/img/accounts/advance-payment-3.png">
+
+Save and submit the Sales Invoice.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/budgeting.md b/erpnext/docs/user/guides/accounts/budgeting.md
new file mode 100644
index 0000000..292fd9e
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/budgeting.md
@@ -0,0 +1,58 @@
+ERPNext will help you set and manage budgets on your Cost Centers. This is
+useful when, for example, you are doing online sales. You have a budget for
+search ads, and you want ERPNext to stop or warn you from over spending, based
+on that budget.
+
+Budgets are also great for planning purposes. When you are making plans for
+the next financial year, you would typically target a revenue based on which
+you would set your expenses. Setting a budget will ensure that your expenses
+do not get out of hand, at any point, as per your plans.
+
+You can define it in the Cost Center. If you have seasonal sales you can also
+define a budget distribution that the budget will follow.
+
+In order to allocate budget, go to Accounts > Setup > Chart of Cost Centers and click on Chart of Cost Center.
+Select a Cost Center and click on Open.
+
+#### Step 1: Click on Edit.
+
+![](assets/old_images/erpnext/budgeting-1.png)  
+
+<img alt="Accounts Receivable" class="screenshot" src="assets/img/accounts/accounts-receivable.png">
+
+#### Step 2: Enter Monthly Distribution.
+
+![](assets/old_images/erpnext/budgeting-2-1.png)
+
+
+If you leave the** **distribution ID blank, ERPNext will calculate on a yearly
+basis or in equal proportion for every month.
+
+#### Step 3:Add New Row and select budget account.  
+
+
+
+![](assets/old_images/erpnext/budgeting-3.png)  
+
+
+
+### To Create New Distribution ID
+
+ERPNext allows you to take a few budget actions. It signifies whether to stop
+, warn or Ignore  if you exceed budgets.  
+
+![](assets/old_images/erpnext/budgeting-4.png)
+
+
+
+These can be defined from the Company record.
+
+![](assets/old_images/erpnext/budgeting-4-1.png)  
+
+
+
+Even if you choose to “ignore” budget overruns, you will get a wealth of
+information from the “Budget vs Actual” variance report. This report shows
+month wise actual expenses as compared to the budgeted expenses.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/chart-of-accounts.md b/erpnext/docs/user/guides/accounts/chart-of-accounts.md
new file mode 100644
index 0000000..67735bc
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/chart-of-accounts.md
@@ -0,0 +1,128 @@
+The Chart of Accounts forms the blueprint of your organization. The overall
+structure of your Chart of Accounts is based on a system of double entry
+accounting that has become a standard all over the world to quantify how a
+company is doing financially.
+
+The Chart of Accounts helps you to answer:
+
+  * What is your organisation worth?
+  * How much debt have you taken?
+  * How much profit are you making (and hence paying tax)?
+  * How much are you selling?
+  * What is your expense break-up
+
+You may note that as a business manager, it is very valuable to see how well
+your business is doing.
+
+> Tip: If you can’t read a Balance Sheet (It took me a long time to
+figure this out) it's a good opportunity to start learning about this. It will
+be worth the effort. You can also take the help of your accountant to setup
+your Chart of Accounts.
+
+Financial statement of your company is easily viewable in ERPNext. An Example
+of a financial statement is given below:
+
+<img class="screenshot" alt="Financial Analytics Balance Sheet" src="assets/img/accounts/financial-analytics-bl.png">
+
+To edit your Chart of Accounts in ERPNext go to:
+
+>  Accounts > Setup > Chart of Accounts
+
+Chart of Accounts is a tree view of the names of the Accounts (Ledgers and
+Groups) that a Company requires to manage its books of accounts. ERPNext sets
+up a simple chart of accounts for each Company you create, but you have to
+modify it according to your needs and legal requirements. For each company,
+Chart of Accounts signifies the way to classify the accounting entries, mostly
+based on statutory (tax, compliance to government regulations) requirements.
+
+Let us understand the main groups of the Chart of Accounts.
+
+<img class="screenshot" alt="Chart of Accounts" src="assets/img/accounts/chart-of-accounts-1.png">
+
+### Balance Sheet Accounts
+
+The Balance Sheet has Application of Funds (/assets) and Sources of Funds
+(Liabilities) that signify the net-worth of your company at any given time.
+When you begin or end a financial period, all the Assets are equal to the
+Liabilities.
+
+> Accounting: If you are new to accounting, you might be wondering, how can
+Assets be equal to Liabilities? That would mean the company has nothing of its
+own. Thats right. All the “investment” made in the company to buy assets (like
+land, furniture, machines) is made by the owners and is a liability to the
+company. If the company would want to shut down, it would need to sell all the
+assets and pay back all the liabilities (including profits) to the owners,
+leaving itself with nothing.
+
+All the accounts under this represent an asset owned by the company like "Bank
+Account", "Land and Property", "Furniture" or a liability (funds that the
+company owes to others) like "Owners funds", "Debt" etc.
+
+Two special accounts to note here are Accounts Receivable (money you have to
+collect from your customers) and Accounts Payable (money you have to pay to
+your suppliers) under Assets and Liabilities respectively.
+
+### Profit and Loss Accounts
+
+Profit and Loss is the group of Income and Expense accounts that represent
+your accounting transactions over a period.
+
+Unlike Balance sheet accounts, Profit and Loss accounts (or PL accounts) do
+not represent net worth (/assets), but rather represent the amount of money
+spent and collected in servicing customers during the period. Hence at the
+beginning and end of your Fiscal Year, they become zero.
+
+In ERPNext it is easy to create a Profit and Loss analysis chart. An example
+of a Profit and Loss analysis chart is given below:
+
+<img class="screenshot" alt="Financial Analytics Profit and Loss Statement" src="assets/img/accounts/financial-analytics-pl.png">
+
+(On the first day of the year you have not made any profit or loss, but you
+still have assets, hence balance sheet accounts never become zero at the
+beginning or end of a period)
+
+### Groups and Ledgers
+
+There are two main kinds of Accounts in ERPNext - Group and Ledger. Groups can
+have sub-groups and ledgers within them, whereas ledgers are the leaf nodes of
+your chart and cannot be further classified.
+
+Accounting Transactions can only be made against Ledger Accounts (not Groups)
+
+> Info: The term "Ledger" means a page in an accounting book where entries are
+made. There is usually one ledger for each account (like a Customer or a
+Supplier).
+
+> Note: An Account “Ledger” is also sometimes called as Account “Head”.
+
+<img class="screenshot" alt="Chart of Accounts" src="assets/img/accounts/chart-of-accounts-2.png">
+
+### Other Account Types
+
+In ERPNext, you can also specify more information when you create a new
+Account, this is there to help you select that particular account in a
+scenario like Bank Account or a Tax Account and has no effect on the Chart
+itself.
+
+### Creating / Editing Accounts
+
+To create new Accounts, explore your Chart of Accounts and click on an Account
+group under which you want to create the new Account. On the right side, you
+will see an option to “Open” or “Add Child” a new Account.
+
+<img class="screenshot" alt="Chart of Accounts" src="assets/img/accounts/chart-of-accounts-3.png">
+
+Option to create will only appear if you click on a Group (folder) type
+Account.
+
+ERPNext creates a standard structure for you when the Company is created but
+it is up to you to modify or add or remove accounts.
+
+Typically, you might want to create Accounts for
+
+  * Types of Expenses (travel, salaries, telephone etc) under Expenses.
+  * Taxes (VAT, Sales Tax etc based on your country) under Current Liabilities.
+  * Types of Sales (for example, Product Sales, Service Sales etc.) under Income.
+  * Types of Assets (building, machinery, furniture etc.) under Fixed Assets.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/credit-limit.md b/erpnext/docs/user/guides/accounts/credit-limit.md
new file mode 100644
index 0000000..1ab5e4d
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/credit-limit.md
@@ -0,0 +1,34 @@
+  
+
+A credit limit is the maximum amount of credit that a financial institution or
+other lender will extend to a debtor for a particular line of credit. From an
+organisation's perspective, it is the maximum amount of credit which a
+customer gets on goods purchased.  
+
+To set credit limit go to Customer - Master
+
+> Selling > Document > Customer 
+
+  
+#### Figure 1: Credit Limit
+
+<img class="screenshot" alt="Credit Limit" src="assets/img/accounts/credit-limit-1.png">
+
+Go to the 'More Info section' and enter the amount in the field Credit Limit.
+
+In case a need arises to allow more credit to the customer as a good-will, the
+Credit Controller has access to submit order even if credit limit is crossed.
+
+To allow any other role to submit transactions by customers whose credit limit
+has expired, go to accounting settings and make changes.
+
+In the field Credit Controller, select the role who would be authorized to
+accept orders or raise credit limits of customers.
+  
+#### Figure 2: Credit Controller
+
+<img class="screenshot" alt="Credit Limit" src="assets/img/accounts/credit-limit-2.png">
+
+Save the changes.
+
+{next}
diff --git a/erpnext/docs/user/accounts/index.md b/erpnext/docs/user/guides/accounts/index.md
similarity index 100%
rename from erpnext/docs/user/accounts/index.md
rename to erpnext/docs/user/guides/accounts/index.md
diff --git a/erpnext/docs/user/accounts/index.txt b/erpnext/docs/user/guides/accounts/index.txt
similarity index 100%
rename from erpnext/docs/user/accounts/index.txt
rename to erpnext/docs/user/guides/accounts/index.txt
diff --git a/erpnext/docs/user/guides/accounts/item-wise-tax.md b/erpnext/docs/user/guides/accounts/item-wise-tax.md
new file mode 100644
index 0000000..b0edc81
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/item-wise-tax.md
@@ -0,0 +1,30 @@
+
+Taxes selected in the Tax and Other Charges in transactions are applied on all the items. If you need different taxes applied on items selected in the same transaction, you should setup you item and tax master as explained in the steps below.
+
+####Step 1: Mention Tax Applicable in the Item master
+
+Item master has tax table where you can list taxes which will be applied on it.
+
+![Item wise Tax](assets/old_images/erpnext/item-wise-tax.png)
+
+Tax rate mentioned in the item master gets preference over tax rate entered in the transactions. 
+
+For example, if you provide tax rate for VAT as 10% for item ABC, where for same VAT ledger 12% rate is entered in the Sales Order/Invoice, for item ABC, tax rate applied would be 10%, as mentioned in the item master.
+
+####Step 2: Setup Taxes and Other Charges
+
+In Taxes and Other Charges master, you should select all the applicable taxes which could be applicable on item.
+
+For example, if few items has VAT 5 applied on them, other has Service Tax applied, and some other has Excise Duty applicable, then you tax master should have all these taxes selected.
+
+![item wise tax master](assets/old_images/erpnext/item-wise-tax-master.png)
+
+####Step 3: Set Tax Rate as Zero in Taxes and Charges Template
+
+In the Taxes and Other Charges master, tax rate will be updated as ZERO. It means, tax rate applicable on items will be pulled from the respective Item master. While for other items, 0% tax will be applied, means no other taxes will be applied on that item.
+
+Based on the above setting, you will have taxes applied on items as mentioned in the respective item master. Check following for an instance.
+
+![item wise tax calculation](assets/old_images/erpnext/item-wise-tax-calc.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/journal-entry.md b/erpnext/docs/user/guides/accounts/journal-entry.md
new file mode 100644
index 0000000..5807f93
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/journal-entry.md
@@ -0,0 +1,71 @@
+All types of accounting entries other than **Sales Invoice** and **Purchase
+Invoice** are made using the **Journal Entry**. A **Journal Entry** 
+is a standard accounting transaction that affects
+multiple Accounts and the sum of debits is equal to the sum of credits.
+
+To create a Journal Entry go to:
+
+> Accounts > Documents > Journal Entry > New
+
+<img class="screenshot" alt="Journal Entry" src="assets/img/accounts/journal-entry.png">
+
+In a Journal Entry, you must select.
+
+  * Type of Voucher from the drop down.
+  * Add rows for the individual accounting entries. In each row, you must specify: 
+    * The Account that will be affected
+    * The amount to Debit or Credit
+    * The Cost Center (if it is an Income or Expense)
+    * Against Voucher: Link it to a voucher or invoice if it affects the “outstanding” amount of that invoice.
+    * Is Advance: Select “Yes” if you want to make it selectable in an Invoice. Other information in case it is a Bank Payment or a bill.
+
+#### Difference
+
+The “Difference” field is the difference between the Debit and Credit amounts.
+This should be zero if the Journal Entry is to be “Submitted”. If this
+number is not zero, you can click on “Make Difference Entry” to add a new row
+with the amount required to make the total as zero.
+
+* * *
+
+## Common Entries
+
+A look at some of the common accounting entries that can be done via Journal
+Voucher.
+
+#### Expenses (non accruing)
+
+Many times it may not be necessary to accrue an expense, but it can be
+directly booked against an expense Account on payment. For example a travel
+allowance or a telephone bill. You can directly debit Telephone Expense
+(instead of your telephone company) and credit your Bank on payment.
+
+  * Debit: Expense Account (like Telephone expense)
+  * Credit: Bank or Cash Account
+
+#### Bad Debts or Write Offs
+
+If you are writing off an Invoice as a bad debt, you can create a Journal
+Voucher similar to a Payment, except instead of debiting your Bank, you can
+debit an Expense Account called Bad Debts.
+
+  * Debit: Bad Debts Written Off
+  * Credit: Customer
+
+> Note: There may be regulations in your country before you can write off bad
+debts.
+
+#### Depreciation
+
+Depreciation is when you write off certain value of your assets as an expense.
+For example if you have a computer that you will use for say 5 years, you can
+distribute its expense over the period and pass a Journal Entry at the end
+of each year reducing its value by a certain percentage.
+
+  * Debit: Depreciation (Expense)
+  * Credit: Asset (the Account under which you had booked the asset to be depreciated)
+
+> Note: There may be regulations in your country that define by how much
+amount you can depreciate a class of Assets.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/making-payments.md b/erpnext/docs/user/guides/accounts/making-payments.md
new file mode 100644
index 0000000..2e7fc67
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/making-payments.md
@@ -0,0 +1,98 @@
+Payments made against Sales Invoices or Purchase Invoices can be made by
+clicking on “Make Payment Entry” button on “Submitted” invoices.
+
+  1. Update the “Bank Account” (you can also set the default account in the Company master).
+  2. Update posting date.
+  3. Enter the cheque number, cheque date.
+  4. Save and Submit.
+
+<img class="screenshot" alt="Manking Payment" src="assets/img/accounts/make-payment.png">
+
+Payments can also be made independent of invoices by creating a new Journal
+Voucher and selecting the type of payment.
+
+#### Incoming Payment
+
+For payments from Customers,
+
+  * Debit: Bank or Cash Account
+  * Credit: Customer
+
+> Note: Remember to add “Against Sales Invoice” or “Is Advance” as applicable.
+
+#### Outgoing Payment
+
+For payments to Suppliers,
+
+  * Debit: Supplier
+  * Credit: Bank or Cash Account
+
+### Example Payment Journal Entry
+
+<img class="screenshot" alt="Manking Payment" src="assets/img/accounts/new-bank-entry.png">
+
+* * *
+
+### Reconciling Cheque Payments
+
+If you are receiving payments or making payments via cheques, the bank
+statements will not accurately match the dates of your entry, this is because
+the bank usually takes time to “clear” these payments. Also you may have
+mailed a cheque to your Supplier and it may be a few days before it is
+received and deposited by the Supplier. In ERPNext you can synchronize your
+bank statements and your Journal Entrys using the “Bank Reconciliation”
+tool.
+
+To use this, go to:
+
+> Accounts > Tools > Bank Reconciliation
+
+Select your “Bank” Account and enter the dates of your statement. Here you
+will get all the “Bank Voucher” type entries. In each of the entry on the
+right most column, update the “Clearance Date” and click on “Update”.
+
+By doing this you will be able to sync your bank statements and entries into
+the system.
+
+* * *
+
+## Managing Outstanding Payments
+
+In most cases, apart from retail sales, billing and payments are separate
+activities. There are several combinations in which these payments are done.
+These cases apply to both sales and purchases.
+
+  * They can be upfront (100% in advance).
+  * Post shipment. Either on delivery or within a few days of delivery.
+  * Part in advance and part on or post delivery.
+  * Payments can be made together for a bunch of invoices.
+  * Advances can be given together for a bunch of invoices (and can be split across invoices).
+
+ERPNext allows you to manage all these scenarios. All accounting entries (GL
+Entry) can be made against a Sales Invoice, Purchase Invoice or Journal
+Vouchers (in special cases, an invoice can be made via a Sales Invoice too).
+
+The total outstanding amount against an invoice is the sum of all the
+accounting entries that are made “against” (or are linked to) that invoice.
+This way you can combine or split payments in Journal Entrys to manage the
+scenarios.
+
+### Matching Payments to Invoices
+
+In complex scenarios, especially in the capital goods industry, sometimes
+there is no direct link between payments and invoices. You send invoices to
+your Customers and your Customer sends you block payments or payments based on
+some schedule that is not linked to your invoices.
+
+In such cases, you can use the Payment to Invoice Matching Tool.
+
+> Accounts > Tools > Payment Reconciliation
+
+In this tool, you can select an account (your Customer’s account) and click on
+“Pull Payment Entries” and it will select all un-linked Journal Entrys and
+Sales Invoices from that Customer.
+
+To cancel off some payments and invoices, select the Invoices and Journal
+Vouchers and click on “Reconcile”.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/multi-currency-accounting.md b/erpnext/docs/user/guides/accounts/multi-currency-accounting.md
new file mode 100644
index 0000000..d0e0db8
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/multi-currency-accounting.md
@@ -0,0 +1,119 @@
+In ERPNext, you can make accounting entries in multiple currency. For example, if you have a bank account in foreign currency, you can make transactions in that currency and system will show bank balance in that specific currency only.
+
+## Setup
+
+To get started with multi-currency accounting, you need to assign accounting currency in Account record. You can define Currency from Chart of Accounts while creating Account.
+
+<img class="screenshot" alt="Set Currency from Chart of Accounts"  	src="assets/img/accounts/multi-currency/chart-of-accounts.png">
+
+You can also assign / modify the currency by opening specific Account record for existing Accounts.
+
+<img class="screenshot" alt="Modify Account Currency"  	src="assets/img/accounts/multi-currency/account.png">
+
+For Customer / Supplier (Party), you can also define it's accounting currency in the Party record. If the Party's accounting currency is different from Company Currency, you have to mention Default Receivable / Payable Account in that currency.
+
+<img class="screenshot" alt="Customer Accounting Currency"  	src="assets/img/accounts/multi-currency/customer.png">
+
+
+Once you defined Accounting Currency in Party / Account record, you are ready to make transactions against them. If Party's accounting currency is different from Company Currency, system will restrict to make transaction for that party with that currency only. If accounting currency is same as Company Currency, you can make transactions for that Party in any currency. But accounting entries (GL Entries) will always be in Party's Accounting Currency. In any case, currency of Receivable Account will always be same as accounting currency of the Party.
+
+You can change accounting currency in Party / Account record, until making any transactions against them. After making accounting entries, system will not allow to change the accounting currency for both Party / Account record.
+
+In case of multi-company setup, accounting currency of Party must be same for all the companies.
+
+## Transactions
+
+### Sales Invoice
+
+In Sales Invoice, transaction currency must be same as accounting currency of Customer if Customer's accounting currency is other than Company Currency. Otherwise, you can select any currency in Invoice. On selection of Customer, system will fetch Receivable account from Customer / Company. The currency of receivable account must be same as Customer's accounting currency.
+
+Now, in POS, Paid Amount will be enetered in transaction currency, instead of earlier Company Currency. Write Off Amount will also be entered in transaction currency.
+
+Outstanding Amount and Advance Amount will always be calculated and shown in Customer's Account Currency.
+
+<img class="screenshot" alt="Sales Invoice Outstanding"  	src="assets/img/accounts/multi-currency/sales-invoice.png">
+
+### Purchase Invoice
+
+Similarly, in Purchase Invoice, accounting entries will be made based on Supplier's accounting currency. Outstanding Amount and Advance Amount will also be shown in the supplier's accounting currency. Write Off Amount will now be entered in transaction currency.
+
+### Journal Entry
+
+In Journal Entry, you can make transactions in different currencies. There is a checkbox "Multi Currency", to enable multi-currency entries. If "Multi Currency" option selected, you will be able to select accounts with different currencies.
+
+<img class="screenshot" alt="Journal Entry Exchange Rate"  	src="assets/img/accounts/multi-currency/journal-entry-multi-currency.png">
+
+ 
+In Accounts table, on selection of foreign currency account, system will show Currency section and fetch Account Currency and Exchange Rate automatically. You can change / modify the Exchange Rate later manually.
+
+In a single Journal Entry, you can select accounts with only one alternate currency, apart from accounts in Company Currency. Debit / Credit amount should be entered in Account Currency, system will calculate and show the Debit / Credit amount in Company Currency automatically.
+
+<img class="screenshot" alt="Journal Entry in multi currency"  	src="assets/img/accounts/multi-currency/journal-entry-row.png">
+
+#### Example 1: Payment Entry  Against Customer With Alternate Currency
+
+Suppose, default currency of the company is INR and customer's accounting currency is USD. Customer made full payment against an outstanding invoice of USD 100. Exchange Rate (USD -> INR) in Sales Invoice was 60.
+
+Exchange Rate in the payment entry should always be same as invoice (60), even if exchange rate on the payment date is 62. The bank account will be credited by the amount considering exchange rate as 62. Hence, Exchnage Gain / Loss will be booked based on exchange rate difference.
+
+<img class="screenshot" alt="Payment Entry"  	src="assets/img/accounts/multi-currency/payment-entry.png">
+
+#### Example 2: Inter-bank Transfer (USD -> INR)
+
+Suppose, default currency of the company is INR. You have an Paypal account for which Currency is USD. You receive payments in the paypal account and lets say, paypal transfers amount once in a week to your other bank account which is managed in INR. 
+
+Paypal account gets debited on different date with different exchange rate, but on transfer date the exchange rate can be different. Hence, there is generally Exchange Loss / Gain on the transfer entry.
+In the bank transfer entry, system sets exchange rate based on the average incoming exchange rate Paypal account. You need to calculate and enter Exchange Loss / Gain based on the average exchange rate and the exchange rate on the transfer date.
+
+Lets say, Paypal account debited by following amounts over the week, which has not been transferred to your other bank account.
+
+<table class="table table-bordered">
+	<thead>
+		<tr>
+			<td>Date</td>
+			<td>Account</td>
+			<td>Debit (USD)</td>
+			<td>Exchange Rate</td>
+		</tr>
+	</thead>
+	<tbody>
+		<tr>
+			<td>2015-09-02</td>
+			<td>Paypal</td>
+			<td>100</td>
+			<td>60</td>
+		</tr>
+		<tr>
+			<td>2015-09-02</td>
+			<td>Paypal</td>
+			<td>100</td>
+			<td>61</td>
+		</tr>
+		<tr>
+			<td>2015-09-02</td>
+			<td>Paypal</td>
+			<td>100</td>
+			<td>64</td>
+		</tr>
+	</tbody>
+</table>
+
+
+Suppose, Exchange Rate on the payment date is 62 and Bank Transfer Entry will be look like below:
+
+<img class="screenshot" alt="Inter Bank Transfer"  	src="assets/img/accounts/multi-currency/bank-transfer.png">
+
+
+## Reports
+
+### General Ledger
+
+In General Ledger, system shows debit / credit amount in both currency if filtered by an Account and Account Currency is different from Company Currency.
+
+<img class="screenshot" alt="General Ledger Report"  	src="assets/img/accounts/multi-currency/general-ledger.png">
+
+### Accounts Receivable / Payable
+
+In Accounts Receivable / Payable report, system shows all the amounts in Party / Account Currency.
+
+<img class="screenshot" alt="Accounts Receivable Report"  	src="assets/img/accounts/multi-currency/accounts-receivable.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/accounts/opening-accounts.md b/erpnext/docs/user/guides/accounts/opening-accounts.md
new file mode 100644
index 0000000..42b7e1d
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/opening-accounts.md
@@ -0,0 +1,94 @@
+Now that you have completed most of the setup, its time to start moving in!
+
+There are two important sets of data you need to enter before you start your
+operations.
+
+  * Opening Account balances.
+  * Opening Stock balances.
+
+To setup your accounts and stock correctly you will need accurate data to work
+with. Make sure you have the data setup for this.
+
+### Opening Accounts
+
+We usually recommend that you start using accounting in a new financial year,
+but you could start midway too. To setup your accounts, you will need the
+following for the “day” you start using accounting in ERPNext:
+
+Opening capital accounts - like your shareholder’s (or owner’) capital, loans,
+bank balances on that day. List of outstanding sales and purchase invoices
+(Payables and Receivables).
+
+Based on Voucher Type
+
+You can select accounts based on the voucher type. In such a scenario, your balance sheet should be balanced.
+
+<img class="screenshot" alt="Opening Account" src="assets/img/accounts/opening-account-1.png">
+
+ Also, note that if there are more than 300 ledgers, the system will crash. Thus to avoid such a situation, you can open accounts by using temporary accounts.
+
+#### Temporary Accounts
+
+A nice way to simplify opening is to use a temporary account
+just for opening. These accounts will become zero once all your old
+invoices and opening balances of bank, debt stock etc are entered.
+In the standard chart of accounts, a **Temperory Opening** account is created under
+assets
+
+#### The Opening Entry
+
+In ERPNext Opening Accounts are setup by submitting a special Journal Entries
+(Journal Entry).
+
+Note: Make sure to set “Is Opening” as “Yes” in the More Info section.
+
+> Setup > Opening Accounts and Stock > Opening Accounting Entries.
+
+Complete Journal Entries on the Debit and Credit side.
+
+![Opening Entry](assets/old_images/erpnext/opening-entry-1.png)
+
+ To update opening balance is to make Journal Entry for an individual/group of accounts.
+
+For example, if you want to update balance in three bank accounts, then make Journal Entrys in this manner.
+
+![Opening Temp Entry](assets/old_images/erpnext/image-temp-opening.png)
+
+
+![Opening Entry](assets/old_images/erpnext/opening-entry-2.png)
+
+Temporary Asset and Liability account is used for balancing purpose. When you update opening balance in Liability Account, you can use Temporary Asset Account for balancing.
+
+This way, you can update opening balance in Asset and Liability accounts.
+
+You can make two Opening Journal Entrys:
+
+  * For all assets (excluding Accounts Receivables): This entry will contain all your assets except the amounts you are expecting from your Customers against outstanding Sales Invoices. You will have to update your receivables by making an individual entry for each Invoice (this is because, the system will help you track the invoices which are yet to be paid). You can credit the sum of all these debits against the **Temperory Opening** account.
+  * For all liabilities: Similarly you need to pass a Journal Entry for your Opening Liabilities (except for the bills you have to pay) against **Temperory Opening** account.
+  * In this method you can update opening balance of specific balancesheet accounts and not for all.
+  * Opening entry is only for balance sheet accounts and not for expense or Income accounts.
+
+After completing the accounting entries, the trial balance report will look
+like the one given below:
+
+
+![Trial Balance](assets/old_images/erpnext/trial-balance-1.png)
+
+#### Outstanding Invoices
+
+After your Opening Journal Entrys are made, you will need to enter each
+Sales Invoice and Purchase Invoice that is yet to be paid.
+
+Since you have already booked the income or expense on these invoices in the
+previous period, select the temp opening account **Temporary Opening** in the “Income” and
+“Expense” accounts.
+
+> Note: Make sure to set each invoice as “Is Opening”!
+
+If you don’t care what items are in that invoice, just make a dummy item entry
+in the Invoice. Item code in the Invoice is not necessary, so it should not be
+such a problem.
+
+Once all your invoices are entered, your **Temperory Opening** account will have a balance of zero!
+
+{next}
diff --git a/erpnext/docs/user/accounts/opening-entry.md b/erpnext/docs/user/guides/accounts/opening-entry.md
similarity index 100%
rename from erpnext/docs/user/accounts/opening-entry.md
rename to erpnext/docs/user/guides/accounts/opening-entry.md
diff --git a/erpnext/docs/user/guides/accounts/point-of-sale-pos-invoice.md b/erpnext/docs/user/guides/accounts/point-of-sale-pos-invoice.md
new file mode 100644
index 0000000..9599b92
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/point-of-sale-pos-invoice.md
@@ -0,0 +1,98 @@
+# Point of Sale Invoice
+
+Point of Sale (POS) is the place where a retail transaction is completed. It
+is the point at which a customer makes a payment to the merchant in exchange
+for goods or services. For retail operations, the delivery of goods, accrual
+of sale and payment all happens in one event, that is usually called the
+“Point of Sale”.
+
+You can make a Sales Invoice of type POS by checking on “Is POS”. When you
+check this, you will notice that some fields get hidden and some new ones
+emerge.
+
+> Tip: In retail, you may not create a separate Customer record for each
+customer. You can create a general Customer called “Walk-in Customer” and make
+all your transactions against this Customer record.
+
+#### Setting Up POS
+
+In ERPNext all Sales and Purchase transactions, like Sales Invoice, Quotation, Sales Order, Purchase Order etc. can be edited via the POS. There two steps to Setup POS:
+
+1. Enable POS View via (Setup > Customize > Feature Setup)
+2. Create a [POS Setting](/contents/setting-up/pos-setting) record
+
+#### Switch to POS View
+
+Open any sales / purchase transaction. Click on the Computer <i class="icon-desktop"></i> Icon.
+
+#### Different sections of the POS
+
+  * Update Stock: If this is checked, Stock Ledger Entries will be made when you “Submit” this Sales Invoice thereby eliminating the need for a separate Delivery Note.
+  * In your Items table, update inventory information like Warehouse (saved as default), Serial Number, or Batch Number if applicable.
+  * Update Payment Details like your Bank / Cash Account, Paid amount etc.
+  * If you are writing off certain amount. For example when you receive extra cash as a result of not having exact denomination of change, check on ‘Write off Outstanding Amount’ and set the Account.
+
+### Adding an Item
+
+At the billing counter, the retailer needs to select Items which the consumer
+buys. In the POS interface you can select an Item by two methods. One, is by
+clicking on the Item image and the other, is through the Barcode / Serial No.
+
+**Select Item** \- To select a product click on the Item image and add it into the cart. A cart is an area that prepares a customer for checkout by allowing to edit product information, adjust taxes and add discounts.
+
+**Barcode / Serial No** \- A Barcode / Serial No is an optical machine-readable representation of data relating to the object to which it is attached. Enter Barcode / Serial No in the box as shown in the image below and pause for a second, the item will be automatically added to the cart.
+
+![POS](assets/old_images/erpnext/pos-add-item.png)
+
+> Tip: To change the quantity of an Item, enter your desired quantity in the
+quantity box. These are mostly used if the same Item is purchased in bulk.
+
+If your product list is very long use the Search field, type the product name
+in Search box.
+
+### Removing an Item
+
+There are two ways to remove an Item.
+
+  * Select an Item by clicking on the row of that Item from Item cart. Then click on “Del” button. OR
+
+  * Enter 0(zero) quantity of any item to delete that item.
+
+To remove multiple Items together, select multiple rows & click on “Del”
+button.
+
+> Delete button appears only when Items are selected.
+
+![POS](assets/old_images/erpnext/pos-remove-item.png)
+
+### Make Payment
+
+After all the Items and their quantities are added into the cart, you are
+ready to make the Payment. Payment process is divided into 3 steps -
+
+  1. Click on “Make Payment” to get the Payment window.
+  2. Select your “Mode of Payment”.
+  3. Click on “Pay” button to Save the document.
+
+![POS Payment](assets/old_images/erpnext/pos-make-payment.png)
+
+Submit the document to finalise the record. After the document is submitted,
+you can either print or email it directly to the customer.
+
+#### Accounting entries (GL Entry) for a Point of Sale:
+
+Debits:
+
+  * Customer (grand total) 
+  * Bank / Cash (payment)
+
+Credits:
+
+  * Income (net total, minus taxes for each Item) 
+  * Taxes (liabilities to be paid to the government)
+  * Customer (payment)
+  * Write Off (optional)
+
+To see entries after “Submit”, click on “View Ledger”.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/purchase-invoice.md b/erpnext/docs/user/guides/accounts/purchase-invoice.md
new file mode 100644
index 0000000..be01e2e
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/purchase-invoice.md
@@ -0,0 +1,71 @@
+Purchase Invoice is the exact opposite of your Sales Invoice. It is the bill
+that your Supplier sends you for products or services delivered. Here you
+accrue expenses to your Supplier. Making a Purchase Invoice is very similar to
+making a Purchase Order.
+
+To make a new Purchase Invoice, go to:
+
+> Accounts > Documents > Purchase Invoice > New Purchase Invoice
+
+or click on “Make Purchase Invoice” in Purchase Order or Purchase Receipt.
+
+<img class="screenshot" alt="Purchase Invoice" src="assets/img/accounts/purchase-invoice.png">
+
+The concept of “Posting Date” is again same as Sales Invoice. “Bill No” and
+“Bill Date” helps to track the bill number as set by your Supplier for
+reference.
+
+#### Accounting Impact
+
+Like in Sales Invoice, you have to enter an Expense or an Asset account for
+each row in your Items table. This helps to indicate if the Item is an Asset
+or an Expense. You must also enter a Cost Center. These can also be set in the
+Item master.
+
+The Purchase Invoice will affect your accounts as follows:
+
+Accounting entries (GL Entry) for a typical double entry “purchase”:
+
+Debits:
+
+  * Expense or Asset (net totals, excluding taxes)
+  * Taxes (/assets if VAT-type or expense again).
+
+Credits:
+
+  * Supplier
+
+To see entries in your Purchase Invoice after you “Submit”, click on “View
+Ledger”.
+
+* * *
+
+#### Is purchase an “Expense” or an “Asset”?
+
+If the Item is consumed immediately on purchase, or if it is a service, then
+the purchase becomes an “Expense”. For example, a telephone bill or travel
+bill is an “Expense” - it is already consumed.
+
+For inventory Items, that have a value, these purchases are not yet “Expense”,
+because they still have a value while they remain in your stock. They are
+“Assets”. If they are raw-materials (used in a process), they will become
+“Expense” the moment they are consumed in the process. If they are to be sold
+to a Customer, they become “Expense” when you ship them to the Customer.
+
+* * *
+
+#### Deducting Taxes at Source
+
+In many countries, the law may require you to deduct taxes, while paying your
+suppliers. These taxes could be based on a standard rate. Under these type of
+schemes, typically if a Supplier crosses a certain threshold of payment, and
+if the type of product is taxable, you may have to deduct some tax (which you
+pay back to your government, on your Supplier’s behalf).
+
+To do this, you will have to make a new Tax Account under “Tax Liabilities” or
+similar and credit this Account by the percent you are bound to deduct for
+every transaction.
+
+For more help, please contact your Accountant!
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/sales-invoice.md b/erpnext/docs/user/guides/accounts/sales-invoice.md
new file mode 100644
index 0000000..7ff5ac2
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/sales-invoice.md
@@ -0,0 +1,74 @@
+A Sales Invoice is a bill that you send to your customers, against which the customer processes the payment. Sales Invoice is an accounting transaction. On submission of Sales Invoice,  the system updates the receivable and books income against a Customer Account.
+
+You can create a Sales Invoice directly from
+
+> Accounting > Documents > Sales Invoice > New Sales Invoice
+
+or Click on Make Invoice at the right hand corner of the Delivery Note.
+
+<img class="screenshot" alt="Sales Invoice" src="assets/img/accounts/sales-invoice.png">
+
+#### Accounting Impact
+
+All Sales must be booked against an “Income Account”. This refers to an
+Account in the “Income” section of your Chart of Accounts. It is a good
+practice to classify your income by type (like product income, service income
+etc). The Income Account must be set for each row of the Items table.
+
+> Tip: To set default Income Accounts for Items, you can set it in the Item or
+Item Group.
+
+The other account that is affected is the Account of the Customer. That is
+automatically set from “Debit To” in the heading section.
+
+You must also mention the Cost Centers in which your Income must be booked.
+Remember that your Cost Centers tell you the profitability of the different
+lines of business or product. You can also set a default Cost Center in the
+Item master.
+
+#### Accounting entries (GL Entry) for a typical double entry “Sale”:
+
+When booking a sale (accrual):
+
+**Debit:** Customer (grand total) **Credit:** Income (net total, minus taxes for each Item) **Credit:** Taxes (liabilities to be paid to the government)
+
+> To see entries in your Sales Invoice after you “Submit”, click on “View
+Ledger”.
+
+#### Dates
+
+Posting Date: The date on which the Sales Invoice will affect your books of
+accounts i.e. your General Ledger. This will affect all your balances in that
+accounting period.
+
+Due Date: The date on which the payment is due (if you have sold on credit).
+This can be automatically set from the Customer master.
+
+#### Recurring Invoices
+
+If you have a contract with a Customer where you bill the Customer on a
+monthly, quarterly, half-yearly or annual basis, you can check the “Recurring
+Invoice” box. Here you can fill in the details of how frequently you want to
+bill this Invoice and the period for which the contract is valid.
+
+ERPNext will automatically create new Invoices and mail it to the email ids
+you set.
+
+* * *
+
+#### "Pro Forma" Invoice
+
+If you want to give an Invoice to a Customer to make a payment before you
+deliver, i.e. you operate on a payment first basis, you should create a
+Quotation and title it as a “Pro-forma Invoice” (or something similar) using
+the Print Heading feature.
+
+“Pro Forma” means for formality. Why do this? Because if you book a Sales
+Invoice it will show up in your “Accounts Receivable” and “Income”. This is
+not ideal as your Customer may or may not decide to pay up. But since your
+Customer wants an “Invoice”, you could give the Customer a Quotation (in
+ERPNext) titled as “Pro Forma Invoice”. This way everyone is happy.
+
+This is a fairly common practice. We follow this at Frappe too.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/setup/accounts-settings.md b/erpnext/docs/user/guides/accounts/setup/accounts-settings.md
new file mode 100644
index 0000000..d7183d8
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/setup/accounts-settings.md
@@ -0,0 +1,10 @@
+
+<img class="screenshot" alt="Account Settings" src="assets/img/accounts/account-settings.png">
+
+* Accounts Frozen Upto: Freeze accounting transactions upto specified date, nobody can make / modify entry except specified role.
+
+* Role Allowed to Set Frozen Accounts & Edit Frozen Entries: Users with this role are allowed to set frozen accounts and create / modify accounting entries against frozen accounts.
+
+* Credit Controller: Role that is allowed to submit transactions that exceed credit limits set.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/accounts/setup/cost-center.md b/erpnext/docs/user/guides/accounts/setup/cost-center.md
new file mode 100644
index 0000000..3a81a5f
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/setup/cost-center.md
@@ -0,0 +1,78 @@
+Your Chart of Accounts is mainly designed to provide reports to the government
+and tax authorities. Most businesses have multiple activities like different
+product lines, market segments, areas of business, etc that share some common
+overheads. They should ideally have their own structure to report, whether they
+are profitable or not. For this purpose, there is an alternate structure,
+called the Chart of Cost Centers.
+
+### Cost Center
+
+You can create a tree of Cost Centers to represent your business better. Each
+Income / Expense entry is also tagged against a Cost Center.
+
+For example, if you have two types of sales:
+
+  * Walk-in Sales
+  * Online Sales
+
+You may not have shipping expenses for your walk-in customers, and no shop-
+rent for your online customers. If you want to get the profitability of each
+of these separately, you should create the two as Cost Centers and mark all
+sales as either "Walk-in" or "Online". Mark your all your purchases in the
+same way.
+
+Thus when you do your analysis you get a better understanding as to which side
+of your business is doing better. Since ERPNext has an option to add multiple
+Companies, you can create Cost Centers for each Company and manage it
+separately.
+
+Chart of Cost Centers
+
+To setup your Chart of Cost Centers go to:
+
+> Accounts > Setup > Chart of Cost Centers
+
+![Chart of Cost Center](assets/old_images/erpnext/chart-of-cost-centers.png)
+
+Cost centers help you in one more activity, budgeting.
+
+### Budgeting
+
+ERPNext will help you set and manage budgets on your Cost Centers. This is
+useful when, for example, you are doing online sales. You have a budget for
+search ads, and you want ERPNext to stop or warn you from over spending, based
+on that budget.
+
+Budgets are also great for planning purposes. When you are making plans for
+the next financial year, you would typically target a revenue based on which
+you would set your expenses. Setting a budget will ensure that your expenses
+do not get out of hand, at any point, as per your plans.
+
+You can define it in the Cost Center. If you have seasonal sales you can also
+define a budget distribution that the budget will follow.
+
+> Accounts > Setup > Budget Distribution > New Budget Distribution
+
+![Budget Distribution](assets/old_images/erpnext/budgeting.png)
+
+#### Budget Actions
+
+ERPNext allows you to either:
+
+  * Stop.
+  * Warn or, 
+  * Ignore 
+
+if you exceed budgets.
+
+These can be defined from the Company record.
+
+Even if you choose to “ignore” budget overruns, you will get a wealth of
+information from the “Budget vs Actual” variance report.
+
+> Note: When you set a budget, it has to be set as per Account under the Cost
+Center. For example if you have a Cost Center “Online Sales”, you can restrict
+“Advertising Budget” by creating a row with that Account and defining the
+amount.
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/setup/fiscal-year.md b/erpnext/docs/user/guides/accounts/setup/fiscal-year.md
new file mode 100644
index 0000000..22824d3
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/setup/fiscal-year.md
@@ -0,0 +1,23 @@
+A fiscal year is also known as a financial year or a budget year. It is used
+for calculating financial statements in businesses and other organisations.
+The fiscal year may or may not be the same as a calendar year. For tax
+purposes, companies can choose to be calendar-year taxpayers or fiscal-year
+taxpayers. In many jurisdictions, regulatory laws regarding accounting and
+taxation require such reports once per twelve months. However, it is not
+mandatory that the period should be a calendar year (that is, 1 January to 31
+December).
+
+A fiscal year usually starts at the beginning of a quarter, such as April 1,
+July 1 or October 1. However, most companies' fiscal year also coincides with
+the calendar year, which starts January 1. For the most part, it is simpler
+and easier that way. For some organizations, there are advantages in starting
+the fiscal year at a different time. For example, businesses that are seasonal
+might start their fiscal year on July 1 or October 1. A business that has most
+of its income in the fall and most of its expenses in the spring might also
+choose to start its fiscal year on October 1. That way, they know what their
+income will be for that year, and can adjust their expenses to maintain their
+desired profit margins.
+
+<img class="screenshot" alt="Fiscal Year" src="assets/img/accounts/fiscal-year.png">
+
+{next}
diff --git a/erpnext/docs/user/accounts/setup/index.md b/erpnext/docs/user/guides/accounts/setup/index.md
similarity index 100%
rename from erpnext/docs/user/accounts/setup/index.md
rename to erpnext/docs/user/guides/accounts/setup/index.md
diff --git a/erpnext/docs/user/accounts/setup/index.txt b/erpnext/docs/user/guides/accounts/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/accounts/setup/index.txt
rename to erpnext/docs/user/guides/accounts/setup/index.txt
diff --git a/erpnext/docs/user/guides/accounts/setup/tax-rule.md b/erpnext/docs/user/guides/accounts/setup/tax-rule.md
new file mode 100644
index 0000000..7d81bfc
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/setup/tax-rule.md
@@ -0,0 +1,21 @@
+You can define which [Tax Template](/contents/setting-up/setting-up-taxes) must be applied on a Sales / Purchase transaction using Tax Rule.
+
+<img class="screenshot" alt="Tax Rule" src="assets/img/accounts/tax-rule.png">
+
+You can define Tax Rules for Sales or Purchase Taxes. 
+While making a Transaction the system will select and apply tax template based on the tax rule defined.
+The system selects Tax Rule with maximum matching Filters.
+
+Let us consider a senario to understand Tax Rule Better.
+
+Suppose we define 2 Tax Rules as below.
+
+<img class="screenshot" alt="Tax Rule" src="assets/img/accounts/tax-rule-1.png">
+
+<img class="screenshot" alt="Tax Rule" src="assets/img/accounts/tax-rule-2.png">
+
+Here Tax Rule 1 has Billing Country as India and Tax Rule 2 has Billing Country as United Kingdom
+
+Now supposed we try to create a Sales Order for a customer whose default Billing Country is India, system shall select Tax Rule 1.
+In case the customers Billing Country was United Kingdom, the system would have selected Tax Rule 2.
+
diff --git a/erpnext/docs/user/guides/accounts/tools/bank-reconciliation.md b/erpnext/docs/user/guides/accounts/tools/bank-reconciliation.md
new file mode 100644
index 0000000..b9ab255
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/tools/bank-reconciliation.md
@@ -0,0 +1,52 @@
+### Bank Reconciliation Statement
+
+A Bank Reconciliation is a process that explains the difference between the
+bank balance shown in an organisation's bank statement, as supplied by the
+bank, and the corresponding amount shown in the organisation's own accounting
+records at a particular point in time.  
+
+Such differences may occur, for example, because a cheque or a list of cheques
+issued by the organisation has not been presented to the bank, a banking
+transaction, such as a credit received, or a charge made by the bank, has not
+yet been recorded in the organisations books, or either the bank or the
+organisation itself has made an error.
+
+The Bank Reconciliation statement in ERPNext comes in the form of a report.
+
+#### Figure 1: Bank Reconciliation Statement
+
+![](assets/old_images/erpnext/bank-reconciliation-2.png)  
+
+  
+
+When you get the report, check whether the field 'Balance as per bank' matches
+the Bank Account Statement. If there is a match then all the clearance dates
+are updated. If there is a mismatch then check clearance dates and journal
+entries.
+
+To add clearance entries go to Accounts > Tools > Bank Reconciliation
+
+### Bank Reconciliation Tool
+
+The Bank Reconciliation tool in ERPNext, helps add clearance dates to the
+account statements. To Reconcile cheque payments go to Accounts and click on
+Bank Reconciliation.  
+
+__Step 1:__ Select the Bank Account against which you intend to reconcile. For
+example; HDFC Bank, ICICI Bank, or Citibank etc.
+
+__Step 2:__ Select the Date range that you wish to reconcile for.
+
+__Step 3:__ Click on 'Get Reconciled Entries'
+
+All the entries in the specified date range will be shown in a table below.
+
+__Step 4:__ Click on the JV from the table and update clearance date.
+
+#### Figure 2: Bank Reconciliation Tool
+
+<img class="screenshot" alt="Bank Reconciliation" src="assets/img/accounts/bank-reconciliation.png">
+
+__Step 5:__ Click on the button 'Update Clearance Date'.
+ 
+{next}
diff --git a/erpnext/docs/user/accounts/tools/index.md b/erpnext/docs/user/guides/accounts/tools/index.md
similarity index 100%
rename from erpnext/docs/user/accounts/tools/index.md
rename to erpnext/docs/user/guides/accounts/tools/index.md
diff --git a/erpnext/docs/user/accounts/tools/index.txt b/erpnext/docs/user/guides/accounts/tools/index.txt
similarity index 100%
rename from erpnext/docs/user/accounts/tools/index.txt
rename to erpnext/docs/user/guides/accounts/tools/index.txt
diff --git a/erpnext/docs/user/guides/accounts/tools/payment-reconciliation.md b/erpnext/docs/user/guides/accounts/tools/payment-reconciliation.md
new file mode 100644
index 0000000..de968fc
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/tools/payment-reconciliation.md
@@ -0,0 +1,31 @@
+Reconciliation is an accounting process used to compare two sets of records to
+ensure the figures are in agreement and are accurate. It is the key process
+used to determine whether the money leaving an account matches the amount
+spent, ensuring the two values are balanced at the end of the recording
+period. In Payment Reconciliation, the invoices are matched against the
+payments made to the bank. Thus if you have many payments which are not
+reconciled with their respective invoices, you can use the payment
+reconciliation tool.
+
+To use Payment Reconciliation Tool go to,
+
+Accounts > Tools > Payment Reconciliation
+
+<img class="screenshot" alt="Payment Reconciliation" src="assets/img/accounts/payment-reconcile-tool.png">
+
+__Step 1:__ Select the Account against whom the payments need to be reconciled.
+
+__Step 2:__ Mention the Voucher Type, whether it is Purchase Invoice, Sales
+Invoice or Journal Entry.
+
+__Step 3:__ Select the Voucher Number and click on 'Get Unreconcilled Entries'.  
+
+* All the payment entries will be pulled into a table below.
+
+__Step 4:__ Click on the entry row to allocate a particular amount.
+
+__Step 5:__ Click on the button 'Reconcile'
+
+* You will get a message that says 'Amount allocated successfully'
+
+{next}
diff --git a/erpnext/docs/user/guides/accounts/tools/payment-tool.md b/erpnext/docs/user/guides/accounts/tools/payment-tool.md
new file mode 100644
index 0000000..0d3c12a
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/tools/payment-tool.md
@@ -0,0 +1,24 @@
+###Payment Tool
+The Payment Tool Feature allows non-accounting personnel to generate Journal Entrys by populating relevant fields in the Journal Entry with account and payment details.
+
+To go to Payment Tool, click on Accounts > Tools > Payment Tool.
+
+1. Select the Company Name.
+2. Select the Party Type (Customer or Supplier) and the name of the customer or supplier against whom the payment has been made or received.
+3. Use the Received Or Paid field to specify 'Received' if payment is being received or 'Paid' if User is making the payment.
+4. Select the Mode of Payment and the Payment Account .
+5. Enter the Reference Number and Reference Date of the payment, for instance, the Cheque no. and Cheque date in case the payment is being made by cheque.
+6. Click on Get Outstanding Vouchers to fetch all the valid Vouchers, Invoices and Orders against which a payment can be made/received. These will appear in the Against Voucher section.
+	* __Note:__ In case User is paying a customer or receiving payment from a supplier, add the details regarding the relevant invoices and orders manually.
+
+<img class="screenshot" alt="Payment Tool" src="assets/img/accounts/payment-tool-1.png">
+
+7. Once details have been fetched, click on the detail entry and enter the payment amount made against that Invoice/Order/Voucher
+
+<img class="screenshot" alt="Payment Tool" src="assets/img/accounts/payment-tool-2.png">
+
+8. Click on 'Make Journal Entry' to generate a new Journal Entry with the relevant Party Details and Credit/Debit details filled in.
+
+<img class="screenshot" alt="Payment Tool" src="assets/img/accounts/payment-tool-3.png">
+	
+{next}
diff --git a/erpnext/docs/user/guides/accounts/tools/period-closing-voucher.md b/erpnext/docs/user/guides/accounts/tools/period-closing-voucher.md
new file mode 100644
index 0000000..9a75ff4
--- /dev/null
+++ b/erpnext/docs/user/guides/accounts/tools/period-closing-voucher.md
@@ -0,0 +1,30 @@
+At the end of every year or (quarterly or maybe even monthly), after completing auditing, you can close your books of accounts. This means that you make all your special entries like:
+
+  * Depreciation
+  * Change in value of Assets
+  * Defer taxes and liabilities
+  * Update bad debts
+
+etc. and book your Profit or Loss.
+
+By doing this, your balance in your Income and Expense Accounts become zero. You start a new Fiscal Year (or period) with a balanced Balance Sheet and fresh Profit and Loss account.
+
+In ERPNext after making all the special entries via Journal Entry for the current fiscal year, you should set all your Income and Expense accounts to zero via:
+
+> Accounts > Tools > Period Closing Voucher
+
+**Posting Date** will be when this entry should be executed. If your Fiscal Year ends on 31st December, then that date should be selected as Posting Date in the Period Closing Voucher.
+
+**Transaction Date** will be Period Closing Voucher's creation date.
+
+**Closing Fiscal Year** will be an year for which you are closing your financial statement.
+
+<img class="screenshot" alt="Period Closing Voucher" src="assets/img/accounts/period-closing-voucher.png">
+
+This voucher will transfer Profit or Loss (availed from P&L statment) to Closing Account Head. You should select a libility account like Reserves and Surplus, or Capital Fund account as Closing Account.
+
+The Period Closing Voucher will make accounting entries (GL Entry) making all your Income and Expense Accounts zero and transferring Profit/Loss balance to the Closing Account.
+
+<div class=well>If accounting entries are made in a closing fiscal year, even after Period Closing Voucher was created for that Fiscal Year, you should create another Period Closing Voucher. Later voucher will only transfer the pending P&L balance into Closing Account Head.</div>
+
+{next}
diff --git a/erpnext/docs/user/buying/index.md b/erpnext/docs/user/guides/buying/index.md
similarity index 100%
rename from erpnext/docs/user/buying/index.md
rename to erpnext/docs/user/guides/buying/index.md
diff --git a/erpnext/docs/user/buying/index.txt b/erpnext/docs/user/guides/buying/index.txt
similarity index 100%
rename from erpnext/docs/user/buying/index.txt
rename to erpnext/docs/user/guides/buying/index.txt
diff --git a/erpnext/docs/user/guides/buying/purchase-order.md b/erpnext/docs/user/guides/buying/purchase-order.md
new file mode 100644
index 0000000..4577535
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/purchase-order.md
@@ -0,0 +1,86 @@
+A Purchase Order is analogous to a Sales Order. It is usually a binding
+contract with your Supplier that you promise to buy a set of Items under the
+given conditions.
+
+A Purchase Order can be automatically created from a Material Request or
+Supplier Quotation.
+
+#### Purchase Order Flow Chart
+
+![Purchase Order](assets/old_images/erpnext/purchase-order-f.jpg)
+
+In ERPNext, you can also make a Purchase Order directly by going to:
+
+> Buying > Documents > Purchase Order > New Purchase Order
+
+#### Create Purchase Order
+
+<img class="screenshot" alt="Purchase Order" src="assets/img/buying/purchase-order.png">
+
+Entering a Purchase Order is very similar to a Purchase Request, additionally
+you will have to set:
+
+  * Supplier.
+  * A “Required By” date on each Item: If you are expecting part delivery, your Supplier will know how much quantity to deliver at which date. This will help you from preventing over-supply. It will also help you to track how well your Supplier is doing on timeliness.
+
+### Taxes
+
+If your Supplier is going to charge you additional taxes or charge like a
+shipping or insurance charge, you can add it here. It will help you to
+accurately track your costs. Also, if some of these charges add to the value
+of the product you will have to mention them in the Taxes table. You can also
+use templates for your taxes. For more information on setting up your taxes
+see the Purchase Taxes and Charges Template.
+
+### Value Added Taxes (VAT)
+
+Many a times, the tax paid by you to a Supplier, for an Item, is the same tax
+which you collect from your Customer. In many regions, what you pay to your
+government is only the difference between what you collect from your Customer
+and what you pay to your Supplier. This is called Value Added Tax (VAT).
+
+For example you buy Items worth X and sell them for 1.3X. So your Customer
+pays 1.3 times the tax you pay your Supplier. Since you have already paid tax
+to your Supplier for X, what you owe your government is only the tax on 0.3X.
+
+This is very easy to track in ERPNext since each tax head is also an Account.
+Ideally you must create two Accounts for each type of VAT you pay and collect,
+“Purchase VAT-X” (asset) and “Sales VAT-X” (liability), or something to that
+effect. Please contact your accountant if you need more help or post a query
+on our forums!
+
+  
+
+#### Purchase UOM and Stock UOM Conversion
+
+You can change your UOM as per your stock requirements in the Purchase Order
+form.
+
+For example, If you have bought your raw material in large quantities with UOM
+-boxes, and wish to stock them in UOM- Nos; you can do so while making your
+Purchase Order.
+
+__Step 1:__ Store UOM as Nos in the Item form.
+
+Note: The UOM in the Item form is the stock UOM.
+
+__Step 2:__ In the Purchase Order mention UOM as Box. (Since material arrives in
+Boxes)
+
+__Step 3:__ In the Warehouse and Reference section, the UOM will be pulled in as
+Nos (from the Item form)
+
+#### Figure 3: Conversion of Purchase UOM to stock UOM
+
+
+<img class="screenshot" alt="Purchase Order - UOM" src="assets/img/buying/purchase-order-uom.png">
+
+__Step 4:__ Mention the UOM conversion factor. For example, (100);If one box has
+100 pieces.  
+
+__Step 5:__  Notice that the stock quantity will be updated accordingly.
+
+__Step 6:__ Save and Submit the Form.
+
+  
+{next}
diff --git a/erpnext/docs/user/guides/buying/purchase-taxes.md b/erpnext/docs/user/guides/buying/purchase-taxes.md
new file mode 100644
index 0000000..9ffacbe
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/purchase-taxes.md
@@ -0,0 +1,38 @@
+For Tax Accounts that you want to use in the tax templates, you must mention
+them as type “Tax” in your Chart of Accounts.
+
+Similar to your Sales Taxes and Charges Template is the Purchase Taxes and
+Charges Master. This is the tax template that you can use in your Purchase
+Orders and Purchase Invoices.
+
+> Buying > Setup > Purchase Taxes and Charges Template > New Purchase Taxes and Charges
+Master
+
+![Purchase-Taxes](assets/old_images/erpnext/purchase-taxes.png)
+
+  
+
+You can specify if the tax / charge is only for valuation (not a part of
+total) or only for total (does not add value to the item) or for both.
+
+If you select a particular tax as your Default tax, the system will apply this
+tax to all the purchase transactions by default. 
+
+### Calculation Type
+
+This can be on Net Total (that is the sum of basic amount). On Previous Row
+Total / Amount (for cumulative taxes or charges). If you select this option,
+the tax will be applied as a percentage of the previous row (in the tax table)
+amount or total. Actual (as mentioned).
+
+  * **Account Head:** The Account ledger under which this tax will be booked.
+  * **Cost Center:** If the tax / charge is an income (like shipping) or expense it needs to be booked against a Cost Center.
+  * **Description:** Description of the tax (that will be printed in invoices / quotes).
+  * **Rate:** Tax rate.
+  * **Amount:** Tax amount.
+  * **Total:** Cumulative total to this point.
+  * **Enter Row:** If based on "Previous Row Total" you can select the row number which will be taken as a base for this calculation (default is the previous row).
+  * **Consider Tax or Charge for:** In this section you can specify if the tax / charge is only for valuation (not a part of total) or only for total (does not add value to the item) or for both.
+  * **Add or Deduct:** Whether you want to add or deduct the tax.
+
+{next}
diff --git a/erpnext/docs/user/guides/buying/setup/buying-settings.md b/erpnext/docs/user/guides/buying/setup/buying-settings.md
new file mode 100644
index 0000000..9fc6973
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/setup/buying-settings.md
@@ -0,0 +1,39 @@
+Buying Settings is where you can define properties which will be applied in the Buying module's transactions. 
+
+![Buying Settings](assets/img/buying/buying-settings.png)
+
+Let us look at the various options that can be configured:
+
+### 1. Supplier Naming By
+
+When a Supplier is saved, system generates a unique identity or name for that Supplier which can be used to refer the Supplier in various Buying transactions.
+
+If not configured otherwise, ERPNext uses the Supplier's Name as the unique name. If you want to identify Suppliers using names like SUPP-00001, SUPP-00002, or such other patterned series, select the value of Supplier Naming By as "Naming Series".
+
+You can define or select the Naming Series pattern from:
+
+> Setup > Settings > Naming Series
+
+[Click here to know more about defining a Naming Series.](/contents/setting-up/settings/naming-series)
+
+### 2. Default Supplier Type
+
+Configure what should be the value of Supplier Type when a new Supplier is created.
+
+### 3. Default Buying Price List
+
+Configure what should be the value of Buying Price List when a new Buying transaction is created.
+
+### 4. Maintain Same Rate Throughout Purchase Cycle
+
+If this is checked, ERPNext will stop you if you change the Item's price in a Purchase Invoice or Purchase Receipt created based on a Purchase Order, i.e. it will maintain the same price throughout the purchase cycle. If there is a requirement where you need the Item's price to change, you should uncheck this option.
+
+### 5. Purchase Order Required
+
+If this option is configured "Yes", ERPNext will prevent you from creating a Purchase Invoice or a Purchase Receipt without first creating a Purchase Order.
+
+### 6. Purchase Receipt Required
+
+If this option is configured "Yes", ERPNext will prevent you from creating a Purchase Invoice without first creating a Purchase Receipt.
+
+{next}
diff --git a/erpnext/docs/user/buying/setup/index.md b/erpnext/docs/user/guides/buying/setup/index.md
similarity index 100%
rename from erpnext/docs/user/buying/setup/index.md
rename to erpnext/docs/user/guides/buying/setup/index.md
diff --git a/erpnext/docs/user/buying/setup/index.txt b/erpnext/docs/user/guides/buying/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/buying/setup/index.txt
rename to erpnext/docs/user/guides/buying/setup/index.txt
diff --git a/erpnext/docs/user/guides/buying/setup/supplier-type.md b/erpnext/docs/user/guides/buying/setup/supplier-type.md
new file mode 100644
index 0000000..1792008
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/setup/supplier-type.md
@@ -0,0 +1,28 @@
+A supplier may be distinguished from a contractor or subcontractor, who
+commonly adds specialized input to deliverables. A supplier is also known as a
+vendor. There are different types of suppliers based on their goods and
+products.
+
+ERPNext allows you to create your own categories of suppliers. These
+categories are known as Supplier Type. For Example, if your suppliers are
+mainly pharmaceutical companies and FMCG distributors, You can create a new
+Type for them and name them accordingly.
+
+Based on what the suppliers supply, they are classified into different
+categories called Supplier Type. There can be different types of suppliers.
+You can create your own category of Supplier Type.
+
+> Buying > Setup > Supplier Type > New Supplier Type
+
+<img class="screenshot" alt="Supplier Type" src="assets/img/buying/supplier-type.png">
+
+You can classify your suppliers from a range of choice available in ERPNext.
+Choose from a set of given options like Distributor, Electrical,Hardware,
+Local, Pharmaceutical, Raw material, Services etc.
+
+Classifying your supplier into different types facilitates accounting and
+payments.
+
+Type your new supplier category and Save.
+
+{next}
diff --git a/erpnext/docs/user/guides/buying/supplier-quotation.md b/erpnext/docs/user/guides/buying/supplier-quotation.md
new file mode 100644
index 0000000..88ceb7c
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/supplier-quotation.md
@@ -0,0 +1,33 @@
+A Supplier Quotation is a formal statement of promise by potential supplier to
+supply the goods or services required by a buyer, at specified prices, and
+within a specified period. A quotation may also contain terms of sale and
+payment, and warranties. Acceptance of quotation by the buyer constitutes an
+agreement binding on both parties.
+
+You can make a supplier quotation from a Material Request
+
+#### Supplier Quotation Flow-Chart
+
+![Supplier Quotation](assets/old_images/erpnext/supplier-quotation-f.jpg)
+
+You can also make a Supplier Quotation directly from:
+
+> Buying > Documents > Supplier Quotation > New Supplier Quotation
+
+#### Create Supplier Quotation
+
+<img class="screenshot" alt="Supplier Quotation" src="assets/img/buying/supplier-quotation.png">
+
+If you have multiple Suppliers who supply you with the same Item, you
+usually send out a message (Request for Quote) to various Suppliers. In
+many cases, especially if you have centralized buying, you may want to record
+all the quotes so that
+
+  * You can easily compare prices in the future 
+  * Audit whether all Suppliers were given the opportunity to quote.
+
+Supplier Quotations are not necessary for most small businesses. Always
+evaluate the cost of collecting information to the value it really provides!
+You could only do this for high value items.
+
+{next}
diff --git a/erpnext/docs/user/guides/buying/supplier.md b/erpnext/docs/user/guides/buying/supplier.md
new file mode 100644
index 0000000..22cee73
--- /dev/null
+++ b/erpnext/docs/user/guides/buying/supplier.md
@@ -0,0 +1,37 @@
+Suppliers are companies or individuals who provide you with products or
+services. They are treated in exactly the same manner as Customers in ERPNext.
+
+You can create a new Supplier via:
+
+> Buying > Documents > Supplier > New Supplier
+
+<img class="screenshot" alt="Supplier Master" src="assets/img/buying/supplier-master.png">
+
+### Contacts and Addresses
+
+Contacts and Addresses in ERPNext are stored separately so that you can attach
+multiple Contacts or Addresses to Customers and Suppliers. To add a Contact or
+Address go to Buying and click on “New Contact” or “New Address”.
+
+> Tip: When you select a Supplier in any transaction, one Contact and Address
+gets pre-selected. This is the “Default Contact or Address”. So make sure you
+set your defaults correctly!
+
+### Integration with Accounts
+
+In ERPNext, there is a separate Account record for each Supplier, of Each
+company.
+
+When you create a new Supplier, ERPNext will automatically create an Account
+Ledger for the Supplier under “Accounts Payable” in the Company set in the
+Supplier record.
+
+> Advanced Tip: If you want to change the Account Group under which the
+Supplier Account is created, you can set it in the Company master.
+
+If you want to create an Account in another Company, just change the Company
+value and “Save” the Supplier again.
+
+> Tip: You can also import from the Data Import Tool
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/assignment.md b/erpnext/docs/user/guides/collaboration-tools/assignment.md
new file mode 100644
index 0000000..959f300
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/assignment.md
@@ -0,0 +1,40 @@
+Assign To feature in ERPNext allows you to allocate particular document to specific user, whom needs to further work on that document.
+
+For example, if Sales Order needs to be approved/submitted by Sales Manager, first draft user can allocate that Sales Order to Sales Manager. On allocating document to Sales Manager, it will be added to that user's ToDo list. Same way, allocation can also be done to Material User and Account user who needs to create Delivery Note and Sales Invoice respectively against this Sales Note.
+
+<div class=well>Permissions restriction cannot be done based on Assigned To</div>
+
+Following are the steps to assign document to another user.
+
+#### Step 1: Click on the Assign To Button
+
+Assign to option is located at the footer of document. Clicking on Assignment Icon on the tool bar will fast-forward you to footer of same document.
+
+![Assigned To Icon](assets/old_images/erpnext/assigned-to-icon.png)
+
+
+![Assigned To](assets/old_images/erpnext/assigned-to.png)
+
+#### Step 2: Assign to User
+
+In the Assign To section, you will find option to select User to whom this document will be assigned to. You can assign one document to multiple people at a time.
+
+![Assign User](assets/old_images/erpnext/assign-user.png)
+
+With assignment, you can also leave a comment for the review of asignee.
+
+####ToDo List of Assignee
+
+This transaction will appear in the To-do list of the ser in “Todo” section.
+
+![Assign Todo](assets/old_images/erpnext/assign-todo.png)
+
+####Removing Assignment
+
+User will be able to remove assignment by clicking on "Assignment Completed" button in the document.
+
+![Assign Remove](assets/old_images/erpnext/assign-remove.png)
+
+Once assignment is set as completed, Status of its ToDo record will be set as Closed.
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/calendar.md b/erpnext/docs/user/guides/collaboration-tools/calendar.md
new file mode 100644
index 0000000..27be7cf
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/calendar.md
@@ -0,0 +1,63 @@
+The Calendar is a tool where you can create and share Events and also see
+auto-generated events from the system.
+
+You can switch calender view based on Month, Week and Day.
+
+###Creating Events in Calender
+
+####Creating Event Manually
+
+To create event manually, you should first determine Calender View. If Event's start and end time will be within one day, then you should first switch to Day view.
+
+This view will 24 hours of a day broken in various slots. You should click on slot for Event Start Time, and drag it down till you reach event end time.
+
+![Calender Event Manually](assets/old_images/erpnext/calender-event-manually.png)
+
+Based on the selection of time slot, Start Time and End Time will be updated in the Event master. Then you can set subject for an event, and save it.
+
+####Event Based on Lead
+
+In the Lead form, you will find a field called Next Contact By and Next Contact Date. Event will be auto created for date and person person specified in this field.
+
+![Calender Event Lead](assets/old_images/erpnext/calender-event-lead.png)
+
+####Birthday Event
+
+Birthday Event is created based on Date of Birth specified in the Employee master.
+
+###Recurring Events
+
+You can set events as recurring in specific interval by Checking the "Repeat This
+Event".
+
+![Calender Event Recurring](assets/old_images/erpnext/calender-event-recurring.png)
+
+###Permission for Event
+
+You can set Event as Private or Public. Private Events will be visible only to you, and if any other user selected in the participants table. Instead of User, you can also assign permission for event based on Role.
+
+Public Event, like Birthday will be visible to all.
+
+![Calender Event Permission](assets/old_images/erpnext/calender-event-permission.png)
+
+###Event Reminders
+
+There are two ways you can receive email reminder for an event.
+
+####Enable Reminder in Event
+
+In the Event master, checking "Send an email reminder in the morning" will trigger notifcation email to all the participants for this event.
+
+![Calender Event Notification](assets/old_images/erpnext/calender-event-notification.png)
+
+####Create Email Digest
+
+To get email reminders for event, you should set Email Digest for Calender Events.
+
+Email Digest can be set from:
+
+`Setup > Email > Email Digest`
+
+![Calender Email Digest](assets/old_images/erpnext/calender-email-digest.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/collaborating-around-forms.md b/erpnext/docs/user/guides/collaboration-tools/collaborating-around-forms.md
new file mode 100644
index 0000000..adfdf87
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/collaborating-around-forms.md
@@ -0,0 +1,19 @@
+### Assigned to
+
+You can email any transaction from the system by clicking on the “Assigned to”
+button in the right sidebar. A log of all your sent emails will be maintained
+in Communication.
+
+![Forms](assets/old_images/erpnext/forms.png)
+
+### Comments
+
+Comments are a great way to add information about a transaction that is not a
+part of the transactions. Like some background information etc. Comments can
+be added in the right sidebar.
+
+### Tags
+
+[Read more about Tags](/contents/collaboration-tools/tags)  
+
+{next}
diff --git a/erpnext/docs/user/collaboration-tools/index.md b/erpnext/docs/user/guides/collaboration-tools/index.md
similarity index 100%
rename from erpnext/docs/user/collaboration-tools/index.md
rename to erpnext/docs/user/guides/collaboration-tools/index.md
diff --git a/erpnext/docs/user/collaboration-tools/index.txt b/erpnext/docs/user/guides/collaboration-tools/index.txt
similarity index 100%
rename from erpnext/docs/user/collaboration-tools/index.txt
rename to erpnext/docs/user/guides/collaboration-tools/index.txt
diff --git a/erpnext/docs/user/guides/collaboration-tools/messages.md b/erpnext/docs/user/guides/collaboration-tools/messages.md
new file mode 100644
index 0000000..dd8a5a8
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/messages.md
@@ -0,0 +1,12 @@
+You can send and receive messages from the system by using the Messages tool.
+If you send a message to a user, and the user is logged in, it will appear as
+a popup message and the unread messages counter in the top toolbar will be
+updated.
+
+![Message List](assets/old_images/erpnext/message-list.png)
+
+You can choose to send message to all the users, or to specific user.
+
+![Messsage To](assets/old_images/erpnext/message-to.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/notes.md b/erpnext/docs/user/guides/collaboration-tools/notes.md
new file mode 100644
index 0000000..601abee
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/notes.md
@@ -0,0 +1,21 @@
+You can store your long notes under this section. It can contain your partner lists, frequently used passwords, terms and conditions, or any other document which needs to be shared. Following are the steps to create new Note.
+
+####Go to Note
+
+`Home > Note > New`
+
+####Notes Details
+
+Enter Title and Context.
+
+![Note](assets/old_images/erpnext/note.png)
+
+####Set Permissions to select Users
+
+To make Note accessible for all, check "Public" under links section. If specific Note is to be made accessible to specific user, they shall be selected in the Share With table.
+
+![Note Permission](assets/old_images/erpnext/note-permission.png)
+
+<div class=well>Notes can also be used as a knowledge base internally. You can also attach file in the Notes, and make it accessible to specific set of users only.</div>
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/tags.md b/erpnext/docs/user/guides/collaboration-tools/tags.md
new file mode 100644
index 0000000..596fac0
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/tags.md
@@ -0,0 +1,5 @@
+Like Assignments and Comments, you can also add your own tags to each type of transactions. These tags can help you search a document and also classify it. ERPNext will also show you all the important tags in the document list.
+
+![Tags](assets/old_images/erpnext/tags-in-list.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/collaboration-tools/to-do.md b/erpnext/docs/user/guides/collaboration-tools/to-do.md
new file mode 100644
index 0000000..b878b67
--- /dev/null
+++ b/erpnext/docs/user/guides/collaboration-tools/to-do.md
@@ -0,0 +1,10 @@
+To Do is a simple tool where all the activities [assigned](https://erpnext.com/collaboration-tools/assignment) to you and assigned
+by you are listed. You can also add your own to-do items in the list.
+
+![Todo List](assets/old_images/erpnext/todo-list.png)
+
+When task is completed, you should simply remove assignment from the assigned document. With this, task will be removed from your Todo list as well. For Todo which are not assigned via document, you can set their status as Closed from the Todo record itself.
+
+![Todo Close](assets/old_images/erpnext/todo-close.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/customer-portal/customer-orders-invoices-and-shipping-status.md b/erpnext/docs/user/guides/customer-portal/customer-orders-invoices-and-shipping-status.md
new file mode 100644
index 0000000..28cde25
--- /dev/null
+++ b/erpnext/docs/user/guides/customer-portal/customer-orders-invoices-and-shipping-status.md
@@ -0,0 +1,22 @@
+ERPNext Web Portal gives your customers quick access to their Orders, Invoices
+and Shipments Customers can check the status of their orders, invoices, and
+shipping status by logging on to the web.
+
+![Portal Menu](assets/old_images/erpnext/portal-menu.png)
+
+Once an order is raised, either using the Shopping Cart or from within
+ERPNext, your customer can view the order and keep an eye on the billing and
+shipment status. When the invoice and payment against these orders are
+submitted, the customer can see the updated status on the portal, at a glance.
+
+![Customer Portal](assets/old_images/erpnext/customer-portal-orders-1.png)
+
+#### Invoice with paid status.
+
+![Invoice Paid](assets/old_images/erpnext/portal-invoice-paid.png)
+
+#### Invoice with billed status.
+
+![Billed Invoice](assets/old_images/erpnext/portal-order-billed.png)
+
+{next}
diff --git a/erpnext/docs/user/customer-portal/index.md b/erpnext/docs/user/guides/customer-portal/index.md
similarity index 100%
rename from erpnext/docs/user/customer-portal/index.md
rename to erpnext/docs/user/guides/customer-portal/index.md
diff --git a/erpnext/docs/user/customer-portal/index.txt b/erpnext/docs/user/guides/customer-portal/index.txt
similarity index 100%
rename from erpnext/docs/user/customer-portal/index.txt
rename to erpnext/docs/user/guides/customer-portal/index.txt
diff --git a/erpnext/docs/user/guides/customer-portal/issues.md b/erpnext/docs/user/guides/customer-portal/issues.md
new file mode 100644
index 0000000..422b214
--- /dev/null
+++ b/erpnext/docs/user/guides/customer-portal/issues.md
@@ -0,0 +1,22 @@
+The customer portal makes it very easy for a customer to raise concerns. A
+simple and intuitive interface facilitates your customer to report their
+concerns as Issues. They can view the complete thread of their
+conversation.
+
+#### Empty Ticket List
+
+![Ticket List](assets/old_images/erpnext/portal-ticket-list-empty.png)
+
+#### New Issue
+
+![New Ticket](assets/old_images/erpnext/portal-new-ticket.png)
+
+#### Open Issue
+
+![Open Issue](assets/old_images/erpnext/portal-ticket-1.png)
+
+#### Reply on Issue
+
+![Reply Issue](assets/old_images/erpnext/portal-ticket-reply.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/customer-portal/portal-login.md b/erpnext/docs/user/guides/customer-portal/portal-login.md
new file mode 100644
index 0000000..1bd8775
--- /dev/null
+++ b/erpnext/docs/user/guides/customer-portal/portal-login.md
@@ -0,0 +1,6 @@
+To login into the customer account, the customer has to use his email id and
+the password sent by ERPNext; generated through the sign-up process.
+
+![Login](assets/old_images/erpnext/customer-portal-login.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/customer-portal/sign-up.md b/erpnext/docs/user/guides/customer-portal/sign-up.md
new file mode 100644
index 0000000..cabd58f
--- /dev/null
+++ b/erpnext/docs/user/guides/customer-portal/sign-up.md
@@ -0,0 +1,22 @@
+Customers have to log-in to the Company Website, and sign-up as a customer.
+
+#### Step 1: Click on Login Icon
+
+![Sign Up](assets/old_images/erpnext/customer-portal-sign-up-1.png)
+
+  
+
+#### Step 2: Click on Sign Up Icon
+
+![Sign Up](assets/old_images/erpnext/customer-portal-sign-up-2.png)
+
+  
+
+#### Step 3: Enter Customer Name and ID
+
+![Sign Up](assets/old_images/erpnext/customer-portal-sign-up-3.png)
+
+After the sign up process, a mail will be sent to the customers email id with
+the password details.
+
+{next}
diff --git a/erpnext/docs/user/guides/customize-erpnext/custom-doctype.md b/erpnext/docs/user/guides/customize-erpnext/custom-doctype.md
new file mode 100644
index 0000000..85d2049
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/custom-doctype.md
@@ -0,0 +1,74 @@
+DocType or Document Type is a tool to insert form in ERPNext. The forms like Sales Order,
+Sales Invoices, Production Order are added as Doctype in the backend. Let's assume we are
+creating a Custom Doctype for a Book.
+
+Custom Doctype allows you to insert custom forms in ERPNext as per your requirement.
+
+To create a new **DocType**, go to:
+
+`Setup > Customize > Doctype > New`
+
+#### Doctype Detail
+
+1. Module: Select module in which this Doctype should be placed.
+1. Document Type: Specify if this Doctype will be to carry master data, or to track transactions. Doctype
+for book will be added as Master.
+1. Is Child table: If this Doctype is to be inserted as table into another Doctype, like Item table
+in the Sales Order Doctype, then you should check Is Child Table. Else no.
+1. Is Single: If checked, this Doctype will become a single form, like Selling Setting, which user will
+not be able to re-produce.
+1. Custom?: This field will be checked by default when adding Custom Doctype.
+
+![Doctype Basic](assets/img/setup/customize/doctype-basics.png)
+
+#### Fields
+
+In the Fields Table, you can add the fields (properties) of the DocType (Article).
+
+Fields are much more than database columns, they can be:
+
+1. Columns in the database
+1. For Layout (section / column breaks)
+1. Child tables (Table type field)
+1. HTML
+1. Actions (button)
+1. Attachments or Images
+
+![Doctype fields](assets/img/setup/customize/Doctype-all-fields.png)
+
+When you add fields, you need to enter the **Type**. **Label** is optional for Section Break and Column Break. **Name** (`fieldname`) is the name of the database table column.
+
+You can also set other properties of the field like whether it is mandatory, read only etc.
+
+#### Naming
+
+In this section, you can define criteria based on which document for this doctype will be named. There are multiple criterion based on which document can be named, like naming based on the value in the specific field, or based on Naming Series, or based on value provided by the user in the prompt, which will be shown when saving document. In the following example, we are doing naming based on the value in the field **book_name**.
+
+![Doctype Naming](assets/img/setup/customize/doctype-field-naming.png)
+
+#### Permission
+
+In this table, you should select roles and define permission roles for them for this Doctype.
+
+![Doctype Permissions](assets/img/setup/customize/Doctype-permissions.png)
+
+#### Save Doctype
+
+On saving doctype, you will get pop-up to provide name for this Doctype.
+
+![Doctype Save](assets/img/setup/customize/Doctype-save.png)
+
+#### Doctype in System
+
+To check this Doctype, open Module defined for this doctype. Since we have added Books doctype in the
+Human Resource module, to access this doctype, go to:
+
+`Human Resource > Document > Book`
+
+![Doctype List](assets/img/setup/customize/Doctype-list-view.png)
+
+#### Book master
+
+Using the fields entered, following is the master one book.
+
+![Doctype List](assets/img/setup/customize/Doctype-book-added.png)
diff --git a/erpnext/docs/user/guides/customize-erpnext/custom-field.md b/erpnext/docs/user/guides/customize-erpnext/custom-field.md
new file mode 100644
index 0000000..ca5449b
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/custom-field.md
@@ -0,0 +1,77 @@
+Custom Field feature allows you to insert fields in the existing masters and transactions as per your requirement. While inseting custom field, you can define its properties like.
+
+* Field Name/Label
+* Field Type
+* Mandatory/Non-Mandatory
+* Insert After Field
+
+To add a Custom Field, go to:
+
+> Setup > Customize > Custom Field > New Custom Field
+
+You can also insert new Custom Field from [Customize Form](https://erpnext.com/customize-erpnext/customize-form) tool.
+
+In Customize Form, for each field, you will find plus (+) option. When click on it, new row will be inserted above that field. You can enter properties for your Custom Field in the newly added blank row.
+
+![Customize Form Custom Field](assets/old_images/erpnext/customize-form-custom-field.png)
+
+Following are the steps to insert Custom Field in the existing form.
+
+####New Custom Field form / Row in Customize Form
+
+As mentioned above, you can insert Custom Field from Custom Field form, and also from Customize Form.
+
+####Select Document/Form
+
+You should select transaction or master in which you want to insert custom field. Let's assume you need to insert a custom link field in the Quotation form. In this case, Document will be "Quotation".
+
+![Custom Field Document](assets/old_images/erpnext/custom-field-document.png)
+
+####Set Field Label
+
+Custom Field's name will be set based on its Label. If you want to create Custom Field with specific name, but with different label, then you should first set Label as you want Field Name to be set. After Custom Field is saved, you can edit the Field Label again.
+
+![Custom Field Label](assets/old_images/erpnext/custom-field-label.png)
+
+####Select Insert After
+
+This field will have all the existing field of the form/doctype selected. Your Custom Field will be placed after field you select in the Insert After field.
+
+![Custom Field Insert](assets/old_images/erpnext/custom-field-insert.png)
+
+####Select Field Type
+
+Click [here](https://erpnext.com/kb/customize/field-types) to learn more about types of field you can set for your Custom Field.
+
+![Custom Field Type](assets/old_images/erpnext/custom-field-type.png)
+
+####Set Option
+
+If you are creating a Link field, then Doctype name with which this field will be linked to will be entered in the Option field. Click [here](https://erpnext.com/kb/customize/creating-custom-link-field) to learn more about creating custom link field.
+
+![Custom Field Link](assets/old_images/erpnext/custom-field-link.png)
+
+If field type is set as Select (drop down field), then all he possible result for this field should be listed in the Options field. Each possible result should be separate by row.
+
+![Custom Field Option](assets/old_images/erpnext/custom-field-option.png)
+
+For other field types, like Data, Date, Currency etc., Opton field will be left blank.
+
+####Set More Properties
+
+You can set properties as:
+
+1. Mandatory: Should this field be mandatory or non-mandatory.
+1. Print Hide: Should this field be visible in the print format or no.
+1. Field Description: It will be short field description which will appear just below that field.
+1. Default Value: Value entered in this field will be auto-updated in this field.
+1. Read Only: Checking this option will make custom field non-editable.
+1. Allow on Submit: Checking this option will allow editing value in the field when in submitted transaction.
+
+![Custom Field Properties](assets/old_images/erpnext/custom-field-properties.png)
+
+####Deleting Custom Field
+
+Given a permission, user will be able to delete Custom Fields. Incase, it was deleted by default, if you add another Custom Field with same name. Then you shall see new field auto-mapped with old-deleted Custom Field.
+
+{next}
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/custom-button.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/custom-button.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/custom-button.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/custom-button.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/custom-script-fetch-values-from-master.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/custom-script-fetch-values-from-master.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/custom-script-fetch-values-from-master.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/custom-script-fetch-values-from-master.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/date-validation.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/date-validation.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/date-validation.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/date-validation.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/generate-item-code-based-on-custom-logic.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/generate-item-code-based-on-custom-logic.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/generate-item-code-based-on-custom-logic.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/generate-item-code-based-on-custom-logic.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/index.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/index.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/index.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/index.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/index.txt b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/index.txt
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/index.txt
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/index.txt
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/make-read-only-after-saving.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/make-read-only-after-saving.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/make-read-only-after-saving.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/make-read-only-after-saving.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-cancel-rights.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-cancel-rights.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-cancel-rights.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-cancel-rights.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-purpose-of-stock-entry.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-purpose-of-stock-entry.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-purpose-of-stock-entry.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-purpose-of-stock-entry.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-user-based-on-child-record.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-user-based-on-child-record.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/restrict-user-based-on-child-record.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/restrict-user-based-on-child-record.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/sales-invoice-id-based-on-sales-order-id.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/sales-invoice-id-based-on-sales-order-id.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/sales-invoice-id-based-on-sales-order-id.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/sales-invoice-id-based-on-sales-order-id.md
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/update-date-field-based-on-value-in-other-date-field.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/update-date-field-based-on-value-in-other-date-field.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/custom-script-examples/update-date-field-based-on-value-in-other-date-field.md
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/custom-script-examples/update-date-field-based-on-value-in-other-date-field.md
diff --git a/erpnext/docs/user/guides/customize-erpnext/custom-scripts/index.md b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/index.md
new file mode 100644
index 0000000..efe484b
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/index.md
@@ -0,0 +1,11 @@
+If you wish to change any ERPNext form formats, you can do so by using Custom
+Scripts. For example, if you wish to add a submit button after saving, to a
+Lead form, you can do so by creating your own script.
+
+> Setup > Customization > Custom Script
+
+![Custom Script](assets/old_images/erpnext/custom-script.png)
+
+### Topics
+
+{index}
diff --git a/erpnext/docs/user/customize-erpnext/custom-scripts/index.txt b/erpnext/docs/user/guides/customize-erpnext/custom-scripts/index.txt
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/custom-scripts/index.txt
rename to erpnext/docs/user/guides/customize-erpnext/custom-scripts/index.txt
diff --git a/erpnext/docs/user/guides/customize-erpnext/customize-form.md b/erpnext/docs/user/guides/customize-erpnext/customize-form.md
new file mode 100644
index 0000000..57487f2
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/customize-form.md
@@ -0,0 +1,107 @@
+<!--markdown-->
+Before we venture to learn form customization tool, click [here](https://kb.frappe.io/kb/customization/form-architecture) to understand the architecture of forms in ERPNext. It shall help you in using Customize Form tool more efficiently.
+
+Customize Form is the tool which allows user to customize the property of standard fields as per the requirement. Let's assume we need to set Project Name field as mandatory in the Sales Order form. Following are the steps which shall be followed to achieve this.
+
+####Step 1: Go to Customize Form
+
+You can go to Customize Form from:
+
+> Setup >> Customize >> Customize Form
+
+System Manager will find Customize Form option in the Sales Order list (or any other form for that matter) view as well.
+
+![Customize Form List View](assets/old_images/erpnext/customize-form-list-view.png)
+
+####Step 2: Select Docytpe/Document
+
+You should select Docytpe/Document which has field-to-be-customized located in it.
+
+![Customize Form Document](assets/old_images/erpnext/customize-form-document.png)
+
+####Step 3:Edit Property
+
+On selecting Doctype/table, you will have all the fields of the table updated as rows in the Customize Form table. You should drill down to field you need to work on, Project Name in this case.
+
+On clicking Project Name row, fields to set various property for this field will be shown. To Customize the mandatory property for a field, there is a field called "Mandatory". Checking this field will set Project Name field as mandatory in the Quotation form.
+
+![Customize Form Mandatory](assets/old_images/erpnext/customize-form-mandatory.png)
+
+Like this, you can customize following properties of the field.
+
+* Change field types (for e.g. you want to increase the number of decimal places, you can convert come fields from Float to Currency).
+* Change labels to suit your industry / language.
+* Make certain fields mandatory.
+* Hide certain fields.
+* Change layout (sequence of fields). To do this, select a field in the grid and click on“Up” or “Down” in the grid toolbar.
+* Add / edit “Select” Options. (for example, you can add more sources in Leads etc).
+
+####Step 4: Update
+
+![Customize Form Update](assets/old_images/erpnext/customize-form-update.png)
+
+Before checking Sales Order form, you should clear cache and refresh browser tab for customization to take effect.
+
+For Customize Form, you can also allow attachments, set max number of attachments and set the default Print Format.
+
+>Note: Though we want you to do everything you can to customize your ERP based on your business needs, we recommend that you do not make “wild” changes to the forms. This is because, these changes may affect certain operations and may mess up your forms. Make small changes and see its effect before doing some more.
+
+Following are the properties which you can customize for a specific field from Customize Form.
+<style>
+    td {
+    padding:5px 10px 5px 5px;
+    };
+    img {
+    align:center;
+    };
+table, th, td {
+    border: 1px solid black;
+    border-collapse: collapse;
+}
+</style>
+<table border="1" width="700px">
+  <tbody>
+    <tr>
+      <td style="text-align: center;"><b>Field property</b></td>
+      <td style="text-align: center;"><b>Purpose</b></td>
+    </tr>
+    <tr>
+      <td>Print hide</td>
+      <td>Checking it will hide field from Standard print format.</td>
+    </tr>
+    <tr>
+      <td>Hidden</td>
+      <td>Checking it field will hide field in the data entry form.</td>
+    </tr>
+    <tr>
+      <td>Mandatory</td>
+      <td>Checking it will set field as mandatory.</td>
+    </tr>
+    <tr>
+      <td>Field Type</td>
+      <td>Click <a href="https://erpnext.com/kb/customize/field-types">here</a> to learn about of fields types.</td>
+    </tr>
+    <tr>
+      <td>Options</td>
+      <td>Possible result for a drop down fields can be listed here. Also for a link field, relevant Doctype can be provided.</td>
+    </tr>
+    <tr>
+      <td>Allow on submit</td>
+      <td>Checking it will let user update value in field even in submitted form.</td>
+    </tr>
+    <tr>
+      <td>Default</td>
+      <td>Value defined in default will be pulled on new record creation.</td>
+    </tr>
+    <tr>
+      <td>Description</td>
+      <td>Gives field description for users understanding.</td>
+    </tr>
+    <tr>
+      <td>Label</td>
+      <td>Label is the field name which appears in form.</td>
+    </tr>
+  </tbody>
+</table>
+
+{next}
diff --git a/erpnext/docs/user/guides/customize-erpnext/document-title.md b/erpnext/docs/user/guides/customize-erpnext/document-title.md
new file mode 100644
index 0000000..89e9c5c
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/document-title.md
@@ -0,0 +1,33 @@
+You can customize the title of documents based on properties so that you have meaningful information for the list views.
+
+For example the default title on **Quotation** is the customer name, but if you are dealing a few customers and sending lots of quotes to the same customer, you may want to customize.
+
+#### Setting Title Fields
+
+From ERPNext Version 6.0 onwards, all transactions have a `title` property. If there is not a title property, you can add a **Custom Field** as title and set the **Title Field** via **Customize Form**.
+
+You can set the default value of that property by using Python style string formatting in **Default** or **Options**
+
+To edit a default title, go to
+
+1. Setup > Customize > Customize Form
+2. Select your transaction
+3. Edit the **Default** field in your form
+
+#### Defining Titles
+
+You can define the title by setting document properties in braces `{}`. For example if your document has properties `customer_name` and `project` here is how you can set the default title:
+
+    {customer_name} for {project}
+
+<img class="screenshot" alt = "Customize Title"
+    src="assets/img/customize/customize-title.gif">
+
+#### Fixed or Editable Titles
+
+If your title is generated as a default title, it can be edited by the user by clicking on the heading of the document.
+
+<img class="screenshot" alt = "Editable Title"
+    src="assets/img/customize/editable-title.gif">
+
+If you want a fixed title, you can set the rule in the **Options** property. In this way, the title will be automatically updated everytime the document is updated.
diff --git a/erpnext/docs/user/guides/customize-erpnext/hiding-modules-and-features.md b/erpnext/docs/user/guides/customize-erpnext/hiding-modules-and-features.md
new file mode 100644
index 0000000..b35a484
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/hiding-modules-and-features.md
@@ -0,0 +1,30 @@
+### Hiding Unused Features
+
+As you have seen from this manual that ERPNext contains tons of features which
+you may not use. We have observed that most users start with using 20% of the
+features, though a different 20%. To hide fields belonging to features you
+dont require, go to:
+
+> Setup > Tools > Hide/Unhide Features
+
+![Hide Features](assets/old_images/erpnext/hide-features.png)
+
+Check / uncheck the features you want to use and refresh your page for the
+changes to take effect.
+
+* * *
+
+### Hiding Module Icons
+
+To hide modules (icons) from the home page, go to:
+
+Setup > Tools> Modules Setup
+
+![Hide/Unhide Modules](assets/old_images/erpnext/hide-module.png)
+
+> Note: Modules are automatically hidden for users that have no permissions on
+the documents within that module. For example, if a user has no permissions on
+Purchase Order, Purchase Request, Supplier, the “Buying” module will
+automatically be hidden.
+
+{next}
diff --git a/erpnext/docs/user/customize-erpnext/index.md b/erpnext/docs/user/guides/customize-erpnext/index.md
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/index.md
rename to erpnext/docs/user/guides/customize-erpnext/index.md
diff --git a/erpnext/docs/user/customize-erpnext/index.txt b/erpnext/docs/user/guides/customize-erpnext/index.txt
similarity index 100%
rename from erpnext/docs/user/customize-erpnext/index.txt
rename to erpnext/docs/user/guides/customize-erpnext/index.txt
diff --git a/erpnext/docs/user/guides/customize-erpnext/print-format.md b/erpnext/docs/user/guides/customize-erpnext/print-format.md
new file mode 100644
index 0000000..74316fa
--- /dev/null
+++ b/erpnext/docs/user/guides/customize-erpnext/print-format.md
@@ -0,0 +1,106 @@
+<!-- no-jinja -->
+
+Print Formats are the layouts that are generated when you want to Print or
+Email a transaction like a Sales Invoice. There are two types of Print
+Formats,
+
+  * The auto-generated “Standard” Print Format: This type of format follows the same layout as the form and is generated automatically by ERPNext.
+  * Based on the Print Format document. There are templates in HTML that will be rendered with data.
+
+ERPNext comes with a number of pre-defined templates in three styles: Modern,
+Classic and Standard.
+
+You can modify the templates or create your own. Editing
+ERPNext templates is not allowed because they may be over-written in an
+upcoming release.
+
+To create your own versions, open an existing template from:
+
+> Setup > Printing > Print Formats
+
+![Print Format](assets/old_images/erpnext/customize/print-format.png)
+
+Select the type of Print Format you want to edit and click on the “Copy”
+button on the right column. A new Print Format will open up with “Is Standard”
+set as “No” and you can edit the Print Format.
+
+Editing a Print Format is a long discussion and you will have to know a bit of
+HTML, CSS, Python to learn this. For help, please post on our forum.
+
+Print Formats are rendered on the server side using the [Jinja Templating Language](http://jinja.pocoo.org/docs/templates/). All forms have access to the doc object which contains information about the document that is being formatted. You can also access common utilities via the frappe module.
+
+For styling, the [Boostrap CSS Framework](http://getbootstrap.com/) is provided and you can enjoy the full range of classes.
+
+> Note: Pre-printed stationary is usually not a good idea because your Prints
+will look incomplete (inconsistent) when you send them by mail.
+
+#### References
+
+1. [Jinja Tempalting Language: Reference](http://jinja.pocoo.org/docs/templates/)
+1. [Bootstrap CSS Framework](http://getbootstrap.com/)
+
+#### Print Settings
+
+To edit / update your print and PDF settings, go to:
+
+> Setup > Printing and Branding > Print Settings
+
+![Print Format](assets/old_images/erpnext/customize/print-settings.png)
+
+#### Example
+
+{% set example = '''<h3>{{ doc.select_print_heading or "Invoice" }}</h3>
+	<div class="row">
+		<div class="col-md-3 text-right">Customer Name</div>
+		<div class="col-md-9">{{ doc.customer_name }}</div>
+	</div>
+	<div class="row">
+		<div class="col-md-3 text-right">Date</div>
+		<div class="col-md-9">{{ doc.get_formatted("invoice_date") }}</div>
+	</div>
+	<table class="table table-bordered">
+		<tbody>
+			<tr>
+				<th>Sr</th>
+				<th>Item Name</th>
+				<th>Description</th>
+				<th class="text-right">Qty</th>
+				<th class="text-right">Rate</th>
+				<th class="text-right">Amount</th>
+			</tr>
+			{%- for row in doc.items -%}
+			<tr>
+				<td style="width: 3%;">{{ row.idx }}</td>
+				<td style="width: 20%;">
+					{{ row.item_name }}
+					{% if row.item_code != row.item_name -%}
+					<br>Item Code: {{ row.item_code}}
+					{%- endif %}
+				</td>
+				<td style="width: 37%;">
+					<div style="border: 0px;">{{ row.description }}</div></td>
+				<td style="width: 10%; text-align: right;">{{ row.qty }} {{ row.uom or row.stock_uom }}</td>
+				<td style="width: 15%; text-align: right;">{{
+					row.get_formatted("rate", doc) }}</td>
+				<td style="width: 15%; text-align: right;">{{
+					row.get_formatted("amount", doc) }}</td>
+			</tr>
+			{%- endfor -%}
+		</tbody>
+	</table>''' %}
+
+    {{ example|e }}
+
+#### Notes
+
+1. To get date and currency formatted values use, `doc.get_formatted("fieldname")`
+1. For translatable strings, us `{{ _("This string is translated") }}`
+
+#### Footers
+
+Many times you may want to have a standard footer for your prints with your
+address and contact information. Unfortunately due to the limited print
+support in HTML pages, it is not possible unless you get it scripted. Either
+you can use pre-printed stationary or add this information in your header.
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/appraisal.md b/erpnext/docs/user/guides/human-resources/appraisal.md
new file mode 100644
index 0000000..7a5f24b
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/appraisal.md
@@ -0,0 +1,24 @@
+In ERPNext, you can manage Employee Appraisals by creating an Appraisal
+Template for each role with the parameters that define the performance by
+giving appropriate weightage to each parameter.
+
+> Human Resource > Appraisal > New
+
+#### Step 1: Select an Appraisal Template
+
+<img class="screenshot" alt="Appraisal" src="assets/img/human-resources/appraisal.png">
+
+After you select the template, the remaining form appears.
+
+#### Step 2: Enter Employee Details
+
+<img class="screenshot" alt="Appraisal" src="assets/img/human-resources/appraisal-employee.png">
+
+Once the Appraisal Template is completed, you can create Appraisal records for
+each period where you track performance. You can give points out of 5 for each
+parameter and the system will calculate the overall performance of the
+Employee.
+
+To make the Appraisal final, make sure to “Submit” it.
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/attendance.md b/erpnext/docs/user/guides/human-resources/attendance.md
new file mode 100644
index 0000000..175c495
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/attendance.md
@@ -0,0 +1,14 @@
+An Attendance record stating that an Employee has been present on a particular
+day can be created manually by:
+
+> Human Resources > Attendance > New Attendance
+
+<img class="screenshot" alt="Attendence" src="assets/img/human-resources/attendence.png">
+
+You can get a monthly report of your Attendance data by going to the “Monthly
+Attendance Details” report.
+
+You can also bulk uppload attendence using the [Upload Attendence Tool ](/contents/human-resources/tools/upload-attendance)
+
+{next}
+
diff --git a/erpnext/docs/user/guides/human-resources/employee.md b/erpnext/docs/user/guides/human-resources/employee.md
new file mode 100644
index 0000000..09bc489
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/employee.md
@@ -0,0 +1,9 @@
+There are many fields you can add in your Employee records.
+
+To create new Employee go to:
+
+> Human Resources > Employee > New
+
+<img class="screenshot" alt="Employee" src="assets/img/human-resources/employee.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/expense-claim.md b/erpnext/docs/user/guides/human-resources/expense-claim.md
new file mode 100644
index 0000000..13cb19d
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/expense-claim.md
@@ -0,0 +1,39 @@
+Expense Claim is made when Employee’s make expenses out of their pocket on
+behalf of the company. For example, if they take a customer out for lunch,
+they can make a request for reimbursement via the Expense Claim form.
+
+To make a new Expense Claim, go to:
+
+> HR > Expense Claim > New Expense Claim
+
+<img class="screenshot" alt="Expense Claim" src="assets/img/human-resources/expense_claim.png">
+
+Set the Employee ID, date and the list of expenses that are to be claimed and
+“Submit” the record.
+
+### Approving Expenses
+
+The person making the claim must also set the id of the user who will
+“Approve” these expenses and set the “Assign To” to notify the user of the
+request Approve.
+
+If the Approver sees the “form”, she or he can update the “Approved Amounts”
+and click on “Approve”. To cancel the claim, they can click on the “Reject”
+button.
+
+Comments can be added in the Comments section explaining why the claim was
+approved or rejected.
+
+### Booking the Expense and Reimbursement
+
+The approved Expense Claim must then be converted into a Journal Entry and a
+payment must be made. Note: This amount should not be clubbed with Salary
+because the amount will then be taxable to the Employee.
+
+### Linking with Task & Project
+
+* To Link Expense Claim with Task or Project specify the Task or the Project while making an Expense Claim
+
+<img class="screenshot" alt="Expense Claim - Project Link" src="assets/img/project/project_expense_claim_link.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/holiday-list.md b/erpnext/docs/user/guides/human-resources/holiday-list.md
new file mode 100644
index 0000000..bd5f195
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/holiday-list.md
@@ -0,0 +1,59 @@
+Holiday List is a list which contains the dates of holidays along with the
+occasion of that holiday. The list is generally valid for one calendar year.  
+
+Most organisations have a standard Holiday-List for their employees. Some even
+have different holiday lists for laborers and a different one for management
+staff.
+
+  
+
+To set up a holiday list in the system, Go to Human Resources Module and Click
+on Holiday List.
+
+  
+
+> Human Resources >Holiday List > New Holiday List  
+
+  
+#### Figure 1: Holiday List
+
+![](assets/old_images/erpnext/holiday-list-1.png)  
+
+  
+
+__Step 1:__ Give a name to the Holiday list
+
+__Step 2:__ Mention the Fiscal Year  
+
+__Step 3:__ State the Weekly  off.  
+
+__Step 4:__ Click on the button 'Get Weekly Off Dates'  
+
+This step will fill the box below with yearly off dates with day as the
+description.
+
+__Step 5:__ Click on Add new row to add more dates  
+
+Mention the holiday reason in the description and select the date from the
+'Date' field.
+
+  
+#### Figure 2: Adding new holidays to the list
+
+![](assets/old_images/erpnext/holiday-list-2.png)  
+
+  
+
+> Note 1: If you have selected a holiday list in the Employment Details form,
+the system will give priority to the form mentioned here. It will fetch the
+list mentioned in the form rather than the one which you may have specified as
+Default; However, if there is no list in the employment details form, the
+default list will be fetched.
+
+
+> Note 2: You can form as many holiday lists as you wish. For example, if you
+have a mill, you can have one list for mill workers and another list for
+office staff. You can manage between lists by attaching their respective
+holiday list to their respective employment detail form.
+
+{next}
diff --git a/erpnext/docs/user/human-resources/human-resource-setup.md b/erpnext/docs/user/guides/human-resources/human-resource-setup.md
similarity index 100%
rename from erpnext/docs/user/human-resources/human-resource-setup.md
rename to erpnext/docs/user/guides/human-resources/human-resource-setup.md
diff --git a/erpnext/docs/user/guides/human-resources/human-resources-reports.md b/erpnext/docs/user/guides/human-resources/human-resources-reports.md
new file mode 100644
index 0000000..ac0a198
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/human-resources-reports.md
@@ -0,0 +1,34 @@
+Human Resources Reports
+
+### Employee Leave Balance
+
+Employee Leave Balance Report shows employees and their respective balance leaves under various leave types. Report is generated as per the number of allowed leaves.
+
+<img alt="Employee Leave Balance" class="screenshot" src="assets/img/human-resources/employee-leave-balance-report.png">
+
+### Employee Birthday
+
+Employee Birthday Report shows Birthdays of your employees.
+
+<img alt="Employee Birthday" class="screenshot" src="assets/img/human-resources/employee-birthday-report.png">
+
+### Employee Information
+
+Employee Information Report shows Report View of important information recorded in Employee master.
+
+<img alt="Employee Information" class="screenshot" src="assets/img/human-resources/employee-information-report.png">
+
+### Monthly Salary Register
+
+Monthly Salary Register shows net pay and its components of employee(s) at a glance.
+
+<img alt="Monthly Salary Register" class="screenshot" src="assets/img/human-resources/monthly-salary-register-report.png">
+
+
+### Monthly Attendance Sheet
+
+Monthly Attendance Sheet shows monthly attendance of selected employee at a glance.
+
+<img alt="Monthly Attendance Sheet" class="screenshot" src="assets/img/human-resources/monthly-attendance-sheet-report.png">
+
+{next}
diff --git a/erpnext/docs/user/human-resources/index.md b/erpnext/docs/user/guides/human-resources/index.md
similarity index 100%
rename from erpnext/docs/user/human-resources/index.md
rename to erpnext/docs/user/guides/human-resources/index.md
diff --git a/erpnext/docs/user/human-resources/index.txt b/erpnext/docs/user/guides/human-resources/index.txt
similarity index 100%
rename from erpnext/docs/user/human-resources/index.txt
rename to erpnext/docs/user/guides/human-resources/index.txt
diff --git a/erpnext/docs/user/human-resources/introduction-to-human-resources.md b/erpnext/docs/user/guides/human-resources/introduction-to-human-resources.md
similarity index 100%
rename from erpnext/docs/user/human-resources/introduction-to-human-resources.md
rename to erpnext/docs/user/guides/human-resources/introduction-to-human-resources.md
diff --git a/erpnext/docs/user/guides/human-resources/job-applicant.md b/erpnext/docs/user/guides/human-resources/job-applicant.md
new file mode 100644
index 0000000..1b8e9a1
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/job-applicant.md
@@ -0,0 +1,25 @@
+You can mantain a list of People who have applied for a [Job Opening](/contents/human-resources/job-opening).
+
+To create a new Job Applicant go to 
+
+> Human Resource > Job Applicant > New
+
+<img class="screenshot" alt="Job Applicant" src="assets/img/human-resources/job-applicant.png">
+
+### Linking with an Email Account
+
+You can link Job Application with an Email account.
+Suppose you link Job Application with an email job@example.com 
+system shall create a New Job Applicant against each email received on the mailbox.
+
+* To link Email Account with Job Applicant, go to
+
+> Setup > Email Account > New 
+
+* Enter the email id and the password, and select 'Enable Incoming'
+
+* In 'Append To' select 'Job Applicant'
+
+<img class="screenshot" alt="Email Account" src="assets/img/human-resources/email-account.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/job-opening.md b/erpnext/docs/user/guides/human-resources/job-opening.md
new file mode 100644
index 0000000..eeb29ec
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/job-opening.md
@@ -0,0 +1,10 @@
+You can make a record of the open vacancies in your company using Job Opening.
+
+To create a new Job Opening go to 
+
+> Human Resource > Job Opening > New
+
+<img class="screenshot" alt="Job Opening" src="assets/img/human-resources/job-opening.png">
+
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/leave-application.md b/erpnext/docs/user/guides/human-resources/leave-application.md
new file mode 100644
index 0000000..8cb1943
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/leave-application.md
@@ -0,0 +1,24 @@
+If your company has a formal system where Employees have to apply for leaves
+to be able to qualify as paid leaveas, you can create Leave Application to
+track approval and usage of leaves. You have to mention the Employee, Leave
+Type and the period for which the leave is taken.
+
+> Human Resources > Leave Application > New Leave Application
+
+<img class="screenshot" alt="Leave Application" src="assets/img/human-resources/leave-application.png">
+
+###Setting Leave Approver
+
+* A leave approver is a user who can approve an leave application for an employee. 
+
+* You need to mention a list of Leave Approvers against an Employee in the Employee Master.
+
+<img class="screenshot" alt="Leave Approver" src="assets/img/human-resources/employee-leave-approver.png">
+
+> Tip : If you want all users to create their own Leave Applications, you can set
+their “Employee ID” as a match rule in the Leave Application Permission
+settings. See the earlier discussion on [Setting Up Permissions](/contents/setting-up/users-and-permissions)
+for more info.
+
+You assign Leaves aginast an Employee check [Leave Allocation](/contents/human-resources/setup/leave-allocation)
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/offer-letter.md b/erpnext/docs/user/guides/human-resources/offer-letter.md
new file mode 100644
index 0000000..34bceee
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/offer-letter.md
@@ -0,0 +1,16 @@
+Offer Letter is given to candidate after Interview & selection which states the offered salary package, 
+designation, grade, department working, no of days entitled for leave.
+
+In ERPNext you can make a record of the Offer Letters that you can given to candidates. To create a new offer Letter go to 
+
+> Human Resource > Offer Letter > New
+
+<img class="screenshot" alt="Offer Letter" src="assets/img/human-resources/offer-letter.png">
+
+> Note: An offer letter can be made only against a [Job Applicant](/contents/human-resources/job-applicant)
+
+There is a pre-designed print format to print you offer letter.
+
+<img class="screenshot" alt="Offer Letter" src="assets/img/human-resources/offer-letter-print.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/salary-and-payroll.md b/erpnext/docs/user/guides/human-resources/salary-and-payroll.md
new file mode 100644
index 0000000..849e4e6
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/salary-and-payroll.md
@@ -0,0 +1,116 @@
+Salary is a fixed amount of money or compensation paid to an employee by an employer in return for the work performed . 
+
+Payroll is the administration of financial records of employees' salaries, wages, bonuses, net pay, and deductions.
+
+To process Payroll in ERPNext,
+
+  1. Create Salary Structures for all Employees.
+  2. Generate Salary Slips via Process Payroll.
+  3. Book the Salary in your Accounts.
+
+### Salary Structure
+
+The Salary Structure represents how Salaries are calculated based on Earnings
+and Deductions. 
+
+Salary structures are used to help organizations:
+  1. Maintain pay levels that are competitive with the external labor market,
+  2. Maintain internal pay relationships among jobs,
+  3. Recognize and reward differences in level of responsibility, skill, and performance, and manage pay expenditures.
+
+The usual components of the salary structure (in india) include:
+
+__Basic Salary:__ It is the taxable base income and generally not more than 40% of CTC.
+
+__House Rent Allowance:__ The HRA constitutes 40 to 50% of the basic salary.
+
+__Special Allowances:__ Makes up for the remainder part of the salary, mostly smaller than the basic salary which is completely taxable.
+
+__Leave Travel Allowance:__ The non-taxable amount paid by the employer to the employee for vacation/trips with family within India.
+
+__Gratuity:__ It is basically a lump sum amount paid by the employer when the employee resigns from the organization or retires.
+
+__PF:__ Fund collected during emergency or old age. 12% of the basic salary is automatically deducted and goes to the employee provident fund.
+
+__Medical Allowance:__ The employer pays the employee for the medical expenditures incurred. It is tax free up to Rs.15,000.
+
+__Bonus:__ Taxable part of the CTC, usually a once a year lump sum amount, given to the employee based on the individual’s as well as the organizational performance for the year.
+
+__Employee Stock Options:__ ESOPS are Free/discounted shares given by the company to the employees. This is done to primarily increase employee retention.
+
+To create a new Salary Structure go to:
+
+> Human Resources > Setup > Salary Structure > New Salary Structure
+
+#### Figure 1:Salary Structure
+
+<img class="screenshot" alt="Salary Structure" src="assets/img/human-resources/salary-structure.png">
+
+### In the Salary Structure,
+
+  * Select the Employee
+  * Set the starting date from which this is valid (Note: There can only be one Salary Structure that can be “Active” for an Employee during any period)
+  * In the “Earnings” and “Deductions” table all your defined Earning Type and Deductions Type will be auto-populated. Set the values of the Earnings and Deductions and save the Salary Structure.
+
+### Leave Without Pay (LWP)
+
+Leave Without Pay (LWP) happens when an Employee runs out of allocated leaves
+or takes a leave without an approval (via Leave Application). If you want
+ERPNext to automatically deduct salary in case of LWP, then you must check on
+the “Apply LWP” column in the Earning Type and Deduction Type masters. The
+amount of pay cut is the proportion of LWP days divided by the total working
+days for the month (based on the Holiday List).
+
+If you don’t want ERPNext to manage LWP, just don’t click on LWP in any of the
+Earning Types and Deduction Types.
+
+* * *
+
+### Creating Salary Slips
+
+Once the Salary Structure is created, you can make a salary slip from the same
+form or you can process your payroll for the month using Process Payroll.
+
+To create a salary slip from Salary Structure, click on the button Make Salary
+Slip.
+
+#### Figure 2: Salary Slip
+
+<img class="screenshot" alt="Salary Slip" src="assets/img/human-resources/salary-slip.png">
+
+You can also create salary slip for multiple employees using Process Payroll:
+
+> Human Resources > Process Payroll
+
+#### Figure 3: Process Payroll
+
+<img class="screenshot" alt="Process Payroll" src="assets/img/human-resources/process-payroll.png">
+
+In Process Payroll,
+
+  1. Select the Company for which you want to create the Salary Slips.
+  2. Select the Month and the Year for which you want to create the Salary Slips.
+  3. Click on “Create Salary Slips”. This will create Salary Slip records for each active Employee for the month selected. If the Salary Slips are created, the system will not create any more Salary Slips. All updates will be shown in the “Activity Log” section.
+  4. Once all Salary Slips are created, you can check if they are created correctly or edit it if you want to deduct Leave Without Pay (LWP).
+  5. After checking, you can “Submit” them all together by clicking on “Submit Salary Slips”. 1. If you want them to be automatically emailed to the Employee, make sure to check the “Send Email” box.
+
+### Booking Salaries in Accounts
+
+The final step is to book the Salaries in your Accounts.
+
+Salaries in businesses are usually dealt with extreme privacy. In most cases,
+the companies issues a single payment to the bank combining all salaries and
+the bank distributes the salaries to each employee’s salary account. This way
+there is only one payment entry in the company’s books of accounts and anyone
+with access to the company’s accounts will not have access to the individual
+salaries.
+
+The salary payment entry is a Journal Entry entry that debits the total
+salary of all Employees to the Salary Account and credits the company’s bank
+Account.
+
+To generate your salary payment voucher from Process Payroll, click on
+“Make Bank Voucher” and a new Journal Entry with the total salaries will be
+created.
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/setup/branch.md b/erpnext/docs/user/guides/human-resources/setup/branch.md
new file mode 100644
index 0000000..931da08
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/branch.md
@@ -0,0 +1,5 @@
+Branches of your organization
+
+<img class="screenshot" alt="Branch" src="assets/img/human-resources/branch.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/setup/deduction-type.md b/erpnext/docs/user/guides/human-resources/setup/deduction-type.md
new file mode 100644
index 0000000..613f55a
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/deduction-type.md
@@ -0,0 +1,10 @@
+You can make a record of the tax and other salary deductions and describe it as Deduction Type
+
+To create a new Deduction Type
+
+> Human Resource > Setup > Deduction Type > New
+
+<img class="screenshot" alt="Deduction Type" src="assets/img/human-resources/deduction-type.png">
+
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/setup/department.md b/erpnext/docs/user/guides/human-resources/setup/department.md
new file mode 100644
index 0000000..3b6e8c0
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/department.md
@@ -0,0 +1,5 @@
+Departments in your organization
+
+<img class="screenshot" alt="Department" src="assets/img/human-resources/department.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/setup/designation.md b/erpnext/docs/user/guides/human-resources/setup/designation.md
new file mode 100644
index 0000000..d680d40
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/designation.md
@@ -0,0 +1,5 @@
+Designations in your organization
+
+<img class="screenshot" alt="Designation" src="assets/img/human-resources/designation.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/setup/earning-type.md b/erpnext/docs/user/guides/human-resources/setup/earning-type.md
new file mode 100644
index 0000000..c469f19
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/earning-type.md
@@ -0,0 +1,10 @@
+You can make a record of the Salary Components and describe it as Earning Type
+
+To create a new Earning Type
+
+> Human Resource > Setup > Earning Type > New
+
+<img class="screenshot" alt="Earning Type" src="assets/img/human-resources/earning-type.png">
+
+
+{next}
diff --git a/erpnext/docs/user/guides/human-resources/setup/employment-type.md b/erpnext/docs/user/guides/human-resources/setup/employment-type.md
new file mode 100644
index 0000000..5f56ebc
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/employment-type.md
@@ -0,0 +1,5 @@
+Various employment contracts you have with your employees.
+
+<img class="screenshot" alt="Employment Type" src="assets/img/human-resources/employment-type.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/setup/holiday-list.md b/erpnext/docs/user/guides/human-resources/setup/holiday-list.md
new file mode 100644
index 0000000..42d6263
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/holiday-list.md
@@ -0,0 +1,5 @@
+You can specify the Holidays for a particular year using Holiday List.
+
+<img class="screenshot" alt="Holiday List" src="assets/img/human-resources/holiday-list.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/setup/hr-settings.md b/erpnext/docs/user/guides/human-resources/setup/hr-settings.md
new file mode 100644
index 0000000..9b404d2
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/hr-settings.md
@@ -0,0 +1,7 @@
+# HR Settings
+
+GLobal settings for HR related documents
+
+<img class="screenshot" alt="HR Settings" src="assets/img/human-resources/hr-settings.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/index.md b/erpnext/docs/user/guides/human-resources/setup/index.md
similarity index 100%
rename from erpnext/docs/user/human-resources/setup/index.md
rename to erpnext/docs/user/guides/human-resources/setup/index.md
diff --git a/erpnext/docs/user/human-resources/setup/index.txt b/erpnext/docs/user/guides/human-resources/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/human-resources/setup/index.txt
rename to erpnext/docs/user/guides/human-resources/setup/index.txt
diff --git a/erpnext/docs/user/guides/human-resources/setup/leave-allocation.md b/erpnext/docs/user/guides/human-resources/setup/leave-allocation.md
new file mode 100644
index 0000000..c828b0f
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/leave-allocation.md
@@ -0,0 +1,7 @@
+Helps you allocate Leaves to a particular Employee
+
+<img class="screenshot" alt="Leave Allocation" src="assets/img/human-resources/leave-allocation.png">
+
+To assign leaves to multiple employees use the [Leave Allocation Tool](/contents/human-resources/tools/leave-allocation-tool)
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/setup/leave-type.md b/erpnext/docs/user/guides/human-resources/setup/leave-type.md
new file mode 100644
index 0000000..93ed0c3
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/setup/leave-type.md
@@ -0,0 +1,9 @@
+Specify the Type of Leave that can be allocated against an Employee
+
+<img class="screenshot" alt="Leave Type" src="assets/img/human-resources/leave-type.png">
+
+* 'Max Days Leave Allowed' specifies the maximum number of days this type of leave can be taken at a strech.
+* 'Is LWP' specifies if the Leave is without Pay.
+* 'Allow Negative Balance' specifies if system can maintain negative leaves.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/tools/index.md b/erpnext/docs/user/guides/human-resources/tools/index.md
similarity index 100%
rename from erpnext/docs/user/human-resources/tools/index.md
rename to erpnext/docs/user/guides/human-resources/tools/index.md
diff --git a/erpnext/docs/user/human-resources/tools/index.txt b/erpnext/docs/user/guides/human-resources/tools/index.txt
similarity index 100%
rename from erpnext/docs/user/human-resources/tools/index.txt
rename to erpnext/docs/user/guides/human-resources/tools/index.txt
diff --git a/erpnext/docs/user/guides/human-resources/tools/leave-allocation-tool.md b/erpnext/docs/user/guides/human-resources/tools/leave-allocation-tool.md
new file mode 100644
index 0000000..e7c5a1d
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/tools/leave-allocation-tool.md
@@ -0,0 +1,5 @@
+Leave Allocation tool helps you allocated a specific number of leaves for your employees.
+
+<img class="screenshot" alt="Leave Application" src="assets/img/human-resources/leave-application.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/human-resources/tools/upload-attendance.md b/erpnext/docs/user/guides/human-resources/tools/upload-attendance.md
new file mode 100644
index 0000000..9595f20
--- /dev/null
+++ b/erpnext/docs/user/guides/human-resources/tools/upload-attendance.md
@@ -0,0 +1,9 @@
+This tool helps you to upload bulk attendence from a csv file.
+
+To upload the attendance go to:
+
+> Human Resources > Upload Attendance
+
+<img class="screenshot" alt="Attendence upload" src="assets/img/human-resources/attendence-upload.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/index.md b/erpnext/docs/user/guides/index.md
new file mode 100644
index 0000000..454b4a8
--- /dev/null
+++ b/erpnext/docs/user/guides/index.md
@@ -0,0 +1,3 @@
+# User Manual
+
+{index}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/index.txt b/erpnext/docs/user/guides/index.txt
new file mode 100644
index 0000000..e9e30ed
--- /dev/null
+++ b/erpnext/docs/user/guides/index.txt
@@ -0,0 +1,15 @@
+introduction
+setting-up
+accounts
+stock
+CRM
+selling
+buying
+manufacturing
+projects
+support
+human-resources
+customer-portal
+website
+collaboration-tools
+customize-erpnext
\ No newline at end of file
diff --git a/erpnext/docs/user/introduction/concepts-and-terms.md b/erpnext/docs/user/guides/introduction/concepts-and-terms.md
similarity index 100%
rename from erpnext/docs/user/introduction/concepts-and-terms.md
rename to erpnext/docs/user/guides/introduction/concepts-and-terms.md
diff --git a/erpnext/docs/user/introduction/do-i-need-an-erp.md b/erpnext/docs/user/guides/introduction/do-i-need-an-erp.md
similarity index 100%
rename from erpnext/docs/user/introduction/do-i-need-an-erp.md
rename to erpnext/docs/user/guides/introduction/do-i-need-an-erp.md
diff --git a/erpnext/docs/user/introduction/getting-started-with-erpnext.md b/erpnext/docs/user/guides/introduction/getting-started-with-erpnext.md
similarity index 100%
rename from erpnext/docs/user/introduction/getting-started-with-erpnext.md
rename to erpnext/docs/user/guides/introduction/getting-started-with-erpnext.md
diff --git a/erpnext/docs/user/introduction/implementation-strategy.md b/erpnext/docs/user/guides/introduction/implementation-strategy.md
similarity index 100%
rename from erpnext/docs/user/introduction/implementation-strategy.md
rename to erpnext/docs/user/guides/introduction/implementation-strategy.md
diff --git a/erpnext/docs/user/introduction/index.md b/erpnext/docs/user/guides/introduction/index.md
similarity index 100%
rename from erpnext/docs/user/introduction/index.md
rename to erpnext/docs/user/guides/introduction/index.md
diff --git a/erpnext/docs/user/introduction/index.txt b/erpnext/docs/user/guides/introduction/index.txt
similarity index 100%
rename from erpnext/docs/user/introduction/index.txt
rename to erpnext/docs/user/guides/introduction/index.txt
diff --git a/erpnext/docs/user/guides/introduction/key-workflows.md b/erpnext/docs/user/guides/introduction/key-workflows.md
new file mode 100644
index 0000000..0d79843
--- /dev/null
+++ b/erpnext/docs/user/guides/introduction/key-workflows.md
@@ -0,0 +1,14 @@
+# Flow Chart Of Transactions In ERPNext
+
+This diagram covers how ERPNext tracks your company information across key
+functions. This diagram does not cover all the features of ERPNext.
+
+![](assets/old_images/erpnext/overview.png)
+
+
+[Full Resolution](assets/old_images/erpnext/overview.png)
+
+_Note: Not all of the steps are mandatory. ERPNext allows you to freely skip
+steps if you want to simplify the process._
+
+{next}
diff --git a/erpnext/docs/user/introduction/open-source.md b/erpnext/docs/user/guides/introduction/open-source.md
similarity index 100%
rename from erpnext/docs/user/introduction/open-source.md
rename to erpnext/docs/user/guides/introduction/open-source.md
diff --git a/erpnext/docs/user/guides/introduction/the-champion.md b/erpnext/docs/user/guides/introduction/the-champion.md
new file mode 100644
index 0000000..4795baa
--- /dev/null
+++ b/erpnext/docs/user/guides/introduction/the-champion.md
@@ -0,0 +1,46 @@
+<!-- no-heading -->
+
+<h1 class="white">The Champion</h1>
+
+<img class="cover" src="assets/old_images/erpnext/implementation-image.png">
+
+We have seen dozens of ERP implementations over the past few years and we
+realize that successful implementation is a lot about intangibles and
+attitude.
+
+**ERPs are not required.**
+
+Like exercise.
+
+Human body may seem like it does not require exercise today or even tomorrow,
+but in the long run, if you wish to maintain your body and its health, you
+should get on the treadmill.
+
+In the same way, ERPs improve the health of your organization over a long run
+by keeping it fit and efficient. The more you delay putting things in order,
+the more time you lose, and the closer you get to a major disaster.
+
+So when you start implementing an ERP, keep your sight on the long term
+benefits. Like exercise, its painful in the short run, but will do wonders if
+you stay on course.
+
+* * *
+
+## The Champion
+
+ERP means organization wide change and it does not happen without effort.
+Every change requires a champion and it is the duty of the champion to
+organize and energize the entire team towards implementation. The champion
+needs to be resilient incase something goes wrong .
+
+In many organizations we have seen, the champion is most often the owner or a
+senior manager. Occasionally, the champion is an outsider who is hired for a
+particular purpose.
+
+In either case, you must identify your champion first.
+
+Most likely it's **you!**
+
+Lets Begin!
+
+{next}
diff --git a/erpnext/docs/user/guides/manufacturing/bill-of-materials.md b/erpnext/docs/user/guides/manufacturing/bill-of-materials.md
new file mode 100644
index 0000000..3ed999d
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/bill-of-materials.md
@@ -0,0 +1,41 @@
+At the heart of the Manufacturing system is the **Bill of Materials** (BOM).
+The **BOM** is a list of all materials (either bought or made) and operations
+that go into a finished product or sub-Item. In ERPNext, the component could
+have its own BOM hence forming a tree of Items with multiple levels.
+
+To make accurate Purchase Requests, you must always maintain correct BOMs.
+To make a new BOM:
+
+> Manufacturing > Bill of Materials > New BOM
+
+<img class="screenshot" alt="Task" src="assets/img/manufacturing/bom.png">
+
+* To add Operations select 'With Operation'. The Operations table shall appear.
+
+<img class="screenshot" alt="Task" src="assets/img/manufacturing/bom-operations.png">
+
+  * Select the Item for which you want to make the BOM.
+  * Add the operations that you have to go through to make that particular Item in the “Operations” table. For each operation, you will be asked to enter a Workstation. You must create new Workstations as and when necessary.
+  * Workstations are defined only for product costing and Production Order Operations scheduling purposes not inventory. 
+  * Inventory is tracked in Warehouses not Workstations.
+
+###Costing of a BOM
+
+* The Costing section in BOM gives an approximate cost of producing the Item.
+
+* Add the list of Items you require for each operation, with its quantity. This Item could be a purchased Item or a sub-assembly with its own BOM. If the row Item is a manufactured Item and has multiple BOMs, select the appropriate BOM. You can also define if a part of the Item goes into scrap.
+
+<img class="screenshot" alt="Costing" src="assets/img/manufacturing/bom-costing.png">
+
+* This cost can be updated on by using the 'Update Cost' button.
+
+<img class="screenshot" alt="Update Cost" src="assets/img/manufacturing/bom-update-cost.png">
+
+### Materials Required(exploded) 
+
+This table lists down all the Material required for the Item to be Manufactured.
+It also fetches sub-assemblies along with the quantity.
+
+<img class="screenshot" alt="Exploded Section" src="assets/img/manufacturing/bom-exploded.png">
+
+{next}
diff --git a/erpnext/docs/user/manufacturing/index.md b/erpnext/docs/user/guides/manufacturing/index.md
similarity index 100%
rename from erpnext/docs/user/manufacturing/index.md
rename to erpnext/docs/user/guides/manufacturing/index.md
diff --git a/erpnext/docs/user/manufacturing/index.txt b/erpnext/docs/user/guides/manufacturing/index.txt
similarity index 100%
rename from erpnext/docs/user/manufacturing/index.txt
rename to erpnext/docs/user/guides/manufacturing/index.txt
diff --git a/erpnext/docs/user/guides/manufacturing/introduction.md b/erpnext/docs/user/guides/manufacturing/introduction.md
new file mode 100644
index 0000000..627fe0f
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/introduction.md
@@ -0,0 +1,24 @@
+<img class="screenshot" alt="Task" src="assets/img/manufacturing/manufacturing.png">
+
+### Types of Production Planning
+
+Broadly there are three types of Production Planning Systems
+
+  * __Make-to-Stock:__ In these systems, production is planned based on a forecast and the Items are then sold to distributors or customers. All fast moving consumer goods that are sold in retail shops like soaps, packaged water etc and electronics like phones etc are Made-to-Stock.
+  * __Make-to-Order:__ In these systems, manufacturing takes place after a firm order is placed by a customer.
+  * __Engineer-to-Order:__ In this case each sale is a separate project and has to be designed and engineered to the requirements of the customer. Common examples of this are any custom business like furniture, machine tools, speciality devices, metal fabrication etc.
+
+Most small and medium sized manufacturing businesses are based on a make-to-
+order or engineer-to-order system and so is ERPNext.
+
+For engineer-to-order systems, the Manufacturing module should be used along
+with the Projects module..
+
+#### Manufacturing and Inventory
+
+You can track work-in-progress by creating work-in-progress Warehouses.
+
+ERPNext will help you track material movement by automatically creating Stock
+Entries from your Production Orders by building from Bill of Materials.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/manufacturing/operation.md b/erpnext/docs/user/guides/manufacturing/operation.md
new file mode 100644
index 0000000..b688f2f
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/operation.md
@@ -0,0 +1,11 @@
+### Operation
+
+Stores a list of all Manufacturing Operations, its description and the Default Workstation for the Operation.
+
+You can also create a Operation by:
+
+> Manufacturing > Documents > Operation > New
+
+<img class="screenshot" alt="Operation" src="assets/img/manufacturing/operation.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/manufacturing/production-order.md b/erpnext/docs/user/guides/manufacturing/production-order.md
new file mode 100644
index 0000000..13c7143
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/production-order.md
@@ -0,0 +1,106 @@
+Production Order (also called as Work Order) is a document that is given to
+the manufacturing shop floor by the Production Planner as a signal to produce
+a certain quantity of a certain Item. Production Order also helps to generate
+the material requirements (Stock Entry) for the Item to be produced from its
+**Bill of Materials**.
+
+The **Production Order** is generated from the **Production Planning
+Tool** based on Sales Orders. You can also create a direct Production Order
+by:
+
+> Manufacturing > Documents > Production Order > New
+
+<img class="screenshot" alt="Production Order" src="assets/img/manufacturing/production-order.png">
+
+### Creating Production Orders
+
+  * Select the Item to be produced.
+  * The default BOM for that item will be fetched by the system. You can also change BOM.
+  * If the selected BOM has operartion mentioned in it, the system shall fetch all operations from BOM.
+  * Mention the Planned Start Date (an Estimated Date at which you want the Production to begin.)
+  * Select Warehouses. Work-in-Progress Warehouse is where your Items will be transferred when you begin production and Target Warehouse is  where you store finished Items before they are shipped.
+
+> Note : You can save a Production Order without selecting the warehouses, but warehouses are mandatory for submitting a Production Order
+
+###Reassigning Workstation/Duration for Operations
+
+* By default the system fetchs workstation and duration for Production Order Operations from the selected BOM.
+
+<img class="screenshot" alt="PO Opeartions" src="assets/img/manufacturing/PO-operations.png">
+
+* If you wish to reassign the wrokstation for a particular opeeration in the Production Order, you can do so before submitting the Production Order.
+
+<img class="screenshot" alt="PO reassigning Operations" src="assets/img/manufacturing/PO-reassigning-operations.png">
+
+* Select the respective operation, and change its workstation.
+* You can also change the Operating Time for that operation
+
+### Capacity Planning in Production Order
+
+* When a Production Order is submitted, based on the Planned Start Date and the availability of the workstations, system schedules all operations for the Production Order (if Production Order has operations specified).
+* Drafts of Time Logs are also created based on the scheduled operations.
+
+### Transfering Materials for Manufacturing
+
+* Once you have submitted your Production Order, you need to Transfer the Raw Materials to initiate the Manufacturing Process.
+* This will create a Stock Entry with all the Items required to complete this Production Order to be added to the WIP Warehouse. (this will add sub-Items with BOM as one Item or explode their children based on your setting above).
+
+* Click on 'Transfer Materials for Manufacturing'.
+
+<img class="screenshot" alt="Transfer Materials" src="assets/img/manufacturing/PO-material-transfer.png">
+
+* Mention the quantity of materials to be transfered.
+
+<img class="screenshot" alt="Material Transfer Qty" src="assets/img/manufacturing/PO-material-transfer-qty.png">
+
+* Submit the Stock Entry
+
+<img class="screenshot" alt="Stock Entry for PO" src="assets/img/manufacturing/PO-SE-for-material-transfer.png">
+
+* Material Transfered for Manufacturing will be updated in the Production Order based on the Stock Entry.
+
+<img class="screenshot" alt="Stock Entry for PO" src="assets/img/manufacturing/PO-material-transfer-updated.png">
+
+### Making Time Logs
+
+* Progress in the Production Order can be tracked using [Time Log](/contents/projects/time-log)
+* Time Logs are created against Production Order Operations.
+* Drafts of Time Logs are also created based on the scheduled operations when an Production Order is Submitted.
+* To create more Time Logs against an operation select 'Make TIme Log' in the respective operation.
+
+<img class="screenshot" alt="Make TL against PO" src="assets/img/manufacturing/PO-operations-make-tl.png">
+
+###Updating Finished Goods
+
+* Once you are done with the Production Order you need to update the Finished Goods.
+* This will create a Stock Entry that will deduct all the sub-Items from the WIP Warehouse and add them to the Finished Goods Warehouse.
+* Click on 'Update Finished Goods'.
+
+<img class="screenshot" alt="Update Finished Goods" src="assets/img/manufacturing/PO-FG-update.png">
+
+* Mention the quantity of materials to be transfered.
+
+<img class="screenshot" alt="Update Finished Goods Qty" src="assets/img/manufacturing/PO-FG-update-qty.png">
+
+ > Tip : You can also partially complete a Production Order by updating the Finished Goods stock creating a Stock Entry.
+ 
+### Stopping a Production Order
+
+* When you stop a Production Order its status is changed to Stop indicating that all production process against that Production Order is to be ceased.
+* To stop the Production Order click on the 'stop' Button
+
+  1. On Submitting the Production Order, the system will reserve a slot for each of the Production Order Operations serially after the planned start date based on the workstation availability. The Workstation availability depends on the Workstation timings, holiday list and if some other Production Order Operation was scheduled in that slot. You can mention the number of days for the system to try scheduling the operations in the Manufacturing Settings. This is set to 30 Days by default. If the operation requires time exceeding the available slot, system shall ask you to break the operations. Once the scheduling is done system shall create Time Logs and save them. You can Modify them and submit them later.
+  2. You can also create additional time logs against an Operation. For doing so select the respective operation and click on 'Make Time Log'
+  3. Transfer Raw Material: This will create a Stock Entry with all the Items required to complete this Production Order to be added to the WIP Warehouse. (this will add sub-Items with BOM as one Item or explode their children based on your setting above).
+  4. Update Finished Goods: This will create a Stock Entry that will deduct all the sub-Items from the WIP Warehouse and add them to the Finished Goods Warehouse.
+  5. To check all Time Logs made against the Production Order click on 'Show Time Logs'
+
+<img class="screenshot" alt="PO - stop" src="assets/img/manufacturing/PO-stop.png">
+
+* You can Also re-start a stopped Production Order.
+
+> Note : In order to make a Production Order against an Item you must specify 'Yes' to "Allow Production Order" on the Item form.
+
+> Note : In order to make a Production Order against an Item you must specify 'Yes' to "Allow Production Order" on the Item form.
+
+{next}
diff --git a/erpnext/docs/user/manufacturing/setup/index.md b/erpnext/docs/user/guides/manufacturing/setup/index.md
similarity index 100%
rename from erpnext/docs/user/manufacturing/setup/index.md
rename to erpnext/docs/user/guides/manufacturing/setup/index.md
diff --git a/erpnext/docs/user/manufacturing/setup/index.txt b/erpnext/docs/user/guides/manufacturing/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/manufacturing/setup/index.txt
rename to erpnext/docs/user/guides/manufacturing/setup/index.txt
diff --git a/erpnext/docs/user/guides/manufacturing/setup/manufacturing-settings.md b/erpnext/docs/user/guides/manufacturing/setup/manufacturing-settings.md
new file mode 100644
index 0000000..39cf23e
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/setup/manufacturing-settings.md
@@ -0,0 +1,15 @@
+* Manufacturing Settings can be found at 
+
+> Manufacturing > Production Order > Setup > Manufacturing Settings
+
+<img class="screenshot" alt="Manufacturing Settings" src="assets/img/manufacturing/manufacturing-settings.png">
+
+* Allow Overtime - Specify if workstations are to allow overtime.(schedule operations outside working hours)
+
+* Allow Production on Holidays - Specify if system is to allow scheduling of operations on Holidays.
+
+* Capacity Planning for (Days) - Specify no. of Days for Capacity Planning.
+
+* Time Between Operations (in mins) - Specify the gap between two Production Operations.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/manufacturing/subcontracting.md b/erpnext/docs/user/guides/manufacturing/subcontracting.md
new file mode 100644
index 0000000..36286a7
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/subcontracting.md
@@ -0,0 +1,40 @@
+Subcontracting is a type of job contract that seeks to outsource certain types
+of work to other companies. It allows work on more than one phase of the
+project to be done at once, often leading to a quicker completion.
+Subcontracting is practiced by various industries. For example, manufacturers
+making a number of products from complex components subcontract certain
+components and package them at their facilities.  
+
+If your business involves outsourcing certain processes to a third party
+Supplier, where you buy the raw material from, you can track this by using the
+sub-contracting feature of ERPNext.  
+
+### Setup Sub-Contracting:
+
+  1. Create separate Items for the unprocessed and the processed product. For example if you supply unpainted X to your Supplier and the Supplier returns you X, you can create two Items: “X-unpainted” and “X”.
+  2. Create a Warehouse for your Supplier so that you can keep track of Items supplied. (you may supply a months worth of Items in one go).
+  3. For the processed Item, in the Item master, set “Is Sub Contracted Item” to “Yes”.
+
+![Subcontract](assets/old_images/erpnext/subcontract.png)
+
+  
+
+__Step 1:__ Make a Bill of Materials for the processed Item, with the unprocessed
+Items as sub-items. For example, If you are manufacturing a pen, the processed
+pen will be named under Bill of Materials(BOM), whereas, the refill, knob, and
+other items which go into the making of pen, will be categorized as sub-items.
+
+__Step 2:__ Make a Purchase Order for the processed Item. When you “Save”, in the “Raw Materials Supplied”, all your un-processed Items will be updated based on your Bill of Materials.
+
+__Step 3:__ Make a Stock Entry to deliver the raw material Items to your Supplier.
+
+__Step 4:__ Receive the Items from your Supplier via Purchase Receipt. Make sure to check the “Consumed Quantity” in the “Raw Materials” table so that the
+correct stock is maintained at the Supplier’s end.
+
+> Note 1: Make sure that the “Rate” of processed Item is the processing rate
+(excluding the raw material rate).
+
+> Note 2: ERPNext will automatically add the raw material rate for your
+valuation purpose when you receive the finished Item in your stock.
+
+{next}
diff --git a/erpnext/docs/user/guides/manufacturing/tools/bom-replace-tool.md b/erpnext/docs/user/guides/manufacturing/tools/bom-replace-tool.md
new file mode 100644
index 0000000..f5b6eb8
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/tools/bom-replace-tool.md
@@ -0,0 +1,44 @@
+# BOM Replace Tool
+
+Replace BOM is the utility to replace BOM of sub-assembly item, which is already updated in the BOM of Finished Good item.
+
+To use the Production Planning Tool, go to:
+
+> Manufacturing > Tools > BOM Replace Tool
+
+Let's consider a scenario to understand this better.
+
+If company manufactures computers, Bill of Material of its finished item will constitute of:
+
+1. Monitor
+1. Key Board
+1. Mouse
+1. CPU
+
+Out of all the items above, CPU is asembled separately. Hence separate BOM will be created for the CPU. Following are the items from the BOM of CPU.
+
+1. 250 GB Hard Disk
+1. Mother Board
+1. Processor
+1. SMTP
+1. DVD player
+
+If we have more items to be added , or existing items to be edited in the BOM of CPU, then we should create new BOM for it.
+
+1. _350 GB Hard Disk_
+1. Mother Board
+1. Processor
+1. SMTP
+1. DVD player
+
+To update new BOM updated in the BOM of finished item, where CPU is selected as raw-material, you can use BOM Replace tool.
+
+<img class="screenshot" alt="BOM replace Tool" src="assets/img/manufacturing/bom-replace-tool.png">
+
+In this tool, you should select Current BOM, and New BOM. On clicking Replace button, current BOM of CPU will be replaced with New BOM in the BOM of finished Item (Computer).
+
+**Will BOM Replace Tool work for replacing finsihed item in BOM?**
+
+No. You should Cancel and Amend current BOM, or create a new BOM for finished item.
+
+{next}
diff --git a/erpnext/docs/user/manufacturing/tools/index.md b/erpnext/docs/user/guides/manufacturing/tools/index.md
similarity index 100%
rename from erpnext/docs/user/manufacturing/tools/index.md
rename to erpnext/docs/user/guides/manufacturing/tools/index.md
diff --git a/erpnext/docs/user/manufacturing/tools/index.txt b/erpnext/docs/user/guides/manufacturing/tools/index.txt
similarity index 100%
rename from erpnext/docs/user/manufacturing/tools/index.txt
rename to erpnext/docs/user/guides/manufacturing/tools/index.txt
diff --git a/erpnext/docs/user/guides/manufacturing/tools/production-planning-tool.md b/erpnext/docs/user/guides/manufacturing/tools/production-planning-tool.md
new file mode 100644
index 0000000..7a7790e
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/tools/production-planning-tool.md
@@ -0,0 +1,62 @@
+Production Planning Tool helps you plan production and purchase of Items for a
+period (usually a week or a month).
+
+This list of Items can be generated from the open Sales Orders in the system
+and will generate:
+
+  * Production Orders for each Item.
+  * Purchase Requests for Items whose Projected Quantity is likely to fall below zero.
+
+To use the Production Planning Tool, go to:
+
+> Manufacturing > Tools > Production Planning Tool
+
+<img class="screenshot" alt="Production Planing Tool" src="assets/img/manufacturing/ppt.png">
+
+
+
+#### Step 1: Select and get Sales Order
+
+* Select sales orders for MRP using filters (Time, Item, and Customer)
+* Click on Get Sales Order to generate a list.
+
+<img class="screenshot" alt="Production Planing Tool" src="assets/img/manufacturing/ppt-get-sales-orders.png">
+
+
+
+#### Step 2: Get Item from Sales Orders.
+
+You can add/remove or change quantity of these Items.
+
+<img class="screenshot" alt="Production Planing Tool" src="assets/img/manufacturing/ppt-get-item.png">
+
+#### Step 3: Create Production Orders
+
+<img class="screenshot" alt="Production Planing Tool" src="assets/img/manufacturing/ppt-create-production-order.png">
+
+
+
+#### Step 4: Create Material Request
+
+Create Material Request for Items with projected shortfall.
+
+<img class="screenshot" alt="Production Planing Tool" src="assets/img/manufacturing/ppt-create-material-request.png">
+
+
+
+The Production Planning Tool is used in two stages:
+
+  * Selection of Open Sales Orders for the period based on “Expected Delivery Date”.
+  * Selection of Items from those Sales Orders.
+
+The tool will update if you have already created Production Orders for a
+particular Item against its Sales Order (“Planned Quantity”).
+
+You can always edit the Item list and increase / reduce quantities to plan
+your production.
+
+> Note: How do you change a Production Plan? The output of the Production
+Planning Tool is the Production Order. Once your orders are created, you can
+change them by amending the Production Orders.
+
+{next}
diff --git a/erpnext/docs/user/guides/manufacturing/workstation.md b/erpnext/docs/user/guides/manufacturing/workstation.md
new file mode 100644
index 0000000..864d116
--- /dev/null
+++ b/erpnext/docs/user/guides/manufacturing/workstation.md
@@ -0,0 +1,19 @@
+### Workstation
+
+Workstation stores information regarding the place where the workstation operations is carried out.
+Data regarding the operation cost of the place can be stored here.
+We can also specify the workstation operation timings and a Holiday List.
+
+You can also create a Workstation by:
+
+> Manufacturing > Documents > Workstation > New
+
+<img class="screenshot" alt="Workstation" src="assets/img/manufacturing/workstation.png">
+
+In workstation specify the workstation working hours under the 'working hour' section. 
+You can also specify the working hours based on shifts.
+While scheduling Production Order, system will check for the availability of the workstation based on the working hours specified.	
+
+> Note : You can enable overtime for your workstation in [Manufacturing Settings](/contents/manufacturing/setup/manufacturing-settings)
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/projects/activity-cost.md b/erpnext/docs/user/guides/projects/activity-cost.md
new file mode 100644
index 0000000..7926953
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/activity-cost.md
@@ -0,0 +1,4 @@
+Activity Cost records the per-hour billing rate and costing rate of an Employee against an Activity Type.
+This rate is pulled by the system while making Time Logs. It is used for Project Costing.
+
+<img class="screenshot" alt="Activity Cost" src="assets/img/project/activity_cost.png">
diff --git a/erpnext/docs/user/guides/projects/activity-type.md b/erpnext/docs/user/guides/projects/activity-type.md
new file mode 100644
index 0000000..62010f0
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/activity-type.md
@@ -0,0 +1,13 @@
+Activity Type makes a list of the different types of activities against which a Time Log can be made.
+
+<img class="screenshot" alt="Activity Type" src="assets/img/project/activity_type.png">
+
+By default the following Activity Types are created.
+
+* Planning
+* Research
+* Proposal Writing
+* Execution
+* Communication
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/projects/index.md b/erpnext/docs/user/guides/projects/index.md
similarity index 100%
rename from erpnext/docs/user/projects/index.md
rename to erpnext/docs/user/guides/projects/index.md
diff --git a/erpnext/docs/user/projects/index.txt b/erpnext/docs/user/guides/projects/index.txt
similarity index 100%
rename from erpnext/docs/user/projects/index.txt
rename to erpnext/docs/user/guides/projects/index.txt
diff --git a/erpnext/docs/user/projects/introduction-to-projects.md b/erpnext/docs/user/guides/projects/introduction-to-projects.md
similarity index 100%
rename from erpnext/docs/user/projects/introduction-to-projects.md
rename to erpnext/docs/user/guides/projects/introduction-to-projects.md
diff --git a/erpnext/docs/user/guides/projects/project.md b/erpnext/docs/user/guides/projects/project.md
new file mode 100644
index 0000000..4d4a45d
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/project.md
@@ -0,0 +1,87 @@
+Project management in ERPNext is Task driven. You can create Project and assign multiple Tasks against it.
+
+<img class="screenshot" alt="Project" src="assets/img/project/project.png">
+
+### Managing tasks
+Project can be divided into multiple Tasks.
+Task can be created via Project document itself or can be created via  [Task](/contents/projects/tasks)
+
+<img class="screenshot" alt="Project" src="assets/img/project/project_task.png">
+
+* To view Task made against a Project click on 'Tasks'
+
+<img class="screenshot" alt="Project - View Task" src="assets/img/project/project_view_task.png">
+
+<img class="screenshot" alt="Project - Task List" src="assets/img/project/project_task_list.png">
+
+* You can also view the Tasks from the Project document itself
+
+<img class="screenshot" alt="Project - Task Grid" src="assets/img/project/project_task_grid.png">
+
+### Managing time
+
+ERPNext uses [Time Log](/contents/projects/time-log) to track the progress of a Project.
+You can create Time Logs against each task.
+The Actual Start and End Time along with the costing shall then be updated based on the Time Log.
+
+* To view Time Log made against a Project click on 'Time Logs'
+
+<img class="screenshot" alt="Project - View Time Log" src="assets/img/project/project_view_time_log.png">
+
+<img class="screenshot" alt="Project - Time Log List" src="assets/img/project/project_time_log_list.png">
+
+* You can also create a Time Log directlly and link it to the Project.
+
+<img class="screenshot" alt="Project - Link Time Log" src="assets/img/project/project_time_log_link.png">
+
+### Managing expenses
+
+You can book [Expense Claim](/contents/human-resources/expense-claim) against a project task.
+The system shall update the total amount from expense claims in the project costing section.
+
+* To view Expense Claims made against a Project click on 'Expense Claims'
+
+<img class="screenshot" alt="Project - View Expense Claim" src="assets/img/project/project_view_expense_claim.png">
+
+* You can also create a Expense Claims directlly and link it to the Project.
+
+<img class="screenshot" alt="Project - Link Expense Claim" src="assets/img/project/project_expense_claim_link.png">
+
+* Total amount of Expense Claims booked against a project is shown under 'Total Expense Claim' in the Project Costing Section
+
+<img class="screenshot" alt="Project - Total Expense Claim" src="assets/img/project/project_total_expense_claim.png">
+
+### Cost Center
+
+You can make a [Cost Center](/contents/accounts/setup/cost-center) against a Project or use an existing cost center to track all expenses made against that project.
+
+<img class="screenshot" alt="Project - Cost Center" src="assets/img/project/project_cost_center.png">
+
+###Project Costing
+
+The Project Costing section helps you track the time and expenses incurred against the project.
+
+<img class="screenshot" alt="Project - Costing" src="assets/img/project/project_costing.png">
+
+* The Costing Section is updated based on Time Logs made.
+
+* Gross Margin is the difference between Total Costing Amount and Total Billing Amount
+
+###Billing
+
+You can make/link a [Sales Order](/contents/selling/sales-order) against a project. Once linked you can use the standard sales module to bill your customer against the Project.
+
+<img class="screenshot" alt="Project - Sales Order" src="assets/img/project/project_sales_order.png">
+
+###Gantt Chart
+
+A Gantt Chart illustrates a project schedule.
+ERPNext gives you a illustrated view of tasks scheduled against that project in Gantt Chart View.
+
+* To view gantt chart against a project, go to that project and click on 'Gantt Chart'
+
+<img class="screenshot" alt="Project - View Gantt Chart" src="assets/img/project/project_view_gantt_chart.png">
+
+<img class="screenshot" alt="Project - Gantt Chart" src="assets/img/project/project_gantt_chart.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/projects/tasks.md b/erpnext/docs/user/guides/projects/tasks.md
new file mode 100644
index 0000000..574a588
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/tasks.md
@@ -0,0 +1,59 @@
+Project is divided into Tasks. 
+In ERPNext, you can also create a Task independently.
+
+<img class="screenshot" alt="Task" src="assets/img/project/task.png">
+
+### Status of the Task
+
+A Task can have either of the following status - Open, Working, Pending Review, Closed, Cancelled.
+
+<img class="screenshot" alt="Task - Status" src="assets/img/project/task_status.png">
+
+* By default each new Task created shall have the status set to 'Open'.
+
+* If a Time Log is made against a task, its status shall be set to 'Working'.
+
+### Dependent Task
+
+You can specify a list of dependent task under the 'Depends On' section.
+
+<img class="screenshot" alt="Depends On" src="assets/img/project/task_depends_on.png">
+
+* You cannot close the parent Task until all 'Dependant Task' are closed.
+
+* If the Dependent Task are delayed and overlap with the expected Start Date of the Parent task, the system will reschedule the parent task.
+
+### Managing Time
+
+ERPNext uses [Time Log](/contents/projects/time-log) to track the progress of a Task.
+You can create multiple Time Logs against each task.
+The Actual Start and End Time along with the costing shall then be updated based on the Time Log.
+
+* To view Time Log made against a Task click on 'Time Logs'
+
+<img class="screenshot" alt="Task - View Time Log" src="assets/img/project/task_view_time_log.png">
+
+<img class="screenshot" alt="Task - Time Log List" src="assets/img/project/task_time_log_list.png">
+
+* You can also create a Time Log directlly and link it to the Task.
+
+<img class="screenshot" alt="Task - Link Time Log" src="assets/img/project/task_time_log_link.png">
+
+### Managing Expenses
+
+You can book [Expense Claim](/contents/human-resource-management/expense-claim) against a task.
+The system shall update the total amount from expense claims in the costing section.
+
+* To view Expense Claims made against a Task click on 'Expense Claims'
+
+<img class="screenshot" alt="Task - View Expense Claim" src="assets/img/project/task_view_expense_claim.png">
+
+* You can also create a Expense Claims directlly and link it to the Task.
+
+<img class="screenshot" alt="Task - Link Expense Claim" src="assets/img/project/task_expense_claim_link.png">
+
+* Total amount of Expense Claims booked against a task is shown under 'Total Expense Claim' in the Task Costing Section
+
+<img class="screenshot" alt="Task - Total Expense Claim" src="assets/img/project/task_total_expense_claim.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/projects/time-log-batch.md b/erpnext/docs/user/guides/projects/time-log-batch.md
new file mode 100644
index 0000000..4135bb1
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/time-log-batch.md
@@ -0,0 +1,23 @@
+You can bill Time Logs by batching them together. This gives you the flexiblity to manage your customer billing in the way you want. To create a new Time Log Batch, go to 
+
+> Projects > Time Log Batch > New Time Log Batch
+
+OR
+
+Just open your Time Log list and check the Items to you want to add to the Time Log. Then click on "Make Time Log Batch" button and these Time Logs will be selected.
+
+<img class="screenshot" alt="Time Log - Drag Calender" src="assets/img/project/time_log_batch.gif">
+
+###Making Sales Invoice
+
+* After submitting the Time Log Batch, "Make Invoice" button shall appear.
+
+<img class="screenshot" alt="Time Log - Drag Calender" src="assets/img/project/time_log_batch_make_invoice.png">
+
+* Click on that button to raise a Sales Invoice against the Time Log Batch.
+
+<img class="screenshot" alt="Time Log - Drag Calender" src="assets/img/project/time_log_batch_sales_invoice.png">
+
+* When you "Submit" the Sales Invoice, the Sales Invoice number will get updated in the Time Logs and Time Log Batch and their status will change to "Billed".
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/projects/time-log.md b/erpnext/docs/user/guides/projects/time-log.md
new file mode 100644
index 0000000..a299b52
--- /dev/null
+++ b/erpnext/docs/user/guides/projects/time-log.md
@@ -0,0 +1,49 @@
+Time Logs are a way to track time worked.
+They can be used to track the following
+
+* Billable work to Customers
+* Production Order Operations
+* Tasks
+* Project
+* Internal References
+
+<img class="screenshot" alt="Time Log" src="assets/img/project/time_log.png">
+
+###Creating Time Logs
+
+1. To create a new Time Log, you can go to 
+> Projects > Time Log > new Time Log
+
+2. You can also create a new Time Log via Calendar
+
+To create Time Logs via Calender, go to Time Log and select Calendar.
+
+<img class="screenshot" alt="Time Log - View Calender" src="assets/img/project/time_log_view_calendar.png">
+
+* To create a Time Log for multiple days, click and drag the cursor across days.
+
+<img class="screenshot" alt="Time Log - Drag Calender" src="assets/img/project/time_log_calendar_day.gif">
+
+* You can also create Time Logs from 'week' and 'day' view of the calender.
+
+<img class="screenshot" alt="Time Log - Drag Calender" src="assets/img/project/time_log_calendar_week.gif">
+
+* Time Logs for Manufacturing processes needs to be created from the Production Order. 
+* To create more Time Logs against Operations select the respective operation and click on the 'Make Time Log' button.
+
+###Billing using Time Logs
+
+* If you wish to bill against a Time Log you need to select the 'Billable' option.
+
+* In the costing section, the system will pull up the Costing & Billing rate from [Activity Cost](/contents/projects/activity-cost) 
+	based on the Employee and Activity Type specified.
+
+* The system shall then calculate the Costing and Billing amount based on the Hours mentioned in the Time Log.
+
+* If 'Billable' is not selected, the system shall display the 'Billing Amount' as 0.
+
+<img class="screenshot" alt="Time Log - Costing" src="assets/img/project/time_log_costing.png">
+
+* After submitting the Time Log, you need to create [Time Log batch](/contents/projects/time-log-batch) to further bill the Time Log.
+
+{next}
diff --git a/erpnext/docs/user/selling/index.md b/erpnext/docs/user/guides/selling/index.md
similarity index 100%
rename from erpnext/docs/user/selling/index.md
rename to erpnext/docs/user/guides/selling/index.md
diff --git a/erpnext/docs/user/selling/index.txt b/erpnext/docs/user/guides/selling/index.txt
similarity index 100%
rename from erpnext/docs/user/selling/index.txt
rename to erpnext/docs/user/guides/selling/index.txt
diff --git a/erpnext/docs/user/guides/selling/quotation.md b/erpnext/docs/user/guides/selling/quotation.md
new file mode 100644
index 0000000..b260d90
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/quotation.md
@@ -0,0 +1,89 @@
+During a sale, the customer may request for a written note about the products
+or services you are planning to offer, along with the prices and other terms
+of engagement. This is called a “Proposal” or an “Estimate” or a “Pro Forma
+Invoice”or a Quotation.
+
+To create a new Quotation go to:
+
+> Selling > Quotation > New Quotation
+
+###Creating Quotation from Oppurtunity
+
+You can also create a Quotation from an Opportunity.
+
+<img class="screenshot" alt="Make Quotation from Opportunity" src="assets/img/selling/make-quote-from-opp.png">
+
+Or You can create a new Quotation and pull details from an Opportunity.
+
+<img class="screenshot" alt="Make Quotation from Opportunity" src="assets/img/selling/make-quotation.gif">
+
+A Quotation contains details about:
+
+  * The recipient of the Quotation
+  * The Items and quantities you are offering.
+  * The rates at which they are offered. For details refer 
+  * The taxes applicable.
+  * Other charges (like shipping, insurance) if applicable.
+  * The validity of contract.
+  * The time of delivery.
+  * Other conditions.
+
+> Tip: Images look great on Quotations. To add images to your Quotations,
+attach the corresponding image in the Item master.
+
+### Rates
+
+The rates you quote may depend on two things.
+
+  * The Price List: If you have multiple Price Lists, you can select a Price List or tag it to the Customer (so that it is auto-selected). Your Item prices will automatically be updated from the Price List.For details refer [Price List](/contents/setting-up/price-lists)
+
+  * The Currency: If you are quoting to a Customer in a different currency, you will have to update the conversion rates to enable ERPNext to save the information in your standard Currency. This will help you to analyze the value of your Quotations in standard Currency.
+
+### Taxes
+
+To add taxes to your Quotation, you can either select a tax template, Sales
+Taxes and Charges Template or add the taxes on your own. To understand taxes in
+detail visit [Taxes](/contents/setting-up/setting-up-taxes)
+
+You can add taxes in the same manner as the Sales Taxes and Charges Template.
+
+### Terms and Conditions
+
+Each Quotation must ideally contain a set of terms, of your contract. It is
+usually a good idea to make templates of your Terms and Conditions, so that
+you have a standard set of terms. You can do this by going to:
+
+> Selling > Terms and Conditions
+
+#### What should Terms and Conditions Contain?
+
+  * Validity of the offer.
+  * Payment Terms (In Advance, On Credit, part advance etc).
+  * What is extra (or payable by the Customer).
+  * Safety / usage warning.
+  * Warranty if any.
+  * Returns Policy.
+  * Terms of shipping, if applicable.
+  * Ways of addressing disputes, indemnity, liability, etc.
+  * Address and Contact of your Company.
+
+### Submission
+
+Quotation is a “Submittable” transaction. Since you send this Quotation to
+your Customer or Lead, you must freeze it so that changes are not made after
+you send the Quotation. See Document Stages.
+
+> Tip: Quotations can also be titled as “Proforma Invoice” or “Proposal”.
+Select the right heading in the “Print Heading” field in the “More Info”
+section. To create new Print Headings go to Setup > Branding and Printing >
+Print Headings.
+
+### Discount
+
+While making your sales transactions like a Quotation (or Sales Order) you
+would already have noticed that there is a “Discount” column. On the left is
+the “Price List Rate” on the right is the “Basic Rate”. You can add a
+“Discount” value to update the basic rate. To understand more about discount
+read [Discount.](http://erpnext.org/discount)
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/sales-order.md b/erpnext/docs/user/guides/selling/sales-order.md
new file mode 100644
index 0000000..313f46e
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/sales-order.md
@@ -0,0 +1,119 @@
+# Sales Order
+
+The Sales Order confirms your sales and triggers purchase (**Material
+Request**) shipment (**Delivery Note**), billing (**Sales Invoice**) and
+manufacturing (**Production Plan**)
+
+A Sales Order is usually a binding Contract with your Customer.
+
+Once your customer confirms the Quotation you can convert your Quotation into
+a Sales Order.
+
+### Sales Order Flow-Chart
+
+![Sales Order](assets/old_images/erpnext/sales-order-f.jpg)
+
+To create a new Sales Order go to:
+
+> Selling > Sales Order > New Sales Order
+
+### Creating Sales Order from Quotation
+
+You can also create a Sales Order from a submitted Quotation.
+
+<img class="screenshot" alt="Make Sales Order from Quotation" src="assets/img/selling/make-SO-from-quote.png">
+
+Or you can create a new Sales Order and pull details from an Quotation.
+
+<img class="screenshot" alt="Make Sales Order from Quotation" src="assets/img/selling/make-so.gif">
+
+Most of the information in your Sales Order is the same as the Quotation.
+There are a few amongst other things that a Sales Order will ask you to
+update.
+
+  * Expected date of delivery.
+  * Customer Purchase Order number: If your customer has sent you a Purchase Order, you can update its number for future reference (in billing).
+
+### Packing List
+
+The “Packing List” table will be automatically updated when you “Save” the
+Sales Order. If any Items in your table are Product Bundle (packets), then the
+“Packing List” will contain the exploded (detailed) list of your Items.
+
+### Reservation and Warehouses
+
+If your Sales Order contains Items for which inventory is tracked (Is Stock
+Item is “Yes”) then, ERPNext will ask you for “Reservation Warehouse”. If you
+have set a default Warehouse for the Item, it will automatically set this
+Warehouse here.
+
+This “reserved” quantity will help you project what is the quantity you need
+to purchase based on all your commitments.
+
+### Sales Team
+
+**Sales Partner:** If this Sale was booked via a Sales Partner, you can update the Sales Partner’s details with commission and other info that you can aggregate.
+
+**Sales Persons:** ERPNext allows you to tag multiple Sales Persons who may have worked on this deal. You can also split the amount in targets of different Sales Persons and track how much incentives they earned on this deal.
+
+### Recurring Sales Orders
+
+If you have a recurring contract with a Customer where you are required to generate a Sales Order on a monthly, quarterly, half-yearly or annual basis, you can check the “Convert To Recurring Order” box. 
+
+Here you can fill in the details like; of how frequently you want to generate an Order in the 'Recurring Type' field, specify the day of of the month on which the Order needs to be generated in the 'Repeat On Day Of Month' field and the date on which the recurring orders should stop in the 'End Date' field.
+
+**Recurring Type:** Here you can update how frequently you want to generate an Order.
+
+**Repeat On Day Of Month:** You can specify the day of of the month on which the Order needs to be generated.
+
+**End Date:** The date on which the recurring orders should stop can be specified here.
+
+On updating the Sales Order, a Recurring ID will be generated which will be same for all recurring orders generated from this particular Sales Order.
+
+ERPNext will automatically create new Order and mail a notification to the email IDs you set in the 'Notification Email Address'field.
+
+<img class="screenshot" alt="Reccuring Sales Order" src="assets/img/selling/recurring-sales-order.png">
+
+### Next Steps
+
+Once you “Submit” your Sales Order, you can now trigger different aspects of
+your organization:
+
+  * To begin purchase click on “Make Purchase Request”
+  * To make a shipment entry click on “Make Delivery Note”
+  * To bill, make “Make Sales Invoice”
+  * To stop further process on this Sales Order, click on “Stop”
+
+### Submission
+
+Sales Order is a “Submittable” transaction. See Document Stages. You will be
+able to execute dependent steps (like making a Delivery Note) only after
+“Submitting” this Sales Order.
+
+### Sales Order with Order type Maintenance
+
+When the 'Order Type' of the Sales Order is 'Maintenance' follow the steps
+given below:
+
+__Step 1:__ Enter Currency, Price list and Item details.
+
+__Step 2:__ Mention taxes and other information.
+
+__Step 3:__ Save and Submit the form
+
+__Step 4:__ Once the form is submitted, the Action button will provide three
+choices.i) Maintenance Visit ii) Maintenance Schedule iii) Invoice.
+
+
+
+> **Note 1:**   
+By clicking on the Action button and selecting 'Maintenance Visit' you can directly fill the visit form. The Sales Order details will be fetched directly.    
+
+> **Note 2:**    
+By clicking on the Action button and selecting 'Maintenance Schedule' you can fill the schedule details. The Sales Order details will be fetched directly.
+
+> **Note 3:**    
+By clicking on the Invoice button you can make an Invoice for your
+services . The sales orders details will be fetched directly.
+
+{next}
diff --git a/erpnext/docs/user/selling/setup/index.md b/erpnext/docs/user/guides/selling/setup/index.md
similarity index 100%
rename from erpnext/docs/user/selling/setup/index.md
rename to erpnext/docs/user/guides/selling/setup/index.md
diff --git a/erpnext/docs/user/selling/setup/index.txt b/erpnext/docs/user/guides/selling/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/selling/setup/index.txt
rename to erpnext/docs/user/guides/selling/setup/index.txt
diff --git a/erpnext/docs/user/guides/selling/setup/item-price.md b/erpnext/docs/user/guides/selling/setup/item-price.md
new file mode 100644
index 0000000..1a25670
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/item-price.md
@@ -0,0 +1,43 @@
+Item Price is the record in which you can log sellig and buying rate of an item.
+
+There are two ways to reach to new Item Price form.
+
+> Selling/Buying/Stock >> Setup >> Item Price >> New Item Price
+
+Or
+
+> Item >> Add/Edit Prices >> Click on "+"  >> New Item Price
+
+Following are the steps to create new Item Price.
+
+Step 1: Select Price List
+
+You can create multiple Price List in ERPNext to track Selling and Buying Price List of an item separtely. Also if item's selling prices id changing based on territory, or due to other criteria, you can create multiple selling Price List for it.
+
+![Item Price list](assets/old_images/erpnext/item-price-list.png)
+
+On selection of Price List, its currency and for selling or buying property will be fetched as well.
+
+To have Item Price fetching in the sales or purchase transaction, you should have Price List id selected in the transaction, just above Item table.
+
+Step 2: Select Item
+
+Select item for which Item Price record is to be created. On selection of Item Code, Item Name and Description will be fetched as well.
+
+![Item Price Item](assets/old_images/erpnext/item-price-item.png)
+
+Step 3: Enter Rate
+
+Enter selling/buying rate of an item in Price List currency.
+
+![Item Price Rate](assets/old_images/erpnext/item-price-rate.png)
+
+Step 4: Save Item Price
+
+To check all Item Price together, go to:
+
+Stock >> Main Report >> Itemwise Price List Rate
+
+You will find option to create new Item Price record (+) in this report as well.
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/setup/product-bundle.md b/erpnext/docs/user/guides/selling/setup/product-bundle.md
new file mode 100644
index 0000000..2b83b0e
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/product-bundle.md
@@ -0,0 +1,47 @@
+#Product Bundle
+
+Product Bundle stands for Sales Bill-of-Material. It's a master where you can list item which are bundled together and 
+sold as one item. For instance, when laptop is delivered, you need to ensure that charger, mouse and laptop bag are 
+delivered and stock level of these items gets affected. To address this scenario, you can set create Product Bundle for 
+the main item, i.e. laptop, and list deliverable items i.e. laptop + charger + other accessories as child items.
+  
+Following are the steps on how to setup Product Bundle master, and how is it used in the sales transactions.
+
+####Create new Product Bundle
+
+To create new Product Bundle, Go to:
+
+Selling > Setup > Product Bundle > New
+
+<img class="screenshot" alt="Product Bundle" src="assets/img/selling/product-bundle.png">
+
+###Select Parent Item
+
+In Product Bundle master, there are two sections. Product Bundle Item and Package Item.
+
+In Product Bundle item, you will select a Parent Item. The parent item must be a <b>non-stock item</b>. 
+This is non-stock item because there is no stock maintained for it but only the Package Items. 
+If you want to maintain stock for the Parent Item, then you must create a regular Bill of Material (BOM) 
+and package them using a Stock Entry Transactions.
+
+###Select Child Items
+
+In Package Item section, you will list all the child items for which we maintain stock and is delivered to customer.
+
+###Product Bundle in the Sales Transactions
+
+When making Sales transactions like Sales Invoice, Sales Order and Delivery Note, 
+Parent Item will be selected in the main item table.
+
+<img class="screenshot" alt="Product Bundle" src="assets/img/selling/product-bundle.gif">
+
+On selection on Parent Item in the main item table, its child items will be fetched in Packing List 
+table of the transaction. If child item is the serialized item, you will be able to specify its Serial Mo. 
+in packing List table itself. On submission of transaction, system will reduce the stock level of child items from 
+warehouse specified in Packing List table.
+
+<div class="well"><b>Use Product Bundle to Manage Schemes:</b>
+<br>
+This work-around in Product Bundle was discovered when a customer dealing into nutrition product asked for feature to manage schemes like "Buy One Get One Free". To manage the same, he created a non-stock item which was used as Parent Item. In description of item, he entered scheme details with items image indicating the offer. The saleable product was selected in Package Item where qty was two. Hence every time they sold one qty of Parent item under scheme, system deducted two quantities of product from Warehouse.</div>
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/setup/sales-partner.md b/erpnext/docs/user/guides/selling/setup/sales-partner.md
new file mode 100644
index 0000000..820caed
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/sales-partner.md
@@ -0,0 +1,34 @@
+People who assist you in getting business are termed as Sales Partners. Sales Partners can be represented by different names in ERPNext. You can call them Channel Partner, Distributor, Dealer, Agent, Retailer, Implementation Partner, Reseller etc.
+
+For each Sales Partner, you can define commission offer to them. When Sales Partner is selected in transactions, there commission is calculated over Net Total of Sales Order/Invoice or Delivery Note.
+
+You can track Sales Personwise commission in the report under Selling module.
+
+To create a sales partner go to:
+
+`Selling > Setup > Sales Partner`
+
+Sales Partners are saved with Sales Partner name provided by user.
+
+<img class="screenshot" alt="Sales Partner" src="assets/img/selling/sales-partner.png">
+
+You can track their address and contact details and also allocate Sales Partner for each Item Group, based on Qty and Amount.
+
+### Including Sales Partners in Your Website
+
+To include the name of your Partner on your website, check the "Show in
+Website" box. When click on "Show in Website", you will see field where you can attach logo of partner's company and enter brief and introduction of partner.
+
+<img class="screenshot" alt="Sales Partner" src="assets/img/selling/sales-partner-website.png">
+
+To see listing of partner, you should go to:
+
+https://example.erpnext.com/partners
+
+![Sales Partner Listing](assets/old_images/erpnext/sales-partner-listing.png)
+
+Following is the complete partners details published on the website.
+
+![Sales Partner Published](assets/old_images/erpnext/sales-partner-published.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/setup/sales-person-target-allocation.md b/erpnext/docs/user/guides/selling/setup/sales-person-target-allocation.md
new file mode 100644
index 0000000..1da5ada
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/sales-person-target-allocation.md
@@ -0,0 +1,86 @@
+With management of Sales Person, ERPNext also allow you to assign target to Sales Persons based on Item Group and Territory. Based on target allocated and actual sales booked by Sales Person, you will get target variance report for the Sales Person.
+
+###1. Sales Person - Item Groupwise Target Allocation
+
+####1.1 Open Sales Person's Master
+
+To allocate target, you should open specific Sales Person master.
+
+`Selling > Setup > Sales Person > (Open Sales Person)`
+
+####1.2 Allocate Item Groupwise Target
+
+In the Sales Person master, you will find table called Sales Person Target.
+
+![Sales Person Target Item Group](assets/old_images/erpnext/sales-person-target-item-group.png)
+
+In this table, you should select Item Group, Fiscal Year, Target Qty and Amount. 
+
+<div class=well>You can give target in amount or quantity, or in both. Item Group can also be left blank. In this case the system will calculate target based on all the Items.</div>
+
+####1.3 Target Distribution
+
+If you wish to spread allocated target across months, then you shoult setup Target Distribution master, and select it in the Sales Person master. Considering our example, target for the month of December will be set as 5 qty (10% of total allocation).
+
+![Sales Person Target Distribution](assets/old_images/erpnext/sales-person-target-distribution.png)
+
+####Report - Sales Person Target Variance Item Groupwise
+
+To check this report, go to:
+
+`Selling > Standard Report > Sales Person Target Variance (Item Group-wise)'
+
+This report will provide you variance between target and actual performance of Sales Person. This report is based on Sales Order report.
+
+![Sales Person Item Group Report](assets/old_images/erpnext/sales-person-item-group-report.png)
+
+As per the report, allocated target to Sales Person for the month of December was 5 qty. However, Sales Order was made for this employee and Item Group for only 3 qty. Hence, variance of 2 qty is shown in the report.
+
+---
+
+###2. Sales Person - Territorywise Target Allocation
+
+To allocate target to Sales Person based on Territory, you can should select specific Sales Person in the Territory master. This Sales Person is entered just for the reference. Sales Person details are not updated in the variance report of Territorywise Target Allocation.
+
+####2.1 Go to Territory master
+
+`Selling > Setup > Territory > (Open specific Territory master)`
+
+In the Territory master, you will find field to select Territory Manager. This field is linked to "Sales Person" master.
+
+![Sales Person Territory Manager](assets/old_images/erpnext/sales-person-territory-manager.png)
+
+####2.2 Allocating Target
+
+Allocation Target in the Territory master is same as in Sales Person master. You can follow same steps as given above to specify target in the Territory master as well.
+
+####2.3 Target Distribution
+
+Using this master, you can divide target Qty or Amount across various months.
+
+####2.4 Report - Territory Target Variance Item Groupwise
+
+This report will provide you variance between target and actual performance of Sales in particular territory. This report is based on Sales Order report. Though Sales Person is defined in the Territory master, its details are not pulled in the report.
+
+![Sales Person Territory Report](assets/old_images/erpnext/sales-person-territory-report.png)
+
+---
+
+###3. Target Distribution
+
+Target Distribution master allows you to divide allocated target across multiple months. If your product and services is seasonal, you can distribute the sales target accordingly. For example, if you are into umbrella business, then target allocated in the monsoon seasion will be higher than in other months.
+
+To create new Budget Distriibution master, go to:
+
+`Accounts > Setup > Budget Distributon`
+
+![Target Distribution](assets/old_images/erpnext/target-distribution.png)
+
+You can link target distribution while allocation targets in Sales Person as well as in Territory master.
+
+###See Also
+
+1. [Managing Sales Person](https://erpnext.com/selling/selling-setup/sales-person)
+2. [Using Sales Person in transactions](https://erpnext.com/kb/selling/managing-sales-persons-in-sales-transactions)
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/setup/selling-settings.md b/erpnext/docs/user/guides/selling/setup/selling-settings.md
new file mode 100644
index 0000000..0588511
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/selling-settings.md
@@ -0,0 +1,71 @@
+Selling Setting is where you can define propertiese which will be applied in your selling transactions. 
+Let's check into each property one by one.
+
+<img class="screenshot" alt="Selling Settings" src="assets/img/selling/selling-settings.png">
+
+####1. Customer Naming By
+
+When customer is saved, system generated unique ID for that Customer. Using that Customer ID, 
+you can select Customer in other transactions.
+
+Bydefault Customer will be saved with Customer Name. If you wish to save Customer using 
+a naming series, you should set Customer Naming By as "Naming Series".
+
+Example of Customer Id's saved in Naming Series - `CUST00001,CUST00002, CUST00003...` and so on.
+
+You can set Naming Series for customer naming from:
+
+> Setup > Settings > Naming Series`
+
+####2. Campaign Naming By
+
+Just like for Customer, you can also configure as how ID will be generated for the Campaign master. 
+Bydefault Campaign will be saved with Campaign Name provided while its creation.
+
+####3. Default Customer Group
+
+Customer Group in this field will be auto-updated when you open new Customer form.
+While converting Quotation created for Lead into Sales Order, system attempts to convert 
+Lead into Customer in the backend. While creating Customer in the backend, system pickup 
+Customer Group and Territory as defined in the Selling Setting. If system doesn't find 
+any values, then following validation message will be raised.
+To resolve this, you should:
+Either manually convert Lead into Customer, and define Customer Group and Territory manually while 
+creating Customer or define Default Customer Group and Territory in the Selling Setting. 
+Then you should have Lead automatically converted into Customer when convert Quotation into Sales Order.
+
+####4. Default Territory
+
+Territory defined in this field will be auto-updated in the Territory field of Customer master.
+
+Just like Customer Group, Territory is also checked when system tries creating Customer in the backend.
+
+####5. Default Price List
+
+Price List set in this field will be auto-updated in the Price List field of Sales transactions.
+
+####6. Sales Order Required
+
+If you wish to make Sales Order creation mandatory before creation of Sales Invoice, then you should 
+set Sales Order Required field as Yes. Bydefault, this will be "No" for a value.
+
+####7. Delivery Note Required
+
+To make Delivery Note creation as mandatory before Sales Invoice creation, you should set 
+this field as "Yes". It will be "No" by default.
+
+####8. Maintain Same Rate Throughout Sales Cycle
+
+System bydefault validates that item price will be same throughout sales cycle 
+(Sales Order - Delivery Note - Sales Invoice). If you could have item price changing within the cycle, 
+and you need to bypass validation of same rate throughout cycle, then you should uncheck this field and save.
+
+####9. Allow User to Edit Price List Rate in Transaction
+
+Item table of the sale transactions has field called Price List Rate. This field be non-editale 
+by default in all the sales transactions. This is to ensure that price of an item is fetched from 
+Item Price record, and user is not able to edit it.
+
+If you need to enable user to edit Item Price, fetched from Price List of an item, you should uncheck this field.
+
+{next}
diff --git a/erpnext/docs/user/guides/selling/setup/shipping-rule.md b/erpnext/docs/user/guides/selling/setup/shipping-rule.md
new file mode 100644
index 0000000..13dfe4c
--- /dev/null
+++ b/erpnext/docs/user/guides/selling/setup/shipping-rule.md
@@ -0,0 +1,6 @@
+Using Shipping Rule you can define the cost for delivering the product to the customer.
+You can define different shipping rules for the same item across different territories.
+
+<img class="screenshot" alt="Shipping Rule" src="assets/img/selling/shipping-rule.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/setting-up/authorization-rule.md b/erpnext/docs/user/guides/setting-up/authorization-rule.md
new file mode 100644
index 0000000..ae1e8ab
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/authorization-rule.md
@@ -0,0 +1,43 @@
+Authorization Rule is a tool to define rule for conditional authorization.
+
+If you sales and purchase transactions of higher value or discount requires an authorization from senior manager, you can set authorization rule for it.
+
+To create new Authorization Rule, go to:
+
+> Setup > Customize > Authorization Rule
+
+Let's consider an example of Authorization Rule to learn better.
+
+Assume that Sales Manager needs to authorize Sales Orders, only if its Grand Total value exceeds 10000. If Sales Orer values is less than 10000, then even Sales User will be able to submit it. It means Submit permision of Sales User will be restricted only upto Sales Order of Grand Total less than 10000.
+
+**Step 1:**
+
+Open new Authorization Rule
+
+**Step 2:**
+
+Select Company and Transaction on which Authorization Rule will be applicable. This functionality is available for limited transactions only.
+
+**Step 3:**
+
+Select Based On. Authorization Rule will be applied based on value selected in this field.
+
+**Step 4:**
+
+Select Role on whom this Authorization Rule will be applicable. As per the example considered, Sales User will be selected as Application To (Role). To be more specific you can also select Applicale To User, if you wish to apply to rule for specific Sales User, and not all Sales User. Its okay to not select Sales User, as its not mandatory.
+
+**Step 5:**
+
+Select approvers Role. It will be Sales Manager role which if assigned to user, will be able to submit Sales Order above 10000. Also you can select specific Sales Manager, and then rule should be applicable for that User only. Selecting Approving User field is not mandatory.
+
+**Step 6:**
+
+Set Above Value. Given the exmaple, Above Value will be set as 10000.
+
+<img class="screenshot" alt="Authorization Rule" src="assets/img/setup/auth-rule.png">
+
+If Sales User tries submitting Sales Order of value higher than 10000, then he will get error message.
+
+>If you wish to restrict Sales User from submitting Sales Orders, then instead of creating Authorization Rule, you should remove submit previledge from Role Permission Manager for Sales User.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/bar-code.md b/erpnext/docs/user/guides/setting-up/bar-code.md
new file mode 100644
index 0000000..5584815
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/bar-code.md
@@ -0,0 +1,50 @@
+A Barcode is a machine-readable code in the form of numbers and a pattern of
+parallel lines of varying widths, printed on a commodity and used especially
+for stock control.
+
+When you purchase an item from any store, you will notice a label with thin,
+black lines across it, along with a variation of different numbers. This label
+is then scanned by the cashier, and the item's description and price
+automatically comes up. This set of lines and numbers on the label are termed
+as bar-code.
+
+A bar-code machine scans the number from the label of an Item. To work with
+ERPNext and the bar-code mechanism, connect the bar-code machine to your
+operating hardware. Then go to ERPNext setup and activate bar-code by going to
+tools and clicking on 'hide / unhide features'. Under Materials, feature
+setup, check the box that says Item Barcode.
+
+> Setup > Customize > Hide/ Unhide Features > Item Barcode.
+
+#### Figure 1: Check the box 'Item Barcode'
+
+<img class="screenshot" alt="Barcode" src="assets/img/setup/barcode-1.png">
+
+
+To start scanning with a bar-code, go to  
+
+> Accounts > Sales Invoice
+
+Under Item, click on Add new row. The item row will expand to show new fields.
+Place your cursor on the bar-code field and begin scanning. The bar-code will
+be updated in the field. Once the bar-code is entered, all the Item details
+will be fetched automatically by the system.
+
+For more ease, activate the POS view in ERPnext. The activation process is
+same as the bar-code activation. Go to Setup and click on 'hide/unhide
+features'. Check the 'POS view' box.
+
+Then go to Accounts and click on Sales Invoice. Check the box 'Is POS'
+
+  
+#### Figure 2: Check the box 'Is POS'
+
+<img class="screenshot" alt="Barcode" src="assets/img/setup/barcode-2.png">
+
+
+Go to Item and click on Add new row.  
+
+The cursor will automatically be placed in the bar-code field. Thus you can
+immediately scan the bar-code and proceed with your operations.
+
+{next}
diff --git a/erpnext/docs/user/setting-up/calculate-incentive-for-sales-team.md b/erpnext/docs/user/guides/setting-up/calculate-incentive-for-sales-team.md
similarity index 100%
rename from erpnext/docs/user/setting-up/calculate-incentive-for-sales-team.md
rename to erpnext/docs/user/guides/setting-up/calculate-incentive-for-sales-team.md
diff --git a/erpnext/docs/user/setting-up/company-setup.md b/erpnext/docs/user/guides/setting-up/company-setup.md
similarity index 100%
rename from erpnext/docs/user/setting-up/company-setup.md
rename to erpnext/docs/user/guides/setting-up/company-setup.md
diff --git a/erpnext/docs/user/guides/setting-up/data/bulk-rename.md b/erpnext/docs/user/guides/setting-up/data/bulk-rename.md
new file mode 100644
index 0000000..fbbbc81
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/data/bulk-rename.md
@@ -0,0 +1,17 @@
+# Bulk Renaming of Records
+
+You can rename a document if ERPNext (if it is allowed) by going to **Menu > Rename** in the document.
+
+Alternatively, if you want to rename a whole bunch of records, just go to:
+
+> Setup > Data > Rename Tool
+
+This tool will allow you to rename multiple records at the same time.
+
+### Example
+
+To rename multiple records, upload a **.csv** file with the old name in the first column and the new name in the second column and click on **Upload**.
+
+<img class="screenshot" alt="Bulk Rename" src="assets/img/setup/data/rename.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/data/data-import-tool.md b/erpnext/docs/user/guides/setting-up/data/data-import-tool.md
new file mode 100644
index 0000000..c59955b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/data/data-import-tool.md
@@ -0,0 +1,110 @@
+The Data Import Tool is a great way to upload (or edit) bulk data, specially
+master data, into the system.
+
+To Open the data import tool, you either go to Setup or go to the Transaction
+you want to Import. If Data Import is allowed, you will see an Import Button:
+
+<img alt="Start Import" class="screenshot" src="assets/img/setup/data-import/data-import-1.png">
+
+The tool has two sections, one to download a template and the second to upload
+the data.
+
+(Note: Only those DocTypes are allowed for Import whose Document Type is
+"Master" or Allow Import property is set.)
+
+### 1\. Downloading The Template
+
+Data in ERPNext is stored in tables, much like a spreadsheet with columns and
+rows of data. Each entity in ERPNext can have multiple child tables associated
+with it too. The child tables are linked to the parent tables and are
+implemented where there are multiple values for any property. For example an
+Item can have multiple prices, An Invoice has multiple Items and so on.
+
+<img alt="Download Template" class="screenshot" src="assets/img/setup/data-import/data-import-2.png">
+
+  * Click on the table you want to download or "All Tables"
+  * For bulk editing, you can click on "Download With Data"
+
+### 2\. Fill in the Template
+
+After downloading the template, open it in a spreadsheet application and fill
+in the data below the column headings.
+
+![Spreadsheet](assets/old_images/erpnext/import-3.png)
+
+Then export your template or save it as a **Comma Separated Values** (CSV)
+file.
+
+![Spreadsheet](assets/old_images/erpnext/import-4.png)
+
+### 3\. Upload the .csv File
+
+Finally attach the .csv file in the section. Click on the "Upload and Import"
+button.
+
+<img alt="Upload" class="screenshot" src="assets/img/setup/data-import/data-import-3.png">
+
+#### Notes:
+
+1. Make sure that if your application allows, use encoding as UTF-8.
+1. Keep the ID column blank for new records.
+
+### 4\. Uploading All Tables (Main + Child)
+
+If you select all tables, you will get columns belonging to all the tables in
+one row separated by `~` columns.
+
+If you have multiple child rows then you must start a new main item on a new
+row. See the example:
+
+
+    Main Table                          ~   Child Table
+    Column 1    Column 2    Column 3    ~   Column 1    Column 2    Column 3
+    v11         v12         v13             c11         c12         c13
+                                            c14         c15         c17
+    v21         v22         v23             c21         c22         c23
+
+> To see how its done, enter a few records manually using forms and export
+"All Tables" with "Download with Data"
+
+### 5\. Overwriting
+
+ERPNext also allows you to overwrite all / certain columns. If you want to
+update certain columns, you can download the template with data. Remember to
+check on the “Overwrite” box before uploading.
+
+> Note: For child records, if you select Overwrite, it will delete all the
+child records of that parent.
+
+### 6\. Upload Limitations
+
+ERPNext restricts the amount of data you can upload in one file. Though the
+number may vary based on the type of data. It is usually safe to upload around
+1000 rows of a table at one go. If the system will not accept, then you will
+see an error.
+
+Why is this? Uploading a lot of data can cause your system to crash, specially
+if there are other users doing things in parallel. Hence ERPNext restricts the
+number of “writes” you can process in one request.
+
+***
+
+#### How to Attach files?
+
+When you open a form, on the right sidebar, you will see a section to attach
+files. Click on “Add” and select the file you want to attach. Click on
+“Upload” and you are set.
+
+#### What is a CSV file?
+
+A CSV (Comma Separated Value) file is a data file that you can upload into
+ERPNext to update various data. Any spreadsheet file from popular spreadsheet
+applications like MS Excel or Open Office Spreadsheet can be saved as a CSV
+file.
+
+If you are using Microsoft Excel and using non-English characters, make sure
+to save your file encoded as UTF-8. For older versions of Excel, there is no
+clear way of saving as UTF-8. So save your file as a CSV, then open it in
+Notepad, and save as “UTF-8”. (Sorry blame Microsoft for this!)
+
+{next}
diff --git a/erpnext/docs/user/setting-up/data/index.md b/erpnext/docs/user/guides/setting-up/data/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/data/index.md
rename to erpnext/docs/user/guides/setting-up/data/index.md
diff --git a/erpnext/docs/user/setting-up/data/index.txt b/erpnext/docs/user/guides/setting-up/data/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/data/index.txt
rename to erpnext/docs/user/guides/setting-up/data/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/email/email-account.md b/erpnext/docs/user/guides/setting-up/email/email-account.md
new file mode 100644
index 0000000..2707609
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/email/email-account.md
@@ -0,0 +1,39 @@
+# Email Accounts
+
+You can manage multiple incoming and outgoing Email Accounts in ERPNext. There has to be atleast one default outgoing account and one default incoming account. If you are on the ERPNext cloud, the default outgoing email is set by us.
+
+> **Note for self implementers:** For outgoing emails, you should setup your own SMTP server or sign up with an SMTP relay service like mandrill.com or sendgrid.com that allows a larger number of transactional emails to be sent. Regular email services like GMail will restrict you to a limited number of emails per day.
+
+### Default Email Accounts
+
+ERPNext will create templates for a bunch of email accounts by default. Not all of them are enabled. To enable them, you must set your account details.
+
+There are 2 types of email accounts, outgoing and incoming. Outgoing email accounts use an SMTP service to send emails and emails are retrived from your inbox using a POP service. Most email providers such as GMail, Outlook or Yahoo provide these services.
+
+<img class="screenshot" alt="Defining Criteria" src="assets/img/setup/email/email-account-list.png">
+
+### Outgoing Email Accounts
+
+All emails sent from the system, either by the user to a contact or notifications or transaction emails, will be sent from an Outgoing Email Account.
+
+To setup an outgoing Email Account, check on **Enable Outgoing** and set your SMTP server settings, if you are using a popular email service, these will be preset for you.
+
+<img class="screenshot" alt="Outgoing EMail" src="assets/img/setup/email/email-account-sending.png">
+
+### Incoming Email Accounts
+
+To setup an incoming Email Account, check on **Enable Incoming** and set your POP3 settings, if you are using a popular email service, these will be preset for you.
+
+<img class="screenshot" alt="Incoming EMail" src="assets/img/setup/email/email-account-incoming.png">
+
+### How ERPNext handles replies
+
+In ERPNext when you send an email to a contact like a customer, the sender will be the user who sent the email. In the **Reply-To** property, the email id will be of the default incoming account (like `replies@yourcompany.com`). ERPNext will automatically extract these emails from the incoming account and tag it to the relvant communication
+
+### Notification for unreplied messages
+
+If you would like ERPNext to notify you if an email is unreplied for a certain amount of time, then you can set **Notify if Unreplied**. Here you can set the number of minutes to wait before notifications are sent and whom the notifications must go to.
+
+<img class="screenshot" alt="Incoming EMail" src="assets/img/setup/email/email-account-unreplied.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/email/email-alerts.md b/erpnext/docs/user/guides/setting-up/email/email-alerts.md
new file mode 100644
index 0000000..c51738a
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/email/email-alerts.md
@@ -0,0 +1,41 @@
+# Email Alerts
+
+You can configure various email alerts in your system to remind you of important activities such as:
+
+1. Completion date of a Task.
+1. Expected Delivery Date of a Sales Order.
+1. Expected Payment Date.
+1. Reminder of followup.
+1. If an Order greater than a particular value is received or sent.
+1. Expiry notification for a Contract.
+1. Completion / Status change of a Task.
+
+For this, you need to setup an Email Alert.
+
+> Setup > Email > Email Alert
+
+### Setting Up An Alert
+
+To setup an Email Alert:
+
+1. Select which Document Type you want watch changes on
+1. Define what events you want to watch. Events are:
+	1. New: When a new document of the selected type is made.
+	2. Save / Submit / Cancel: When a document of the selected type is saved, submitted, cancelled.
+	3. Value Change: When a particular value in the selected type changes.
+	4. Days Before / Days After: Trigger this alert a few days before or after the **Reference Date.** To set the days, set **Days Before or After**. This can be useful in reminding you of upcoming due dates or reminding you to follow up on certain leads of quotations.
+1. Set additional conditions if you want.
+1. Set the recipients of this alert. The recipient could either be a field of the document or a list of fixed email ids.
+1. Compose the message
+
+---
+
+### Example
+
+1. Defining the Criteria
+    <img class="screenshot" alt="Defining Criteria" src="assets/img/setup/email/email-alert-1.png">
+
+1. Setting the Recipients and Message
+    <img class="screenshot" alt="Set Message" src="assets/img/setup/email/email-alert-2.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/email/email-digest.md b/erpnext/docs/user/guides/setting-up/email/email-digest.md
new file mode 100644
index 0000000..dc6dd8d
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/email/email-digest.md
@@ -0,0 +1,17 @@
+# Email Digest
+
+Email Digests allow you to get regular updates about your sales, expenses and other critical numbers directly in your Inbox.
+
+Email Digests are a great way for top managers to keep track of the big numbers like “Sales Booked” or “Amount Collected” or “Invoices Raised” etc.
+
+To set up Email Digest, go to:
+
+> Setup > Email > Email Digest
+
+## Example
+
+Set your frequency, check all the items you want to receive in your weekly update and select the user ids whom you want to send the Digest to.
+
+<img class="screenshot" alt="Email Digest" src="assets/img/setup/email/email-digest.png">
+
+{next}
diff --git a/erpnext/docs/user/setting-up/email/index.md b/erpnext/docs/user/guides/setting-up/email/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/email/index.md
rename to erpnext/docs/user/guides/setting-up/email/index.md
diff --git a/erpnext/docs/user/setting-up/email/index.txt b/erpnext/docs/user/guides/setting-up/email/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/email/index.txt
rename to erpnext/docs/user/guides/setting-up/email/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/email/sending-email.md b/erpnext/docs/user/guides/setting-up/email/sending-email.md
new file mode 100644
index 0000000..ff9c03a
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/email/sending-email.md
@@ -0,0 +1,9 @@
+# Sending Email from any Document
+
+In ERPNext you can send any document as email (with a PDF attachment) by clicking on `Menu > Email` from any open document.
+
+<img class="screenshot" alt="Send Email" src="assets/img/setup/email/send-email.gif">
+
+**Note:** You must have outgoing [email accounts](/contents/setting-up/email/email-account) setup for this.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/email/setting-up-email.md b/erpnext/docs/user/guides/setting-up/email/setting-up-email.md
new file mode 100644
index 0000000..448cf4b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/email/setting-up-email.md
@@ -0,0 +1,95 @@
+Emails are the nervous system of business communication and ERPNext has been
+designed to make good use of this.
+
+## Sending Emails
+
+You can email any document from the system, by clicking on the “Email” button
+on the right sidebar. Before that you will need to set your outgoing email
+settings (SMTP server).
+
+All emails sent from the system are added to the Communication table.
+
+> **Info:** What is SMTP? There are two types of email services, sending and
+receiving emails. Sending is done via a protocol called SMTP (Simple Mail
+Transfer Protocol) and the server (computer) that sends your email to its
+destination is called SMTP Server.
+
+
+Bulk Emails, especially those that are sent without consent (spam), are considered as bad behavior. While it may be okay to send emails to those who have “opted-in” to receive mails, it is very difficult for the internet community to know what is spam and what is allowed. To overcome this problem, most email servers share a black and white list of email senders. If your emails have been marked as spam, you will be blacklisted. So be careful. Many times, it may be a good idea to send email via whitelisted services also known as SMTP relay services which are paid services.These
+services will block you from sending spam while ensuring that most of your email does not go in the spam folder. There are many such services available like SendGrid and SMTP.com.
+
+To setup your outgoing mails, go to
+
+> Setup > Outgoing Email Settings
+
+#### Figure 1: Set up outgoing mail server.
+
+![Email Settings](assets/old_images/erpnext/email-settings1.png)
+
+Set your outgoing mail server settings here. These are the same settings you
+would use in your Outlook, Thunderbird, Apple Mail or other such email
+applications. If you are not sure, get in touch with your email service
+provider.
+
+> **Tip:** If you are using EPRNext hosted service, keep the first section
+blank. Emails will still be sent from your email id, but via our SMTP relay
+service.
+
+### Creating Issues from Incoming Emails
+
+A very useful email integration is to sync the incoming emails from support
+inbox into Issue, so that you can track, assign and monitor support
+issues.
+
+> **Case Study:** Here at ERPNext, we have regularly tracked incoming support
+issues via email at “support@erpnext.com”. At the time of writing we had
+answered more than 3000 tickets via this system.
+
+To setup your Support integration, go to:
+
+> Setup > Support Email Settings
+
+#### Figure 2: Setup support Integration
+
+![Email Settings](assets/old_images/erpnext/email-settings2.png)
+
+To make ERPNext pull emails from your mail box, enter the POP3 settings. (POP3
+is a way of extracting emails from your mailbox. It should be fairly easy to
+find out what your POP3 settings are. If you have problems, contact your email
+service provider). If you want to setup an auto reply, check on the “Send
+Autoreply” box and whenever someone sends an email, an autoreply will be sent.
+Add a custom signature which you want to send with your replies.
+
+### Setting Auto-notification on Documents
+
+ERPNext allows you to automatically email documents on “Submission” to the
+contact mentioned in the document. To set this up, go to:
+
+> Setup > Tools > Enable / Disable Notifications.
+
+#### Figure 3: Set Auto Notification
+
+![Auto Notification](assets/old_images/erpnext/auto-notification.png)
+
+Check on the transactions you want to send via email directly on Submission
+and add a custom message if you want on these documents.
+
+### Email Digests
+
+Email Digests allow you to get regular updates about your sales, expenses and
+other critical numbers directly in your Inbox.
+
+Set your frequency, check all the items you want to receive in your weekly
+update and select the user ids whom you want to send the Digest to.
+
+Email Digests are a great way for top managers to keep track of the big
+numbers like “Sales Booked” or “Amount Collected” or “Invoices Raised” etc.
+
+To setup Email Digests, go to:
+
+> Setup > Email Digest > New Email Digest
+
+#### Figure 4: Set up Email Digest
+
+![Email Digest](assets/old_images/erpnext/email-digest.png)
+
diff --git a/erpnext/docs/user/setting-up/index.md b/erpnext/docs/user/guides/setting-up/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/index.md
rename to erpnext/docs/user/guides/setting-up/index.md
diff --git a/erpnext/docs/user/setting-up/index.txt b/erpnext/docs/user/guides/setting-up/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/index.txt
rename to erpnext/docs/user/guides/setting-up/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/pos-setting.md b/erpnext/docs/user/guides/setting-up/pos-setting.md
new file mode 100644
index 0000000..74be63b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/pos-setting.md
@@ -0,0 +1,23 @@
+# Point of Sale Setting
+
+POS includes advanced features to cater to different functionality, such as
+inventory management, CRM, financials, warehousing, etc., all built into the
+POS software. Prior to the modern POS, all of these functions were done
+independently and required the manual re-keying of information, which could
+lead to entry errors.
+
+If you are in retail operations, you want your Point of Sale to be as quick
+and efficient as possible. To do this, you can create a POS Setting for a user
+from:
+
+> Accounts > Setup > Point-of-Sale Setting
+
+Set default values as defined.
+
+<img class="screenshot" alt="POS Setting" src="assets/img/pos-setting/pos-setting.png">
+
+> Important : If you specify a particular User, the POS setting will be
+applied only to that User. If the User option is left blank, the setting will
+be set for all users. To understand POS in detail visit [Point of Sale](/contents/accounts/point-of-sale-pos-invoice)
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/price-lists.md b/erpnext/docs/user/guides/setting-up/price-lists.md
new file mode 100644
index 0000000..19ac41f
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/price-lists.md
@@ -0,0 +1,21 @@
+ERPNext lets you maintain multiple selling and buying prices for an Item using Price Lists. A PriceList is a name you can give to a set of Item prices. 
+
+Why would you want Price Lists? You have different prices for different zones (based on the shipping costs), for different currencies etc.
+
+An Item can have multiple prices based on customer, currency, region, shipping cost etc, which can be stored as different rate plans. In ERPNext, you are required to store all the lists separately. Buying Price List is different from Selling Price List and thus is stored separately.
+
+You can create new Price List
+
+> Selling/Buying/Stock  > Setup > Price List >> New
+
+<img class="screenshot" alt="Price List" src="assets/img/price-list/price-list.png">
+
+* These Price List will be used when creating Item Price record to track selling or buying price of an item. Click here to learn more about Item Price.
+
+* To disable specific Price List, uncheck Enabled field in it. Disabled Price List will not be availale for selection in the Sales and Purchase transactions.
+
+* Standard Buying and Selling Price List are created by default.
+
+To disable specific Price List, uncheck Enabled field in it. Disabled Price List will not be availale for selection in the Sales and Purchase transactions.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/print/address-template.md b/erpnext/docs/user/guides/setting-up/print/address-template.md
new file mode 100644
index 0000000..e2b31080
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/address-template.md
@@ -0,0 +1,31 @@
+# Address Template
+
+Each region has its own way of defining Addresses. To manage multiple address formats for your Documents (like Quotation, Purchase Invoice etc.), you can create country-wise **Address Templates**.
+
+> Setup > Printing and Branding > Address Template
+
+A default Address Template is created when you setup the system. You can either edit or update it or create a new template.
+
+One template is default and will apply to all countries that do not have an specific template.
+
+#### Template
+
+The templating engine is based on HTML and the [Jinja Templating](http://jinja.pocoo.org/docs/templates/) system and all the fields (including Custom Fields) will be available for creating the template.
+
+Here is the default template:
+
+	{{ address_line1 }}<br>
+	{% if address_line2 %}{{ address_line2 }}<br>{% endif -%}
+	{{ city }}<br>
+	{% if state %}{{ state }}<br>{% endif -%}
+	{% if pincode %}PIN:  {{ pincode }}<br>{% endif -%}
+	{{ country }}<br>
+	{% if phone %}Phone: {{ phone }}<br>{% endif -%}
+	{% if fax %}Fax: {{ fax }}<br>{% endif -%}
+	{% if email_id %}Email: {{ email_id }}<br>{% endif -%}
+
+### Example
+
+<img class="screenshot" alt="Print Heading" src="assets/img/setup/print/address-format.png">
+
+{next}
diff --git a/erpnext/docs/user/setting-up/print/index.md b/erpnext/docs/user/guides/setting-up/print/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/print/index.md
rename to erpnext/docs/user/guides/setting-up/print/index.md
diff --git a/erpnext/docs/user/setting-up/print/index.txt b/erpnext/docs/user/guides/setting-up/print/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/print/index.txt
rename to erpnext/docs/user/guides/setting-up/print/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/print/letter-head.md b/erpnext/docs/user/guides/setting-up/print/letter-head.md
new file mode 100644
index 0000000..fec38e9
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/letter-head.md
@@ -0,0 +1,23 @@
+# Letter Heads
+
+You can manage multiple letter heads in ERPNext. In a letter head you can:
+
+  * Create an image with your logo, brand and other information that you want to put on your letter head.
+  * Attach the image in your Letter Head record by clicking on image icon to automatically generate the HTML required for this Letter Head.
+  * If you want to make this the default letter head, click on “Is Default”.
+
+Your letter head will now appear in all Prints and Emails of documents.
+
+You can create / manage Letter Heads from:
+
+> Setup > Printing > Letter Head > New Letter Head
+
+### Example
+
+<img class="screenshot" alt="Print Heading" src="assets/img/setup/print/letter-head.png">
+
+This is how the letter head looks in a document print:
+
+<img class="screenshot" alt="Print Heading" src="assets/img/setup/print/letter-head-1.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/print/print-format-builder.md b/erpnext/docs/user/guides/setting-up/print/print-format-builder.md
new file mode 100644
index 0000000..36db3ae
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/print-format-builder.md
@@ -0,0 +1,37 @@
+# Print Format Builder
+
+The Print Format Builder helps you quickly make a simple customized Print Format by dragging and dropping data fields and adding custom text or HTML.
+
+You can create a new Print Format either by going to:
+
+> Setup > Printing and Branding > Print Format Builder
+
+or Open the document for which you want to make a print format. Click the Printer icon, or go to Menu > Print and click on the **Edit** button. Note: You must have System Manager permission to do this.
+
+### Step 1: Make a new Format
+
+<img class="screenshot" alt="Send Email" src="assets/img/setup/print/print-format-builder-1.gif">
+
+### Step 2: Add a new Field
+
+To add a field, just drag it from the left sidebar and add it in your layout. You can edit the layout by clicking on the settings <i class="octicon octicon-gear"></i> icon.
+
+<img class="screenshot" alt="Send Email" src="assets/img/setup/print/print-format-builder-2.gif">
+
+### Step 3
+
+To remove a field, just drag it back into the fields sidebar.
+
+<img class="screenshot" alt="Send Email" src="assets/img/setup/print/print-format-builder-3.gif">
+
+### Step 4
+
+You can add customized text, HTML in your print format, just add the **Custom HTML** field (in dark colour) and add it to the the place where you want to add the text.
+
+Then click on **Edit HTML** to edit your content.
+
+<img class="screenshot" alt="Send Email" src="assets/img/setup/print/print-format-builder-4.gif">
+
+To save your format, just click on the **Save** button on the top.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/print/print-headings.md b/erpnext/docs/user/guides/setting-up/print/print-headings.md
new file mode 100644
index 0000000..e63e253
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/print-headings.md
@@ -0,0 +1,17 @@
+Print Headings are the names which you can give to your sales invoices,
+supplier quotations etc. You can create a list of names for different business
+communications.
+
+You can create print headings from :
+
+> Setup > Printing > Print Heading > New Print Heading
+
+#### Figure 1: Save Print Heading
+
+<img class="screenshot" alt="Print Heading" src="assets/img/setup/print/print-heading.png">
+
+Example of a change in print heading is shown below:
+
+<img class="screenshot" alt="Print Heading" src="assets/img/setup/print/print-heading-1.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/print/print-settings.md b/erpnext/docs/user/guides/setting-up/print/print-settings.md
new file mode 100644
index 0000000..e998d62
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/print-settings.md
@@ -0,0 +1,11 @@
+# Print Settings
+
+In Print Settings you can set your default printing preferences like Paper Size, default text size, whether you want output as PDF or HTML etc.
+
+To edit print settings, go to:
+
+> Setup > Printing and Branding > Print Settings
+
+<img class="screenshot" alt="Print Settings" src="assets/img/setup/print/print-settings.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/print/terms-and-conditions.md b/erpnext/docs/user/guides/setting-up/print/terms-and-conditions.md
new file mode 100644
index 0000000..d025157
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/print/terms-and-conditions.md
@@ -0,0 +1,25 @@
+Terms and conditions are the general and special arrangements, provisions, requirements, rules, specifications, and standards that a company follows. These specifications are an integral part of an agreement or contract that the company gets into with its customers, suppliers or partners.
+
+### 1. Make a new Terms and Conditions
+
+To setup Terms and Condition master, go to:
+
+`Selling > Terms and Condition > New`
+
+<img class="screenshot" alt="Terms and Conditions" src="assets/img/setup/print/terms-1.png">
+
+### 2. Editing in HTML
+
+Content of Terms and Condition can be formatted as per your preference, and also insert images where needed. If you have expertise in HTML, you will also find option to edit the content of Terms and Condition in HTML.
+
+<img class="screenshot" alt="Terms and Conditions, Edit HTML" src="assets/img/setup/print/terms-2.png">
+
+This also allows you to use Terms and Condition master for footer, which otherwise is not availale in ERPNext as dedicated functionality. Since contents of Terms and Condition is always the last to appear in the print format, details of footer should be inserted at the end of the content, so that it actually appears as footer in the print format.
+
+### 3. Select in Transaction
+
+In transactions, you will find section of Terms and Condition where you will be able to search and fetched required Terms and Condition master.
+
+<img class="screenshot" alt="Terms and Conditions, Select in document" src="assets/img/setup/print/terms-3.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setting-up-taxes.md b/erpnext/docs/user/guides/setting-up/setting-up-taxes.md
new file mode 100644
index 0000000..3923ddc
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setting-up-taxes.md
@@ -0,0 +1,99 @@
+One of the primary motivator for compulsory use of accounting tools is
+calculation of Taxes. You may or may not make money but your government will
+(to help your country be safe and prosperous). And if you don’t calculate your
+taxes correctly, they get very unhappy. Ok, philosophy aside, ERPNext allows
+you to make configurable tax templates that you can apply to your sales or
+purchase.
+
+### Tax Accounts
+
+For Tax Accounts that you want to use in the tax templates, you must go to
+Chart of Accounts and mention them as type “Tax” in your Chart of Item.
+
+## Item Tax
+
+If some of your Items require different tax rates as compared to others,
+mention them in the Item tax table. Even if you have selected your sales and
+purchase taxes as default tax rates, the system will pull the Item tax rate
+for calculations. Item tax will get preference over other sales or purchase
+taxes. However, if you wish to apply default sales and purchase taxes, do not
+mention item tax rates in the Item master. The system will then select the
+sales or purchase tax rate specified by you as default rates.
+
+Item Tax table can be found as a section within the Item Master document.
+
+<img class="screenshot" alt="Item Tax" src="assets/img/taxes/item-tax.png">
+
+  * **Inclusive and Exclusive Tax**: ERPNext allows you to enter Item rates which are tax inclusive.
+
+<img class="screenshot" alt="Inclusive Tax" src="assets/img/taxes/inclusive-tax.png">
+
+  * **Exception to the rule**: Item tax settings are required only if a particular Item has a different tax rate than the rate defined in the standard tax Account
+  * **Item tax is overwrite-able**: You can overwrite or change the item tax rate by going to the Item master in the Item tax table.
+
+## Sales Taxes and Charges Template
+
+You must usually collect taxes from your Customer and pay them to the
+government. At times, you may have to pay multiple taxes to multiple
+government bodies like local government, state or provincial and federal or
+central government.
+
+The way ERPNext sets up taxes is via templates. Other types of charges that
+may apply to your invoices (like shipping, insurance etc.) can also be
+configured as taxes.
+
+Select template and modify as per your need.
+
+To create a new sales tax template called Sales Taxes and Charges Template, you
+have to go to:
+
+> Setup > Accounts > Sales Taxes and Charge Master
+
+<img class="screenshot" alt="Sales Tax Master" src="assets/img/taxes/sales-tax-master.png">
+
+When you create a new master, you will have to add a row for each tax type.
+
+The tax rate you define here will be the standard tax rate for all Items. If
+there are Items that have different rates, they must be added in the Item Tax
+table in the Item master.
+
+In each row, you have to mention:
+
+  * Calculation Type:
+
+    * On Net Total : This can be on net total (total amount without taxes).
+    * On Previous Row Total/Amount: You can apply taxes on previous row total / amount. If you select this option, the tax will be applied as a percentage of the previous row (in the tax table) amount or total. Previous row amount means a particular tax amount.And, previous row total means net total plus taxes applied up to that row. In the Enter Row Field, mention row number on which you want to apply the current tax. If you want to apply the tax on the 3rd row, mention "3" in the Enter Row field.
+
+    * Actual : Enter as per actual amount in rate column.
+
+  * Account Head: The Account ledger under which this tax will be booked
+
+  * Cost Center: If the tax / charge is an income (like shipping) it needs to be booked against - a Cost Center.
+  * Description: Description of the tax (that will be printed in invoices / quotes).
+  * Rate: Tax rate.
+  * Amount: Tax amount.
+  * Total: Cumulative total to this point.
+  * Enter Row: If based on "Previous Row Total" you can select the row number which will be taken as a base for this calculation (default is the previous row).
+  * Is this Tax included in Basic Rate?: If you check this, it means that this tax will not be shown below the item table, but will be included in the rate in your main item table. This is useful when you want to give a flat price (inclusive of all taxes) to your customers.
+
+Once you setup your template, you can select this in your sales transactions.
+
+## Purchase Taxes and Charges Template
+
+Similar to your Sales Taxes and Charges Template is the Purchase Taxes and
+Charges Master.
+
+This is the tax template that you can use in your Purchase Orders and Purchase
+Invoices. If you have value added taxes (VAT), where you pay to the government
+the difference between your incoming and outgoing taxes, you can select the
+same Account that you use for sales taxes.
+
+The columns in this table are similar to the Sales Taxes and Charges Template
+with the difference as follows:
+
+Consider Tax or Charge for: In this section you can specify if the tax /
+charge is only for valuation (not a part of total) or only for total (does not
+add value to the item) or for both.
+
+{next}
+
diff --git a/erpnext/docs/user/guides/setting-up/settings/global-defaults.md b/erpnext/docs/user/guides/setting-up/settings/global-defaults.md
new file mode 100644
index 0000000..ca654e5
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/settings/global-defaults.md
@@ -0,0 +1,11 @@
+# Global Defaults
+
+You can set default values for your documents from Global Defaults
+
+> Setup > Settings > Global Defaults
+
+Whenever a new document is created, these values will be set as default.
+
+<img class="screenshot" alt="Global Defaults" src="assets/img/setup/settings/global-defaults.png">
+
+{next}
diff --git a/erpnext/docs/user/setting-up/settings/index.md b/erpnext/docs/user/guides/setting-up/settings/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/settings/index.md
rename to erpnext/docs/user/guides/setting-up/settings/index.md
diff --git a/erpnext/docs/user/setting-up/settings/index.txt b/erpnext/docs/user/guides/setting-up/settings/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/settings/index.txt
rename to erpnext/docs/user/guides/setting-up/settings/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/settings/module-settings.md b/erpnext/docs/user/guides/setting-up/settings/module-settings.md
new file mode 100644
index 0000000..be0a47b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/settings/module-settings.md
@@ -0,0 +1,15 @@
+# Show or Hide Modules
+
+You can globally switch off certain desktop module via:
+
+> Setup > Settings > Show or Hide Modules
+
+For example if you are in the services business, you want to hide the Manufacturing Module, you can do this via **Show or Hide Modules**
+
+### Example
+
+Check / uncheck the items to show / hide.
+
+<img class="screenshot" alt="Module Settings" src="assets/img/setup/settings/show-hide-modules.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/settings/naming-series.md b/erpnext/docs/user/guides/setting-up/settings/naming-series.md
new file mode 100644
index 0000000..16f73ea
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/settings/naming-series.md
@@ -0,0 +1,48 @@
+# Naming Series
+
+### 1. Introduction
+
+Data records are broadly classified as “Master” or “Transaction”. A master
+record is a record that has a “name”, for example a Customer, Item, Supplier,
+Employee etc. A Transaction is a record that has a “number”. Examples of
+transactions include Sales Invoices, Quotations etc. You make transactions
+against a number of master records.
+
+ERPNext allows you to make prefixes to your transactions, with each prefix
+forming its own series. For example a series with prefix INV12 will have
+numbers INV120001, INV120002 and so on.
+
+You can have multiple series for all your transactions. It is common to have a
+separate series for each financial year. For example in Sales Invoice you
+could have:
+
+  * INV120001
+  * INV120002
+  * INV-A-120002
+
+etc. You could also have a separate series for each type of Customer or for
+each of your retail outlets.
+
+### 2. Managing Naming Series for Documents
+
+To setup a series, go to:
+
+> Setup > Tools > Update Numbering Series
+
+In this form,
+
+  1. Select the transaction for which you want to make the series The system will update the current series in the text box.
+  2. Edit the series as required with unique prefixes for each series. Each prefix must be on a new line.
+  3. The first prefix will be the default prefix. If you want the user to explicitly select a series instead of the default one, check the “User must always select” check box.
+
+You can also update the starting point of a series by entering the series
+name and the starting point in the “Update Series” section.
+
+### 3. Example
+
+See how to set the naming series
+
+<img class="screenshot" alt="Naming Series" src="assets/img/setup/settings/naming-series.gif">
+
+{next}
+
diff --git a/erpnext/docs/user/guides/setting-up/settings/system-settings.md b/erpnext/docs/user/guides/setting-up/settings/system-settings.md
new file mode 100644
index 0000000..4b2dcee
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/settings/system-settings.md
@@ -0,0 +1,11 @@
+# System Settings
+
+You can localize ERPNext to use particular timezone, date, number or currency format and also set global session expiry via System Settings.
+
+To open System Settings, go to:
+
+> Setup > Settings > System Settings
+
+<img class="screenshot" alt="System Settings" src="assets/img/setup/settings/system-settings.png">
+
+{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/index.md b/erpnext/docs/user/guides/setting-up/setup-wizard/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/setup-wizard/index.md
rename to erpnext/docs/user/guides/setting-up/setup-wizard/index.md
diff --git a/erpnext/docs/user/setting-up/setup-wizard/index.txt b/erpnext/docs/user/guides/setting-up/setup-wizard/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/setup-wizard/index.txt
rename to erpnext/docs/user/guides/setting-up/setup-wizard/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-1-language.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-1-language.md
new file mode 100644
index 0000000..79ead1b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-1-language.md
@@ -0,0 +1,11 @@
+# Step 1: Language
+
+Select your language. ERPNext is available in more than 20 languages.
+
+<img alt="Language" class="screenshot" src="assets/img/setup-wizard/step-1.png">
+
+---
+
+Translations are contributed by the ERPNext Community. If you want to contribute, [please checkout the translator portal](https://translate.erpnext.com).
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-10-item.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-10-item.md
new file mode 100644
index 0000000..6896f4b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-10-item.md
@@ -0,0 +1,16 @@
+# Step 9: Item Names
+
+In this final step, please enter the names of the Items you buy or sell.
+
+<img alt="Add Items" class="screenshot"
+src="assets/img/setup-wizard/step-10.png">
+
+Please set the group of the item (Product / Service) and unit of measure. Don't worry you will be able to edit all of this later.
+
+---
+
+## Thats it!
+
+Once you are done with the setup wizard you will see the familiar desktop page.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-2-currency-and-timezone.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-2-currency-and-timezone.md
new file mode 100644
index 0000000..ad5147b
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-2-currency-and-timezone.md
@@ -0,0 +1,13 @@
+# Step 2: Currency and Timezone
+
+Set your country name, currency and timezone.
+
+<img alt="Currency" class="screenshot" src="assets/img/setup-wizard/step-2.png">
+
+---
+
+### Default Currency
+
+For most countries, your currency and timezone will be automatically set
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-3-user-details.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-3-user-details.md
new file mode 100644
index 0000000..f586778
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-3-user-details.md
@@ -0,0 +1,12 @@
+# Step 3: User Details
+
+Enter Users Profile Details like Name, User ID and preferred password.
+
+<img alt="User" class="screenshot"
+src="assets/img/setup-wizard/step-3.png">
+
+---
+
+Note: Add your own photograph, not your company's
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-4-company-details.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-4-company-details.md
new file mode 100644
index 0000000..197fa55
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-4-company-details.md
@@ -0,0 +1,22 @@
+# Step 4: Company Details
+
+Enter Company Details like Name, Abbreviation and Financial Year Details.
+
+<img alt="Company Details" class="screenshot"
+src="assets/img/setup-wizard/step-4.png">
+
+---
+
+### Company Abbreviation
+
+These will be appened to your **Account** Heads, for example if your abbreviation is **WP**, then your Sales account will be **Sales - WPL**
+
+For Example: East Wind will be abbreviated as EW. Shades of Green will be abbreviated as SOG. In case you wish to give your own abbreviation, you can do so. The text field allows any type of text.
+
+### Financial Year
+
+Any annual period at the end of which a firm's accounts are made up is called a Financial Year. Some countries have their account year starting from 1st January and some 1st April.
+
+The end date will be set automatically
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-5-letterhead-and-logo.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-5-letterhead-and-logo.md
new file mode 100644
index 0000000..4ead081
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-5-letterhead-and-logo.md
@@ -0,0 +1,24 @@
+# Step 5: Letterhead and Logo
+
+Attach Company Letterhead and Company Logo.
+
+<img alt="Company Logo and Letterhead" class="screenshot"
+src="assets/img/setup-wizard/step-5.png">
+
+---
+
+### Letterhead
+
+A letterhead is the heading at the top of a sheet of letter paper (stationery). That heading usually consists of a name and an address, and a logo or corporate design.
+
+Click on the box ‘Attach Letterhead’ . Select the image file from the place it is stored and click enter.
+
+You may choose to skip this step if your letterhead is not ready.
+
+To select letterhead later through the setup module, read [Letter-head](/contents/setting-up/print/letter-head)
+
+#### To "attach as web-link"
+
+For any attachments in ERPNext, you can also attach as a web-link. If you are using other tools like Dropbox or Google Docs to manage your files, you can set its public link.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-6-add-users.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-6-add-users.md
new file mode 100644
index 0000000..4aeadf3
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-6-add-users.md
@@ -0,0 +1,8 @@
+# Step 6: Add Users
+
+Add other users and assign them roles based on their job responsibilities.
+
+<img alt="Users" class="screenshot"
+src="assets/img/setup-wizard/step-6.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-7-tax-details.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-7-tax-details.md
new file mode 100644
index 0000000..fef997a
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-7-tax-details.md
@@ -0,0 +1,22 @@
+# Step 6: Tax Details
+
+Enter any three types of taxes which you regularly pay. This wizard will create a tax master which will calculate the taxes as per the tax-type.
+
+<img alt="Tax Details" class="screenshot"
+src="assets/img/setup-wizard/step-7.png">
+
+Just set the tax name and the standard percentage levied.
+
+---
+
+Some examples of tax types are given below.
+
+#### VAT
+
+A value added tax (VAT) is a form of consumption tax. From the perspective of the buyer, it is a tax on the purchase price. From that of the seller, it is a tax only on the value added to a product, material, or a service. From an accounting point of view, by the stage of its manufacture or distribution. The manufacturer remits to the government the difference between these two amounts, and retains the rest for themselves to offset the taxes they had previously paid on the inputs.
+
+The purpose of VAT is to generate tax revenues to the government similar to the corporate income tax or the personal income tax. For Example: When you shop at a departmental store and avail discount on the products, the store charges you 5% extra on the total bill as the VAT.
+
+To setup VAT in the setup wizard , simply enter the percentage amount levied by your government. To setup VAT at a later stage read [setting-up-taxes](/contents/setting-up/setting-up-taxes)
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-8-customer-names.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-8-customer-names.md
new file mode 100644
index 0000000..e0dd743
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-8-customer-names.md
@@ -0,0 +1,23 @@
+# Step 7: Customers
+
+Enter your Customer names and the contact person from that organisation.
+
+
+<img alt="Customers" class="screenshot"
+src="assets/img/setup-wizard/step-8.png">
+
+---
+
+#### Difference between a customer name and a contact name
+
+A customer name is the name of the organisation and a contact name is the name of the user who is operating the ERPNext system.
+
+For Example: If American Power Mills is an organisation name and their founder Shiv Agarwal has installed ERPNext on his system. Then,
+
+Customer Name: American Power Mills
+
+Contact Name:  Shiv Agarwal
+
+To understand Customer in detail visit [Customer Details](/contents/CRM/customer)
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/setup-wizard/step-9-suppliers.md b/erpnext/docs/user/guides/setting-up/setup-wizard/step-9-suppliers.md
new file mode 100644
index 0000000..1fb702c
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/setup-wizard/step-9-suppliers.md
@@ -0,0 +1,12 @@
+# Step 8: Suppliers
+
+Enter a few of your Suppliers' names.
+
+<img alt="Suppliers" class="screenshot"
+src="assets/img/setup-wizard/step-9.png">
+
+---
+
+To understand Suppliers in detail visit [Supplier Master](/contents/buying/supplier-master)
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/sms-setting.md b/erpnext/docs/user/guides/setting-up/sms-setting.md
new file mode 100644
index 0000000..0d324d7
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/sms-setting.md
@@ -0,0 +1,40 @@
+# SMS Setting
+
+To integrate SMS in ERPNext, approach a SMS Gateway Provider who provides HTTP
+API. They will create an account for you and will provide an unique username
+and password.
+
+To configure SMS Settings in ERPNext, find out their HTTP API (a document
+which describes the method of accessing their SMS interface from 3rd party
+applications). In this document, you will get an URL which is used to send the
+SMS using HTTP request. Using this URL, you can configure SMS Settings in
+ERPNext.
+
+Example URL:  
+
+    
+    
+    http://instant.smses.com/web2sms.php?username=<USERNAME>&password;=<PASSWORD>&to;=<MOBILENUMBER>&sender;=<SENDERID>&message;=<MESSAGE>
+    
+
+![SMS Settings](assets/old_images/erpnext/sms-setting2.jpg)
+
+> Note: the string up to the "?" is the SMS Gateway URL
+
+Example:
+
+    
+    
+    http://instant.smses.com/web2sms.php?username=abcd&password;=abcd&to;=9900XXXXXX&sender;
+    =DEMO&message;=THIS+IS+A+TEST+SMS
+
+The above URL will send SMS from account abcd to mobile number 9900XXXXXX with
+sender ID as DEMO with text message as "THIS IS A TEST SMS"
+
+Note that some parameters in the URL are static.You will get static values
+from your SMS Provider like username, password etc. These static values should
+be entered in the Static Parameters table.
+
+![SMS Setting](assets/old_images/erpnext/sms-settings1.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/stock-reconciliation-for-non-serialized-item.md b/erpnext/docs/user/guides/setting-up/stock-reconciliation-for-non-serialized-item.md
new file mode 100644
index 0000000..21049c4
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/stock-reconciliation-for-non-serialized-item.md
@@ -0,0 +1,158 @@
+Stock Reconciliation is the process of counting and evaluating stock-in-trade,
+usually at an organisations year end in order to value the total stock for
+preparation of the accounts. In this process actual physical stocks are
+checked and recorded in the system. The actual stocks and the stock in the system should be in agreement and accurate. If they are not, you can
+use the stock reconciliation tool to reconcile stock balance and value with actuals.
+
+**Difference between Serialized and Non-serialized Items.**
+
+A serial number is a unique, identifying number or group of numbers and
+letters assigned to an individual Item. Serialized items are generally high value items for which you need to warranty's and service agreements. Mostly items as machinery, equipments and high-value electronics (computers, printers etc.) are serialized.
+
+Non Serialized items are generally fast moving and low value item, hence doesn't need tracking for each unit. Items like screw, cotton waste, other consumables, stationary products can be categorized as non-serialized.
+
+> Stock Reconciliation option is available for the non serialized Items only. For seriazlized and batch items, you should create Material Receipt entry in Stock Entry form.
+
+### Opening Stocks
+
+You can upload your opening stock balance in the system using Stock Reconciliation.
+Stock Reconciliation will update your stock for a given Item on a given date
+for a given Warehouse to the given quantity.
+
+To perform Stock Reconciliation, go to:
+
+> Stock > Tools > Stock Reconciliation > New
+
+#### Step 1: Download Template
+
+A predefined template of an spreadsheet file should be followed for importing item's stock levels and valuations. Open new Stock Reconciliation form to see download option.
+
+<img class="screenshot" alt="Stock Reconciliation" src="assets/img/setup/stock-recon-1.png">
+
+#### Step 2: Enter Data in csv file.
+
+![Stock Reco Data](assets/old_images/erpnext/stock-reco-data.png)
+
+The csv format is case-sensitive. Do not edit the headers which are preset in the template. In the Item Code and Warehouse column, enter exact Item Code and Warehouse as created in your ERPNext account. For quatity, enter stock level you wish to set for that item, in a specific warehouse. If you do not want to change the quantity or valuation rate of an Item, you should leave it blank.
+
+Note: Make sure you do not put zero if you do not want to change the quantity
+amount or valuation amount. The system will calculate zero as zero quantity.
+So leave the field blank.
+
+#### **Step 3: Upload file and Enter Values in Stock Reconciliation Form
+
+<img class="screenshot" alt="Stock Reconciliation" src="assets/img/setup/stock-recon-2.png">
+
+**Posting Date**
+
+Posting Date will be date when you want uploaded stock to reflect in the report. Posting Date selection option allows you making back dated stock reconcialiation as well.
+
+**Difference Account:**
+
+When making Stock Reconciliation for updating **opening balance**, then you should select Balance Sheet account. By default **Temporary Opening** is created in the chart of account which can be used here.
+
+If you are making Stock Reconciliation for **correcting stock level or valuation of an item**, then you can select any expense account in which you would want difference amount (derived from difference of valuation of item) should be booked. If Expense Account is selected as Difference Account, you will also need to select Cost Center as it is mandatory with any income and expense account selection.
+
+After reviewing saved Reconciliation Data, submit the Stock Reconciliation. On
+successful submission, the data will be updated in the system. To check the
+submitted data go to stock and view stock level report.
+
+Note: While filling the valuation rates of Items, if you wish to find out the
+valuation rates of all items, you can go to stock and click on Item Prices
+report. The report will show you all types of rates.
+
+#### Step 4: Review the reconciliation data
+
+![Stock Reco Review](assets/old_images/erpnext/stock-reco-upload.png)
+
+### Stock Ledger Report
+
+![Stock Reco Ledger](assets/old_images/erpnext/stock-reco-ledger.png)
+
+**How Stock Reconciliation Works**
+
+Stock Reconciliation on a specific date means balance quantity frozen for that item on reconciliation date, and shall not get affected due to stock entries made before its date.
+
+Example:
+
+Item Code: ABC001
+Warehouse: Mumbai
+Let's assume stock as on 10th January is 100 nos.
+Stock Reconciliation is made on 12th January to bring stock balance to 150 nos.
+Existing Stock Ledger:
+<html>
+<style>
+    td {
+    padding:5px 10px 5px 5px;
+    };
+    img {
+    align:center;
+    };
+	table, th, td {
+    border: 1px solid black;
+    border-collapse: collapse;
+	}
+</style>
+ <table border="1" cellspacing="0px">
+            <tbody>
+                <tr align="center" bgcolor="#EEE">
+                    <td><b>Posting Date</b>
+                    </td>
+                    <td><b>Qty</b>
+                    </td>
+                    <td><b>Balance Qty</b>
+                    </td>
+                    <td><b>Voucher Type</b>
+                    </td>
+                </tr>
+                <tr>
+                    <td>10/01/2014</td>
+                    <td align="center">100</td>
+                    <td>100&nbsp;</td>
+                    <td>Purchase Receipt</td>
+                </tr>
+                <tr>
+                    <td>12/01/2014</td>
+                    <td align="center">50</td>
+                    <td>150</td>
+                    <td>Stock Reconciliation</td>
+                </tr>
+            </tbody>
+        </table>
+</html>
+Let's assume Purchase Receipt entry is made on 5th January, 2014, that is on date before Stock Reconciliation entry.
+<html>
+	<table border="1" cellspacing="0px">
+        <tbody>
+            <tr align="center" bgcolor="#EEE">
+                <td><b>Posting Date</b></td>
+                <td><b>Qty</b></td>
+                <td><b>Balance Qty</b></td>
+                <td><b>Voucher Type</b></td>
+            </tr>
+            <tr>
+                <td>05/01/2014</td>
+                <td align="center">20</td>
+                <td style="text-align: center;">20</td>
+                <td>Purchase Receipt</td>
+            </tr>
+            <tr>
+                <td>10/01/2014</td>
+                <td align="center">100</td>
+                <td style="text-align: center;">120</td>
+                <td>Purchase Receipt</td>
+            </tr>
+            <tr>
+                <td>12/01/2014</td>
+                <td align="center"><br></td>
+                <td style="text-align: center;"><b>150</b></td>
+                <td>Stock Reconciliation<br></td>
+            </tr>
+        </tbody>
+	</table>
+</html>
+As per the updated logic, irrespective of receipt/issue entry made for an item, balance quantity as set via Stock Reconciliation will not be affected.
+
+> Check out the video tutorial at https://www.youtube.com/watch?v=0yPgrtfeCTs
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/territory.md b/erpnext/docs/user/guides/setting-up/territory.md
new file mode 100644
index 0000000..7ef1a23
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/territory.md
@@ -0,0 +1,10 @@
+If your business operates in multiple Territories (could be countries, states
+or cities) it is usually a great idea to build your structure in the system.
+Once you group your Customers by Territories, you can set annual targets for
+each Item Group and get reports that will show your actual performance in the
+territory v/s what you had planned.
+You can also set different pricing for the same product sold across different territories.
+
+<img class="screenshot" alt="Territory Tree" src="assets/img/crm/territory-tree.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/setting-up/third-party-backups.md b/erpnext/docs/user/guides/setting-up/third-party-backups.md
new file mode 100644
index 0000000..5f352c9
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/third-party-backups.md
@@ -0,0 +1,54 @@
+If you wish to store your backups on a periodic basis,on Dropbox, you can do
+it directly through ERPNext.
+
+> Setup > Manage 3rd Party Backups
+
+__Step 1:__ Click on Setup.
+
+__Step 2:__ Click on Manage Third Party Backup
+
+#### Figure 1: Manage Third Party Backup
+
+![Third Party Backups](assets/old_images/erpnext/third-party-backups.png)
+
+On the Backup Manager page, enter the email addresses of those people whom you
+wish to notify about the upload status. Under the topic 'Sync with Dropbox',
+select whether you wish to upload Daily, Weekly or Never. 
+
+__Step 3__ Click on **Allow Dropbox Access**.
+
+> Tip: In future, if you wish to discontinue uploading backups to dropbox,
+then select the Never option.
+
+#### Figure 2: Allow Dropbox Access
+
+![Backup Manager](assets/old_images/erpnext/backup-manager.png)
+
+You need to login to your dropbox account, with your user id and password.
+
+![Dropbox Access](assets/old_images/erpnext/dropbox-access.png)
+
+## Open Source Users
+
+Installing Pre-Requisites
+
+    
+    
+    pip install dropbox
+    pip install google-api-python-client
+    
+
+  
+
+#### Create an App in Dropbox
+
+First create your Dropbox account and create a new app (https://www.dropbox.com/developers/apps).
+After successful creation of account you will receive `app_key`, `app_secret` and `access_type`. Now edit `site_config.json` of your site (/frappe-bench/sites/your-site/) and add the following lines:
+- `"dropbox_access_key": "app_key",` and 
+- `"dropbox_secret_key": "app_secret"`
+
+Then you can go to the "Integrations" module and Allow Dropbox Access.
+
+> Note: Please ensure Allow Pop-ups are enabled in your browser.
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/users-and-permissions/adding-users.md b/erpnext/docs/user/guides/setting-up/users-and-permissions/adding-users.md
new file mode 100644
index 0000000..c3408a6
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/users-and-permissions/adding-users.md
@@ -0,0 +1,43 @@
+# Adding Users
+
+Users can be added by the System Manager. If you are a System Manager, you can add Users via
+
+> Setup > User
+
+### 1. List of Users
+
+<img class="screenshot" src="assets/img/setup/users/user-1.png" alt="User List">
+
+
+To add a new user, click on "New"
+
+### 2. Add the user details
+
+Add user details such as First Name, Last Name, Email etc.
+
+The user's Email will become the user id.
+
+After adding these details, save the user.
+
+### 3. Setting Roles
+
+After saving, you will see a list of roles and a checkbox next to it. Just check the roles you want the
+the user to have and save the document. To click on what permissions translate into roles, click on the role
+name.
+
+<img class="screenshot" src="assets/img/setup/users/user-2.png" alt="User Roles">
+
+### 4. Setting Module Access
+
+Users will have access to all modules for which they have role based access. If you want to block certain modules for certain users, un-check the module from the list.
+
+<img class="screenshot" src="assets/img/setup/users/user-3.png" alt="User Block Module">
+
+### 5. Security Settings
+
+If you wish to give the user access to the system only between office hours,
+or during weekends, mention it under security settings.
+
+<img class="screenshot" src="assets/img/setup/users/user-4.png" alt="User Security">
+
+{next}
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/index.md b/erpnext/docs/user/guides/setting-up/users-and-permissions/index.md
similarity index 100%
rename from erpnext/docs/user/setting-up/users-and-permissions/index.md
rename to erpnext/docs/user/guides/setting-up/users-and-permissions/index.md
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/index.txt b/erpnext/docs/user/guides/setting-up/users-and-permissions/index.txt
similarity index 100%
rename from erpnext/docs/user/setting-up/users-and-permissions/index.txt
rename to erpnext/docs/user/guides/setting-up/users-and-permissions/index.txt
diff --git a/erpnext/docs/user/guides/setting-up/users-and-permissions/role-based-permissions.md b/erpnext/docs/user/guides/setting-up/users-and-permissions/role-based-permissions.md
new file mode 100644
index 0000000..d9c476d
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/users-and-permissions/role-based-permissions.md
@@ -0,0 +1,74 @@
+# Role Based Permissions
+
+ERPNext has a role-based permission system. It means that you can assign Roles to Users, and set Permissions on Roles. The permission structure also allows you to define different permission rules for different fields, using a concept called **Permission "Level"** of a field. Once roles are assigned to a user, it gives you the ability to limit access for a user to only specific documents.
+
+To start with, go to:
+> Setup > Permissions > Role Permissions Manager
+
+<img alt="Manage Read, Write, Create, Submit, Amend access using the Role Permissions Manager" class="screenshot" src="assets/img/users-and-permissions/setting-up-permissions-leave-application.png">
+
+Permissions are applied on a combination of:
+
+  * **Roles:** As we saw earlier, Users are assigned to Roles and it is on these Roles that permission rules are applied.
+
+  *Examples of Roles include Accounts Manager, Employee, HR User.*
+
+  * **Document Types:** Each type of document, master or transaction, has a separate list of Role based permissions.
+
+  *Examples of Document Types are Sales Invoice, Leave Application, Stock Entry, etc.*
+
+  * **Permission "Levels":** In each document, you can group fields by "levels". Each group of field is denoted by a unique number (0, 1, 2, 3, etc.). A separate set of permission rules can be applied to each field group. By default all fields are of level 0.
+
+    *Permission "Level" connects the group of fields with level X to a permission rule with level X.*
+
+  * **Document Stages:** Permissions are applied on each stage of the document like on Creation, Saving, Submission, Cancellation and Amendment. A role can be permitted to Print, Email, Import or Export data, access Reports, or define User Permissions.
+
+  * **Apply User Permissions:** This switch decides whether User Permissions should be applied for the role on selected Document Stages.
+
+	If enabled, a user with that role will be able to access only specific Documents for that Document Type. Such specific Document access is defined in the list of User Permissions. Additionally, User Permissions defined for other Document Types also get applied if they are related to the current Document Type through Link Fields.
+
+	To set, User Permissions go to:
+    > Setup > Permissions > [User Permissions Manager](/contents/setting-up/users-and-permissions/user-permissions)
+
+---
+
+**To add a new rule**, click on "Add a New Rule" button and a pop-up box will ask you to select a Role and a Permission Level. Once you select this and click on "Add", this will add a new row to your rules table.
+
+---
+
+Leave Application is a good **example** that encompasses all areas of Permission System.
+
+<img class="screenshot" alt="Leave Application Form should be created by an Employee, and approved by Leave Approver or HR User" src="assets/img/users-and-permissions/setting-up-permissions-leave-application-form.png">
+
+   1. **It should be created by an Employee.**
+     For this, Employee Role should be given Read, Write, Create permissions.
+
+<img class="screenshot" alt="Giving Read, Write and Create Permissions to Employee for Leave Application"  src="assets/img/users-and-permissions/setting-up-permissions-employee-role.png">
+
+   1. **An Employee should only be able to access his/her Leave Application.**
+     Hence, Apply User Permissions should be enabled for Employee Role, and a User Permission record should be created for each User Employee combination. (This effort is reduced for Employee Document Type, by programmatically creating User Permission records.)
+
+<img class="screenshot" alt="Limiting access to Leave Applications for a user with Employee Role via User Permissions Manager" src="assets/old_images/erpnext/setting-up-permissions-employee-user-permissions.png">
+
+   1. **HR Manager should be able to see all Leave Applications.**
+     Create a Permission Rule for HR Manager at Level 0, with Read permissions. Apply User Permissions should be disabled.
+
+<img class="screenshot" alt="Giving Submit and Cancel permissions to HR Manager for Leave Applications. 'Apply User Permissions' is unchecked to give full access." src="assets/img/users-and-permissions/setting-up-permissions-hr-manager-role.png">
+
+   2. **Leave Approver should be able to see and update Leave Applications applicable to him/her.**
+     Leave Approver is given Read and Write access at Level 0, with Apply User Permissions enabled. Relevant Employee Documents should be enlisted in the User Permissions of Leave Approvers. (This effort is reduced for Leave Approvers mentioned in Employee Documents, by programmatically creating User Permission records.)
+
+<img class="screenshot" alt="Giving Read, Write and Submit permissions to Leave Approver for Leave Applications.'Apply User Permissions' is checked to limit access based on Employee." src="assets/img/users-and-permissions/setting-up-permissions-leave-approver-role.png">
+
+   3. **It should be Approved / Rejected only by HR User or Leave Approver.**
+     The Status field of Leave Application is set at Level 1. HR User and Leave Approver are given Read and Write permissions for Level 1, while everyone else (All) are given Read permission for Level 1.
+
+<img class="screenshot" alt="Limiting read access for a set of fields to certain Roles" src="assets/old_images/erpnext/setting-up-permissions-level-1.png">
+
+
+   4. **HR User should be able to delegate Leave Applications to his/her subordinates**
+     HR User is given the right to Set User Permissions. A User with HR User role would be able to defined User Permissions on Leave Application for other users.
+
+<img class="screenshot" alt="Let HR User delegate access to Leave Applications by checking 'Set User Permissions'. This will allow HR User to access User Permissions Manager for 'Leave Application'" src="assets/img/users-and-permissions/setting-up-permissions-hr-user-role.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/users-and-permissions/sharing.md b/erpnext/docs/user/guides/setting-up/users-and-permissions/sharing.md
new file mode 100644
index 0000000..e39c010
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/users-and-permissions/sharing.md
@@ -0,0 +1,9 @@
+# Sharing
+
+In addition to user and role permissions, you can also Share a document with another user if you have sharing rights.
+
+To share a document, open the document, click on the "+" icon under sharing and select the user
+
+<img class="screenshot" src="assets/img/setup/users/share.gif">
+
+{next}
diff --git a/erpnext/docs/user/guides/setting-up/users-and-permissions/user-permissions.md b/erpnext/docs/user/guides/setting-up/users-and-permissions/user-permissions.md
new file mode 100644
index 0000000..58b89dc
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/users-and-permissions/user-permissions.md
@@ -0,0 +1,72 @@
+# User Permissions
+
+Limit access for a User to a set of documents using User Permissions Manager
+
+Role Base Permissions define the periphery of document types within which a user with a set of Roles can move around in. However, you can have an even finer control by defining User Permissions for a User. By setting specific documents in User Permissions list, you can limit access for that User to specific documents of a particular DocType, on the condition that "Apply User Permissions" is checked in Role Permissions Manager.
+
+To start with, go to:
+> Setup > Permissions > User Permissions Manager
+
+<figure>
+	<img src="assets/img/users-and-permissions/user-permissions-company.png"
+		class="img-responsive" alt="User Permissions Manager">
+	<figcaption>User Permissions Manager displaying how users can access only a specific Company.</figcaption>
+</figure>
+
+#### Example
+
+User 'aromn@example.com' has Sales User role and we want to limit the user to access records for only a specific Company 'Wind Power LLC'.
+
+  1. We add a User Permissions row for Company.
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permission-user-limited-by-company.png"
+			class="img-responsive" alt="User Permissions For Company">
+		<figcaption>Add User Permissions row for a combination of User 'aromn@example.com' and Company 'Wind Power LLC'.</figcaption>
+	</figure>
+
+  1. Also Role "All" has only Read permission for Company, with 'Apply User Permissions' checked.
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permissions-company-role-all.png"
+			class="img-responsive" alt="Role Permissions for All on Company">
+		<figcaption>Read Permission with Apply User Permissions checked for DocType Company.</figcaption>
+	</figure>
+
+  1. The combined effect of the above two rules lead to User 'aromn@example.com' having only Read access to Company 'Wind Power LLC'.
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permissions-company-wind-power-llc.png"
+			class="img-responsive" alt="Effect of Role and User Permissions on Company">
+		<figcaption>Access is limited to Company 'Wind Power LLC'.</figcaption>
+	</figure>
+
+  1. We want this User Permission on Company to get applied on other documents like Quotation, Sales Order, etc.
+These forms have a **Link Field based on Company**. As a result, User Permissions on Company also get applied on these documents, which leads to User 'aromn@example.com' to acces these documents having Company 'Wind Power LLC'.
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permissions-quotation-sales-user.png"
+			class="img-responsive" alt="Sales User Role Permissions for Quotation">
+		<figcaption>Users with Sales User Role can Read, Write, Create, Submit and Cancel Quotations based on their User Permissions, since 'Apply User Permissions' is checked.</figcaption>
+	</figure>
+	<figure>
+		<img src="assets/old_images/erpnext/user-permissions-quotation-list.png"
+			class="img-responsive" alt="Quotation List limited to results for Company 'Wind Power LLC'">
+		<figcaption>Quotation List is limited to results for Company 'Wind Power LLC' for User 'aromn@example.com'.</figcaption>
+	</figure>
+
+  1. User Permissions get applied automatically based on Link Fields, just like how it worked for Quotation. But, Lead Form has 4 Link fields: Territory, Company, Lead Owner and Next Contact By. Say, you want Leads to limit access to Users based only on Territory, even though you have defined User Permissions for DocTypes User, Territory and Company. You can do this by setting 'Ignore User Permissions' for Link fields: Company, Lead Owner and Next Contact By.
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permissions-lead-role-permissions.png"
+			class="img-responsive" alt="Role Permissions on Lead for Sales User Role">
+		<figcaption>Sales User can Read, Write and Create Leads limited by User Permissions.</figcaption>
+	</figure>
+	<figure>
+		<img src="assets/img/users-and-permissions/user-permissions-ignore-user-permissions.png"
+			class="img-responsive" alt="Set Ingore User Permissions from Setup > Customize > Customize Form">
+		<figcaption>Check 'Ingore User Permissions' for Company, Lead Owner and Next Contact By fields using Setup > Customize > Customize Form for Lead.</figcaption>
+	</figure>
+	<figure>
+		<img src="assets/old_images/erpnext/user-permissions-lead-based-on-territory.png"
+			class="img-responsive" alt="Lead List is limited to records with Territory 'United States'">
+		<figcaption>Due to the effect of the above combination, User 'aromn@example.com' can only access Leads with Territory 'United States'.</figcaption>
+	</figure>
+
+{next}
+
diff --git a/erpnext/docs/user/guides/setting-up/workflows.md b/erpnext/docs/user/guides/setting-up/workflows.md
new file mode 100644
index 0000000..329eaf5
--- /dev/null
+++ b/erpnext/docs/user/guides/setting-up/workflows.md
@@ -0,0 +1,66 @@
+In order to allow multiple people to submit multiple requests, for approvals,
+by multiple users, ERPNext requires you to fill the workflow conditions.
+ERPNext tracks the multiple permissions before submission.
+
+Example of a leave application workflow is given below:
+
+If an user applies for a leave, then his request will be sent to the HR
+department. The HR department(HR User) will either reject or approve this
+request. Once this process is completed, the user's Manager(leave approver)
+will get an indication that the HR department has Accepted or Rejected. The
+Manager, who is the approving authority, will either Approve or Reject this
+request. Accordingly,the user will get his Approved or Rejected status.
+
+![Workflow](assets/old_images/erpnext/workflow-leave-fl.jpg)
+
+To make this Workflow and transition rules go to :
+
+> Setup > Workflow > New Workflow
+
+#### Step 1: Enter the different states of Leave Approval Process.
+
+<img class="screenshot" alt="Workflow" src="assets/img/setup/workflow-1.png">
+
+#### Step 2: Enter Transition Rules.
+
+<img class="screenshot" alt="Workflow" src="assets/img/setup/workflow-2.png">
+
+#### Notes:
+
+> Note 1: When you make a workflow you essentially overwrite the code that is
+written for that document. Thus the document will function based on your
+workflow and not based on the pre-set code settings. Hence there might be no
+submit button / option if you have not specified it in the workflow.
+
+> Note 2: Document status of saved is 0, of submitted is 1, and of cancelled is
+2.
+
+> Note 3: A document cannot be cancelled unless it is submitted.
+
+> Note 4: If you wish to give the option to cancel, you will have to write a
+workflow transition step that says from submitted you can cancel.
+
+  
+
+#### Example of a Leave Application Process:  
+
+Go to the Human Resources Module and click on Leave Application. Apply for a
+Leave.
+
+When a Leave Application is submitted, the status on the right hand corner of
+the page shows as "Applied"
+
+![Workflow Employee LA](assets/old_images/erpnext/workflow-employee-la.png)
+
+When the HR User logs in, he can either Approve or Reject. If approved the
+status on the right hand corner of the page shows as Approved. However, a blue
+band of information is displayed saying approval is pending by leave approver.
+
+![Leave Approver](assets/old_images/erpnext/workflow-hr-user-la.png)
+
+When the leave approver opens the Leave Application page, he should select the
+status and convert to Approved or Rejected.
+
+![Workflow Leave Approver](assets/old_images/erpnext/workflow-leave-approver-la.png)
+
+{next}
diff --git a/erpnext/docs/user/stock/accounting-of-inventory-stock/index.md b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/index.md
similarity index 100%
rename from erpnext/docs/user/stock/accounting-of-inventory-stock/index.md
rename to erpnext/docs/user/guides/stock/accounting-of-inventory-stock/index.md
diff --git a/erpnext/docs/user/stock/accounting-of-inventory-stock/index.txt b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/index.txt
similarity index 100%
rename from erpnext/docs/user/stock/accounting-of-inventory-stock/index.txt
rename to erpnext/docs/user/guides/stock/accounting-of-inventory-stock/index.txt
diff --git a/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md
new file mode 100644
index 0000000..f630691
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md
@@ -0,0 +1,38 @@
+Existing Users, need to follow some steps to activate the new Perpetual
+Inventory system. As Perpetual Inventory always maintains a sync between stock
+and account balance, it is not possible to enable it with existing Warehouse
+setup. You have to create a whole new set of Warehouses, each linked to
+relevant account.
+
+Steps:
+
+  * Nullify the balance of account heads (stock-in-hand / fixed-asset) which you are using to maintain available stock value, through a Journal Entry.
+
+  * As existing warehouses are linked to stock transactions which does not have corresponding accounting entries, those warehouses can not be used for perpetual inventory. You have to create new warehouses for the future stock transactions which will be linked to their respective accounts. While creating new warehouses, select an account group under which the child account for the warehouse will be created.
+
+  * Setup the following default accounts for each Company 
+
+    * Stock Received But Not Billed
+    * Stock Adjustment Account
+    * Expenses Included In Valuation
+    * Cost Center
+  * Activate Perpetual Inventory
+
+> Setup > Accounts Settings > Make Accounting Entry For Every Stock Movement
+
+![Activation](assets/old_images/erpnext/accounting-for-stock-1.png)  
+  
+
+  * Create Stock Entry (Material Transfer) to transfer available stock from existing warehouse to new warehouse. As stock will be available in the new warehouse, you should select the new warehouse for all the future transactions.
+
+System will not post any accounting entries for existing stock transactions
+submitted prior to the activation of Perpetual Inventory as those old
+warehouses will not be linked to any account. If you create any new
+transaction or modify/amend existing transactions, with old warehouse, there
+will be no corresponding accounting entries. You have to manually sync stock
+and account balance through Journal Entry.
+
+> Note: If you are already using old Perpetual Inventory system, it will be
+deactivated automatically. You need to follow the above steps to reactivate
+it.
+
diff --git a/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/perpetual-inventory.md b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/perpetual-inventory.md
new file mode 100644
index 0000000..b6adc36
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/accounting-of-inventory-stock/perpetual-inventory.md
@@ -0,0 +1,371 @@
+In perpetual inventory, system creates accounting entries for each stock
+transactions, so that stock and account balance will always remain same. The
+account balance will be posted against their respective account heads for each
+Warehouse. On saving of a Warehouse, the system will automatically create an
+account head with the same name as warehouse. As account balance is maintained
+for each Warehouse, you should create Warehouses, based on the type of items
+(Current / Fixed Assets) it stores.
+
+At the time of items received in a particular warehouse, the balance of asset
+account (linked to that warehouse) will be increased. Similarly when you
+deliver some items from that warehouse, an expense will be booked and the
+asset account will be reduced, based on the valuation amount of those items.
+
+## **Activation**
+
+  1. Setup the following default accounts for each Company 
+
+    * Stock Received But Not Billed
+    * Stock Adjustment Account
+    * Expenses Included In Valuation
+    * Cost Center
+  2. In perpetual inventory, the system will maintain seperate account balance for each warehouse under separate account head. To create that account head, enter "Create Account Under" in Warehouse master.
+
+  3. Activate Perpetual Inventory
+
+> Setup > Accounts Settings > Make Accounting Entry For Every Stock Movement
+
+* * *
+
+## **Example**
+
+Consider following Chart of Accounts and Warehouse setup for your company:
+
+#### Chart of Accounts
+
+  * Assets (Dr) 
+    * Current Assets
+    * Accounts Receivable 
+      * Jane Doe
+    * Stock Assets 
+      * Stores
+      * Finished Goods
+      * Work In Progress
+    * Tax Assets 
+      * VAT
+    * Fixed Assets
+    * Fixed Asset Warehouse
+  * Liabilities (Cr) 
+    * Current Liabilities
+    * Accounts Payable 
+      * East Wind Inc.
+    * Stock Liabilities 
+      * Stock Received But Not Billed
+    * Tax Liabilities 
+      * Service Tax
+  * Income (Cr) 
+    * Direct Income
+    * Sales Account
+  * Expenses (Dr) 
+    * Direct Expenses
+    * Stock Expenses 
+      * Cost of Goods Sold
+      * Expenses Included In Valuation
+      * Stock Adjustment
+      * Shipping Charges
+      * Customs Duty
+
+#### Warehouse - Account Configuration
+
+  * Stores
+  * Work In Progress
+  * Finished Goods
+  * Fixed Asset Warehouse
+
+### **Purchase Receipt**
+
+Suppose you have purchased _10 nos_ of item "RM0001" at _$200_ and _5 nos_ of
+item "Desktop" at **$100** from supplier "East Wind Inc". Following are the
+details of Purchase Receipt:
+
+**Supplier:** East Wind Inc.
+
+**Items:**
+
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Item</th>
+            <th>Warehouse</th>
+            <th>Qty</th>
+            <th>Rate</th>
+            <th>Amount</th>
+            <th>Valuation Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>RM0001</td>
+            <td>Stores</td>
+            <td>10</td>
+            <td>200</td>
+            <td>2000</td>
+            <td>2200</td>
+        </tr>
+        <tr>
+            <td>Desktop</td>
+            <td>Fixed Asset Warehouse</td>
+            <td>5</td>
+            <td>100</td>
+            <td>500</td>
+            <td>550</td>
+        </tr>
+    </tbody>
+</table>
+<p><strong>Taxes:</strong>
+</p>
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Account</th>
+            <th>Amount</th>
+            <th>Category</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>Shipping Charges</td>
+            <td>100</td>
+            <td>Total and Valuation</td>
+        </tr>
+        <tr>
+            <td>VAT</td>
+            <td>120</td>
+            <td>Total</td>
+        </tr>
+        <tr>
+            <td>Customs Duty</td>
+            <td>150</td>
+            <td>Valuation</td>
+        </tr>
+    </tbody>
+</table>
+<p><strong>Stock Ledger</strong>
+</p>
+
+![pr<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-2.png)
+
+**General Ledger**
+
+![pr<em>general</em>ledger](assets/old_images/erpnext/accounting-for-stock-3.png)
+
+As stock balance increases through Purchase Receipt, "Store" and "Fixed Asset
+Warehouse" accounts are debited and a temporary account "Stock Receipt But Not
+Billed" account is credited, to maintain double entry accounting system. At the same time, negative expense is booked in account "Expense included in Valuation" for the amount added for valuation purpose, to avoid double expense booking.
+
+* * *
+
+### **Purchase Invoice**
+
+On receiving Bill from supplier, for the above Purchase Receipt, you will make
+Purchase Invoice for the same. The general ledger entries are as follows:
+
+**General Ledger**
+
+![pi<em>general</em>ledger](assets/old_images/erpnext/accounting-for-stock-4.png)
+
+Here "Stock Received But Not Billed" account is debited and nullified the
+effect of Purchase Receipt.
+
+* * *
+
+### **Delivery Note**
+
+Lets say, you have an order from "Jane Doe" to deliver 5 nos of item "RM0001"
+at $300. Following are the details of Delivery Note:
+
+**Customer:** Jane Doe
+
+**Items:**
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Item</th>
+            <th>Warehouse</th>
+            <th>Qty</th>
+            <th>Rate</th>
+            <th>Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>RM0001</td>
+            <td>Stores</td>
+            <td>5</td>
+            <td>300</td>
+            <td>1500</td>
+        </tr>
+    </tbody>
+</table>
+<p><strong>Taxes:</strong>
+</p>
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Account</th>
+            <th>Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>Service Tax</td>
+            <td>150</td>
+        </tr>
+        <tr>
+            <td>VAT</td>
+            <td>100</td>
+        </tr>
+    </tbody>
+</table>
+
+**Stock Ledger**
+
+![dn<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-5.png)
+
+**General Ledger**
+
+![dn<em>general</em>ledger](assets/old_images/erpnext/accounting-for-stock-6.png)
+
+As item is delivered from "Stores" warehouse, "Stores" account is credited and
+equal amount is debited to the expense account "Cost of Goods Sold". The
+debit/credit amount is equal to the total valuation amount (buying cost) of
+the selling items. And valuation amount is calculated based on your prefferred
+valuation method (FIFO / Moving Average) or actual cost of serialized items.
+
+    
+    
+        
+    In this example, we have considered valuation method as FIFO. 
+    Valuation Rate  = Purchase Rate + Charges Included in Valuation 
+                    = 200 + (250 * (2000 / 2500) / 10) 
+                    = 220
+    Total Valuation Amount  = 220 * 5 
+                            = 1100
+        
+    
+
+* * *
+
+### **Sales Invoice with Update Stock**
+
+Lets say, you did not make Delivery Note against the above order and instead
+you have made Sales Invoice directly, with "Update Stock" options. The details
+of the Sales Invoice are same as the above Delivery Note.
+
+**Stock Ledger**
+
+![si<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-7.png)
+
+**General Ledger**
+
+![si<em>general</em>ledger](assets/old_images/erpnext/accounting-for-stock-8.png)
+
+Here, apart from normal account entries for invoice, "Stores" and "Cost of
+Goods Sold" accounts are also affected based on the valuation amount.
+
+* * *
+
+### **Stock Entry (Material Receipt)**
+
+**Items:**
+
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Item</th>
+            <th>Target Warehouse</th>
+            <th>Qty</th>
+            <th>Rate</th>
+            <th>Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>RM0001</td>
+            <td>Stores</td>
+            <td>50</td>
+            <td>220</td>
+            <td>11000</td>
+        </tr>
+    </tbody>
+</table>
+
+**Stock Ledger**
+
+![mr<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-9.png)
+
+**General Ledger**
+
+![mr<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-10.png)
+
+* * *
+
+### **Stock Entry (Material Issue)**
+
+**Items:**
+
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Item</th>
+            <th>Source Warehouse</th>
+            <th>Qty</th>
+            <th>Rate</th>
+            <th>Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>RM0001</td>
+            <td>Stores</td>
+            <td>10</td>
+            <td>220</td>
+            <td>2200</td>
+        </tr>
+    </tbody>
+</table>
+
+**Stock Ledger**
+
+![mi<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-11.png)
+
+**General Ledger**
+
+![mi<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-12.png)
+
+* * *
+
+### **Stock Entry (Material Transfer)**
+
+**Items:**
+
+<table class="table table-bordered">
+    <thead>
+        <tr>
+            <th>Item</th>
+            <th>Source Warehouse</th>
+            <th>Target Warehouse</th>
+            <th>Qty</th>
+            <th>Rate</th>
+            <th>Amount</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>RM0001</td>
+            <td>Stores</td>
+            <td>Work In Progress</td>
+            <td>10</td>
+            <td>220</td>
+            <td>2200</td>
+        </tr>
+    </tbody>
+</table>
+
+**Stock Ledger**
+
+![mtn<em>stock</em>ledger](assets/old_images/erpnext/accounting-for-stock-13.png)
+
+**General Ledger**
+
+![mtn<em>general</em>ledger](assets/old_images/erpnext/accounting-for-stock-14.png)
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/batch.md b/erpnext/docs/user/guides/stock/batch.md
new file mode 100644
index 0000000..cdb9cdd
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/batch.md
@@ -0,0 +1,25 @@
+Batch inventory feature in ERPNext allows you to group multiple units of an item, 
+and assign them a unique value/number/tag called Batch No.
+
+The practise of stocking based on batch is mainly followed in the pharmaceutical industry. 
+Medicines/drugs produced in a particular batched is assigned a unique id. 
+This helps them updating and tracking manufacturing and expiry date for all the units produced under specific batch.
+
+> Note: To set item as a batch item, "Has Batch No" field should be updated as Yes in the Item master.
+
+On every stock transaction (Purchase Receipt, Delivery Note, POS Invoice) made for batch item, 
+you should provide item's Batch No. To create new Batch No. master for an item, go to:
+
+> Stock > Setup > Batch > New
+
+Batch master is created before creation of Purchase Receipt. 
+Hence eveytime there is Purchase Receipt or Production entry being made for a batch item, 
+you will first create its Batch No, and then select it in Purcase order or Production Entry.
+
+<img class="screenshot" alt="batch" src="assets/img/stock/batch.png">
+
+> Note: In stock transactions, Batch IDs will be filtered based on Item Code, Warehouse, 
+Batch Expiry Date (compared with Posting date of a transaction) and Actual Qty in Warehouse. 
+While searching for Batch ID  without value in Warehouse field, then Actual Qty filter won't be applied.
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/delivery-note.md b/erpnext/docs/user/guides/stock/delivery-note.md
new file mode 100644
index 0000000..e2cdd5e
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/delivery-note.md
@@ -0,0 +1,56 @@
+A Delivery Note is made when a shipment is shipped from the company’s
+Warehouse.
+
+A copy of the Delivery Note is usually sent with the transporter. The Delivery
+Note contains the list of Items that are sent in the shipment and updates the
+inventory.
+
+The entry of the Delivery Note is very similar to a Purchase Receipt. You can
+create a new Delivery Note from:
+
+> Stock > Delivery Note > New
+
+or from a “Submitted” Sales Order (that is not already shipped) by clicking on
+“Make Delivery Note”.
+
+<img class="screenshot" alt="Delivery Note" src="assets/img/stock/delivery-note.png">
+
+You can also “fetch” the details from an unshipped Sales Order.
+
+You will notice that all the information about unshipped Items and other
+details are carried over from your Sales Order.
+
+### Shipping Packets or Items with Product Bundle
+
+If you are shipping Items that have a [Product Bundle](/contents/selling/setup/sales-bom), ERPNext will automatically
+create a “Packing List” table for you based on the sub-Items in that Item.
+
+If your Items are serialized, then for Product Bundle type of Items, you will have
+to update the Serial Number in the “Packing List” table.
+
+### Packing Items in to Cases, for Container Shipment
+
+If you are doing container shipment or by weight, then you can use the Packing
+Slip to breakup your Delivery Note into smaller units. To make a Packing Slip
+go to:
+
+> Stock > Packing Slip > New Packing Slip
+
+You can create multiple Packing Slips for your Delivery Note and ERPNext will
+ensure that the quantities in the Packing Slip do not exceed the quantities in
+the Delivery Note.
+
+* * *
+
+#### Q. How to Print Without Amounts?
+
+If you want to print your Delivery Notes without the amount (this might be
+useful if you are shipping high value items), just check the “Print without
+Amount” box in the “More Info” section.
+
+#### What happens when the Delivery Note is “Submitted”?
+
+A Stock Ledger Entry is made for each Item and stock is updated. Pending
+Quantity in the Sales Order is updated (if applicable).
+
+{next}
diff --git a/erpnext/docs/user/stock/index.md b/erpnext/docs/user/guides/stock/index.md
similarity index 100%
rename from erpnext/docs/user/stock/index.md
rename to erpnext/docs/user/guides/stock/index.md
diff --git a/erpnext/docs/user/stock/index.txt b/erpnext/docs/user/guides/stock/index.txt
similarity index 100%
rename from erpnext/docs/user/stock/index.txt
rename to erpnext/docs/user/guides/stock/index.txt
diff --git a/erpnext/docs/user/guides/stock/installation-note.md b/erpnext/docs/user/guides/stock/installation-note.md
new file mode 100644
index 0000000..d59c8e4
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/installation-note.md
@@ -0,0 +1,5 @@
+You can use installation note to record the instalation of a product having a serial number.
+
+<img class="screenshot" alt="Installation Note" src="assets/img/stock/installation-note.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/item-price.md b/erpnext/docs/user/guides/stock/item-price.md
new file mode 100644
index 0000000..1a25670
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item-price.md
@@ -0,0 +1,43 @@
+Item Price is the record in which you can log sellig and buying rate of an item.
+
+There are two ways to reach to new Item Price form.
+
+> Selling/Buying/Stock >> Setup >> Item Price >> New Item Price
+
+Or
+
+> Item >> Add/Edit Prices >> Click on "+"  >> New Item Price
+
+Following are the steps to create new Item Price.
+
+Step 1: Select Price List
+
+You can create multiple Price List in ERPNext to track Selling and Buying Price List of an item separtely. Also if item's selling prices id changing based on territory, or due to other criteria, you can create multiple selling Price List for it.
+
+![Item Price list](assets/old_images/erpnext/item-price-list.png)
+
+On selection of Price List, its currency and for selling or buying property will be fetched as well.
+
+To have Item Price fetching in the sales or purchase transaction, you should have Price List id selected in the transaction, just above Item table.
+
+Step 2: Select Item
+
+Select item for which Item Price record is to be created. On selection of Item Code, Item Name and Description will be fetched as well.
+
+![Item Price Item](assets/old_images/erpnext/item-price-item.png)
+
+Step 3: Enter Rate
+
+Enter selling/buying rate of an item in Price List currency.
+
+![Item Price Rate](assets/old_images/erpnext/item-price-rate.png)
+
+Step 4: Save Item Price
+
+To check all Item Price together, go to:
+
+Stock >> Main Report >> Itemwise Price List Rate
+
+You will find option to create new Item Price record (+) in this report as well.
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/item-valuation-fifo-and-moving-average.md b/erpnext/docs/user/guides/stock/item-valuation-fifo-and-moving-average.md
new file mode 100644
index 0000000..2e1f286
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item-valuation-fifo-and-moving-average.md
@@ -0,0 +1,28 @@
+### How are Items Valued?
+
+One of the major features of any inventory system is that you can find out the
+value of any item based on its historic or average price. You can also find
+the value of all your items for your balance sheet.
+
+Valuation is important because:
+
+  * The buying price may fluctuate.
+  * The value may change because of some process (value add).
+  * The value may change because of decay, loss etc.
+
+You may encounter these terms, so lets clarify:
+
+  * Rate: Rate at which the transaction takes place.
+  * Valuation Rate: Rate at which the items value is set for your valuation.
+
+There are two major ways in which ERPNext values your items.
+
+  * **FIFO (First In First Out):** In this system, ERPNext assumes that you will consume / sell those Items first which you bought first. For example, if you buy an Item at price X and then after a few days at price Y, whenever you sell your Item, ERPNext will reduce the quantity of the Item priced at X first and then Y.
+
+![FIFO](assets/old_images/erpnext/fifo.png)
+
+  * **Moving Average:** In this method, ERPNext assumes that the value of the item at any point is the average price of the units of that Item in stock. For example, if the value of an Item is X in a Warehouse with quantity Y and another quantity Y1 is added to the Warehouse at cost X1, the new value X2 would be:
+
+> New Value X2 = (X * Y + X1 * Y1) / (Y + Y1)
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/item/index.md b/erpnext/docs/user/guides/stock/item/index.md
new file mode 100644
index 0000000..a369612
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item/index.md
@@ -0,0 +1,91 @@
+An Item is your companys' product or a service. The term Item is applicable to your core products as well as your raw materials. It can be a product or service that you buy/sell from your customers/ suppliers. ERPNext allows you to manage all sorts of items like raw-materials, sub-assemblies, finished goods, item variants and service items.
+
+ERPNext is optimized for itemized management of your sales and purchase. If you are in services, you can create an Item for each services that your offer. Completing the Item Master is very essential for successful implementation of ERPNext.
+
+## Item Properties
+
+  * **Item Name:** Item name is the actual name of your product or service.
+  * **Item Code:** Item Code is a short-form to denote your Item. If you have very few Items, it is advisable to keep the Item Name and the Item Code same. This helps new users to recognise and update Item details in all transactions. In case you have lot of Items with long names and the list runs in hundreds, it is advisable to code. To understand naming Item codes see [Item Codification](/contents/stock/item/item-codification)
+  * **Item Group:** Item Group is used to categorize an Item under various criterias like products, raw materials, services, sub-assemblies, consumables or all Item groups. Create your default Item Group list under Setup> Item Group and pre-select the option while filling your New Item details under [Item Group](/contents/stock/setup/item-group)
+  * **Default Unit of Measure:** This is the default measuring unit that you will use for your product. It could be in nos, kgs, meters, etc. You can store all the UOM’s that your product will require under Set Up> Master Data > UOM. These can be preselected while filling New Item by using % sign to get a pop up of the UOM list.
+  * **Brand:** If you have more than one brand save them under Set Up> Master Data> Brand and pre-select them while filling a New Item.
+  * **Variant:** A Item Variant is a different version of a Item.To learn more about managing varaints see [Item Variants](/contents/stock/item/item-variants)
+  
+### Upload an Image
+
+To upload an image for your icon that will appear in all transactions, save
+the partially filled form. Only after your file is saved  the 'upload' button will
+work above the Image icon. Click on this sign and upload the image.
+
+### Inventory : Warehouse and Stock Setting
+
+In ERPNext, you can select different type of Warehouses to stock your
+different Items. This can be selected based on Item types. It could be Fixed
+Asset Item, Stock Item or even Manufacturing Item.
+
+  * **Stock Item:** If you are maintaining stock of this Item in your Inventory, ERPNext will make a stock ledger entry for each transaction of this item.
+  * **Default Warehouse:** This is the Warehouse that is automatically selected in your transactions. 
+  * **Allowance Percentage:** This is the percent by which you will be allowed to over-bill or over-deliver this Item. If not set, it will select from the Global Defaults. 
+  * **Valuation Method:** There are two options to maintain valuation of stock. FIFO (first in - first out) and Moving Average. To understand this topic in detail please visit “ Item Valuation, FIFO and Moving Average”.
+
+### Serialized and Batched Inventory
+
+These numbers help to track individual units or batches of Items which you sell. It also tracks warranty and returns. In case any individual Item is recalled by the supplier the number system helps to track individual Item. The numbering system also manages expiry dates. Please note that if you sell your items in thousands, and if the items are very small like pens or erasers, you need not serialize them. In ERPNext, you will have to mention the serial number in some accounting entries. To create serial numbers you will have to manually create all the numbers in your entries. If your product is not a big consumer durable Item, if it has no warranty and has no chances of being recalled, avoid giving serial numbers.
+
+> Important: Once you mark an item as serialized or batched or neither, you cannot change it after you have made any stock entry.
+
+  * [Discussion on Serialized Inventory](/contents/setting-up/stock-reconciliation-for-non-serialized-item)  
+
+### Re Ordering
+
+  * **Re-order level** suggests the amount of stock balance in the Warehouse. 
+  * **Re-order Qty** suggests the amount of stock to be ordered to maintain minimum stock levels.
+  * **Minimum Order Qty** is the minimum quantity for which a Material Request / Purchase Order must be made.
+
+### Item Tax
+
+These settings are required only if a particular Item has a different tax rate
+than the rate defined in the standard tax Account. For example, If you have a
+tax Account, “VAT 10%” and this particular Item is exempted from tax, then you
+select “VAT 10%” in the first column, and set “0” as the tax rate in the
+second column.
+
+Go to [Setting Up Taxes](/contents/setting-up/setting-up-taxes) to understand this topic in detail.
+
+### Inspection
+
+Inspection Required: If an incoming inspection (at the time of delivery from
+the Supplier) is mandatory for this Item, mention “Inspection Required” as
+“Yes”. The system will ensure that a Quality Inspection will be prepared and
+approved before a Purchase Receipt is submitted.
+
+Inspection Criteria: If a Quality Inspection is prepared for this Item, then
+this template of criteria will automatically be updated in the Quality
+Inspection table of the Quality Inspection. Examples of Criteria are: Weight,
+Length, Finish etc.
+
+### Purchase Details
+
+![Purchase Details](assets/old_images/erpnext/item-purchase.png)
+
+**Lead time days:** Lead time days are the number of days required for the Item to reach the warehouse.
+
+**Default Expense Account:** It is the account in which cost of the Item will be debited.
+
+**Default Cost Centre:** It is used for tracking expense for this Item.
+
+### Sales Details
+
+![Sales Details](assets/old_images/erpnext/item-sales.png)
+
+**Default Income Account:** Income account selected here will be fetched automatically in sales invoice for this item.
+
+**Cost Centre:** Cost center selected here will be fetched automatically in sales invoice for this item.
+
+### Manufacturing And Website
+
+![Manufacturing](assets/old_images/erpnext/item-manufacturing-website.png)
+
+Visit [Manufacturing](/contents/manufacturing) and [Website ](/contents/website)to understand these topics in detail.
+
+{next}
diff --git a/erpnext/docs/user/stock/item/index.txt b/erpnext/docs/user/guides/stock/item/index.txt
similarity index 100%
rename from erpnext/docs/user/stock/item/index.txt
rename to erpnext/docs/user/guides/stock/item/index.txt
diff --git a/erpnext/docs/user/stock/item/item-codification.md b/erpnext/docs/user/guides/stock/item/item-codification.md
similarity index 100%
rename from erpnext/docs/user/stock/item/item-codification.md
rename to erpnext/docs/user/guides/stock/item/item-codification.md
diff --git a/erpnext/docs/user/guides/stock/item/item-variants.md b/erpnext/docs/user/guides/stock/item/item-variants.md
new file mode 100644
index 0000000..1f3300d
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item/item-variants.md
@@ -0,0 +1,24 @@
+A Item Variant is a different version of a Item, such as differing sizes or differing colours.
+Without Item variants, you would have to treat the small, medium and large versions of a t-shirt as three separate Items; 
+Item variants let you treat the small, medium and large versions of a t-shirt as variations of the same Item.
+
+To use Item Variants in ERPNext, create an Item and check 'Has Variants'
+
+* The Item shall then be referred as a 'Template'
+
+<img class="screenshot" alt="Has Variants" src="assets/img/stock/item-has-variants.png">
+
+On selecting 'Has Variants' a table shall appear. Specify the variant attributes for the Item in the table.
+In case the attribute has Numeric Values, you can specify the range and increment values here. 
+
+<img class="screenshot" alt="Valid Attributes" src="assets/img/stock/item-attributes.png">
+
+> Note: You cannot make Transactions against a 'Template'
+
+To create 'Item Variants' against a 'Template' select 'Make Variants'
+
+<img class="screenshot" alt="Make Variants" src="assets/img/stock/make-variant.png">
+
+<img class="screenshot" alt="Make Variants" src="assets/img/stock/make-variant-1.png">
+
+To learn more about setting Attributes Master check [Item Attributes](/contents/stock/setup/item-attribute)
diff --git a/erpnext/docs/user/guides/stock/item/purchase-details.md b/erpnext/docs/user/guides/stock/item/purchase-details.md
new file mode 100644
index 0000000..e4acac6
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item/purchase-details.md
@@ -0,0 +1,22 @@
+# purchase details
+
+# How Do I Track Warranty Status?
+
+To track a warranty period, it is necessary that the Item is a serialized Item.
+When this Item is delivered, the delivery date and the expiry period is saved in the serial number master. Through the serial number master you can track the warranty status.
+
+A warranty means a guarantee or a promise which provides assurance by one party to the other party which allows for a legal remedy if that promise is not true or followed. A warranty period is a time period in which a purchased product may be returned or exchanged.
+
+![Warranty](assets/old_images/erpnext/faq-warranty.png)
+
+# How To Name A Manufacturer Part Number?
+
+Go to the purchase details section of the Item form, and enter the number on the right hand side in the field ‘Manufacturer Part Number’
+
+> Stock > Item
+
+A manufacturer part number is a series of numbers and /or letters that has been given to a part by the manufacturer. The manufacturer part number belongs to the manufacturer and helps distinguish the part from other manufacturers. If two parts come from different manufacturers, they will have different MPNs. This allows businesses to identify which company made the part.
+
+![Part No](assets/old_images/erpnext/faq-manufacturer-part-no.png)
+
+__For Example:__ A refrigerator will have different parts which will have manufacturer part number. Thus, when any part fails and you want to replace it, you can simply order that part based on its part number.
diff --git a/erpnext/docs/user/guides/stock/item/reorder.md b/erpnext/docs/user/guides/stock/item/reorder.md
new file mode 100644
index 0000000..6b3d513
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/item/reorder.md
@@ -0,0 +1,26 @@
+# Re-Order 
+
+# How To Setup Re-order Level?
+
+Go to the Re-order section of the Item form in the Stock module.
+
+> Stock > Item
+
+The Re-order level is the point at which stock on a particular item has diminished to a point where it needs to be replenished. To order based on Re-order level can avoid shortages. Re-order level can be determined based on the lead time and the average daily consumption.
+
+![Reorder Level](assets/old_images/erpnext/faq-reorder-level.png)
+
+__For example:__ You can set your reorder level of bath towels at 10. When there are only 10 towels remaining in stock, the system will either send a mail or take action depending upon what you have selected in global settings.
+
+# How To Setup Reorder Quantity?
+
+To setup Reorder quantity, go to the Re-order section of the Item form. In the field ‘Re-order Qty’ type the amount that is needed.
+
+> Stock> Item
+
+Re-order quantity is the quantity to order, so that the sum of ordering cost and holding cost is at its minimum.The re-order quantity is based on the minimum order quantity specified by the supplier and many other factors.
+
+![Reorder Quantity](assets/old_images/erpnext/faq-reorder-qty.png)
+
+__For example:__ If reorder level is 100 items, your reorder quantity may not necessarily be 100 items. The Reorder quantity can be greater than or equal to reorder level. It may depend upon lead time, discount, transportation and average daily consumption.
+
diff --git a/erpnext/docs/user/guides/stock/material-request.md b/erpnext/docs/user/guides/stock/material-request.md
new file mode 100644
index 0000000..e1555db
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/material-request.md
@@ -0,0 +1,30 @@
+A Material Request is a simple document identifying a requirement of a set of
+Items (products or services) for a particular reason.
+
+![Workflow](assets/old_images/erpnext/material-request-workflow.jpg)
+
+To generate a Material Request manually go to:
+
+> Stock > Documents > Material Request > New
+
+#### Creating Material Request 
+
+<img class="screenshot" alt="Material Request" src="assets/img/buying/material-request.png">
+
+A Material Request can be generated:
+
+  * Automatically from a Sales Order.
+  * Automatically when the Projected Quantity of an Item in stores reaches a particular level.
+  * Automatically from your Bill of Materials if you use Production Plan to plan your manufacturing activities.
+  * If your Items are inventory items, you must also mention the Warehouse where you expect these Items to be delivered. This helps to keep track of the [Projected Quantity](/contents/stock/projected-quantity) for this Item.
+
+A Material Request can be of type:
+
+* Purchase - If the request material is to be purchased.
+* Material Transfer - If the requested material is to be shifted from one warehouse to another.
+* Material Issue - If the requested material is to be Issued.
+
+> Info: Material Request is not mandatory. It is ideal if you have centralized
+buying so that you can collect this information from various departments.
+
+{next}
diff --git a/erpnext/docs/user/stock/opening-stock.md b/erpnext/docs/user/guides/stock/opening-stock.md
similarity index 100%
rename from erpnext/docs/user/stock/opening-stock.md
rename to erpnext/docs/user/guides/stock/opening-stock.md
diff --git a/erpnext/docs/user/guides/stock/projected-quantity.md b/erpnext/docs/user/guides/stock/projected-quantity.md
new file mode 100644
index 0000000..0cac9aa
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/projected-quantity.md
@@ -0,0 +1,26 @@
+Projected Quantity is the level of stock that is predicted for a particular
+Item, based on the current stock levels and other requirements. It is the
+quantity of gross inventory that includes supply and demand in the past which
+is done as part of the planning process.
+
+The projected inventory is used by the planning system to monitor the reorder
+point and to determine the reorder quantity. The projected Quantity is used by
+the planning engine to monitor the safety stock levels. These levels are
+maintained to serve unexpected demands.
+
+Having a tight control of the projected inventory is crucial to determine
+shortages and to calculate the right order quantity.
+
+![Projected Quantity Stock Report](assets/old_images/erpnext/projected-quantity-stock-report.png)
+
+
+> Projected Qty = Actual Qty + Planned Qty + Requested Qty + Ordered Qty -
+Reserved Qty
+
+  * Actual Qty: Quantity available in the warehouse.
+  * Planned Qty: Quantity, for which, Production Order has been raised, but is pending to be manufactured.
+  * Requested Qty: Quantity requested for purchase, but not ordered.
+  * Ordered Qty: Quantity ordered for purchase, but not received.
+  * Reserved Qty: Quantity ordered for sale, but not delivered.
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/purchase-receipt.md b/erpnext/docs/user/guides/stock/purchase-receipt.md
new file mode 100644
index 0000000..0a79b96
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/purchase-receipt.md
@@ -0,0 +1,78 @@
+Purchase Receipts are made when you accept material from your Supplier usually
+against a Purchase Order.
+
+You can also accept Purchase Receipts directly ( Set Purchase Order
+Required as “No” in Global Defaults).
+
+You can make a Purchase Receipt directly from:
+
+> Stock > Purchase Receipt > New Purchase Receipt
+
+or from a “Submitted” Purchase Order, by clicking on “Make Purchase Receipt”.
+
+<img class="screenshot" alt="Purchase Receipt" src="assets/img/stock/purchase-receipt.png">
+
+### Rejections
+
+In the Purchase Receipt, you are required to enter whether all the materials
+you receive are of acceptable quality (in case you check). If you have any
+rejections, update the “Rejected Quantity” column in the Items table.
+
+If you reject, you are required to enter a “Rejected Warehouse” to indicate
+where you are storing the rejected Items.
+
+### Quality Inspections
+
+If for certain Items, it is mandatory to record Quality Inspections (if you
+have set it in your Item master), you will need to update the “Quality
+Inspection No” (QA No) column. The system will only allow you to “Submit” the
+Purchase Receipt if you update the “Quality Inspection No”.
+
+### UOM Conversions
+
+If your Purchase Order for an Item is in a different Unit of Measure (UOM)
+than what you stock (Stock UOM), then you will need to update the “UOM
+Conversion Factor”. 
+
+### Currency Conversions
+
+Since the incoming Item affects the value of your inventory, it is important
+to convert it into your base Currency, if you have ordered in another
+Currency. You will need to update the Currency Conversion Rate if applicable.
+
+### Taxes and Valuation
+
+Some of your taxes and charges may affect your Items value. For example, a Tax
+may not be added to your Item’s valuation, because if you sell the Item, you
+will have to add the tax at that time. So make sure to mark all your taxes in
+the Taxes and Charges table correctly for accurate valuation.
+
+### Serial Numbers and Batches
+
+If your Item is serialized or batched, you will have to enter Serial Number
+and Batch in the Item's table. You are allowed to enter multiple Serial Numbers
+in one row (each on a separate line) and you must enter the same number of
+Serial Numbers as the quantity. You must enter each Batch number on a separate
+line.
+
+* * *
+
+#### What happens when the Purchase Receipt is “Submitted”?
+
+A Stock Ledger Entry is created for each Item adding the Item in the Warehouse
+by the “Accepted Quantity” If you have rejections, a Stock Ledger Entry is
+made for each Rejection. The “Pending Quantity” is updated in the Purchase
+Order.
+
+* * *
+
+#### Adding value to your Items post Purchase Receipt:
+
+Some times, certain expenses that add value to your purchased Items are known
+only after a while. Common example is, if you are importing the Items, you
+will come to know of Customs Duty etc only when your “Clearing Agent” sends
+you a bill. If you want to attribute this cost to your purchased Items, you
+will have to use the Landed Cost Wizard. Why “Landed Cost”? Because it
+represents the charges that you paid when it landed in your possession.
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/purchase-return.md b/erpnext/docs/user/guides/stock/purchase-return.md
new file mode 100644
index 0000000..df86353
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/purchase-return.md
@@ -0,0 +1,21 @@
+ERPNext has an option for products that are need to be returned to the
+supplier. This may be on account of a number of reasons like defects in goods,
+quality not matching, the buyer not needing the stock, etc.
+
+You can create a Purchase Return by simply making a Purchase Receipt with negative quantity.
+
+First open the original Purchase Receipt, against which supplier delivered the items.
+
+<img class="screenshot" alt="Original Purchase Receipt" src="assets/img/stock/purchase-return-original-purchase-receipt.png">
+
+Then click on "Make Purchase Return", it will open a new Purchase Receipt with "Is Return" checked, items and taxes with negative amount.
+
+<img class="screenshot" alt="Return Against Purchase Receipt" src="assets/img/stock/purchase-return-against-purchase-receipt.png">
+
+On submission of Return Purchase Return, system will decrease item qty from the mentioned warehouse. To maintain correct stock valuation, stock balance will also go up according to the original purchase rate of the returned items.
+
+<img class="screenshot" alt="Return Stock Ledger" src="assets/img/stock/purchase-return-stock-ledger.png">
+
+If Perpetual Inventory enabled, system will also post accounting entry against warehouse account to sync warehouse account balance with stock balance as per Stock Ledger.
+
+<img class="screenshot" alt="Return Stock Ledger" src="assets/img/stock/purchase-return-general-ledger.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/sales-return.md b/erpnext/docs/user/guides/stock/sales-return.md
new file mode 100644
index 0000000..0105820
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/sales-return.md
@@ -0,0 +1,27 @@
+Goods sold being returned is quite a common practice in business. They could
+be returned by the customer on quality issues, non-delivery on agreed date, or
+any other reason. 
+
+In ERPNext, you can create a Sales Return by simply making a Delivery Note / Sales Invoice with negative quantity.
+
+First open the original Delivery Note / Sales Invoice, against which customer returned the items.
+
+<img class="screenshot" alt="Original Delivery Note" src="assets/img/stock/sales-return-original-delivery-note.png">
+
+Then click on "Make Sales Return", it will open a new Delivery Note with "Is Return" checked, items and taxes with negative amount.
+
+<img class="screenshot" alt="Return Against Delivery Note" src="assets/img/stock/sales-return-against-delivery-note.png">
+
+You can also create the return entry against original Sales Invoice, to return stock along with credit note, check "Update Stock" option in Return Sales Invoice.
+
+<img class="screenshot" alt="Return Against Sales Invoice" src="assets/img/stock/sales-return-against-sales-invoice.png">
+
+On submission of Return Delivery Note / Sales Invoice, system will increase stock balance in the mentioned warehouse. To maintain correct stock valuation, stock balance will go up according to the original purchase rate of the returned items.
+
+<img class="screenshot" alt="Return Stock Ledger" src="assets/img/stock/sales-return-stock-ledger.png">
+
+In case of Return Sales Invoice, Customer account will be credited and associated income and tax account will be debited.
+
+If Perpetual Inventory enabled, system will also post accounting entry against warehouse account to sync warehouse account balance with stock balance as per Stock Ledger.
+
+<img class="screenshot" alt="Return Stock Ledger" src="assets/img/stock/sales-return-general-ledger.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/serial-no.md b/erpnext/docs/user/guides/stock/serial-no.md
new file mode 100644
index 0000000..daeb7e1
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/serial-no.md
@@ -0,0 +1,33 @@
+As we discussed in the **Item** section, if an **Item** is _serialized_, a
+**Serial Number** (Serial No) record is maintained for each quantity of that
+**Item**. This information is helpful in tracking the location of the Serial
+No, its warranty and end-of-life (expiry) information.
+
+**Serial Nos** are also useful to maintain fixed assets. **Maintenance Schedules** can also be created against serial numbers for planning and scheduling maintenance activity for these assets (if they require maintenance).
+
+You can also track from which **Supplier** you purchased the **Serial No** and
+to which **Customer** you have sold it. The **Serial No** status will tell you
+its current inventory status.
+
+If your Item is _serialized_ you will have to enter the Serial Nos in the
+related column with each Serial No in a new line.
+You can maintain single units of serialized items using Serial Number.
+
+### Serial Nos and Inventory
+
+Inventory of an Item can only be affected if the Serial No is transacted via a
+Stock transaction (Stock Entry, Purchase Receipt, Delivery Note, Sales
+Invoice). When a new Serial No is created directly, its warehouse cannot be
+set.
+
+<img class="screenshot" alt="Serial Number" src="assets/img/stock/serial-no.png">
+
+* The Status is set based on Stock Entry.
+
+* Only Serial Numbers with status 'Available' can be delivered.
+
+* Serial Nos can automatically be created from a Stock Entry or Purchase Receipt. If you mention Serial No in the Serial Nos column, it will automatically create those serial Nos.
+
+* If in the Item Master, the Serial No Series is mentioned, you can leave the Serial No column blank in a Stock Entry / Purchase Receipt and Serial Nos will automatically be set from that series.
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/setup/index.md b/erpnext/docs/user/guides/stock/setup/index.md
similarity index 100%
rename from erpnext/docs/user/stock/setup/index.md
rename to erpnext/docs/user/guides/stock/setup/index.md
diff --git a/erpnext/docs/user/stock/setup/index.txt b/erpnext/docs/user/guides/stock/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/stock/setup/index.txt
rename to erpnext/docs/user/guides/stock/setup/index.txt
diff --git a/erpnext/docs/user/guides/stock/setup/item-attribute.md b/erpnext/docs/user/guides/stock/setup/item-attribute.md
new file mode 100644
index 0000000..d34f3a6
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/setup/item-attribute.md
@@ -0,0 +1,16 @@
+You can define Attributes and attribute values for your Item Variants here.
+
+<img class="screenshot" alt="Attribute Master" src="assets/img/stock/item-attribute.png">
+
+#### Non Numeric Attributes
+
+* For Non Numeric Attributes, specify attributes values along with its abbreviation in the Attribute Value Table.
+
+<img class="screenshot" alt="Attribute Master" src="assets/img/stock/item-attribute-non-numeric.png">
+
+#### Numeric Attributes
+
+* If your attribute is Numeric, select Numeric Values
+* Specify the Range and the Increment Value
+
+<img class="screenshot" alt="Attribute Master" src="assets/img/stock/item-attribute-numeric.png">
diff --git a/erpnext/docs/user/guides/stock/setup/item-group.md b/erpnext/docs/user/guides/stock/setup/item-group.md
new file mode 100644
index 0000000..0f8b655
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/setup/item-group.md
@@ -0,0 +1,26 @@
+Item Group is the classification category. Depending on the type of product,
+categorise it under its respective field. If the product is
+service oriented, name it under the group head - service. If the
+product is used as a raw-material, you have to name it under the Raw-material
+category. In case, your product is used only in trading, you can categorise it
+under Trading.
+
+<img class="screenshot" alt="Item Group Tree" src="assets/img/stock/item-group-tree.png">
+
+### Create a Item Group
+
+* Select an Item Group under which you wish to create the group.
+
+* Select 'Add Child'
+
+<img class="screenshot" alt="Add Item Group" src="assets/img/stock/item-group-new.gif">
+
+### Delete an Item Group
+
+* Select the Item Group you want to delete.
+
+* Select 'delete'
+
+<img class="screenshot" alt="Add Item Group" src="assets/img/stock/item-group-del.gif">
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/setup/stock-settings.md b/erpnext/docs/user/guides/stock/setup/stock-settings.md
new file mode 100644
index 0000000..9e79b6a
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/setup/stock-settings.md
@@ -0,0 +1,5 @@
+You can set default settings for your stock related transactions here.
+
+<img class="screenshot" alt="Stock Settings" src="assets/img/stock/stock-settings.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/stock-entry.md b/erpnext/docs/user/guides/stock/stock-entry.md
new file mode 100644
index 0000000..f0c88bf
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/stock-entry.md
@@ -0,0 +1,43 @@
+A Stock Entry is a simple document that lets you record Item movement from a
+Warehouse, to a Warehouse and between Warehouses.
+
+To make a Stock Entry you have to go to:
+
+> Stock > Stock Entry > New
+
+<img class="screenshot" alt="Stock Entry" src="assets/img/stock/stock-entry.png">
+
+Stock Entries can be made for the following purposes:
+
+* Material Issue - If the material is being issued. (Outgoing Material)
+* Material Receipt - If the material is being received. (Incoming Material)
+* Material Transfer - If the material is being moved from one warehouse to another.
+* Material Transfer for Manufacturing - If the material being transfered is for Manufacturing Process.
+* Manufacture - If the Material is being received from a Manufacturing/Production Operation.
+* Repack - If the Original item/items is being repacked into new item/items.
+* Subcontract - If the Material is being issued for a sub-contract activity.
+
+In the Stock Entry you have to update the Items table with all your
+transactions. For each row, you must enter a “Source Warehouse” or a “Target
+Warehouse” or both (if you are recording a movement).
+
+**Additional Costs:**
+
+If the stock entry is an incoming entry i.e any item is receiving at a target warehouse, you can add related additional costs (like Shipping Charges, Customs Duty, Operating Costs etc) assotiated with the process. The additional costs will be considered to calculate valuation rate of the items.
+
+To add additional costs, enter the description and amount of the cost in the Additional Costs table.
+
+<img class="screenshot" alt="Stock Entry Additional Costs" src="assets/img/stock/additional-costs-table.png">
+
+The added additional costs will be distributed among the receiving items (where the target warehouse mentioned) proportionately based on Basic Amount of the items. And the distributed additional cost will be added to the basic rate of the item, to calculate valuation rate.
+
+<img class="screenshot" alt="Stock Entry Item Valuation Rate" src="assets/img/stock/stock-entry-item-valuation-rate.png">
+
+If perpetual inventory system is enabled, additional costs will be booked in "Expense Included In Valuation" account.
+
+<img class="screenshot" alt="Additional Costs General Ledger" src="assets/img/stock/additional-costs-general-ledger.png">
+
+
+> **Note:** To update Stock from a spreadsheet, see Stock Reconciliation.
+
+{next}
diff --git a/erpnext/docs/user/stock/stock-how-to.md b/erpnext/docs/user/guides/stock/stock-how-to.md
similarity index 100%
rename from erpnext/docs/user/stock/stock-how-to.md
rename to erpnext/docs/user/guides/stock/stock-how-to.md
diff --git a/erpnext/docs/user/stock/tools/index.md b/erpnext/docs/user/guides/stock/tools/index.md
similarity index 100%
rename from erpnext/docs/user/stock/tools/index.md
rename to erpnext/docs/user/guides/stock/tools/index.md
diff --git a/erpnext/docs/user/stock/tools/index.txt b/erpnext/docs/user/guides/stock/tools/index.txt
similarity index 100%
rename from erpnext/docs/user/stock/tools/index.txt
rename to erpnext/docs/user/guides/stock/tools/index.txt
diff --git a/erpnext/docs/user/guides/stock/tools/landed-cost-voucher.md b/erpnext/docs/user/guides/stock/tools/landed-cost-voucher.md
new file mode 100644
index 0000000..d67ff23
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/tools/landed-cost-voucher.md
@@ -0,0 +1,33 @@
+Landed Cost is the total cost of a product to reach the product at the buyer’s door. Landed costs include the original cost of the item, complete shipping costs, customs duties, taxes, insurance and currency conversion fees etc. All of these components might not be applicable in every shipment, but relevant components must be considered as a part of the landed cost.
+
+> To understand landed cost better, let’s take an example based on our daily lives. You need to purchase a new washing machine for your home. Before making actual purchase, you probably do some investigation to know the best price. In this process, you often found a better deal from a store which is long away from your home. But you should also consider shipping cost while buying from that store. Total cost including transportation might be more than the price you get in your nearby store. In that case you will choose to buy from  your nearest store, as landed cost of the item is cheaper in the nearest store.
+
+Similarly in business, identifying landed cost for a item / product is very crucial, as it helps to decide selling cost of that item and impacts company’s profitability. Hence all applicable landed cost charges should be included in item’s valuation rate.
+
+According to the [Third-Party Logistics Study](http://www.3plstudy.com/), only 45% of the respondents stated that they use Landed Cost extensively. The main reasons of not using Landed Cost are unavailability of necessary data (49%), lack of right tools (48%), do not have sufficient time (31%) and not sure how to apply landed cost (27%).
+
+### Landed Cost via Purchase Receipt
+
+In ERPNext, you can add landed cost related charges in “Taxes and Charges” table while creating Purchase Receipt (PR). You should add those charges for “Total and Valuation” or “Valuation”. Charges which are payable to the same supplier from whom you are buying the items, should be tagged as “Total and Valuation”. Otherwise if applicable charges are payable to a 3rd party, it should be tagged as “Valuation”. On submission of PR, system will calculate landed cost of all items, considering those charges and that landed cost will be considered to calculate item’s valuation rate (based on FIFO / Moving Average method).
+
+But in reality, while making Purchase Receipt we might not know all the charges which are applicable for landed cost. Your transporter can send the invoice after 1 month, but there is no point in waiting for booking Purchase Receipt till then. Companies who imports their products / parts, pays a huge amount as Customs Duty. And generally they get invoices from Customs Department after a period of time. In these cases, “Landed Cost Voucher” becomes handy, as it allows you to add those additional charges on a later date, and to update landed cost of purchased items.
+
+### Landed Cost Voucher
+
+You can update landed cost any time in the future via Landed Cost Voucher.
+
+> Stock > Tools > Landed Cost Voucher
+
+In the document, you can select multiple Purchase Receipts and fetch all items from those Purchase Receipts. Then you should add applicable charges in “Taxes and Charges” table. You can easily delete an item if the added charges is not applicable to that item. The added charges are proportionately distributed among all the items based their amount.
+
+<img class="screenshot" alt="Landed Cost Vouher" src="assets/img/stock/landed-cost.png">
+
+### What happend on submission?
+
+1. On submission of Landed Cost Voucher, the applicable landed cost charges are updated in Purchase Receipt Item table.
+
+2. Valuation Rate of items are recalculated based on new landed cost. 
+
+3. If you are using “Perpetual Inventory”, the system will post general ledger entries to correct Stock-in-Hand balance. It will debit (increase) corresponding “warehouse account” and credit (decrease) “Expense Included in Valuation” account. If items are already delivered, the Cost-of-Goods-Sold (CoGS) value has been booked as per old valuation rate. Hence, general ledger entries are reposted for all future outgoing entries of associated items, to correct CoGS value.
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/tools/packing-slip.md b/erpnext/docs/user/guides/stock/tools/packing-slip.md
new file mode 100644
index 0000000..ea21fe2
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/tools/packing-slip.md
@@ -0,0 +1,7 @@
+A packing slip is a document listing the items in a shipment. Usually attached to the goods delivered.
+While Shipping a product 'Draft' for Delivery Notes are created.
+You can make a Packing Slip from these Delivery Notes (Draft)
+
+<img class="screenshot" alt="Packing Slip" src="assets/img/stock/packing-slip.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/tools/quality-inspection.md b/erpnext/docs/user/guides/stock/tools/quality-inspection.md
new file mode 100644
index 0000000..020447c
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/tools/quality-inspection.md
@@ -0,0 +1,8 @@
+In ERPNext, you can mark your incoming or outgoing products for Quality
+Inspection. To enable ERPNext to perform this function, go to :
+
+> Stock > Quality Inspection > New
+
+<img class="screenshot" alt="Quality Inspection" src="assets/img/stock/quality-inspection.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/guides/stock/tools/stock-uom-replace-utility.md b/erpnext/docs/user/guides/stock/tools/stock-uom-replace-utility.md
new file mode 100644
index 0000000..d8e92f4
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/tools/stock-uom-replace-utility.md
@@ -0,0 +1,10 @@
+#Stock UOM Replace Utility
+
+This tool will help you to change the UOM (Unit of measurement) of an existing Item.
+
+You need to select an Item, system fetches the Existing UOM of that item. You can then select the new UOM for that item 
+and specify the conversion factor.
+
+<img class="screenshot" alt="Stock Uom Replace" src="assets/img/stock/uom-replace.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/stock/warehouse.md b/erpnext/docs/user/guides/stock/warehouse.md
new file mode 100644
index 0000000..ec32215
--- /dev/null
+++ b/erpnext/docs/user/guides/stock/warehouse.md
@@ -0,0 +1,38 @@
+A warehouse is a commercial building for storage of goods. Warehouses are used
+by manufacturers, importers, exporters, wholesalers, transport businesses,
+customs, etc. They are usually large plain buildings in industrial areas of
+cities, towns, and villages. They mostly have loading docks to load and unload
+goods from trucks.
+
+To go to Warehouse, click on Stock and go to Warehouse under Masters.  You
+could also go to the Setup module and click on Warehouse under Master Data.
+
+> Stock > Warehouse > New Warehouse
+
+<img class="screenshot" alt="Warehouse" src="assets/img/stock/warehouse.png">
+
+In ERPNext, every Warehouse must belong to a specific company, to maintain
+company wise stock balance. The Warehouses are saved with their respective
+company’s abbreviations. This facilitates in identifying which Warehouse
+belongs to which company, at a glance.
+
+You can include user restrictions for these Warehouses. In case you do not
+wish a particular user to operate on a particular Warehouse, you can refrain
+the user from accessing that Warehouse.
+
+### Merge Warehouse
+
+In day to day transactions, duplicate entries are done by mistake, resulting
+in duplicate Warehouses. Duplicate records can be merged into a single
+Warehouse. From the top bar of the system select the File menu. Select Rename
+and Enter the correct Warehouse and check the Merge button. The system will
+replace all the links of wrong Warehouse with the correct Warehouse, in all
+transactions. Also, the available quantity (actual qty, reserved qty, ordered
+qty etc) of all items in the duplicate warehouse will be transferred to the
+correct warehouse. Once merging is done, delete the duplicate Warehouse.
+
+> Note: ERPNext system maintains stock balance for every distinct combination
+of Item and Warehouse. Thus you can get stock balance for any specific Item in
+a particular Warehouse on any particular date.
+
+{next}
diff --git a/erpnext/docs/user/support/index.md b/erpnext/docs/user/guides/support/index.md
similarity index 100%
rename from erpnext/docs/user/support/index.md
rename to erpnext/docs/user/guides/support/index.md
diff --git a/erpnext/docs/user/support/index.txt b/erpnext/docs/user/guides/support/index.txt
similarity index 100%
rename from erpnext/docs/user/support/index.txt
rename to erpnext/docs/user/guides/support/index.txt
diff --git a/erpnext/docs/user/guides/support/issue.md b/erpnext/docs/user/guides/support/issue.md
new file mode 100644
index 0000000..9033a95
--- /dev/null
+++ b/erpnext/docs/user/guides/support/issue.md
@@ -0,0 +1,47 @@
+Issue is an incoming query from your Customer, usually via email or
+from the “Contact” section of your website. (To fully integrate the Support
+Ticket to email, see the Email Settings section).
+
+> Tip: A dedicated support email id is a good way to integrate incoming
+queries via email. For example, you can send support queries to ERPNext at
+support@erpnext.com and it will automatically create a Issue in the
+Frappe system.
+
+
+
+> Support > Issue > New Issue
+
+<img class="screenshot" alt="Issue" src="assets/img/support/issue.png">
+
+#### Discussion Thread
+
+When a new email is fetched from your mailbox, a new Issue record is
+created and an automatic reply is sent to the sender indicating the Support
+Ticket Number. The sender can send additional information to this email. All
+subsequent emails containing this Issue number in the subject will be
+added to this Issue thread. The sender can also add attachments to
+the email.
+
+Issue maintains all the emails which are sent back and forth against
+this issue in the system so that you can track what transpired between the
+sender and the person responding.
+
+#### Status
+
+When a new Issue is created, its status is “Open”, when it is
+replied, its status becomes “Waiting for Reply”. If the sender replies back
+its status again becomes “Open”.
+
+#### Closing
+
+You can either “Close” the Issue manually by clicking on “Close
+Ticket” in the toolbar or if its status is “Waiting For Reply” . If the sender
+does not reply in 7 days, then the Issue closes automatically.
+
+#### Allocation
+
+You can allocate the Issue by using the “Assign To” feature in the
+right sidebar. This will add a new To Do to the user and also send a message
+indicating that this Issue is allocated.
+
+{next}
diff --git a/erpnext/docs/user/guides/support/maintenance-schedule.md b/erpnext/docs/user/guides/support/maintenance-schedule.md
new file mode 100644
index 0000000..2510da5
--- /dev/null
+++ b/erpnext/docs/user/guides/support/maintenance-schedule.md
@@ -0,0 +1,31 @@
+All machines require regular maintenance, specially those that contain a lot
+of moving parts, so if you are in the business of maintaining those or have
+some of them in your own premises, this is a useful tool to plan a calendar of
+activities for its maintenance.
+
+If the Customer Issue refers to “Breakdown Maintenance”, this refers to
+“Preventive Maintenance”.
+
+To create a new Maintenance Schedule go to:
+
+> Support > Maintenance Schedule > New Maintenance Schedule
+
+<img class="screenshot" alt="Maintenance Schedule" src="assets/img/support/maintenance-schedule.png">
+
+In the Maintenance Schedule, there are two sections:
+
+In the first section, you select the Items for which you want to generate the
+schedule and set how frequently you want to plan a visit or a maintenance.
+These can be optionally fetched from a Sales Order. After selecting the Items,
+“Save” the record.
+
+The second section contains the maintenance activities planned in the
+schedule. “Generate Schedule” will generate a separate row for each
+maintenance activity.
+
+Each Item in a Maintenance Schedule is allocated to a Sales Person.
+
+When the document is “Submitted” Calendar events are created in the User of
+the Sales Person for each maintenance.
+
+{next}
diff --git a/erpnext/docs/user/guides/support/maintenance-visit.md b/erpnext/docs/user/guides/support/maintenance-visit.md
new file mode 100644
index 0000000..690c2a8
--- /dev/null
+++ b/erpnext/docs/user/guides/support/maintenance-visit.md
@@ -0,0 +1,17 @@
+A Maintenance Visit is a record of a visit made by an engineer to a
+Customer’s premise usually against a Customer Issue. You can create a new
+Maintenance Visit from:
+
+> Support > Maintenance Visit > New Maintenance Visit
+
+<img class="screenshot" alt="Maintenance Visit" src="assets/img/support/maintenance-visit.png">
+
+The Maintenance Visit contains information about the:
+
+  * Customer.
+  * The Items that were inspected / maintenance activity was carried out on.
+  * Details of actions taken.
+  * The person who carried out the actions.
+  * Feedback from the Customer.
+
+{next}
diff --git a/erpnext/docs/user/guides/support/warranty-claim.md b/erpnext/docs/user/guides/support/warranty-claim.md
new file mode 100644
index 0000000..8506b3e
--- /dev/null
+++ b/erpnext/docs/user/guides/support/warranty-claim.md
@@ -0,0 +1,23 @@
+If you are selling **Items** under warranty or if you have sold and extended
+service contract like the Annual Maintenance Contract (AMC), your **Customer**
+may call you about an issue or a break-down and give you the Serial No of this
+Item.
+
+To record this, you can create a new **Warranty Claim** and add the
+**Customer** and **Item** / **Serial No**. The system will then automatically
+fetch the Serial No’s details and indicate whether this is under warranty or
+AMC.
+
+You must also add a description of the **Customer**’s issue and assign it to
+the person who needs to look into solving the issue.
+
+To create a new **Warranty Claim**:
+
+> Support > Warranty Claim > New Warranty Claim
+
+![Warranty Claim](assets/img/support/warranty-claim.png)
+
+If a Customer visit is required to address the issue, you can create a new
+Maintenance Visit record from this.
+
+{next}
diff --git a/erpnext/docs/user/guides/website/add-products-to-website.md b/erpnext/docs/user/guides/website/add-products-to-website.md
new file mode 100644
index 0000000..77035c8
--- /dev/null
+++ b/erpnext/docs/user/guides/website/add-products-to-website.md
@@ -0,0 +1,69 @@
+### Add Products to the Website
+
+To list your Item on the Website, fill the Item details and save the file.
+Once the file is saved, a plus (+) button will appear next to the Image icon.
+Click on the plus button and add your Item image. The html code will be
+generated automatically.
+
+##### Step 1: Save Image
+
+![Webimage](assets/old_images/erpnext/item-webimage.png)
+
+  
+
+##### Step 2: Check the 'Show in Website' box.
+
+Under the Website section, please check the box that says 'show in Website'.
+Once the box is checked, the page will display other fields for entering
+information.
+
+![Webimage](assets/old_images/erpnext/item-webimage-1.png)
+
+  
+
+##### Step 3: Enter Website Details
+
+![Webimage](assets/old_images/erpnext/item-webimage-2.png)
+
+The page name will be generated automatically. Mention the Item-Group under
+which the Item will be displayed.
+
+#### Item Groups
+
+Mention the Item Group under this column. If you wish to list your Item under
+the broad category products, name your Item Group as Products. In case you
+have various varieties of Item and want to classify them under different
+names, make Item Groups with those names and check the box that says 'show in
+Website'. For Example, if you wish to create a category called 'Bags', create
+a Item Group named Bags.
+
+![Item Group](assets/old_images/erpnext/itemgroup-webimage-bags.png)
+
+Once the Item Group is created go to the Website Settings page under Website.
+Enter the Label, Url, and Parent Label.
+
+![Item Group](assets/old_images/erpnext/itemgroup-website-settings.png)
+
+  
+
+#### Webpage labels
+
+![Webpage](assets/old_images/erpnext/webpage-labels.png)
+
+Add more Items under a particular Item Group.
+
+To add more Items under a certain Label, mention the Item Group on the Item
+Page. The Items will be added automatically on the Webpage, under the Item
+Group Label. For Example, To add Item-Kiddies Bag and Butterfly Print Bag,
+check the 'Show in Website'box. The Items will be placed under the Label Bags
+on the Webpage.
+
+![Item Group](assets/old_images/erpnext/itemgroup-websettings.png)
+
+  
+
+Item Group Display
+
+![Item Group Display](assets/old_images/erpnext/webpage-itemgroup-display.png)
+
+{next}
diff --git a/erpnext/docs/user/guides/website/blog-post.md b/erpnext/docs/user/guides/website/blog-post.md
new file mode 100644
index 0000000..043dfde
--- /dev/null
+++ b/erpnext/docs/user/guides/website/blog-post.md
@@ -0,0 +1,20 @@
+Blogs are a great way to share your thoughts about your business and keep your
+customers and readers updated of what you are up to.
+
+In the age of internet, writing assumes a lot of significance because when
+people come to your website, they want to read about you and your product.
+
+To create a new blog, just create a new Blog from:
+
+> Website > Blog > New Blog
+
+<img class="screenshot" alt="Blog Post" src="assets/img/website/blog-post.png">
+
+You can format a blog using the Markdown format.You can also access your blog
+by going to the page “blog.html”.
+
+#### A sample blog-page.
+
+<img class="screenshot" alt="Blog Sample" src="assets/img/website/blog-sample.png">
+
+{next}
diff --git a/erpnext/docs/user/guides/website/blogger.md b/erpnext/docs/user/guides/website/blogger.md
new file mode 100644
index 0000000..8ef573d
--- /dev/null
+++ b/erpnext/docs/user/guides/website/blogger.md
@@ -0,0 +1,6 @@
+Blogger is a user who can post blogs. 
+You can mention a shori bio about the blogger and also set a avatar here.
+
+<img class="screenshot" alt="Blogger" src="assets/img/website/blogger.png">
+
+{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/website/index.md b/erpnext/docs/user/guides/website/index.md
similarity index 100%
rename from erpnext/docs/user/website/index.md
rename to erpnext/docs/user/guides/website/index.md
diff --git a/erpnext/docs/user/website/index.txt b/erpnext/docs/user/guides/website/index.txt
similarity index 100%
rename from erpnext/docs/user/website/index.txt
rename to erpnext/docs/user/guides/website/index.txt
diff --git a/erpnext/docs/user/website/introduction-to-website.md b/erpnext/docs/user/guides/website/introduction-to-website.md
similarity index 100%
rename from erpnext/docs/user/website/introduction-to-website.md
rename to erpnext/docs/user/guides/website/introduction-to-website.md
diff --git a/erpnext/docs/user/guides/website/product-listing-on-website.md b/erpnext/docs/user/guides/website/product-listing-on-website.md
new file mode 100644
index 0000000..defd196
--- /dev/null
+++ b/erpnext/docs/user/guides/website/product-listing-on-website.md
@@ -0,0 +1,68 @@
+### Listing Item on Website
+
+To list your Item on the Website, fill the Item details and save the file.
+Once the file is saved, a plus (+) button will appear next to the Image icon.
+Click on the plus button and add your Item image. The html code will be
+generated automatically.
+
+##### Step 1: Save Image
+
+![Webimage](assets/old_images/erpnext/item-webimage.png)
+
+  
+
+##### Step 2: Check the 'Show in Website' box.
+
+Under the Website section, please check the box that says 'show in Website'.
+Once the box is checked, the page will display other fields for entering
+information.
+
+![Webimage](assets/old_images/erpnext/item-webimage-1.png)
+
+  
+
+##### Step 3: Enter Website Details
+
+![Webimage](assets/old_images/erpnext/item-webimage-2.png)
+
+The page name will be generated automatically. Mention the Item-Group under
+which the Item will be displayed.
+
+#### Item Groups
+
+Mention the Item Group under this column. If you wish to list your Item under
+the broad category products, name your Item Group as Products. In case you
+have various varieties of Item and want to classify them under different
+names, make Item Groups with those names and check the box that says 'show in
+Website'. For Example, if you wish to create a category called 'Bags', create
+a Item Group named Bags.
+
+![Item Group](assets/old_images/erpnext/itemgroup-webimage-bags.png)
+
+Once the Item Group is created go to the Website Settings page under Website.
+Enter the Label, Url, and Parent Label.
+
+![Item Group](assets/old_images/erpnext/itemgroup-website-settings.png)
+
+  
+
+#### Webpage labels
+
+![Webpage](assets/old_images/erpnext/webpage-labels.png)
+
+Add more Items under a particular Item Group.
+
+To add more Items under a certain Label, mention the Item Group on the Item
+Page. The Items will be added automatically on the Webpage, under the Item
+Group Label. For Example, To add Item-Kiddies Bag and Butterfly Print Bag,
+check the 'Show in Website'box. The Items will be placed under the Label Bags
+on the Webpage.
+
+![Item Group](assets/old_images/erpnext/itemgroup-websettings.png)
+
+  
+
+Item Group Display
+
+![Item Group Display](assets/old_images/erpnext/webpage-itemgroup-display.png)
+
diff --git a/erpnext/docs/user/website/setup/index.md b/erpnext/docs/user/guides/website/setup/index.md
similarity index 100%
rename from erpnext/docs/user/website/setup/index.md
rename to erpnext/docs/user/guides/website/setup/index.md
diff --git a/erpnext/docs/user/website/setup/index.txt b/erpnext/docs/user/guides/website/setup/index.txt
similarity index 100%
rename from erpnext/docs/user/website/setup/index.txt
rename to erpnext/docs/user/guides/website/setup/index.txt
diff --git a/erpnext/docs/user/website/setup/social-login-keys.md b/erpnext/docs/user/guides/website/setup/social-login-keys.md
similarity index 100%
rename from erpnext/docs/user/website/setup/social-login-keys.md
rename to erpnext/docs/user/guides/website/setup/social-login-keys.md
diff --git a/erpnext/docs/user/guides/website/setup/website-settings.md b/erpnext/docs/user/guides/website/setup/website-settings.md
new file mode 100644
index 0000000..5f86a04
--- /dev/null
+++ b/erpnext/docs/user/guides/website/setup/website-settings.md
@@ -0,0 +1,45 @@
+Most of the website related settings can be defined here.
+
+<img class="screenshot" alt="Website Settings" src="assets/img/website/website-settings.png">
+
+####Landing Page
+
+* Home Page: You can specify which [Web Page](/contents/website/web-page) must be the homepage of the website
+
+* Home Page is Products: if Checked, the Home page will be the default Item Group for the website.
+
+* Title Prefix: Set the browser title.
+
+####Website Theme
+
+Select the theme for the website. You can create new Theme for you website also.
+
+<img class="screenshot" alt="Website Theme" src="assets/img/website/website-theme.png">
+
+* Select 'create new website theme' if you wish to customize the default website theme.
+
+####Banner
+
+You can add a banner/ logo to your website here. Attach the image and click on set banner from Image.
+An HTML code will be generated by the system under Banner HTML.
+
+<img class="screenshot" alt="Banner" src="assets/img/website/banner.png">
+
+####Top Bar
+
+You can set the menus items in the Top Bar here.
+
+<img class="screenshot" alt="Top Bar" src="assets/img/website/top-bar.png">
+
+ * Similarlly you can also set sidebar and footer links.
+ 
+####Integrations & Miscellaneous Settings
+
+You can integrate the website using Google Analytics and enable social media sharing for post shared on the website.
+
+<img class="screenshot" alt="Integrations" src="assets/img/website/integrations.png">
+
+* You can disable public signup to your ERPNext account by checking 'disable signup'
+
+{next}
+
diff --git a/erpnext/docs/user/guides/website/shopping-cart.md b/erpnext/docs/user/guides/website/shopping-cart.md
new file mode 100644
index 0000000..8f9235f
--- /dev/null
+++ b/erpnext/docs/user/guides/website/shopping-cart.md
@@ -0,0 +1,41 @@
+On the Webpage, a shopping cart is an icon that allows you to store all the
+things that you have earmarked for purchasing. It is a graphical
+representation of a shopping basket or a shopping cart that allows you to save
+the items you intend to buy.
+
+This software displays the price of the product . It also displays shipping
+and handling charges, along with taxes, if applicable.
+
+To set up a shopping cart, go to the selling module.
+
+> Selling > Shopping Cart Settings
+
+#### Step 1: Enter Company Details and Default Territory.
+
+![Shopping Cart](assets/old_images/erpnext/shopping-cart-1.png)
+
+  
+
+#### Step 2: Enter Price List, Tax Master and Shipping Rule.
+
+![Shopping Cart](assets/old_images/erpnext/shopping-cart-2.png)
+
+  
+
+#### Shopping Cart Display
+
+On the Website, the shopping cart image will be seen below the Item price.
+Customers can click on the cart and enter the amount of quantity they wish to
+buy. The Item number will be stored on the right hand corner of the page, next
+to the flower sign.
+
+![Shopping Cart](assets/old_images/erpnext/shopping-cart-display-1.png)
+
+  
+
+Click on the flower sign on the right hand side to see the cart details. Click
+on the cart to get the final amount details.
+
+![Shopping Cart](assets/old_images/erpnext/shopping-cart-display-amount.png)
+
+{next}
diff --git a/erpnext/docs/user/website/styling-the-website.md b/erpnext/docs/user/guides/website/styling-the-website.md
similarity index 100%
rename from erpnext/docs/user/website/styling-the-website.md
rename to erpnext/docs/user/guides/website/styling-the-website.md
diff --git a/erpnext/docs/user/guides/website/web-form.md b/erpnext/docs/user/guides/website/web-form.md
new file mode 100644
index 0000000..5bffbda
--- /dev/null
+++ b/erpnext/docs/user/guides/website/web-form.md
@@ -0,0 +1,36 @@
+# Web Forms
+
+<p class="lead">Add forms to the website that will add / update data in your tables. Allow users to edit / manage multiple web forms</p>
+
+You can add forms in your website for example, Contact Us, Inquiry, Complaint etc. Data from these can fill up records like Lead, Opportunity, Issue etc. The user can also be allowed manage multiple records (like Complaints etc.)
+
+---
+
+### Creating
+
+To create a new **Web Form** go to:
+
+> Website > Web Form > New
+
+1. Set the Web Form title and url.
+1. Select the **DocType** in which you want the user to store the records.
+1. Select if you require the user to login, edit records, manage multiple records etc.
+1. Add the fields you want in the record.
+
+<img class="screenshot" alt="Web Form" src="assets/img/website/web-form.png">
+
+---
+
+### Viewing
+
+Once you create the web form, you can view it on the url and test it out!
+
+<img class="screenshot" alt="Web form" src="assets/img/website/web-form-view.png">
+
+---
+
+### Results
+
+Your data will be stored in the table you have selected
+
+{next}
diff --git a/erpnext/docs/user/guides/website/web-page.md b/erpnext/docs/user/guides/website/web-page.md
new file mode 100644
index 0000000..440f8bb
--- /dev/null
+++ b/erpnext/docs/user/guides/website/web-page.md
@@ -0,0 +1,32 @@
+<p class="lead">Static Content like your Home Page, About Us, Contact Us, Terms pages can be created using the Web Page. </p>
+
+To create a new Web Page, go to:
+
+> Website > Web Page > New
+
+<img class="screenshot" alt="Web Page" src="assets/img/website/web-page.png">
+
+#### Title
+
+The first thing to set is the title of your page. The title has the maximum
+weight for search engines so choose a title that reflects the keywords that
+you are targeting for your audience.
+
+#### Content
+
+After selecting your layout, you can add content (text, images, etc) to each
+of your content boxes. You can add content in Markdown or HTML format. Read
+the section on how to format using Markdown, for more details.
+
+#### Page Link
+
+The web link to your page will be the value of the “Page Name” field +
+“.html”. For example if your page name is contact-us, the web link of your
+page will be yoursite.com/contact-us.html.
+
+#### Images
+
+You can attach images to your web page and show them using the  HTML tag or
+using markdown format. the link to your file will be assets/manual_erpnext_com/old_images/erpnext/filename
+
+{next}
diff --git a/erpnext/docs/user/human-resources/appraisal.md b/erpnext/docs/user/human-resources/appraisal.md
deleted file mode 100644
index 4596c39..0000000
--- a/erpnext/docs/user/human-resources/appraisal.md
+++ /dev/null
@@ -1,24 +0,0 @@
-In ERPNext, you can manage Employee Appraisals by creating an Appraisal
-Template for each role with the parameters that define the performance by
-giving appropriate weightage to each parameter.
-
-> Human Resource > Appraisal > New
-
-#### Step 1: Select an Appraisal Template
-
-<img class="screenshot" alt="Appraisal" src="/assets/manual_erpnext_com/img/human-resources/appraisal.png">
-
-After you select the template, the remaining form appears.
-
-#### Step 2: Enter Employee Details
-
-<img class="screenshot" alt="Appraisal" src="/assets/manual_erpnext_com/img/human-resources/appraisal-employee.png">
-
-Once the Appraisal Template is completed, you can create Appraisal records for
-each period where you track performance. You can give points out of 5 for each
-parameter and the system will calculate the overall performance of the
-Employee.
-
-To make the Appraisal final, make sure to “Submit” it.
-
-{next}
diff --git a/erpnext/docs/user/human-resources/attendance.md b/erpnext/docs/user/human-resources/attendance.md
deleted file mode 100644
index dc95780..0000000
--- a/erpnext/docs/user/human-resources/attendance.md
+++ /dev/null
@@ -1,14 +0,0 @@
-An Attendance record stating that an Employee has been present on a particular
-day can be created manually by:
-
-> Human Resources > Attendance > New Attendance
-
-<img class="screenshot" alt="Attendence" src="/assets/manual_erpnext_com/img/human-resources/attendence.png">
-
-You can get a monthly report of your Attendance data by going to the “Monthly
-Attendance Details” report.
-
-You can also bulk uppload attendence using the [Upload Attendence Tool ](/contents/human-resources/tools/upload-attendance)
-
-{next}
-
diff --git a/erpnext/docs/user/human-resources/employee.md b/erpnext/docs/user/human-resources/employee.md
deleted file mode 100644
index 491aa36..0000000
--- a/erpnext/docs/user/human-resources/employee.md
+++ /dev/null
@@ -1,9 +0,0 @@
-There are many fields you can add in your Employee records.
-
-To create new Employee go to:
-
-> Human Resources > Employee > New
-
-<img class="screenshot" alt="Employee" src="/assets/manual_erpnext_com/img/human-resources/employee.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/expense-claim.md b/erpnext/docs/user/human-resources/expense-claim.md
deleted file mode 100644
index 200b7fb..0000000
--- a/erpnext/docs/user/human-resources/expense-claim.md
+++ /dev/null
@@ -1,39 +0,0 @@
-Expense Claim is made when Employee’s make expenses out of their pocket on
-behalf of the company. For example, if they take a customer out for lunch,
-they can make a request for reimbursement via the Expense Claim form.
-
-To make a new Expense Claim, go to:
-
-> HR > Expense Claim > New Expense Claim
-
-<img class="screenshot" alt="Expense Claim" src="/assets/manual_erpnext_com/img/human-resources/expense_claim.png">
-
-Set the Employee ID, date and the list of expenses that are to be claimed and
-“Submit” the record.
-
-### Approving Expenses
-
-The person making the claim must also set the id of the user who will
-“Approve” these expenses and set the “Assign To” to notify the user of the
-request Approve.
-
-If the Approver sees the “form”, she or he can update the “Approved Amounts”
-and click on “Approve”. To cancel the claim, they can click on the “Reject”
-button.
-
-Comments can be added in the Comments section explaining why the claim was
-approved or rejected.
-
-### Booking the Expense and Reimbursement
-
-The approved Expense Claim must then be converted into a Journal Entry and a
-payment must be made. Note: This amount should not be clubbed with Salary
-because the amount will then be taxable to the Employee.
-
-### Linking with Task & Project
-
-* To Link Expense Claim with Task or Project specify the Task or the Project while making an Expense Claim
-
-<img class="screenshot" alt="Expense Claim - Project Link" src="/assets/manual_erpnext_com/img/project/project_expense_claim_link.png">
-
-{next}
diff --git a/erpnext/docs/user/human-resources/holiday-list.md b/erpnext/docs/user/human-resources/holiday-list.md
deleted file mode 100644
index 47dac5b..0000000
--- a/erpnext/docs/user/human-resources/holiday-list.md
+++ /dev/null
@@ -1,59 +0,0 @@
-Holiday List is a list which contains the dates of holidays along with the
-occasion of that holiday. The list is generally valid for one calendar year.  
-
-Most organisations have a standard Holiday-List for their employees. Some even
-have different holiday lists for laborers and a different one for management
-staff.
-
-  
-
-To set up a holiday list in the system, Go to Human Resources Module and Click
-on Holiday List.
-
-  
-
-> Human Resources >Holiday List > New Holiday List  
-
-  
-#### Figure 1: Holiday List
-
-![](/assets/manual_erpnext_com/old_images/erpnext/holiday-list-1.png)  
-
-  
-
-__Step 1:__ Give a name to the Holiday list
-
-__Step 2:__ Mention the Fiscal Year  
-
-__Step 3:__ State the Weekly  off.  
-
-__Step 4:__ Click on the button 'Get Weekly Off Dates'  
-
-This step will fill the box below with yearly off dates with day as the
-description.
-
-__Step 5:__ Click on Add new row to add more dates  
-
-Mention the holiday reason in the description and select the date from the
-'Date' field.
-
-  
-#### Figure 2: Adding new holidays to the list
-
-![](/assets/manual_erpnext_com/old_images/erpnext/holiday-list-2.png)  
-
-  
-
-> Note 1: If you have selected a holiday list in the Employment Details form,
-the system will give priority to the form mentioned here. It will fetch the
-list mentioned in the form rather than the one which you may have specified as
-Default; However, if there is no list in the employment details form, the
-default list will be fetched.
-
-
-> Note 2: You can form as many holiday lists as you wish. For example, if you
-have a mill, you can have one list for mill workers and another list for
-office staff. You can manage between lists by attaching their respective
-holiday list to their respective employment detail form.
-
-{next}
diff --git a/erpnext/docs/user/human-resources/human-resources-reports.md b/erpnext/docs/user/human-resources/human-resources-reports.md
deleted file mode 100644
index f73c1ab..0000000
--- a/erpnext/docs/user/human-resources/human-resources-reports.md
+++ /dev/null
@@ -1,34 +0,0 @@
-Human Resources Reports
-
-### Employee Leave Balance
-
-Employee Leave Balance Report shows employees and their respective balance leaves under various leave types. Report is generated as per the number of allowed leaves.
-
-<img alt="Employee Leave Balance" class="screenshot" src="/assets/manual_erpnext_com/img/human-resources/employee-leave-balance-report.png">
-
-### Employee Birthday
-
-Employee Birthday Report shows Birthdays of your employees.
-
-<img alt="Employee Birthday" class="screenshot" src="/assets/manual_erpnext_com/img/human-resources/employee-birthday-report.png">
-
-### Employee Information
-
-Employee Information Report shows Report View of important information recorded in Employee master.
-
-<img alt="Employee Information" class="screenshot" src="/assets/manual_erpnext_com/img/human-resources/employee-information-report.png">
-
-### Monthly Salary Register
-
-Monthly Salary Register shows net pay and its components of employee(s) at a glance.
-
-<img alt="Monthly Salary Register" class="screenshot" src="/assets/manual_erpnext_com/img/human-resources/monthly-salary-register-report.png">
-
-
-### Monthly Attendance Sheet
-
-Monthly Attendance Sheet shows monthly attendance of selected employee at a glance.
-
-<img alt="Monthly Attendance Sheet" class="screenshot" src="/assets/manual_erpnext_com/img/human-resources/monthly-attendance-sheet-report.png">
-
-{next}
diff --git a/erpnext/docs/user/human-resources/job-applicant.md b/erpnext/docs/user/human-resources/job-applicant.md
deleted file mode 100644
index 8ccd91a..0000000
--- a/erpnext/docs/user/human-resources/job-applicant.md
+++ /dev/null
@@ -1,25 +0,0 @@
-You can mantain a list of People who have applied for a [Job Opening](/contents/human-resources/job-opening).
-
-To create a new Job Applicant go to 
-
-> Human Resource > Job Applicant > New
-
-<img class="screenshot" alt="Job Applicant" src="/assets/manual_erpnext_com/img/human-resources/job-applicant.png">
-
-### Linking with an Email Account
-
-You can link Job Application with an Email account.
-Suppose you link Job Application with an email job@example.com 
-system shall create a New Job Applicant against each email received on the mailbox.
-
-* To link Email Account with Job Applicant, go to
-
-> Setup > Email Account > New 
-
-* Enter the email id and the password, and select 'Enable Incoming'
-
-* In 'Append To' select 'Job Applicant'
-
-<img class="screenshot" alt="Email Account" src="/assets/manual_erpnext_com/img/human-resources/email-account.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/job-opening.md b/erpnext/docs/user/human-resources/job-opening.md
deleted file mode 100644
index abe0af6..0000000
--- a/erpnext/docs/user/human-resources/job-opening.md
+++ /dev/null
@@ -1,10 +0,0 @@
-You can make a record of the open vacancies in your company using Job Opening.
-
-To create a new Job Opening go to 
-
-> Human Resource > Job Opening > New
-
-<img class="screenshot" alt="Job Opening" src="/assets/manual_erpnext_com/img/human-resources/job-opening.png">
-
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/leave-application.md b/erpnext/docs/user/human-resources/leave-application.md
deleted file mode 100644
index 32cca01..0000000
--- a/erpnext/docs/user/human-resources/leave-application.md
+++ /dev/null
@@ -1,24 +0,0 @@
-If your company has a formal system where Employees have to apply for leaves
-to be able to qualify as paid leaveas, you can create Leave Application to
-track approval and usage of leaves. You have to mention the Employee, Leave
-Type and the period for which the leave is taken.
-
-> Human Resources > Leave Application > New Leave Application
-
-<img class="screenshot" alt="Leave Application" src="/assets/manual_erpnext_com/img/human-resources/leave-application.png">
-
-###Setting Leave Approver
-
-* A leave approver is a user who can approve an leave application for an employee. 
-
-* You need to mention a list of Leave Approvers against an Employee in the Employee Master.
-
-<img class="screenshot" alt="Leave Approver" src="/assets/manual_erpnext_com/img/human-resources/employee-leave-approver.png">
-
-> Tip : If you want all users to create their own Leave Applications, you can set
-their “Employee ID” as a match rule in the Leave Application Permission
-settings. See the earlier discussion on [Setting Up Permissions](/contents/setting-up/users-and-permissions)
-for more info.
-
-You assign Leaves aginast an Employee check [Leave Allocation](/contents/human-resources/setup/leave-allocation)
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/offer-letter.md b/erpnext/docs/user/human-resources/offer-letter.md
deleted file mode 100644
index 75dd848..0000000
--- a/erpnext/docs/user/human-resources/offer-letter.md
+++ /dev/null
@@ -1,16 +0,0 @@
-Offer Letter is given to candidate after Interview & selection which states the offered salary package, 
-designation, grade, department working, no of days entitled for leave.
-
-In ERPNext you can make a record of the Offer Letters that you can given to candidates. To create a new offer Letter go to 
-
-> Human Resource > Offer Letter > New
-
-<img class="screenshot" alt="Offer Letter" src="/assets/manual_erpnext_com/img/human-resources/offer-letter.png">
-
-> Note: An offer letter can be made only against a [Job Applicant](/contents/human-resources/job-applicant)
-
-There is a pre-designed print format to print you offer letter.
-
-<img class="screenshot" alt="Offer Letter" src="/assets/manual_erpnext_com/img/human-resources/offer-letter-print.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/salary-and-payroll.md b/erpnext/docs/user/human-resources/salary-and-payroll.md
deleted file mode 100644
index 168d605..0000000
--- a/erpnext/docs/user/human-resources/salary-and-payroll.md
+++ /dev/null
@@ -1,116 +0,0 @@
-Salary is a fixed amount of money or compensation paid to an employee by an employer in return for the work performed . 
-
-Payroll is the administration of financial records of employees' salaries, wages, bonuses, net pay, and deductions.
-
-To process Payroll in ERPNext,
-
-  1. Create Salary Structures for all Employees.
-  2. Generate Salary Slips via Process Payroll.
-  3. Book the Salary in your Accounts.
-
-### Salary Structure
-
-The Salary Structure represents how Salaries are calculated based on Earnings
-and Deductions. 
-
-Salary structures are used to help organizations:
-  1. Maintain pay levels that are competitive with the external labor market,
-  2. Maintain internal pay relationships among jobs,
-  3. Recognize and reward differences in level of responsibility, skill, and performance, and manage pay expenditures.
-
-The usual components of the salary structure (in india) include:
-
-__Basic Salary:__ It is the taxable base income and generally not more than 40% of CTC.
-
-__House Rent Allowance:__ The HRA constitutes 40 to 50% of the basic salary.
-
-__Special Allowances:__ Makes up for the remainder part of the salary, mostly smaller than the basic salary which is completely taxable.
-
-__Leave Travel Allowance:__ The non-taxable amount paid by the employer to the employee for vacation/trips with family within India.
-
-__Gratuity:__ It is basically a lump sum amount paid by the employer when the employee resigns from the organization or retires.
-
-__PF:__ Fund collected during emergency or old age. 12% of the basic salary is automatically deducted and goes to the employee provident fund.
-
-__Medical Allowance:__ The employer pays the employee for the medical expenditures incurred. It is tax free up to Rs.15,000.
-
-__Bonus:__ Taxable part of the CTC, usually a once a year lump sum amount, given to the employee based on the individual’s as well as the organizational performance for the year.
-
-__Employee Stock Options:__ ESOPS are Free/discounted shares given by the company to the employees. This is done to primarily increase employee retention.
-
-To create a new Salary Structure go to:
-
-> Human Resources > Setup > Salary Structure > New Salary Structure
-
-#### Figure 1:Salary Structure
-
-<img class="screenshot" alt="Salary Structure" src="/assets/manual_erpnext_com/img/human-resources/salary-structure.png">
-
-### In the Salary Structure,
-
-  * Select the Employee
-  * Set the starting date from which this is valid (Note: There can only be one Salary Structure that can be “Active” for an Employee during any period)
-  * In the “Earnings” and “Deductions” table all your defined Earning Type and Deductions Type will be auto-populated. Set the values of the Earnings and Deductions and save the Salary Structure.
-
-### Leave Without Pay (LWP)
-
-Leave Without Pay (LWP) happens when an Employee runs out of allocated leaves
-or takes a leave without an approval (via Leave Application). If you want
-ERPNext to automatically deduct salary in case of LWP, then you must check on
-the “Apply LWP” column in the Earning Type and Deduction Type masters. The
-amount of pay cut is the proportion of LWP days divided by the total working
-days for the month (based on the Holiday List).
-
-If you don’t want ERPNext to manage LWP, just don’t click on LWP in any of the
-Earning Types and Deduction Types.
-
-* * *
-
-### Creating Salary Slips
-
-Once the Salary Structure is created, you can make a salary slip from the same
-form or you can process your payroll for the month using Process Payroll.
-
-To create a salary slip from Salary Structure, click on the button Make Salary
-Slip.
-
-#### Figure 2: Salary Slip
-
-<img class="screenshot" alt="Salary Slip" src="/assets/manual_erpnext_com/img/human-resources/salary-slip.png">
-
-You can also create salary slip for multiple employees using Process Payroll:
-
-> Human Resources > Process Payroll
-
-#### Figure 3: Process Payroll
-
-<img class="screenshot" alt="Process Payroll" src="/assets/manual_erpnext_com/img/human-resources/process-payroll.png">
-
-In Process Payroll,
-
-  1. Select the Company for which you want to create the Salary Slips.
-  2. Select the Month and the Year for which you want to create the Salary Slips.
-  3. Click on “Create Salary Slips”. This will create Salary Slip records for each active Employee for the month selected. If the Salary Slips are created, the system will not create any more Salary Slips. All updates will be shown in the “Activity Log” section.
-  4. Once all Salary Slips are created, you can check if they are created correctly or edit it if you want to deduct Leave Without Pay (LWP).
-  5. After checking, you can “Submit” them all together by clicking on “Submit Salary Slips”. 1. If you want them to be automatically emailed to the Employee, make sure to check the “Send Email” box.
-
-### Booking Salaries in Accounts
-
-The final step is to book the Salaries in your Accounts.
-
-Salaries in businesses are usually dealt with extreme privacy. In most cases,
-the companies issues a single payment to the bank combining all salaries and
-the bank distributes the salaries to each employee’s salary account. This way
-there is only one payment entry in the company’s books of accounts and anyone
-with access to the company’s accounts will not have access to the individual
-salaries.
-
-The salary payment entry is a Journal Entry entry that debits the total
-salary of all Employees to the Salary Account and credits the company’s bank
-Account.
-
-To generate your salary payment voucher from Process Payroll, click on
-“Make Bank Voucher” and a new Journal Entry with the total salaries will be
-created.
-
-{next}
diff --git a/erpnext/docs/user/human-resources/setup/branch.md b/erpnext/docs/user/human-resources/setup/branch.md
deleted file mode 100644
index bb982a2..0000000
--- a/erpnext/docs/user/human-resources/setup/branch.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Branches of your organization
-
-<img class="screenshot" alt="Branch" src="/assets/manual_erpnext_com/img/human-resources/branch.png">
-
-{next}
diff --git a/erpnext/docs/user/human-resources/setup/deduction-type.md b/erpnext/docs/user/human-resources/setup/deduction-type.md
deleted file mode 100644
index a2697b9..0000000
--- a/erpnext/docs/user/human-resources/setup/deduction-type.md
+++ /dev/null
@@ -1,10 +0,0 @@
-You can make a record of the tax and other salary deductions and describe it as Deduction Type
-
-To create a new Deduction Type
-
-> Human Resource > Setup > Deduction Type > New
-
-<img class="screenshot" alt="Deduction Type" src="/assets/manual_erpnext_com/img/human-resources/deduction-type.png">
-
-
-{next}
diff --git a/erpnext/docs/user/human-resources/setup/department.md b/erpnext/docs/user/human-resources/setup/department.md
deleted file mode 100644
index 57aa80f..0000000
--- a/erpnext/docs/user/human-resources/setup/department.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Departments in your organization
-
-<img class="screenshot" alt="Department" src="/assets/manual_erpnext_com/img/human-resources/department.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/designation.md b/erpnext/docs/user/human-resources/setup/designation.md
deleted file mode 100644
index 1d115f9..0000000
--- a/erpnext/docs/user/human-resources/setup/designation.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Designations in your organization
-
-<img class="screenshot" alt="Designation" src="/assets/manual_erpnext_com/img/human-resources/designation.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/earning-type.md b/erpnext/docs/user/human-resources/setup/earning-type.md
deleted file mode 100644
index 3e74db3..0000000
--- a/erpnext/docs/user/human-resources/setup/earning-type.md
+++ /dev/null
@@ -1,10 +0,0 @@
-You can make a record of the Salary Components and describe it as Earning Type
-
-To create a new Earning Type
-
-> Human Resource > Setup > Earning Type > New
-
-<img class="screenshot" alt="Earning Type" src="/assets/manual_erpnext_com/img/human-resources/earning-type.png">
-
-
-{next}
diff --git a/erpnext/docs/user/human-resources/setup/employment-type.md b/erpnext/docs/user/human-resources/setup/employment-type.md
deleted file mode 100644
index b6f6cd3..0000000
--- a/erpnext/docs/user/human-resources/setup/employment-type.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Various employment contracts you have with your employees.
-
-<img class="screenshot" alt="Employment Type" src="/assets/manual_erpnext_com/img/human-resources/employment-type.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/holiday-list.md b/erpnext/docs/user/human-resources/setup/holiday-list.md
deleted file mode 100644
index 600c781..0000000
--- a/erpnext/docs/user/human-resources/setup/holiday-list.md
+++ /dev/null
@@ -1,5 +0,0 @@
-You can specify the Holidays for a particular year using Holiday List.
-
-<img class="screenshot" alt="Holiday List" src="/assets/manual_erpnext_com/img/human-resources/holiday-list.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/hr-settings.md b/erpnext/docs/user/human-resources/setup/hr-settings.md
deleted file mode 100644
index aa7cf6c..0000000
--- a/erpnext/docs/user/human-resources/setup/hr-settings.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# HR Settings
-
-GLobal settings for HR related documents
-
-<img class="screenshot" alt="HR Settings" src="/assets/manual_erpnext_com/img/human-resources/hr-settings.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/leave-allocation.md b/erpnext/docs/user/human-resources/setup/leave-allocation.md
deleted file mode 100644
index 28c53a5..0000000
--- a/erpnext/docs/user/human-resources/setup/leave-allocation.md
+++ /dev/null
@@ -1,7 +0,0 @@
-Helps you allocate Leaves to a particular Employee
-
-<img class="screenshot" alt="Leave Allocation" src="/assets/manual_erpnext_com/img/human-resources/leave-allocation.png">
-
-To assign leaves to multiple employees use the [Leave Allocation Tool](/contents/human-resources/tools/leave-allocation-tool)
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/setup/leave-type.md b/erpnext/docs/user/human-resources/setup/leave-type.md
deleted file mode 100644
index 6621c78..0000000
--- a/erpnext/docs/user/human-resources/setup/leave-type.md
+++ /dev/null
@@ -1,9 +0,0 @@
-Specify the Type of Leave that can be allocated against an Employee
-
-<img class="screenshot" alt="Leave Type" src="/assets/manual_erpnext_com/img/human-resources/leave-type.png">
-
-* 'Max Days Leave Allowed' specifies the maximum number of days this type of leave can be taken at a strech.
-* 'Is LWP' specifies if the Leave is without Pay.
-* 'Allow Negative Balance' specifies if system can maintain negative leaves.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/tools/leave-allocation-tool.md b/erpnext/docs/user/human-resources/tools/leave-allocation-tool.md
deleted file mode 100644
index 9e9fbf3..0000000
--- a/erpnext/docs/user/human-resources/tools/leave-allocation-tool.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Leave Allocation tool helps you allocated a specific number of leaves for your employees.
-
-<img class="screenshot" alt="Leave Application" src="/assets/manual_erpnext_com/img/human-resources/leave-application.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/human-resources/tools/upload-attendance.md b/erpnext/docs/user/human-resources/tools/upload-attendance.md
deleted file mode 100644
index 164460e..0000000
--- a/erpnext/docs/user/human-resources/tools/upload-attendance.md
+++ /dev/null
@@ -1,9 +0,0 @@
-This tool helps you to upload bulk attendence from a csv file.
-
-To upload the attendance go to:
-
-> Human Resources > Upload Attendance
-
-<img class="screenshot" alt="Attendence upload" src="/assets/manual_erpnext_com/img/human-resources/attendence-upload.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/index.md b/erpnext/docs/user/index.md
index 454b4a8..0394638 100644
--- a/erpnext/docs/user/index.md
+++ b/erpnext/docs/user/index.md
@@ -1,3 +1,3 @@
-# User Manual
+# User Manual and Videos
 
 {index}
\ No newline at end of file
diff --git a/erpnext/docs/user/index.txt b/erpnext/docs/user/index.txt
index d5cf10d..8d9bd8a 100644
--- a/erpnext/docs/user/index.txt
+++ b/erpnext/docs/user/index.txt
@@ -1,15 +1,2 @@
-introduction
-setting-up
-accounts
-stock
-CRM
-selling
-buying
-manufacturing
-projects
-support
-human-resources
-customer-portal
-website
-collaboration-tools
-customize-erpnext
+guides
+videos
diff --git a/erpnext/docs/user/introduction/key-workflows.md b/erpnext/docs/user/introduction/key-workflows.md
deleted file mode 100644
index ddec7de..0000000
--- a/erpnext/docs/user/introduction/key-workflows.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Flow Chart Of Transactions In ERPNext
-
-This diagram covers how ERPNext tracks your company information across key
-functions. This diagram does not cover all the features of ERPNext.
-
-![](/assets/manual_erpnext_com/old_images/erpnext/overview.png)
-
-
-[Full Resolution](/assets/manual_erpnext_com/old_images/erpnext/overview.png)
-
-_Note: Not all of the steps are mandatory. ERPNext allows you to freely skip
-steps if you want to simplify the process._
-
-{next}
diff --git a/erpnext/docs/user/introduction/the-champion.md b/erpnext/docs/user/introduction/the-champion.md
deleted file mode 100644
index 32d3cd3..0000000
--- a/erpnext/docs/user/introduction/the-champion.md
+++ /dev/null
@@ -1,46 +0,0 @@
-<!-- no-heading -->
-
-<h1 class="white">The Champion</h1>
-
-<img class="cover" src="/assets/manual_erpnext_com/old_images/erpnext/implementation-image.png">
-
-We have seen dozens of ERP implementations over the past few years and we
-realize that successful implementation is a lot about intangibles and
-attitude.
-
-**ERPs are not required.**
-
-Like exercise.
-
-Human body may seem like it does not require exercise today or even tomorrow,
-but in the long run, if you wish to maintain your body and its health, you
-should get on the treadmill.
-
-In the same way, ERPs improve the health of your organization over a long run
-by keeping it fit and efficient. The more you delay putting things in order,
-the more time you lose, and the closer you get to a major disaster.
-
-So when you start implementing an ERP, keep your sight on the long term
-benefits. Like exercise, its painful in the short run, but will do wonders if
-you stay on course.
-
-* * *
-
-## The Champion
-
-ERP means organization wide change and it does not happen without effort.
-Every change requires a champion and it is the duty of the champion to
-organize and energize the entire team towards implementation. The champion
-needs to be resilient incase something goes wrong .
-
-In many organizations we have seen, the champion is most often the owner or a
-senior manager. Occasionally, the champion is an outsider who is hired for a
-particular purpose.
-
-In either case, you must identify your champion first.
-
-Most likely it's **you!**
-
-Lets Begin!
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/bill-of-materials.md b/erpnext/docs/user/manufacturing/bill-of-materials.md
deleted file mode 100644
index 7a40076..0000000
--- a/erpnext/docs/user/manufacturing/bill-of-materials.md
+++ /dev/null
@@ -1,41 +0,0 @@
-At the heart of the Manufacturing system is the **Bill of Materials** (BOM).
-The **BOM** is a list of all materials (either bought or made) and operations
-that go into a finished product or sub-Item. In ERPNext, the component could
-have its own BOM hence forming a tree of Items with multiple levels.
-
-To make accurate Purchase Requests, you must always maintain correct BOMs.
-To make a new BOM:
-
-> Manufacturing > Bill of Materials > New BOM
-
-<img class="screenshot" alt="Task" src="/assets/manual_erpnext_com/img/manufacturing/bom.png">
-
-* To add Operations select 'With Operation'. The Operations table shall appear.
-
-<img class="screenshot" alt="Task" src="/assets/manual_erpnext_com/img/manufacturing/bom-operations.png">
-
-  * Select the Item for which you want to make the BOM.
-  * Add the operations that you have to go through to make that particular Item in the “Operations” table. For each operation, you will be asked to enter a Workstation. You must create new Workstations as and when necessary.
-  * Workstations are defined only for product costing and Production Order Operations scheduling purposes not inventory. 
-  * Inventory is tracked in Warehouses not Workstations.
-
-###Costing of a BOM
-
-* The Costing section in BOM gives an approximate cost of producing the Item.
-
-* Add the list of Items you require for each operation, with its quantity. This Item could be a purchased Item or a sub-assembly with its own BOM. If the row Item is a manufactured Item and has multiple BOMs, select the appropriate BOM. You can also define if a part of the Item goes into scrap.
-
-<img class="screenshot" alt="Costing" src="/assets/manual_erpnext_com/img/manufacturing/bom-costing.png">
-
-* This cost can be updated on by using the 'Update Cost' button.
-
-<img class="screenshot" alt="Update Cost" src="/assets/manual_erpnext_com/img/manufacturing/bom-update-cost.png">
-
-### Materials Required(exploded) 
-
-This table lists down all the Material required for the Item to be Manufactured.
-It also fetches sub-assemblies along with the quantity.
-
-<img class="screenshot" alt="Exploded Section" src="/assets/manual_erpnext_com/img/manufacturing/bom-exploded.png">
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/introduction.md b/erpnext/docs/user/manufacturing/introduction.md
deleted file mode 100644
index 278dfaf..0000000
--- a/erpnext/docs/user/manufacturing/introduction.md
+++ /dev/null
@@ -1,24 +0,0 @@
-<img class="screenshot" alt="Task" src="/assets/manual_erpnext_com/img/manufacturing/manufacturing.png">
-
-### Types of Production Planning
-
-Broadly there are three types of Production Planning Systems
-
-  * __Make-to-Stock:__ In these systems, production is planned based on a forecast and the Items are then sold to distributors or customers. All fast moving consumer goods that are sold in retail shops like soaps, packaged water etc and electronics like phones etc are Made-to-Stock.
-  * __Make-to-Order:__ In these systems, manufacturing takes place after a firm order is placed by a customer.
-  * __Engineer-to-Order:__ In this case each sale is a separate project and has to be designed and engineered to the requirements of the customer. Common examples of this are any custom business like furniture, machine tools, speciality devices, metal fabrication etc.
-
-Most small and medium sized manufacturing businesses are based on a make-to-
-order or engineer-to-order system and so is ERPNext.
-
-For engineer-to-order systems, the Manufacturing module should be used along
-with the Projects module..
-
-#### Manufacturing and Inventory
-
-You can track work-in-progress by creating work-in-progress Warehouses.
-
-ERPNext will help you track material movement by automatically creating Stock
-Entries from your Production Orders by building from Bill of Materials.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/manufacturing/operation.md b/erpnext/docs/user/manufacturing/operation.md
deleted file mode 100644
index f0b4c25..0000000
--- a/erpnext/docs/user/manufacturing/operation.md
+++ /dev/null
@@ -1,11 +0,0 @@
-### Operation
-
-Stores a list of all Manufacturing Operations, its description and the Default Workstation for the Operation.
-
-You can also create a Operation by:
-
-> Manufacturing > Documents > Operation > New
-
-<img class="screenshot" alt="Operation" src="/assets/manual_erpnext_com/img/manufacturing/operation.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/manufacturing/production-order.md b/erpnext/docs/user/manufacturing/production-order.md
deleted file mode 100644
index 5ac1301..0000000
--- a/erpnext/docs/user/manufacturing/production-order.md
+++ /dev/null
@@ -1,106 +0,0 @@
-Production Order (also called as Work Order) is a document that is given to
-the manufacturing shop floor by the Production Planner as a signal to produce
-a certain quantity of a certain Item. Production Order also helps to generate
-the material requirements (Stock Entry) for the Item to be produced from its
-**Bill of Materials**.
-
-The **Production Order** is generated from the **Production Planning
-Tool** based on Sales Orders. You can also create a direct Production Order
-by:
-
-> Manufacturing > Documents > Production Order > New
-
-<img class="screenshot" alt="Production Order" src="/assets/manual_erpnext_com/img/manufacturing/production-order.png">
-
-### Creating Production Orders
-
-  * Select the Item to be produced.
-  * The default BOM for that item will be fetched by the system. You can also change BOM.
-  * If the selected BOM has operartion mentioned in it, the system shall fetch all operations from BOM.
-  * Mention the Planned Start Date (an Estimated Date at which you want the Production to begin.)
-  * Select Warehouses. Work-in-Progress Warehouse is where your Items will be transferred when you begin production and Target Warehouse is  where you store finished Items before they are shipped.
-
-> Note : You can save a Production Order without selecting the warehouses, but warehouses are mandatory for submitting a Production Order
-
-###Reassigning Workstation/Duration for Operations
-
-* By default the system fetchs workstation and duration for Production Order Operations from the selected BOM.
-
-<img class="screenshot" alt="PO Opeartions" src="/assets/manual_erpnext_com/img/manufacturing/PO-operations.png">
-
-* If you wish to reassign the wrokstation for a particular opeeration in the Production Order, you can do so before submitting the Production Order.
-
-<img class="screenshot" alt="PO reassigning Operations" src="/assets/manual_erpnext_com/img/manufacturing/PO-reassigning-operations.png">
-
-* Select the respective operation, and change its workstation.
-* You can also change the Operating Time for that operation
-
-### Capacity Planning in Production Order
-
-* When a Production Order is submitted, based on the Planned Start Date and the availability of the workstations, system schedules all operations for the Production Order (if Production Order has operations specified).
-* Drafts of Time Logs are also created based on the scheduled operations.
-
-### Transfering Materials for Manufacturing
-
-* Once you have submitted your Production Order, you need to Transfer the Raw Materials to initiate the Manufacturing Process.
-* This will create a Stock Entry with all the Items required to complete this Production Order to be added to the WIP Warehouse. (this will add sub-Items with BOM as one Item or explode their children based on your setting above).
-
-* Click on 'Transfer Materials for Manufacturing'.
-
-<img class="screenshot" alt="Transfer Materials" src="/assets/manual_erpnext_com/img/manufacturing/PO-material-transfer.png">
-
-* Mention the quantity of materials to be transfered.
-
-<img class="screenshot" alt="Material Transfer Qty" src="/assets/manual_erpnext_com/img/manufacturing/PO-material-transfer-qty.png">
-
-* Submit the Stock Entry
-
-<img class="screenshot" alt="Stock Entry for PO" src="/assets/manual_erpnext_com/img/manufacturing/PO-SE-for-material-transfer.png">
-
-* Material Transfered for Manufacturing will be updated in the Production Order based on the Stock Entry.
-
-<img class="screenshot" alt="Stock Entry for PO" src="/assets/manual_erpnext_com/img/manufacturing/PO-material-transfer-updated.png">
-
-### Making Time Logs
-
-* Progress in the Production Order can be tracked using [Time Log](/contents/projects/time-log)
-* Time Logs are created against Production Order Operations.
-* Drafts of Time Logs are also created based on the scheduled operations when an Production Order is Submitted.
-* To create more Time Logs against an operation select 'Make TIme Log' in the respective operation.
-
-<img class="screenshot" alt="Make TL against PO" src="/assets/manual_erpnext_com/img/manufacturing/PO-operations-make-tl.png">
-
-###Updating Finished Goods
-
-* Once you are done with the Production Order you need to update the Finished Goods.
-* This will create a Stock Entry that will deduct all the sub-Items from the WIP Warehouse and add them to the Finished Goods Warehouse.
-* Click on 'Update Finished Goods'.
-
-<img class="screenshot" alt="Update Finished Goods" src="/assets/manual_erpnext_com/img/manufacturing/PO-FG-update.png">
-
-* Mention the quantity of materials to be transfered.
-
-<img class="screenshot" alt="Update Finished Goods Qty" src="/assets/manual_erpnext_com/img/manufacturing/PO-FG-update-qty.png">
-
- > Tip : You can also partially complete a Production Order by updating the Finished Goods stock creating a Stock Entry.
- 
-### Stopping a Production Order
-
-* When you stop a Production Order its status is changed to Stop indicating that all production process against that Production Order is to be ceased.
-* To stop the Production Order click on the 'stop' Button
-
-  1. On Submitting the Production Order, the system will reserve a slot for each of the Production Order Operations serially after the planned start date based on the workstation availability. The Workstation availability depends on the Workstation timings, holiday list and if some other Production Order Operation was scheduled in that slot. You can mention the number of days for the system to try scheduling the operations in the Manufacturing Settings. This is set to 30 Days by default. If the operation requires time exceeding the available slot, system shall ask you to break the operations. Once the scheduling is done system shall create Time Logs and save them. You can Modify them and submit them later.
-  2. You can also create additional time logs against an Operation. For doing so select the respective operation and click on 'Make Time Log'
-  3. Transfer Raw Material: This will create a Stock Entry with all the Items required to complete this Production Order to be added to the WIP Warehouse. (this will add sub-Items with BOM as one Item or explode their children based on your setting above).
-  4. Update Finished Goods: This will create a Stock Entry that will deduct all the sub-Items from the WIP Warehouse and add them to the Finished Goods Warehouse.
-  5. To check all Time Logs made against the Production Order click on 'Show Time Logs'
-
-<img class="screenshot" alt="PO - stop" src="/assets/manual_erpnext_com/img/manufacturing/PO-stop.png">
-
-* You can Also re-start a stopped Production Order.
-
-> Note : In order to make a Production Order against an Item you must specify 'Yes' to "Allow Production Order" on the Item form.
-
-> Note : In order to make a Production Order against an Item you must specify 'Yes' to "Allow Production Order" on the Item form.
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/setup/manufacturing-settings.md b/erpnext/docs/user/manufacturing/setup/manufacturing-settings.md
deleted file mode 100644
index 6b2639c..0000000
--- a/erpnext/docs/user/manufacturing/setup/manufacturing-settings.md
+++ /dev/null
@@ -1,15 +0,0 @@
-* Manufacturing Settings can be found at 
-
-> Manufacturing > Production Order > Setup > Manufacturing Settings
-
-<img class="screenshot" alt="Manufacturing Settings" src="/assets/manual_erpnext_com/img/manufacturing/manufacturing-settings.png">
-
-* Allow Overtime - Specify if workstations are to allow overtime.(schedule operations outside working hours)
-
-* Allow Production on Holidays - Specify if system is to allow scheduling of operations on Holidays.
-
-* Capacity Planning for (Days) - Specify no. of Days for Capacity Planning.
-
-* Time Between Operations (in mins) - Specify the gap between two Production Operations.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/manufacturing/subcontracting.md b/erpnext/docs/user/manufacturing/subcontracting.md
deleted file mode 100644
index aba0e70..0000000
--- a/erpnext/docs/user/manufacturing/subcontracting.md
+++ /dev/null
@@ -1,40 +0,0 @@
-Subcontracting is a type of job contract that seeks to outsource certain types
-of work to other companies. It allows work on more than one phase of the
-project to be done at once, often leading to a quicker completion.
-Subcontracting is practiced by various industries. For example, manufacturers
-making a number of products from complex components subcontract certain
-components and package them at their facilities.  
-
-If your business involves outsourcing certain processes to a third party
-Supplier, where you buy the raw material from, you can track this by using the
-sub-contracting feature of ERPNext.  
-
-### Setup Sub-Contracting:
-
-  1. Create separate Items for the unprocessed and the processed product. For example if you supply unpainted X to your Supplier and the Supplier returns you X, you can create two Items: “X-unpainted” and “X”.
-  2. Create a Warehouse for your Supplier so that you can keep track of Items supplied. (you may supply a months worth of Items in one go).
-  3. For the processed Item, in the Item master, set “Is Sub Contracted Item” to “Yes”.
-
-![Subcontract](/assets/manual_erpnext_com/old_images/erpnext/subcontract.png)
-
-  
-
-__Step 1:__ Make a Bill of Materials for the processed Item, with the unprocessed
-Items as sub-items. For example, If you are manufacturing a pen, the processed
-pen will be named under Bill of Materials(BOM), whereas, the refill, knob, and
-other items which go into the making of pen, will be categorized as sub-items.
-
-__Step 2:__ Make a Purchase Order for the processed Item. When you “Save”, in the “Raw Materials Supplied”, all your un-processed Items will be updated based on your Bill of Materials.
-
-__Step 3:__ Make a Stock Entry to deliver the raw material Items to your Supplier.
-
-__Step 4:__ Receive the Items from your Supplier via Purchase Receipt. Make sure to check the “Consumed Quantity” in the “Raw Materials” table so that the
-correct stock is maintained at the Supplier’s end.
-
-> Note 1: Make sure that the “Rate” of processed Item is the processing rate
-(excluding the raw material rate).
-
-> Note 2: ERPNext will automatically add the raw material rate for your
-valuation purpose when you receive the finished Item in your stock.
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/tools/bom-replace-tool.md b/erpnext/docs/user/manufacturing/tools/bom-replace-tool.md
deleted file mode 100644
index 4a07abb..0000000
--- a/erpnext/docs/user/manufacturing/tools/bom-replace-tool.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# BOM Replace Tool
-
-Replace BOM is the utility to replace BOM of sub-assembly item, which is already updated in the BOM of Finished Good item.
-
-To use the Production Planning Tool, go to:
-
-> Manufacturing > Tools > BOM Replace Tool
-
-Let's consider a scenario to understand this better.
-
-If company manufactures computers, Bill of Material of its finished item will constitute of:
-
-1. Monitor
-1. Key Board
-1. Mouse
-1. CPU
-
-Out of all the items above, CPU is asembled separately. Hence separate BOM will be created for the CPU. Following are the items from the BOM of CPU.
-
-1. 250 GB Hard Disk
-1. Mother Board
-1. Processor
-1. SMTP
-1. DVD player
-
-If we have more items to be added , or existing items to be edited in the BOM of CPU, then we should create new BOM for it.
-
-1. _350 GB Hard Disk_
-1. Mother Board
-1. Processor
-1. SMTP
-1. DVD player
-
-To update new BOM updated in the BOM of finished item, where CPU is selected as raw-material, you can use BOM Replace tool.
-
-<img class="screenshot" alt="BOM replace Tool" src="/assets/manual_erpnext_com/img/manufacturing/bom-replace-tool.png">
-
-In this tool, you should select Current BOM, and New BOM. On clicking Replace button, current BOM of CPU will be replaced with New BOM in the BOM of finished Item (Computer).
-
-**Will BOM Replace Tool work for replacing finsihed item in BOM?**
-
-No. You should Cancel and Amend current BOM, or create a new BOM for finished item.
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/tools/production-planning-tool.md b/erpnext/docs/user/manufacturing/tools/production-planning-tool.md
deleted file mode 100644
index aa07f40..0000000
--- a/erpnext/docs/user/manufacturing/tools/production-planning-tool.md
+++ /dev/null
@@ -1,62 +0,0 @@
-Production Planning Tool helps you plan production and purchase of Items for a
-period (usually a week or a month).
-
-This list of Items can be generated from the open Sales Orders in the system
-and will generate:
-
-  * Production Orders for each Item.
-  * Purchase Requests for Items whose Projected Quantity is likely to fall below zero.
-
-To use the Production Planning Tool, go to:
-
-> Manufacturing > Tools > Production Planning Tool
-
-<img class="screenshot" alt="Production Planing Tool" src="/assets/manual_erpnext_com/img/manufacturing/ppt.png">
-
-
-
-#### Step 1: Select and get Sales Order
-
-* Select sales orders for MRP using filters (Time, Item, and Customer)
-* Click on Get Sales Order to generate a list.
-
-<img class="screenshot" alt="Production Planing Tool" src="/assets/manual_erpnext_com/img/manufacturing/ppt-get-sales-orders.png">
-
-
-
-#### Step 2: Get Item from Sales Orders.
-
-You can add/remove or change quantity of these Items.
-
-<img class="screenshot" alt="Production Planing Tool" src="/assets/manual_erpnext_com/img/manufacturing/ppt-get-item.png">
-
-#### Step 3: Create Production Orders
-
-<img class="screenshot" alt="Production Planing Tool" src="/assets/manual_erpnext_com/img/manufacturing/ppt-create-production-order.png">
-
-
-
-#### Step 4: Create Material Request
-
-Create Material Request for Items with projected shortfall.
-
-<img class="screenshot" alt="Production Planing Tool" src="/assets/manual_erpnext_com/img/manufacturing/ppt-create-material-request.png">
-
-
-
-The Production Planning Tool is used in two stages:
-
-  * Selection of Open Sales Orders for the period based on “Expected Delivery Date”.
-  * Selection of Items from those Sales Orders.
-
-The tool will update if you have already created Production Orders for a
-particular Item against its Sales Order (“Planned Quantity”).
-
-You can always edit the Item list and increase / reduce quantities to plan
-your production.
-
-> Note: How do you change a Production Plan? The output of the Production
-Planning Tool is the Production Order. Once your orders are created, you can
-change them by amending the Production Orders.
-
-{next}
diff --git a/erpnext/docs/user/manufacturing/workstation.md b/erpnext/docs/user/manufacturing/workstation.md
deleted file mode 100644
index 168fddf..0000000
--- a/erpnext/docs/user/manufacturing/workstation.md
+++ /dev/null
@@ -1,19 +0,0 @@
-### Workstation
-
-Workstation stores information regarding the place where the workstation operations is carried out.
-Data regarding the operation cost of the place can be stored here.
-We can also specify the workstation operation timings and a Holiday List.
-
-You can also create a Workstation by:
-
-> Manufacturing > Documents > Workstation > New
-
-<img class="screenshot" alt="Workstation" src="/assets/manual_erpnext_com/img/manufacturing/workstation.png">
-
-In workstation specify the workstation working hours under the 'working hour' section. 
-You can also specify the working hours based on shifts.
-While scheduling Production Order, system will check for the availability of the workstation based on the working hours specified.	
-
-> Note : You can enable overtime for your workstation in [Manufacturing Settings](/contents/manufacturing/setup/manufacturing-settings)
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/projects/activity-cost.md b/erpnext/docs/user/projects/activity-cost.md
deleted file mode 100644
index 18d7245..0000000
--- a/erpnext/docs/user/projects/activity-cost.md
+++ /dev/null
@@ -1,4 +0,0 @@
-Activity Cost records the per-hour billing rate and costing rate of an Employee against an Activity Type.
-This rate is pulled by the system while making Time Logs. It is used for Project Costing.
-
-<img class="screenshot" alt="Activity Cost" src="/assets/manual_erpnext_com/img/project/activity_cost.png">
diff --git a/erpnext/docs/user/projects/activity-type.md b/erpnext/docs/user/projects/activity-type.md
deleted file mode 100644
index 10fe79b..0000000
--- a/erpnext/docs/user/projects/activity-type.md
+++ /dev/null
@@ -1,13 +0,0 @@
-Activity Type makes a list of the different types of activities against which a Time Log can be made.
-
-<img class="screenshot" alt="Activity Type" src="/assets/manual_erpnext_com/img/project/activity_type.png">
-
-By default the following Activity Types are created.
-
-* Planning
-* Research
-* Proposal Writing
-* Execution
-* Communication
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/projects/project.md b/erpnext/docs/user/projects/project.md
deleted file mode 100644
index e378d47..0000000
--- a/erpnext/docs/user/projects/project.md
+++ /dev/null
@@ -1,87 +0,0 @@
-Project management in ERPNext is Task driven. You can create Project and assign multiple Tasks against it.
-
-<img class="screenshot" alt="Project" src="/assets/manual_erpnext_com/img/project/project.png">
-
-### Managing tasks
-Project can be divided into multiple Tasks.
-Task can be created via Project document itself or can be created via  [Task](/contents/projects/tasks)
-
-<img class="screenshot" alt="Project" src="/assets/manual_erpnext_com/img/project/project_task.png">
-
-* To view Task made against a Project click on 'Tasks'
-
-<img class="screenshot" alt="Project - View Task" src="/assets/manual_erpnext_com/img/project/project_view_task.png">
-
-<img class="screenshot" alt="Project - Task List" src="/assets/manual_erpnext_com/img/project/project_task_list.png">
-
-* You can also view the Tasks from the Project document itself
-
-<img class="screenshot" alt="Project - Task Grid" src="/assets/manual_erpnext_com/img/project/project_task_grid.png">
-
-### Managing time
-
-ERPNext uses [Time Log](/contents/projects/time-log) to track the progress of a Project.
-You can create Time Logs against each task.
-The Actual Start and End Time along with the costing shall then be updated based on the Time Log.
-
-* To view Time Log made against a Project click on 'Time Logs'
-
-<img class="screenshot" alt="Project - View Time Log" src="/assets/manual_erpnext_com/img/project/project_view_time_log.png">
-
-<img class="screenshot" alt="Project - Time Log List" src="/assets/manual_erpnext_com/img/project/project_time_log_list.png">
-
-* You can also create a Time Log directlly and link it to the Project.
-
-<img class="screenshot" alt="Project - Link Time Log" src="/assets/manual_erpnext_com/img/project/project_time_log_link.png">
-
-### Managing expenses
-
-You can book [Expense Claim](/contents/human-resources/expense-claim) against a project task.
-The system shall update the total amount from expense claims in the project costing section.
-
-* To view Expense Claims made against a Project click on 'Expense Claims'
-
-<img class="screenshot" alt="Project - View Expense Claim" src="/assets/manual_erpnext_com/img/project/project_view_expense_claim.png">
-
-* You can also create a Expense Claims directlly and link it to the Project.
-
-<img class="screenshot" alt="Project - Link Expense Claim" src="/assets/manual_erpnext_com/img/project/project_expense_claim_link.png">
-
-* Total amount of Expense Claims booked against a project is shown under 'Total Expense Claim' in the Project Costing Section
-
-<img class="screenshot" alt="Project - Total Expense Claim" src="/assets/manual_erpnext_com/img/project/project_total_expense_claim.png">
-
-### Cost Center
-
-You can make a [Cost Center](/contents/accounts/setup/cost-center) against a Project or use an existing cost center to track all expenses made against that project.
-
-<img class="screenshot" alt="Project - Cost Center" src="/assets/manual_erpnext_com/img/project/project_cost_center.png">
-
-###Project Costing
-
-The Project Costing section helps you track the time and expenses incurred against the project.
-
-<img class="screenshot" alt="Project - Costing" src="/assets/manual_erpnext_com/img/project/project_costing.png">
-
-* The Costing Section is updated based on Time Logs made.
-
-* Gross Margin is the difference between Total Costing Amount and Total Billing Amount
-
-###Billing
-
-You can make/link a [Sales Order](/contents/selling/sales-order) against a project. Once linked you can use the standard sales module to bill your customer against the Project.
-
-<img class="screenshot" alt="Project - Sales Order" src="/assets/manual_erpnext_com/img/project/project_sales_order.png">
-
-###Gantt Chart
-
-A Gantt Chart illustrates a project schedule.
-ERPNext gives you a illustrated view of tasks scheduled against that project in Gantt Chart View.
-
-* To view gantt chart against a project, go to that project and click on 'Gantt Chart'
-
-<img class="screenshot" alt="Project - View Gantt Chart" src="/assets/manual_erpnext_com/img/project/project_view_gantt_chart.png">
-
-<img class="screenshot" alt="Project - Gantt Chart" src="/assets/manual_erpnext_com/img/project/project_gantt_chart.png">
-
-{next}
diff --git a/erpnext/docs/user/projects/tasks.md b/erpnext/docs/user/projects/tasks.md
deleted file mode 100644
index 49d8250..0000000
--- a/erpnext/docs/user/projects/tasks.md
+++ /dev/null
@@ -1,59 +0,0 @@
-Project is divided into Tasks. 
-In ERPNext, you can also create a Task independently.
-
-<img class="screenshot" alt="Task" src="/assets/manual_erpnext_com/img/project/task.png">
-
-### Status of the Task
-
-A Task can have either of the following status - Open, Working, Pending Review, Closed, Cancelled.
-
-<img class="screenshot" alt="Task - Status" src="/assets/manual_erpnext_com/img/project/task_status.png">
-
-* By default each new Task created shall have the status set to 'Open'.
-
-* If a Time Log is made against a task, its status shall be set to 'Working'.
-
-### Dependent Task
-
-You can specify a list of dependent task under the 'Depends On' section.
-
-<img class="screenshot" alt="Depends On" src="/assets/manual_erpnext_com/img/project/task_depends_on.png">
-
-* You cannot close the parent Task until all 'Dependant Task' are closed.
-
-* If the Dependent Task are delayed and overlap with the expected Start Date of the Parent task, the system will reschedule the parent task.
-
-### Managing Time
-
-ERPNext uses [Time Log](/contents/projects/time-log) to track the progress of a Task.
-You can create multiple Time Logs against each task.
-The Actual Start and End Time along with the costing shall then be updated based on the Time Log.
-
-* To view Time Log made against a Task click on 'Time Logs'
-
-<img class="screenshot" alt="Task - View Time Log" src="/assets/manual_erpnext_com/img/project/task_view_time_log.png">
-
-<img class="screenshot" alt="Task - Time Log List" src="/assets/manual_erpnext_com/img/project/task_time_log_list.png">
-
-* You can also create a Time Log directlly and link it to the Task.
-
-<img class="screenshot" alt="Task - Link Time Log" src="/assets/manual_erpnext_com/img/project/task_time_log_link.png">
-
-### Managing Expenses
-
-You can book [Expense Claim](/contents/human-resource-management/expense-claim) against a task.
-The system shall update the total amount from expense claims in the costing section.
-
-* To view Expense Claims made against a Task click on 'Expense Claims'
-
-<img class="screenshot" alt="Task - View Expense Claim" src="/assets/manual_erpnext_com/img/project/task_view_expense_claim.png">
-
-* You can also create a Expense Claims directlly and link it to the Task.
-
-<img class="screenshot" alt="Task - Link Expense Claim" src="/assets/manual_erpnext_com/img/project/task_expense_claim_link.png">
-
-* Total amount of Expense Claims booked against a task is shown under 'Total Expense Claim' in the Task Costing Section
-
-<img class="screenshot" alt="Task - Total Expense Claim" src="/assets/manual_erpnext_com/img/project/task_total_expense_claim.png">
-
-{next}
diff --git a/erpnext/docs/user/projects/time-log-batch.md b/erpnext/docs/user/projects/time-log-batch.md
deleted file mode 100644
index c678d039..0000000
--- a/erpnext/docs/user/projects/time-log-batch.md
+++ /dev/null
@@ -1,23 +0,0 @@
-You can bill Time Logs by batching them together. This gives you the flexiblity to manage your customer billing in the way you want. To create a new Time Log Batch, go to 
-
-> Projects > Time Log Batch > New Time Log Batch
-
-OR
-
-Just open your Time Log list and check the Items to you want to add to the Time Log. Then click on "Make Time Log Batch" button and these Time Logs will be selected.
-
-<img class="screenshot" alt="Time Log - Drag Calender" src="/assets/manual_erpnext_com/img/project/time_log_batch.gif">
-
-###Making Sales Invoice
-
-* After submitting the Time Log Batch, "Make Invoice" button shall appear.
-
-<img class="screenshot" alt="Time Log - Drag Calender" src="/assets/manual_erpnext_com/img/project/time_log_batch_make_invoice.png">
-
-* Click on that button to raise a Sales Invoice against the Time Log Batch.
-
-<img class="screenshot" alt="Time Log - Drag Calender" src="/assets/manual_erpnext_com/img/project/time_log_batch_sales_invoice.png">
-
-* When you "Submit" the Sales Invoice, the Sales Invoice number will get updated in the Time Logs and Time Log Batch and their status will change to "Billed".
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/projects/time-log.md b/erpnext/docs/user/projects/time-log.md
deleted file mode 100644
index 1ddf9442..0000000
--- a/erpnext/docs/user/projects/time-log.md
+++ /dev/null
@@ -1,49 +0,0 @@
-Time Logs are a way to track time worked.
-They can be used to track the following
-
-* Billable work to Customers
-* Production Order Operations
-* Tasks
-* Project
-* Internal References
-
-<img class="screenshot" alt="Time Log" src="/assets/manual_erpnext_com/img/project/time_log.png">
-
-###Creating Time Logs
-
-1. To create a new Time Log, you can go to 
-> Projects > Time Log > new Time Log
-
-2. You can also create a new Time Log via Calendar
-
-To create Time Logs via Calender, go to Time Log and select Calendar.
-
-<img class="screenshot" alt="Time Log - View Calender" src="/assets/manual_erpnext_com/img/project/time_log_view_calendar.png">
-
-* To create a Time Log for multiple days, click and drag the cursor across days.
-
-<img class="screenshot" alt="Time Log - Drag Calender" src="/assets/manual_erpnext_com/img/project/time_log_calendar_day.gif">
-
-* You can also create Time Logs from 'week' and 'day' view of the calender.
-
-<img class="screenshot" alt="Time Log - Drag Calender" src="/assets/manual_erpnext_com/img/project/time_log_calendar_week.gif">
-
-* Time Logs for Manufacturing processes needs to be created from the Production Order. 
-* To create more Time Logs against Operations select the respective operation and click on the 'Make Time Log' button.
-
-###Billing using Time Logs
-
-* If you wish to bill against a Time Log you need to select the 'Billable' option.
-
-* In the costing section, the system will pull up the Costing & Billing rate from [Activity Cost](/contents/projects/activity-cost) 
-	based on the Employee and Activity Type specified.
-
-* The system shall then calculate the Costing and Billing amount based on the Hours mentioned in the Time Log.
-
-* If 'Billable' is not selected, the system shall display the 'Billing Amount' as 0.
-
-<img class="screenshot" alt="Time Log - Costing" src="/assets/manual_erpnext_com/img/project/time_log_costing.png">
-
-* After submitting the Time Log, you need to create [Time Log batch](/contents/projects/time-log-batch) to further bill the Time Log.
-
-{next}
diff --git a/erpnext/docs/user/selling/quotation.md b/erpnext/docs/user/selling/quotation.md
deleted file mode 100644
index ecee115..0000000
--- a/erpnext/docs/user/selling/quotation.md
+++ /dev/null
@@ -1,89 +0,0 @@
-During a sale, the customer may request for a written note about the products
-or services you are planning to offer, along with the prices and other terms
-of engagement. This is called a “Proposal” or an “Estimate” or a “Pro Forma
-Invoice”or a Quotation.
-
-To create a new Quotation go to:
-
-> Selling > Quotation > New Quotation
-
-###Creating Quotation from Oppurtunity
-
-You can also create a Quotation from an Opportunity.
-
-<img class="screenshot" alt="Make Quotation from Opportunity" src="/assets/manual_erpnext_com/img/selling/make-quote-from-opp.png">
-
-Or You can create a new Quotation and pull details from an Opportunity.
-
-<img class="screenshot" alt="Make Quotation from Opportunity" src="/assets/manual_erpnext_com/img/selling/make-quotation.gif">
-
-A Quotation contains details about:
-
-  * The recipient of the Quotation
-  * The Items and quantities you are offering.
-  * The rates at which they are offered. For details refer 
-  * The taxes applicable.
-  * Other charges (like shipping, insurance) if applicable.
-  * The validity of contract.
-  * The time of delivery.
-  * Other conditions.
-
-> Tip: Images look great on Quotations. To add images to your Quotations,
-attach the corresponding image in the Item master.
-
-### Rates
-
-The rates you quote may depend on two things.
-
-  * The Price List: If you have multiple Price Lists, you can select a Price List or tag it to the Customer (so that it is auto-selected). Your Item prices will automatically be updated from the Price List.For details refer [Price List](/contents/setting-up/price-lists)
-
-  * The Currency: If you are quoting to a Customer in a different currency, you will have to update the conversion rates to enable ERPNext to save the information in your standard Currency. This will help you to analyze the value of your Quotations in standard Currency.
-
-### Taxes
-
-To add taxes to your Quotation, you can either select a tax template, Sales
-Taxes and Charges Template or add the taxes on your own. To understand taxes in
-detail visit [Taxes](/contents/setting-up/setting-up-taxes)
-
-You can add taxes in the same manner as the Sales Taxes and Charges Template.
-
-### Terms and Conditions
-
-Each Quotation must ideally contain a set of terms, of your contract. It is
-usually a good idea to make templates of your Terms and Conditions, so that
-you have a standard set of terms. You can do this by going to:
-
-> Selling > Terms and Conditions
-
-#### What should Terms and Conditions Contain?
-
-  * Validity of the offer.
-  * Payment Terms (In Advance, On Credit, part advance etc).
-  * What is extra (or payable by the Customer).
-  * Safety / usage warning.
-  * Warranty if any.
-  * Returns Policy.
-  * Terms of shipping, if applicable.
-  * Ways of addressing disputes, indemnity, liability, etc.
-  * Address and Contact of your Company.
-
-### Submission
-
-Quotation is a “Submittable” transaction. Since you send this Quotation to
-your Customer or Lead, you must freeze it so that changes are not made after
-you send the Quotation. See Document Stages.
-
-> Tip: Quotations can also be titled as “Proforma Invoice” or “Proposal”.
-Select the right heading in the “Print Heading” field in the “More Info”
-section. To create new Print Headings go to Setup > Branding and Printing >
-Print Headings.
-
-### Discount
-
-While making your sales transactions like a Quotation (or Sales Order) you
-would already have noticed that there is a “Discount” column. On the left is
-the “Price List Rate” on the right is the “Basic Rate”. You can add a
-“Discount” value to update the basic rate. To understand more about discount
-read [Discount.](http://erpnext.org/discount)
-
-{next}
diff --git a/erpnext/docs/user/selling/sales-order.md b/erpnext/docs/user/selling/sales-order.md
deleted file mode 100644
index e0984b0..0000000
--- a/erpnext/docs/user/selling/sales-order.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Sales Order
-
-The Sales Order confirms your sales and triggers purchase (**Material
-Request**) shipment (**Delivery Note**), billing (**Sales Invoice**) and
-manufacturing (**Production Plan**)
-
-A Sales Order is usually a binding Contract with your Customer.
-
-Once your customer confirms the Quotation you can convert your Quotation into
-a Sales Order.
-
-### Sales Order Flow-Chart
-
-![Sales Order](/assets/manual_erpnext_com/old_images/erpnext/sales-order-f.jpg)
-
-To create a new Sales Order go to:
-
-> Selling > Sales Order > New Sales Order
-
-### Creating Sales Order from Quotation
-
-You can also create a Sales Order from a submitted Quotation.
-
-<img class="screenshot" alt="Make Sales Order from Quotation" src="/assets/manual_erpnext_com/img/selling/make-SO-from-quote.png">
-
-Or you can create a new Sales Order and pull details from an Quotation.
-
-<img class="screenshot" alt="Make Sales Order from Quotation" src="/assets/manual_erpnext_com/img/selling/make-so.gif">
-
-Most of the information in your Sales Order is the same as the Quotation.
-There are a few amongst other things that a Sales Order will ask you to
-update.
-
-  * Expected date of delivery.
-  * Customer Purchase Order number: If your customer has sent you a Purchase Order, you can update its number for future reference (in billing).
-
-### Packing List
-
-The “Packing List” table will be automatically updated when you “Save” the
-Sales Order. If any Items in your table are Product Bundle (packets), then the
-“Packing List” will contain the exploded (detailed) list of your Items.
-
-### Reservation and Warehouses
-
-If your Sales Order contains Items for which inventory is tracked (Is Stock
-Item is “Yes”) then, ERPNext will ask you for “Reservation Warehouse”. If you
-have set a default Warehouse for the Item, it will automatically set this
-Warehouse here.
-
-This “reserved” quantity will help you project what is the quantity you need
-to purchase based on all your commitments.
-
-### Sales Team
-
-**Sales Partner:** If this Sale was booked via a Sales Partner, you can update the Sales Partner’s details with commission and other info that you can aggregate.
-
-**Sales Persons:** ERPNext allows you to tag multiple Sales Persons who may have worked on this deal. You can also split the amount in targets of different Sales Persons and track how much incentives they earned on this deal.
-
-### Recurring Sales Orders
-
-If you have a recurring contract with a Customer where you are required to generate a Sales Order on a monthly, quarterly, half-yearly or annual basis, you can check the “Convert To Recurring Order” box. 
-
-Here you can fill in the details like; of how frequently you want to generate an Order in the 'Recurring Type' field, specify the day of of the month on which the Order needs to be generated in the 'Repeat On Day Of Month' field and the date on which the recurring orders should stop in the 'End Date' field.
-
-**Recurring Type:** Here you can update how frequently you want to generate an Order.
-
-**Repeat On Day Of Month:** You can specify the day of of the month on which the Order needs to be generated.
-
-**End Date:** The date on which the recurring orders should stop can be specified here.
-
-On updating the Sales Order, a Recurring ID will be generated which will be same for all recurring orders generated from this particular Sales Order.
-
-ERPNext will automatically create new Order and mail a notification to the email IDs you set in the 'Notification Email Address'field.
-
-<img class="screenshot" alt="Reccuring Sales Order" src="/assets/manual_erpnext_com/img/selling/recurring-sales-order.png">
-
-### Next Steps
-
-Once you “Submit” your Sales Order, you can now trigger different aspects of
-your organization:
-
-  * To begin purchase click on “Make Purchase Request”
-  * To make a shipment entry click on “Make Delivery Note”
-  * To bill, make “Make Sales Invoice”
-  * To stop further process on this Sales Order, click on “Stop”
-
-### Submission
-
-Sales Order is a “Submittable” transaction. See Document Stages. You will be
-able to execute dependent steps (like making a Delivery Note) only after
-“Submitting” this Sales Order.
-
-### Sales Order with Order type Maintenance
-
-When the 'Order Type' of the Sales Order is 'Maintenance' follow the steps
-given below:
-
-__Step 1:__ Enter Currency, Price list and Item details.
-
-__Step 2:__ Mention taxes and other information.
-
-__Step 3:__ Save and Submit the form
-
-__Step 4:__ Once the form is submitted, the Action button will provide three
-choices.i) Maintenance Visit ii) Maintenance Schedule iii) Invoice.
-
-
-
-> **Note 1:**   
-By clicking on the Action button and selecting 'Maintenance Visit' you can directly fill the visit form. The Sales Order details will be fetched directly.    
-
-> **Note 2:**    
-By clicking on the Action button and selecting 'Maintenance Schedule' you can fill the schedule details. The Sales Order details will be fetched directly.
-
-> **Note 3:**    
-By clicking on the Invoice button you can make an Invoice for your
-services . The sales orders details will be fetched directly.
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/item-price.md b/erpnext/docs/user/selling/setup/item-price.md
deleted file mode 100644
index eea33ea..0000000
--- a/erpnext/docs/user/selling/setup/item-price.md
+++ /dev/null
@@ -1,43 +0,0 @@
-Item Price is the record in which you can log sellig and buying rate of an item.
-
-There are two ways to reach to new Item Price form.
-
-> Selling/Buying/Stock >> Setup >> Item Price >> New Item Price
-
-Or
-
-> Item >> Add/Edit Prices >> Click on "+"  >> New Item Price
-
-Following are the steps to create new Item Price.
-
-Step 1: Select Price List
-
-You can create multiple Price List in ERPNext to track Selling and Buying Price List of an item separtely. Also if item's selling prices id changing based on territory, or due to other criteria, you can create multiple selling Price List for it.
-
-![Item Price list](/assets/manual_erpnext_com/old_images/erpnext/item-price-list.png)
-
-On selection of Price List, its currency and for selling or buying property will be fetched as well.
-
-To have Item Price fetching in the sales or purchase transaction, you should have Price List id selected in the transaction, just above Item table.
-
-Step 2: Select Item
-
-Select item for which Item Price record is to be created. On selection of Item Code, Item Name and Description will be fetched as well.
-
-![Item Price Item](/assets/manual_erpnext_com/old_images/erpnext/item-price-item.png)
-
-Step 3: Enter Rate
-
-Enter selling/buying rate of an item in Price List currency.
-
-![Item Price Rate](/assets/manual_erpnext_com/old_images/erpnext/item-price-rate.png)
-
-Step 4: Save Item Price
-
-To check all Item Price together, go to:
-
-Stock >> Main Report >> Itemwise Price List Rate
-
-You will find option to create new Item Price record (+) in this report as well.
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/product-bundle.md b/erpnext/docs/user/selling/setup/product-bundle.md
deleted file mode 100644
index b80459d..0000000
--- a/erpnext/docs/user/selling/setup/product-bundle.md
+++ /dev/null
@@ -1,47 +0,0 @@
-#Product Bundle
-
-Product Bundle stands for Sales Bill-of-Material. It's a master where you can list item which are bundled together and 
-sold as one item. For instance, when laptop is delivered, you need to ensure that charger, mouse and laptop bag are 
-delivered and stock level of these items gets affected. To address this scenario, you can set create Product Bundle for 
-the main item, i.e. laptop, and list deliverable items i.e. laptop + charger + other accessories as child items.
-  
-Following are the steps on how to setup Product Bundle master, and how is it used in the sales transactions.
-
-####Create new Product Bundle
-
-To create new Product Bundle, Go to:
-
-Selling > Setup > Product Bundle > New
-
-<img class="screenshot" alt="Product Bundle" src="/assets/manual_erpnext_com/img/selling/product-bundle.png">
-
-###Select Parent Item
-
-In Product Bundle master, there are two sections. Product Bundle Item and Package Item.
-
-In Product Bundle item, you will select a Parent Item. The parent item must be a <b>non-stock item</b>. 
-This is non-stock item because there is no stock maintained for it but only the Package Items. 
-If you want to maintain stock for the Parent Item, then you must create a regular Bill of Material (BOM) 
-and package them using a Stock Entry Transactions.
-
-###Select Child Items
-
-In Package Item section, you will list all the child items for which we maintain stock and is delivered to customer.
-
-###Product Bundle in the Sales Transactions
-
-When making Sales transactions like Sales Invoice, Sales Order and Delivery Note, 
-Parent Item will be selected in the main item table.
-
-<img class="screenshot" alt="Product Bundle" src="/assets/manual_erpnext_com/img/selling/product-bundle.gif">
-
-On selection on Parent Item in the main item table, its child items will be fetched in Packing List 
-table of the transaction. If child item is the serialized item, you will be able to specify its Serial Mo. 
-in packing List table itself. On submission of transaction, system will reduce the stock level of child items from 
-warehouse specified in Packing List table.
-
-<div class="well"><b>Use Product Bundle to Manage Schemes:</b>
-<br>
-This work-around in Product Bundle was discovered when a customer dealing into nutrition product asked for feature to manage schemes like "Buy One Get One Free". To manage the same, he created a non-stock item which was used as Parent Item. In description of item, he entered scheme details with items image indicating the offer. The saleable product was selected in Package Item where qty was two. Hence every time they sold one qty of Parent item under scheme, system deducted two quantities of product from Warehouse.</div>
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/sales-partner.md b/erpnext/docs/user/selling/setup/sales-partner.md
deleted file mode 100644
index 024c204..0000000
--- a/erpnext/docs/user/selling/setup/sales-partner.md
+++ /dev/null
@@ -1,34 +0,0 @@
-People who assist you in getting business are termed as Sales Partners. Sales Partners can be represented by different names in ERPNext. You can call them Channel Partner, Distributor, Dealer, Agent, Retailer, Implementation Partner, Reseller etc.
-
-For each Sales Partner, you can define commission offer to them. When Sales Partner is selected in transactions, there commission is calculated over Net Total of Sales Order/Invoice or Delivery Note.
-
-You can track Sales Personwise commission in the report under Selling module.
-
-To create a sales partner go to:
-
-`Selling > Setup > Sales Partner`
-
-Sales Partners are saved with Sales Partner name provided by user.
-
-<img class="screenshot" alt="Sales Partner" src="/assets/manual_erpnext_com/img/selling/sales-partner.png">
-
-You can track their address and contact details and also allocate Sales Partner for each Item Group, based on Qty and Amount.
-
-### Including Sales Partners in Your Website
-
-To include the name of your Partner on your website, check the "Show in
-Website" box. When click on "Show in Website", you will see field where you can attach logo of partner's company and enter brief and introduction of partner.
-
-<img class="screenshot" alt="Sales Partner" src="/assets/manual_erpnext_com/img/selling/sales-partner-website.png">
-
-To see listing of partner, you should go to:
-
-https://example.erpnext.com/partners
-
-![Sales Partner Listing](/assets/manual_erpnext_com/old_images/erpnext/sales-partner-listing.png)
-
-Following is the complete partners details published on the website.
-
-![Sales Partner Published](/assets/manual_erpnext_com/old_images/erpnext/sales-partner-published.png)
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/sales-person-target-allocation.md b/erpnext/docs/user/selling/setup/sales-person-target-allocation.md
deleted file mode 100644
index 9358ec0..0000000
--- a/erpnext/docs/user/selling/setup/sales-person-target-allocation.md
+++ /dev/null
@@ -1,86 +0,0 @@
-With management of Sales Person, ERPNext also allow you to assign target to Sales Persons based on Item Group and Territory. Based on target allocated and actual sales booked by Sales Person, you will get target variance report for the Sales Person.
-
-###1. Sales Person - Item Groupwise Target Allocation
-
-####1.1 Open Sales Person's Master
-
-To allocate target, you should open specific Sales Person master.
-
-`Selling > Setup > Sales Person > (Open Sales Person)`
-
-####1.2 Allocate Item Groupwise Target
-
-In the Sales Person master, you will find table called Sales Person Target.
-
-![Sales Person Target Item Group](/assets/manual_erpnext_com/old_images/erpnext/sales-person-target-item-group.png)
-
-In this table, you should select Item Group, Fiscal Year, Target Qty and Amount. 
-
-<div class=well>You can give target in amount or quantity, or in both. Item Group can also be left blank. In this case the system will calculate target based on all the Items.</div>
-
-####1.3 Target Distribution
-
-If you wish to spread allocated target across months, then you shoult setup Target Distribution master, and select it in the Sales Person master. Considering our example, target for the month of December will be set as 5 qty (10% of total allocation).
-
-![Sales Person Target Distribution](/assets/manual_erpnext_com/old_images/erpnext/sales-person-target-distribution.png)
-
-####Report - Sales Person Target Variance Item Groupwise
-
-To check this report, go to:
-
-`Selling > Standard Report > Sales Person Target Variance (Item Group-wise)'
-
-This report will provide you variance between target and actual performance of Sales Person. This report is based on Sales Order report.
-
-![Sales Person Item Group Report](/assets/manual_erpnext_com/old_images/erpnext/sales-person-item-group-report.png)
-
-As per the report, allocated target to Sales Person for the month of December was 5 qty. However, Sales Order was made for this employee and Item Group for only 3 qty. Hence, variance of 2 qty is shown in the report.
-
----
-
-###2. Sales Person - Territorywise Target Allocation
-
-To allocate target to Sales Person based on Territory, you can should select specific Sales Person in the Territory master. This Sales Person is entered just for the reference. Sales Person details are not updated in the variance report of Territorywise Target Allocation.
-
-####2.1 Go to Territory master
-
-`Selling > Setup > Territory > (Open specific Territory master)`
-
-In the Territory master, you will find field to select Territory Manager. This field is linked to "Sales Person" master.
-
-![Sales Person Territory Manager](/assets/manual_erpnext_com/old_images/erpnext/sales-person-territory-manager.png)
-
-####2.2 Allocating Target
-
-Allocation Target in the Territory master is same as in Sales Person master. You can follow same steps as given above to specify target in the Territory master as well.
-
-####2.3 Target Distribution
-
-Using this master, you can divide target Qty or Amount across various months.
-
-####2.4 Report - Territory Target Variance Item Groupwise
-
-This report will provide you variance between target and actual performance of Sales in particular territory. This report is based on Sales Order report. Though Sales Person is defined in the Territory master, its details are not pulled in the report.
-
-![Sales Person Territory Report](/assets/manual_erpnext_com/old_images/erpnext/sales-person-territory-report.png)
-
----
-
-###3. Target Distribution
-
-Target Distribution master allows you to divide allocated target across multiple months. If your product and services is seasonal, you can distribute the sales target accordingly. For example, if you are into umbrella business, then target allocated in the monsoon seasion will be higher than in other months.
-
-To create new Budget Distriibution master, go to:
-
-`Accounts > Setup > Budget Distributon`
-
-![Target Distribution](/assets/manual_erpnext_com/old_images/erpnext/target-distribution.png)
-
-You can link target distribution while allocation targets in Sales Person as well as in Territory master.
-
-###See Also
-
-1. [Managing Sales Person](https://erpnext.com/selling/selling-setup/sales-person)
-2. [Using Sales Person in transactions](https://erpnext.com/kb/selling/managing-sales-persons-in-sales-transactions)
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/selling-settings.md b/erpnext/docs/user/selling/setup/selling-settings.md
deleted file mode 100644
index 5fc7bb5..0000000
--- a/erpnext/docs/user/selling/setup/selling-settings.md
+++ /dev/null
@@ -1,71 +0,0 @@
-Selling Setting is where you can define propertiese which will be applied in your selling transactions. 
-Let's check into each property one by one.
-
-<img class="screenshot" alt="Selling Settings" src="/assets/manual_erpnext_com/img/selling/selling-settings.png">
-
-####1. Customer Naming By
-
-When customer is saved, system generated unique ID for that Customer. Using that Customer ID, 
-you can select Customer in other transactions.
-
-Bydefault Customer will be saved with Customer Name. If you wish to save Customer using 
-a naming series, you should set Customer Naming By as "Naming Series".
-
-Example of Customer Id's saved in Naming Series - `CUST00001,CUST00002, CUST00003...` and so on.
-
-You can set Naming Series for customer naming from:
-
-> Setup > Settings > Naming Series`
-
-####2. Campaign Naming By
-
-Just like for Customer, you can also configure as how ID will be generated for the Campaign master. 
-Bydefault Campaign will be saved with Campaign Name provided while its creation.
-
-####3. Default Customer Group
-
-Customer Group in this field will be auto-updated when you open new Customer form.
-While converting Quotation created for Lead into Sales Order, system attempts to convert 
-Lead into Customer in the backend. While creating Customer in the backend, system pickup 
-Customer Group and Territory as defined in the Selling Setting. If system doesn't find 
-any values, then following validation message will be raised.
-To resolve this, you should:
-Either manually convert Lead into Customer, and define Customer Group and Territory manually while 
-creating Customer or define Default Customer Group and Territory in the Selling Setting. 
-Then you should have Lead automatically converted into Customer when convert Quotation into Sales Order.
-
-####4. Default Territory
-
-Territory defined in this field will be auto-updated in the Territory field of Customer master.
-
-Just like Customer Group, Territory is also checked when system tries creating Customer in the backend.
-
-####5. Default Price List
-
-Price List set in this field will be auto-updated in the Price List field of Sales transactions.
-
-####6. Sales Order Required
-
-If you wish to make Sales Order creation mandatory before creation of Sales Invoice, then you should 
-set Sales Order Required field as Yes. Bydefault, this will be "No" for a value.
-
-####7. Delivery Note Required
-
-To make Delivery Note creation as mandatory before Sales Invoice creation, you should set 
-this field as "Yes". It will be "No" by default.
-
-####8. Maintain Same Rate Throughout Sales Cycle
-
-System bydefault validates that item price will be same throughout sales cycle 
-(Sales Order - Delivery Note - Sales Invoice). If you could have item price changing within the cycle, 
-and you need to bypass validation of same rate throughout cycle, then you should uncheck this field and save.
-
-####9. Allow User to Edit Price List Rate in Transaction
-
-Item table of the sale transactions has field called Price List Rate. This field be non-editale 
-by default in all the sales transactions. This is to ensure that price of an item is fetched from 
-Item Price record, and user is not able to edit it.
-
-If you need to enable user to edit Item Price, fetched from Price List of an item, you should uncheck this field.
-
-{next}
diff --git a/erpnext/docs/user/selling/setup/shipping-rule.md b/erpnext/docs/user/selling/setup/shipping-rule.md
deleted file mode 100644
index a5f9477..0000000
--- a/erpnext/docs/user/selling/setup/shipping-rule.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Using Shipping Rule you can define the cost for delivering the product to the customer.
-You can define different shipping rules for the same item across different territories.
-
-<img class="screenshot" alt="Shipping Rule" src="/assets/manual_erpnext_com/img/selling/shipping-rule.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/setting-up/authorization-rule.md b/erpnext/docs/user/setting-up/authorization-rule.md
deleted file mode 100644
index fca4fd6..0000000
--- a/erpnext/docs/user/setting-up/authorization-rule.md
+++ /dev/null
@@ -1,43 +0,0 @@
-Authorization Rule is a tool to define rule for conditional authorization.
-
-If you sales and purchase transactions of higher value or discount requires an authorization from senior manager, you can set authorization rule for it.
-
-To create new Authorization Rule, go to:
-
-> Setup > Customize > Authorization Rule
-
-Let's consider an example of Authorization Rule to learn better.
-
-Assume that Sales Manager needs to authorize Sales Orders, only if its Grand Total value exceeds 10000. If Sales Orer values is less than 10000, then even Sales User will be able to submit it. It means Submit permision of Sales User will be restricted only upto Sales Order of Grand Total less than 10000.
-
-**Step 1:**
-
-Open new Authorization Rule
-
-**Step 2:**
-
-Select Company and Transaction on which Authorization Rule will be applicable. This functionality is available for limited transactions only.
-
-**Step 3:**
-
-Select Based On. Authorization Rule will be applied based on value selected in this field.
-
-**Step 4:**
-
-Select Role on whom this Authorization Rule will be applicable. As per the example considered, Sales User will be selected as Application To (Role). To be more specific you can also select Applicale To User, if you wish to apply to rule for specific Sales User, and not all Sales User. Its okay to not select Sales User, as its not mandatory.
-
-**Step 5:**
-
-Select approvers Role. It will be Sales Manager role which if assigned to user, will be able to submit Sales Order above 10000. Also you can select specific Sales Manager, and then rule should be applicable for that User only. Selecting Approving User field is not mandatory.
-
-**Step 6:**
-
-Set Above Value. Given the exmaple, Above Value will be set as 10000.
-
-<img class="screenshot" alt="Authorization Rule" src="/assets/manual_erpnext_com/img/setup/auth-rule.png">
-
-If Sales User tries submitting Sales Order of value higher than 10000, then he will get error message.
-
->If you wish to restrict Sales User from submitting Sales Orders, then instead of creating Authorization Rule, you should remove submit previledge from Role Permission Manager for Sales User.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/bar-code.md b/erpnext/docs/user/setting-up/bar-code.md
deleted file mode 100644
index 556d4e3..0000000
--- a/erpnext/docs/user/setting-up/bar-code.md
+++ /dev/null
@@ -1,50 +0,0 @@
-A Barcode is a machine-readable code in the form of numbers and a pattern of
-parallel lines of varying widths, printed on a commodity and used especially
-for stock control.
-
-When you purchase an item from any store, you will notice a label with thin,
-black lines across it, along with a variation of different numbers. This label
-is then scanned by the cashier, and the item's description and price
-automatically comes up. This set of lines and numbers on the label are termed
-as bar-code.
-
-A bar-code machine scans the number from the label of an Item. To work with
-ERPNext and the bar-code mechanism, connect the bar-code machine to your
-operating hardware. Then go to ERPNext setup and activate bar-code by going to
-tools and clicking on 'hide / unhide features'. Under Materials, feature
-setup, check the box that says Item Barcode.
-
-> Setup > Customize > Hide/ Unhide Features > Item Barcode.
-
-#### Figure 1: Check the box 'Item Barcode'
-
-<img class="screenshot" alt="Barcode" src="/assets/manual_erpnext_com/img/setup/barcode-1.png">
-
-
-To start scanning with a bar-code, go to  
-
-> Accounts > Sales Invoice
-
-Under Item, click on Add new row. The item row will expand to show new fields.
-Place your cursor on the bar-code field and begin scanning. The bar-code will
-be updated in the field. Once the bar-code is entered, all the Item details
-will be fetched automatically by the system.
-
-For more ease, activate the POS view in ERPnext. The activation process is
-same as the bar-code activation. Go to Setup and click on 'hide/unhide
-features'. Check the 'POS view' box.
-
-Then go to Accounts and click on Sales Invoice. Check the box 'Is POS'
-
-  
-#### Figure 2: Check the box 'Is POS'
-
-<img class="screenshot" alt="Barcode" src="/assets/manual_erpnext_com/img/setup/barcode-2.png">
-
-
-Go to Item and click on Add new row.  
-
-The cursor will automatically be placed in the bar-code field. Thus you can
-immediately scan the bar-code and proceed with your operations.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/data/bulk-rename.md b/erpnext/docs/user/setting-up/data/bulk-rename.md
deleted file mode 100644
index 216edc6..0000000
--- a/erpnext/docs/user/setting-up/data/bulk-rename.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# Bulk Renaming of Records
-
-You can rename a document if ERPNext (if it is allowed) by going to **Menu > Rename** in the document.
-
-Alternatively, if you want to rename a whole bunch of records, just go to:
-
-> Setup > Data > Rename Tool
-
-This tool will allow you to rename multiple records at the same time.
-
-### Example
-
-To rename multiple records, upload a **.csv** file with the old name in the first column and the new name in the second column and click on **Upload**.
-
-<img class="screenshot" alt="Bulk Rename" src="/assets/manual_erpnext_com/img/setup/data/rename.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/data/data-import-tool.md b/erpnext/docs/user/setting-up/data/data-import-tool.md
deleted file mode 100644
index ffb700d..0000000
--- a/erpnext/docs/user/setting-up/data/data-import-tool.md
+++ /dev/null
@@ -1,110 +0,0 @@
-The Data Import Tool is a great way to upload (or edit) bulk data, specially
-master data, into the system.
-
-To Open the data import tool, you either go to Setup or go to the Transaction
-you want to Import. If Data Import is allowed, you will see an Import Button:
-
-<img alt="Start Import" class="screenshot" src="/assets/manual_erpnext_com/img/setup/data-import/data-import-1.png">
-
-The tool has two sections, one to download a template and the second to upload
-the data.
-
-(Note: Only those DocTypes are allowed for Import whose Document Type is
-"Master" or Allow Import property is set.)
-
-### 1\. Downloading The Template
-
-Data in ERPNext is stored in tables, much like a spreadsheet with columns and
-rows of data. Each entity in ERPNext can have multiple child tables associated
-with it too. The child tables are linked to the parent tables and are
-implemented where there are multiple values for any property. For example an
-Item can have multiple prices, An Invoice has multiple Items and so on.
-
-<img alt="Download Template" class="screenshot" src="/assets/manual_erpnext_com/img/setup/data-import/data-import-2.png">
-
-  * Click on the table you want to download or "All Tables"
-  * For bulk editing, you can click on "Download With Data"
-
-### 2\. Fill in the Template
-
-After downloading the template, open it in a spreadsheet application and fill
-in the data below the column headings.
-
-![Spreadsheet](/assets/manual_erpnext_com/old_images/erpnext/import-3.png)
-
-Then export your template or save it as a **Comma Separated Values** (CSV)
-file.
-
-![Spreadsheet](/assets/manual_erpnext_com/old_images/erpnext/import-4.png)
-
-### 3\. Upload the .csv File
-
-Finally attach the .csv file in the section. Click on the "Upload and Import"
-button.
-
-<img alt="Upload" class="screenshot" src="/assets/manual_erpnext_com/img/setup/data-import/data-import-3.png">
-
-#### Notes:
-
-1. Make sure that if your application allows, use encoding as UTF-8.
-1. Keep the ID column blank for new records.
-
-### 4\. Uploading All Tables (Main + Child)
-
-If you select all tables, you will get columns belonging to all the tables in
-one row separated by `~` columns.
-
-If you have multiple child rows then you must start a new main item on a new
-row. See the example:
-
-
-    Main Table                          ~   Child Table
-    Column 1    Column 2    Column 3    ~   Column 1    Column 2    Column 3
-    v11         v12         v13             c11         c12         c13
-                                            c14         c15         c17
-    v21         v22         v23             c21         c22         c23
-
-> To see how its done, enter a few records manually using forms and export
-"All Tables" with "Download with Data"
-
-### 5\. Overwriting
-
-ERPNext also allows you to overwrite all / certain columns. If you want to
-update certain columns, you can download the template with data. Remember to
-check on the “Overwrite” box before uploading.
-
-> Note: For child records, if you select Overwrite, it will delete all the
-child records of that parent.
-
-### 6\. Upload Limitations
-
-ERPNext restricts the amount of data you can upload in one file. Though the
-number may vary based on the type of data. It is usually safe to upload around
-1000 rows of a table at one go. If the system will not accept, then you will
-see an error.
-
-Why is this? Uploading a lot of data can cause your system to crash, specially
-if there are other users doing things in parallel. Hence ERPNext restricts the
-number of “writes” you can process in one request.
-
-***
-
-#### How to Attach files?
-
-When you open a form, on the right sidebar, you will see a section to attach
-files. Click on “Add” and select the file you want to attach. Click on
-“Upload” and you are set.
-
-#### What is a CSV file?
-
-A CSV (Comma Separated Value) file is a data file that you can upload into
-ERPNext to update various data. Any spreadsheet file from popular spreadsheet
-applications like MS Excel or Open Office Spreadsheet can be saved as a CSV
-file.
-
-If you are using Microsoft Excel and using non-English characters, make sure
-to save your file encoded as UTF-8. For older versions of Excel, there is no
-clear way of saving as UTF-8. So save your file as a CSV, then open it in
-Notepad, and save as “UTF-8”. (Sorry blame Microsoft for this!)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/email/email-account.md b/erpnext/docs/user/setting-up/email/email-account.md
deleted file mode 100644
index 104341f..0000000
--- a/erpnext/docs/user/setting-up/email/email-account.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Email Accounts
-
-You can manage multiple incoming and outgoing Email Accounts in ERPNext. There has to be atleast one default outgoing account and one default incoming account. If you are on the ERPNext cloud, the default outgoing email is set by us.
-
-> **Note for self implementers:** For outgoing emails, you should setup your own SMTP server or sign up with an SMTP relay service like mandrill.com or sendgrid.com that allows a larger number of transactional emails to be sent. Regular email services like GMail will restrict you to a limited number of emails per day.
-
-### Default Email Accounts
-
-ERPNext will create templates for a bunch of email accounts by default. Not all of them are enabled. To enable them, you must set your account details.
-
-There are 2 types of email accounts, outgoing and incoming. Outgoing email accounts use an SMTP service to send emails and emails are retrived from your inbox using a POP service. Most email providers such as GMail, Outlook or Yahoo provide these services.
-
-<img class="screenshot" alt="Defining Criteria" src="/assets/manual_erpnext_com/img/setup/email/email-account-list.png">
-
-### Outgoing Email Accounts
-
-All emails sent from the system, either by the user to a contact or notifications or transaction emails, will be sent from an Outgoing Email Account.
-
-To setup an outgoing Email Account, check on **Enable Outgoing** and set your SMTP server settings, if you are using a popular email service, these will be preset for you.
-
-<img class="screenshot" alt="Outgoing EMail" src="/assets/manual_erpnext_com/img/setup/email/email-account-sending.png">
-
-### Incoming Email Accounts
-
-To setup an incoming Email Account, check on **Enable Incoming** and set your POP3 settings, if you are using a popular email service, these will be preset for you.
-
-<img class="screenshot" alt="Incoming EMail" src="/assets/manual_erpnext_com/img/setup/email/email-account-incoming.png">
-
-### How ERPNext handles replies
-
-In ERPNext when you send an email to a contact like a customer, the sender will be the user who sent the email. In the **Reply-To** property, the email id will be of the default incoming account (like `replies@yourcompany.com`). ERPNext will automatically extract these emails from the incoming account and tag it to the relvant communication
-
-### Notification for unreplied messages
-
-If you would like ERPNext to notify you if an email is unreplied for a certain amount of time, then you can set **Notify if Unreplied**. Here you can set the number of minutes to wait before notifications are sent and whom the notifications must go to.
-
-<img class="screenshot" alt="Incoming EMail" src="/assets/manual_erpnext_com/img/setup/email/email-account-unreplied.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/email/email-alerts.md b/erpnext/docs/user/setting-up/email/email-alerts.md
deleted file mode 100644
index c2d91a9..0000000
--- a/erpnext/docs/user/setting-up/email/email-alerts.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# Email Alerts
-
-You can configure various email alerts in your system to remind you of important activities such as:
-
-1. Completion date of a Task.
-1. Expected Delivery Date of a Sales Order.
-1. Expected Payment Date.
-1. Reminder of followup.
-1. If an Order greater than a particular value is received or sent.
-1. Expiry notification for a Contract.
-1. Completion / Status change of a Task.
-
-For this, you need to setup an Email Alert.
-
-> Setup > Email > Email Alert
-
-### Setting Up An Alert
-
-To setup an Email Alert:
-
-1. Select which Document Type you want watch changes on
-1. Define what events you want to watch. Events are:
-	1. New: When a new document of the selected type is made.
-	2. Save / Submit / Cancel: When a document of the selected type is saved, submitted, cancelled.
-	3. Value Change: When a particular value in the selected type changes.
-	4. Days Before / Days After: Trigger this alert a few days before or after the **Reference Date.** To set the days, set **Days Before or After**. This can be useful in reminding you of upcoming due dates or reminding you to follow up on certain leads of quotations.
-1. Set additional conditions if you want.
-1. Set the recipients of this alert. The recipient could either be a field of the document or a list of fixed email ids.
-1. Compose the message
-
----
-
-### Example
-
-1. Defining the Criteria
-    <img class="screenshot" alt="Defining Criteria" src="/assets/manual_erpnext_com/img/setup/email/email-alert-1.png">
-
-1. Setting the Recipients and Message
-    <img class="screenshot" alt="Set Message" src="/assets/manual_erpnext_com/img/setup/email/email-alert-2.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/email/email-digest.md b/erpnext/docs/user/setting-up/email/email-digest.md
deleted file mode 100644
index a53137a..0000000
--- a/erpnext/docs/user/setting-up/email/email-digest.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# Email Digest
-
-Email Digests allow you to get regular updates about your sales, expenses and other critical numbers directly in your Inbox.
-
-Email Digests are a great way for top managers to keep track of the big numbers like “Sales Booked” or “Amount Collected” or “Invoices Raised” etc.
-
-To set up Email Digest, go to:
-
-> Setup > Email > Email Digest
-
-## Example
-
-Set your frequency, check all the items you want to receive in your weekly update and select the user ids whom you want to send the Digest to.
-
-<img class="screenshot" alt="Email Digest" src="/assets/manual_erpnext_com/img/setup/email/email-digest.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/email/sending-email.md b/erpnext/docs/user/setting-up/email/sending-email.md
deleted file mode 100644
index 420372d..0000000
--- a/erpnext/docs/user/setting-up/email/sending-email.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Sending Email from any Document
-
-In ERPNext you can send any document as email (with a PDF attachment) by clicking on `Menu > Email` from any open document.
-
-<img class="screenshot" alt="Send Email" src="/assets/manual_erpnext_com/img/setup/email/send-email.gif">
-
-**Note:** You must have outgoing [email accounts](/contents/setting-up/email/email-account) setup for this.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/email/setting-up-email.md b/erpnext/docs/user/setting-up/email/setting-up-email.md
deleted file mode 100644
index c38789d..0000000
--- a/erpnext/docs/user/setting-up/email/setting-up-email.md
+++ /dev/null
@@ -1,95 +0,0 @@
-Emails are the nervous system of business communication and ERPNext has been
-designed to make good use of this.
-
-## Sending Emails
-
-You can email any document from the system, by clicking on the “Email” button
-on the right sidebar. Before that you will need to set your outgoing email
-settings (SMTP server).
-
-All emails sent from the system are added to the Communication table.
-
-> **Info:** What is SMTP? There are two types of email services, sending and
-receiving emails. Sending is done via a protocol called SMTP (Simple Mail
-Transfer Protocol) and the server (computer) that sends your email to its
-destination is called SMTP Server.
-
-
-Bulk Emails, especially those that are sent without consent (spam), are considered as bad behavior. While it may be okay to send emails to those who have “opted-in” to receive mails, it is very difficult for the internet community to know what is spam and what is allowed. To overcome this problem, most email servers share a black and white list of email senders. If your emails have been marked as spam, you will be blacklisted. So be careful. Many times, it may be a good idea to send email via whitelisted services also known as SMTP relay services which are paid services.These
-services will block you from sending spam while ensuring that most of your email does not go in the spam folder. There are many such services available like SendGrid and SMTP.com.
-
-To setup your outgoing mails, go to
-
-> Setup > Outgoing Email Settings
-
-#### Figure 1: Set up outgoing mail server.
-
-![Email Settings](/assets/manual_erpnext_com/old_images/erpnext/email-settings1.png)
-
-Set your outgoing mail server settings here. These are the same settings you
-would use in your Outlook, Thunderbird, Apple Mail or other such email
-applications. If you are not sure, get in touch with your email service
-provider.
-
-> **Tip:** If you are using EPRNext hosted service, keep the first section
-blank. Emails will still be sent from your email id, but via our SMTP relay
-service.
-
-### Creating Issues from Incoming Emails
-
-A very useful email integration is to sync the incoming emails from support
-inbox into Issue, so that you can track, assign and monitor support
-issues.
-
-> **Case Study:** Here at ERPNext, we have regularly tracked incoming support
-issues via email at “support@erpnext.com”. At the time of writing we had
-answered more than 3000 tickets via this system.
-
-To setup your Support integration, go to:
-
-> Setup > Support Email Settings
-
-#### Figure 2: Setup support Integration
-
-![Email Settings](/assets/manual_erpnext_com/old_images/erpnext/email-settings2.png)
-
-To make ERPNext pull emails from your mail box, enter the POP3 settings. (POP3
-is a way of extracting emails from your mailbox. It should be fairly easy to
-find out what your POP3 settings are. If you have problems, contact your email
-service provider). If you want to setup an auto reply, check on the “Send
-Autoreply” box and whenever someone sends an email, an autoreply will be sent.
-Add a custom signature which you want to send with your replies.
-
-### Setting Auto-notification on Documents
-
-ERPNext allows you to automatically email documents on “Submission” to the
-contact mentioned in the document. To set this up, go to:
-
-> Setup > Tools > Enable / Disable Notifications.
-
-#### Figure 3: Set Auto Notification
-
-![Auto Notification](/assets/manual_erpnext_com/old_images/erpnext/auto-notification.png)
-
-Check on the transactions you want to send via email directly on Submission
-and add a custom message if you want on these documents.
-
-### Email Digests
-
-Email Digests allow you to get regular updates about your sales, expenses and
-other critical numbers directly in your Inbox.
-
-Set your frequency, check all the items you want to receive in your weekly
-update and select the user ids whom you want to send the Digest to.
-
-Email Digests are a great way for top managers to keep track of the big
-numbers like “Sales Booked” or “Amount Collected” or “Invoices Raised” etc.
-
-To setup Email Digests, go to:
-
-> Setup > Email Digest > New Email Digest
-
-#### Figure 4: Set up Email Digest
-
-![Email Digest](/assets/manual_erpnext_com/old_images/erpnext/email-digest.png)
-
diff --git a/erpnext/docs/user/setting-up/pos-setting.md b/erpnext/docs/user/setting-up/pos-setting.md
deleted file mode 100644
index c64a8ed..0000000
--- a/erpnext/docs/user/setting-up/pos-setting.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Point of Sale Setting
-
-POS includes advanced features to cater to different functionality, such as
-inventory management, CRM, financials, warehousing, etc., all built into the
-POS software. Prior to the modern POS, all of these functions were done
-independently and required the manual re-keying of information, which could
-lead to entry errors.
-
-If you are in retail operations, you want your Point of Sale to be as quick
-and efficient as possible. To do this, you can create a POS Setting for a user
-from:
-
-> Accounts > Setup > Point-of-Sale Setting
-
-Set default values as defined.
-
-<img class="screenshot" alt="POS Setting" src="/assets/manual_erpnext_com/img/pos-setting/pos-setting.png">
-
-> Important : If you specify a particular User, the POS setting will be
-applied only to that User. If the User option is left blank, the setting will
-be set for all users. To understand POS in detail visit [Point of Sale](/contents/accounts/point-of-sale-pos-invoice)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/price-lists.md b/erpnext/docs/user/setting-up/price-lists.md
deleted file mode 100644
index 772cb74..0000000
--- a/erpnext/docs/user/setting-up/price-lists.md
+++ /dev/null
@@ -1,21 +0,0 @@
-ERPNext lets you maintain multiple selling and buying prices for an Item using Price Lists. A PriceList is a name you can give to a set of Item prices. 
-
-Why would you want Price Lists? You have different prices for different zones (based on the shipping costs), for different currencies etc.
-
-An Item can have multiple prices based on customer, currency, region, shipping cost etc, which can be stored as different rate plans. In ERPNext, you are required to store all the lists separately. Buying Price List is different from Selling Price List and thus is stored separately.
-
-You can create new Price List
-
-> Selling/Buying/Stock  > Setup > Price List >> New
-
-<img class="screenshot" alt="Price List" src="/assets/manual_erpnext_com/img/price-list/price-list.png">
-
-* These Price List will be used when creating Item Price record to track selling or buying price of an item. Click here to learn more about Item Price.
-
-* To disable specific Price List, uncheck Enabled field in it. Disabled Price List will not be availale for selection in the Sales and Purchase transactions.
-
-* Standard Buying and Selling Price List are created by default.
-
-To disable specific Price List, uncheck Enabled field in it. Disabled Price List will not be availale for selection in the Sales and Purchase transactions.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/address-template.md b/erpnext/docs/user/setting-up/print/address-template.md
deleted file mode 100644
index 802d258..0000000
--- a/erpnext/docs/user/setting-up/print/address-template.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Address Template
-
-Each region has its own way of defining Addresses. To manage multiple address formats for your Documents (like Quotation, Purchase Invoice etc.), you can create country-wise **Address Templates**.
-
-> Setup > Printing and Branding > Address Template
-
-A default Address Template is created when you setup the system. You can either edit or update it or create a new template.
-
-One template is default and will apply to all countries that do not have an specific template.
-
-#### Template
-
-The templating engine is based on HTML and the [Jinja Templating](http://jinja.pocoo.org/docs/templates/) system and all the fields (including Custom Fields) will be available for creating the template.
-
-Here is the default template:
-
-	{{ address_line1 }}<br>
-	{% if address_line2 %}{{ address_line2 }}<br>{% endif -%}
-	{{ city }}<br>
-	{% if state %}{{ state }}<br>{% endif -%}
-	{% if pincode %}PIN:  {{ pincode }}<br>{% endif -%}
-	{{ country }}<br>
-	{% if phone %}Phone: {{ phone }}<br>{% endif -%}
-	{% if fax %}Fax: {{ fax }}<br>{% endif -%}
-	{% if email_id %}Email: {{ email_id }}<br>{% endif -%}
-
-### Example
-
-<img class="screenshot" alt="Print Heading" src="/assets/manual_erpnext_com/img/setup/print/address-format.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/letter-head.md b/erpnext/docs/user/setting-up/print/letter-head.md
deleted file mode 100644
index 71ad4f1..0000000
--- a/erpnext/docs/user/setting-up/print/letter-head.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Letter Heads
-
-You can manage multiple letter heads in ERPNext. In a letter head you can:
-
-  * Create an image with your logo, brand and other information that you want to put on your letter head.
-  * Attach the image in your Letter Head record by clicking on image icon to automatically generate the HTML required for this Letter Head.
-  * If you want to make this the default letter head, click on “Is Default”.
-
-Your letter head will now appear in all Prints and Emails of documents.
-
-You can create / manage Letter Heads from:
-
-> Setup > Printing > Letter Head > New Letter Head
-
-### Example
-
-<img class="screenshot" alt="Print Heading" src="/assets/manual_erpnext_com/img/setup/print/letter-head.png">
-
-This is how the letter head looks in a document print:
-
-<img class="screenshot" alt="Print Heading" src="/assets/manual_erpnext_com/img/setup/print/letter-head-1.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/print-format-builder.md b/erpnext/docs/user/setting-up/print/print-format-builder.md
deleted file mode 100644
index 906ef9a..0000000
--- a/erpnext/docs/user/setting-up/print/print-format-builder.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Print Format Builder
-
-The Print Format Builder helps you quickly make a simple customized Print Format by dragging and dropping data fields and adding custom text or HTML.
-
-You can create a new Print Format either by going to:
-
-> Setup > Printing and Branding > Print Format Builder
-
-or Open the document for which you want to make a print format. Click the Printer icon, or go to Menu > Print and click on the **Edit** button. Note: You must have System Manager permission to do this.
-
-### Step 1: Make a new Format
-
-<img class="screenshot" alt="Send Email" src="/assets/manual_erpnext_com/img/setup/print/print-format-builder-1.gif">
-
-### Step 2: Add a new Field
-
-To add a field, just drag it from the left sidebar and add it in your layout. You can edit the layout by clicking on the settings <i class="octicon octicon-gear"></i> icon.
-
-<img class="screenshot" alt="Send Email" src="/assets/manual_erpnext_com/img/setup/print/print-format-builder-2.gif">
-
-### Step 3
-
-To remove a field, just drag it back into the fields sidebar.
-
-<img class="screenshot" alt="Send Email" src="/assets/manual_erpnext_com/img/setup/print/print-format-builder-3.gif">
-
-### Step 4
-
-You can add customized text, HTML in your print format, just add the **Custom HTML** field (in dark colour) and add it to the the place where you want to add the text.
-
-Then click on **Edit HTML** to edit your content.
-
-<img class="screenshot" alt="Send Email" src="/assets/manual_erpnext_com/img/setup/print/print-format-builder-4.gif">
-
-To save your format, just click on the **Save** button on the top.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/print-headings.md b/erpnext/docs/user/setting-up/print/print-headings.md
deleted file mode 100644
index 3a2c49a..0000000
--- a/erpnext/docs/user/setting-up/print/print-headings.md
+++ /dev/null
@@ -1,17 +0,0 @@
-Print Headings are the names which you can give to your sales invoices,
-supplier quotations etc. You can create a list of names for different business
-communications.
-
-You can create print headings from :
-
-> Setup > Printing > Print Heading > New Print Heading
-
-#### Figure 1: Save Print Heading
-
-<img class="screenshot" alt="Print Heading" src="/assets/manual_erpnext_com/img/setup/print/print-heading.png">
-
-Example of a change in print heading is shown below:
-
-<img class="screenshot" alt="Print Heading" src="/assets/manual_erpnext_com/img/setup/print/print-heading-1.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/print-settings.md b/erpnext/docs/user/setting-up/print/print-settings.md
deleted file mode 100644
index 02170e1..0000000
--- a/erpnext/docs/user/setting-up/print/print-settings.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Print Settings
-
-In Print Settings you can set your default printing preferences like Paper Size, default text size, whether you want output as PDF or HTML etc.
-
-To edit print settings, go to:
-
-> Setup > Printing and Branding > Print Settings
-
-<img class="screenshot" alt="Print Settings" src="/assets/manual_erpnext_com/img/setup/print/print-settings.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/print/terms-and-conditions.md b/erpnext/docs/user/setting-up/print/terms-and-conditions.md
deleted file mode 100644
index 3a15d82..0000000
--- a/erpnext/docs/user/setting-up/print/terms-and-conditions.md
+++ /dev/null
@@ -1,25 +0,0 @@
-Terms and conditions are the general and special arrangements, provisions, requirements, rules, specifications, and standards that a company follows. These specifications are an integral part of an agreement or contract that the company gets into with its customers, suppliers or partners.
-
-### 1. Make a new Terms and Conditions
-
-To setup Terms and Condition master, go to:
-
-`Selling > Terms and Condition > New`
-
-<img class="screenshot" alt="Terms and Conditions" src="/assets/manual_erpnext_com/img/setup/print/terms-1.png">
-
-### 2. Editing in HTML
-
-Content of Terms and Condition can be formatted as per your preference, and also insert images where needed. If you have expertise in HTML, you will also find option to edit the content of Terms and Condition in HTML.
-
-<img class="screenshot" alt="Terms and Conditions, Edit HTML" src="/assets/manual_erpnext_com/img/setup/print/terms-2.png">
-
-This also allows you to use Terms and Condition master for footer, which otherwise is not availale in ERPNext as dedicated functionality. Since contents of Terms and Condition is always the last to appear in the print format, details of footer should be inserted at the end of the content, so that it actually appears as footer in the print format.
-
-### 3. Select in Transaction
-
-In transactions, you will find section of Terms and Condition where you will be able to search and fetched required Terms and Condition master.
-
-<img class="screenshot" alt="Terms and Conditions, Select in document" src="/assets/manual_erpnext_com/img/setup/print/terms-3.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setting-up-taxes.md b/erpnext/docs/user/setting-up/setting-up-taxes.md
deleted file mode 100644
index fefb786..0000000
--- a/erpnext/docs/user/setting-up/setting-up-taxes.md
+++ /dev/null
@@ -1,99 +0,0 @@
-One of the primary motivator for compulsory use of accounting tools is
-calculation of Taxes. You may or may not make money but your government will
-(to help your country be safe and prosperous). And if you don’t calculate your
-taxes correctly, they get very unhappy. Ok, philosophy aside, ERPNext allows
-you to make configurable tax templates that you can apply to your sales or
-purchase.
-
-### Tax Accounts
-
-For Tax Accounts that you want to use in the tax templates, you must go to
-Chart of Accounts and mention them as type “Tax” in your Chart of Item.
-
-## Item Tax
-
-If some of your Items require different tax rates as compared to others,
-mention them in the Item tax table. Even if you have selected your sales and
-purchase taxes as default tax rates, the system will pull the Item tax rate
-for calculations. Item tax will get preference over other sales or purchase
-taxes. However, if you wish to apply default sales and purchase taxes, do not
-mention item tax rates in the Item master. The system will then select the
-sales or purchase tax rate specified by you as default rates.
-
-Item Tax table can be found as a section within the Item Master document.
-
-<img class="screenshot" alt="Item Tax" src="/assets/manual_erpnext_com/img/taxes/item-tax.png">
-
-  * **Inclusive and Exclusive Tax**: ERPNext allows you to enter Item rates which are tax inclusive.
-
-<img class="screenshot" alt="Inclusive Tax" src="/assets/manual_erpnext_com/img/taxes/inclusive-tax.png">
-
-  * **Exception to the rule**: Item tax settings are required only if a particular Item has a different tax rate than the rate defined in the standard tax Account
-  * **Item tax is overwrite-able**: You can overwrite or change the item tax rate by going to the Item master in the Item tax table.
-
-## Sales Taxes and Charges Template
-
-You must usually collect taxes from your Customer and pay them to the
-government. At times, you may have to pay multiple taxes to multiple
-government bodies like local government, state or provincial and federal or
-central government.
-
-The way ERPNext sets up taxes is via templates. Other types of charges that
-may apply to your invoices (like shipping, insurance etc.) can also be
-configured as taxes.
-
-Select template and modify as per your need.
-
-To create a new sales tax template called Sales Taxes and Charges Template, you
-have to go to:
-
-> Setup > Accounts > Sales Taxes and Charge Master
-
-<img class="screenshot" alt="Sales Tax Master" src="/assets/manual_erpnext_com/img/taxes/sales-tax-master.png">
-
-When you create a new master, you will have to add a row for each tax type.
-
-The tax rate you define here will be the standard tax rate for all Items. If
-there are Items that have different rates, they must be added in the Item Tax
-table in the Item master.
-
-In each row, you have to mention:
-
-  * Calculation Type:
-
-    * On Net Total : This can be on net total (total amount without taxes).
-    * On Previous Row Total/Amount: You can apply taxes on previous row total / amount. If you select this option, the tax will be applied as a percentage of the previous row (in the tax table) amount or total. Previous row amount means a particular tax amount.And, previous row total means net total plus taxes applied up to that row. In the Enter Row Field, mention row number on which you want to apply the current tax. If you want to apply the tax on the 3rd row, mention "3" in the Enter Row field.
-
-    * Actual : Enter as per actual amount in rate column.
-
-  * Account Head: The Account ledger under which this tax will be booked
-
-  * Cost Center: If the tax / charge is an income (like shipping) it needs to be booked against - a Cost Center.
-  * Description: Description of the tax (that will be printed in invoices / quotes).
-  * Rate: Tax rate.
-  * Amount: Tax amount.
-  * Total: Cumulative total to this point.
-  * Enter Row: If based on "Previous Row Total" you can select the row number which will be taken as a base for this calculation (default is the previous row).
-  * Is this Tax included in Basic Rate?: If you check this, it means that this tax will not be shown below the item table, but will be included in the rate in your main item table. This is useful when you want to give a flat price (inclusive of all taxes) to your customers.
-
-Once you setup your template, you can select this in your sales transactions.
-
-## Purchase Taxes and Charges Template
-
-Similar to your Sales Taxes and Charges Template is the Purchase Taxes and
-Charges Master.
-
-This is the tax template that you can use in your Purchase Orders and Purchase
-Invoices. If you have value added taxes (VAT), where you pay to the government
-the difference between your incoming and outgoing taxes, you can select the
-same Account that you use for sales taxes.
-
-The columns in this table are similar to the Sales Taxes and Charges Template
-with the difference as follows:
-
-Consider Tax or Charge for: In this section you can specify if the tax /
-charge is only for valuation (not a part of total) or only for total (does not
-add value to the item) or for both.
-
-{next}
-
diff --git a/erpnext/docs/user/setting-up/settings/global-defaults.md b/erpnext/docs/user/setting-up/settings/global-defaults.md
deleted file mode 100644
index e1cced2..0000000
--- a/erpnext/docs/user/setting-up/settings/global-defaults.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Global Defaults
-
-You can set default values for your documents from Global Defaults
-
-> Setup > Settings > Global Defaults
-
-Whenever a new document is created, these values will be set as default.
-
-<img class="screenshot" alt="Global Defaults" src="/assets/manual_erpnext_com/img/setup/settings/global-defaults.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/settings/module-settings.md b/erpnext/docs/user/setting-up/settings/module-settings.md
deleted file mode 100644
index 81f10e5..0000000
--- a/erpnext/docs/user/setting-up/settings/module-settings.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Show or Hide Modules
-
-You can globally switch off certain desktop module via:
-
-> Setup > Settings > Show or Hide Modules
-
-For example if you are in the services business, you want to hide the Manufacturing Module, you can do this via **Show or Hide Modules**
-
-### Example
-
-Check / uncheck the items to show / hide.
-
-<img class="screenshot" alt="Module Settings" src="/assets/manual_erpnext_com/img/setup/settings/show-hide-modules.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/settings/naming-series.md b/erpnext/docs/user/setting-up/settings/naming-series.md
deleted file mode 100644
index d15404a..0000000
--- a/erpnext/docs/user/setting-up/settings/naming-series.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Naming Series
-
-### 1. Introduction
-
-Data records are broadly classified as “Master” or “Transaction”. A master
-record is a record that has a “name”, for example a Customer, Item, Supplier,
-Employee etc. A Transaction is a record that has a “number”. Examples of
-transactions include Sales Invoices, Quotations etc. You make transactions
-against a number of master records.
-
-ERPNext allows you to make prefixes to your transactions, with each prefix
-forming its own series. For example a series with prefix INV12 will have
-numbers INV120001, INV120002 and so on.
-
-You can have multiple series for all your transactions. It is common to have a
-separate series for each financial year. For example in Sales Invoice you
-could have:
-
-  * INV120001
-  * INV120002
-  * INV-A-120002
-
-etc. You could also have a separate series for each type of Customer or for
-each of your retail outlets.
-
-### 2. Managing Naming Series for Documents
-
-To setup a series, go to:
-
-> Setup > Tools > Update Numbering Series
-
-In this form,
-
-  1. Select the transaction for which you want to make the series The system will update the current series in the text box.
-  2. Edit the series as required with unique prefixes for each series. Each prefix must be on a new line.
-  3. The first prefix will be the default prefix. If you want the user to explicitly select a series instead of the default one, check the “User must always select” check box.
-
-You can also update the starting point of a series by entering the series
-name and the starting point in the “Update Series” section.
-
-### 3. Example
-
-See how to set the naming series
-
-<img class="screenshot" alt="Naming Series" src="/assets/manual_erpnext_com/img/setup/settings/naming-series.gif">
-
-{next}
-
diff --git a/erpnext/docs/user/setting-up/settings/system-settings.md b/erpnext/docs/user/setting-up/settings/system-settings.md
deleted file mode 100644
index ca594c8..0000000
--- a/erpnext/docs/user/setting-up/settings/system-settings.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# System Settings
-
-You can localize ERPNext to use particular timezone, date, number or currency format and also set global session expiry via System Settings.
-
-To open System Settings, go to:
-
-> Setup > Settings > System Settings
-
-<img class="screenshot" alt="System Settings" src="/assets/manual_erpnext_com/img/setup/settings/system-settings.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-1-language.md b/erpnext/docs/user/setting-up/setup-wizard/step-1-language.md
deleted file mode 100644
index 002e8bd..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-1-language.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Step 1: Language
-
-Select your language. ERPNext is available in more than 20 languages.
-
-<img alt="Language" class="screenshot" src="/assets/manual_erpnext_com/img/setup-wizard/step-1.png">
-
----
-
-Translations are contributed by the ERPNext Community. If you want to contribute, [please checkout the translator portal](https://translate.erpnext.com).
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-10-item.md b/erpnext/docs/user/setting-up/setup-wizard/step-10-item.md
deleted file mode 100644
index 34f5def..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-10-item.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Step 9: Item Names
-
-In this final step, please enter the names of the Items you buy or sell.
-
-<img alt="Add Items" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-10.png">
-
-Please set the group of the item (Product / Service) and unit of measure. Don't worry you will be able to edit all of this later.
-
----
-
-## Thats it!
-
-Once you are done with the setup wizard you will see the familiar desktop page.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-2-currency-and-timezone.md b/erpnext/docs/user/setting-up/setup-wizard/step-2-currency-and-timezone.md
deleted file mode 100644
index 932900f..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-2-currency-and-timezone.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Step 2: Currency and Timezone
-
-Set your country name, currency and timezone.
-
-<img alt="Currency" class="screenshot" src="/assets/manual_erpnext_com/img/setup-wizard/step-2.png">
-
----
-
-### Default Currency
-
-For most countries, your currency and timezone will be automatically set
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-3-user-details.md b/erpnext/docs/user/setting-up/setup-wizard/step-3-user-details.md
deleted file mode 100644
index b7bef77..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-3-user-details.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Step 3: User Details
-
-Enter Users Profile Details like Name, User ID and preferred password.
-
-<img alt="User" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-3.png">
-
----
-
-Note: Add your own photograph, not your company's
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-4-company-details.md b/erpnext/docs/user/setting-up/setup-wizard/step-4-company-details.md
deleted file mode 100644
index fc8ba55..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-4-company-details.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Step 4: Company Details
-
-Enter Company Details like Name, Abbreviation and Financial Year Details.
-
-<img alt="Company Details" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-4.png">
-
----
-
-### Company Abbreviation
-
-These will be appened to your **Account** Heads, for example if your abbreviation is **WP**, then your Sales account will be **Sales - WPL**
-
-For Example: East Wind will be abbreviated as EW. Shades of Green will be abbreviated as SOG. In case you wish to give your own abbreviation, you can do so. The text field allows any type of text.
-
-### Financial Year
-
-Any annual period at the end of which a firm's accounts are made up is called a Financial Year. Some countries have their account year starting from 1st January and some 1st April.
-
-The end date will be set automatically
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-5-letterhead-and-logo.md b/erpnext/docs/user/setting-up/setup-wizard/step-5-letterhead-and-logo.md
deleted file mode 100644
index 706552d..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-5-letterhead-and-logo.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Step 5: Letterhead and Logo
-
-Attach Company Letterhead and Company Logo.
-
-<img alt="Company Logo and Letterhead" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-5.png">
-
----
-
-### Letterhead
-
-A letterhead is the heading at the top of a sheet of letter paper (stationery). That heading usually consists of a name and an address, and a logo or corporate design.
-
-Click on the box ‘Attach Letterhead’ . Select the image file from the place it is stored and click enter.
-
-You may choose to skip this step if your letterhead is not ready.
-
-To select letterhead later through the setup module, read [Letter-head](/contents/setting-up/print/letter-head)
-
-#### To "attach as web-link"
-
-For any attachments in ERPNext, you can also attach as a web-link. If you are using other tools like Dropbox or Google Docs to manage your files, you can set its public link.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-6-add-users.md b/erpnext/docs/user/setting-up/setup-wizard/step-6-add-users.md
deleted file mode 100644
index 546bc5a..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-6-add-users.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Step 6: Add Users
-
-Add other users and assign them roles based on their job responsibilities.
-
-<img alt="Users" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-6.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-7-tax-details.md b/erpnext/docs/user/setting-up/setup-wizard/step-7-tax-details.md
deleted file mode 100644
index 0f8d7a1..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-7-tax-details.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Step 6: Tax Details
-
-Enter any three types of taxes which you regularly pay. This wizard will create a tax master which will calculate the taxes as per the tax-type.
-
-<img alt="Tax Details" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-7.png">
-
-Just set the tax name and the standard percentage levied.
-
----
-
-Some examples of tax types are given below.
-
-#### VAT
-
-A value added tax (VAT) is a form of consumption tax. From the perspective of the buyer, it is a tax on the purchase price. From that of the seller, it is a tax only on the value added to a product, material, or a service. From an accounting point of view, by the stage of its manufacture or distribution. The manufacturer remits to the government the difference between these two amounts, and retains the rest for themselves to offset the taxes they had previously paid on the inputs.
-
-The purpose of VAT is to generate tax revenues to the government similar to the corporate income tax or the personal income tax. For Example: When you shop at a departmental store and avail discount on the products, the store charges you 5% extra on the total bill as the VAT.
-
-To setup VAT in the setup wizard , simply enter the percentage amount levied by your government. To setup VAT at a later stage read [setting-up-taxes](/contents/setting-up/setting-up-taxes)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-8-customer-names.md b/erpnext/docs/user/setting-up/setup-wizard/step-8-customer-names.md
deleted file mode 100644
index b67c144..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-8-customer-names.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Step 7: Customers
-
-Enter your Customer names and the contact person from that organisation.
-
-
-<img alt="Customers" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-8.png">
-
----
-
-#### Difference between a customer name and a contact name
-
-A customer name is the name of the organisation and a contact name is the name of the user who is operating the ERPNext system.
-
-For Example: If American Power Mills is an organisation name and their founder Shiv Agarwal has installed ERPNext on his system. Then,
-
-Customer Name: American Power Mills
-
-Contact Name:  Shiv Agarwal
-
-To understand Customer in detail visit [Customer Details](/contents/CRM/customer)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/setup-wizard/step-9-suppliers.md b/erpnext/docs/user/setting-up/setup-wizard/step-9-suppliers.md
deleted file mode 100644
index 743a96b..0000000
--- a/erpnext/docs/user/setting-up/setup-wizard/step-9-suppliers.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Step 8: Suppliers
-
-Enter a few of your Suppliers' names.
-
-<img alt="Suppliers" class="screenshot"
-src="/assets/manual_erpnext_com/img/setup-wizard/step-9.png">
-
----
-
-To understand Suppliers in detail visit [Supplier Master](/contents/buying/supplier-master)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/sms-setting.md b/erpnext/docs/user/setting-up/sms-setting.md
deleted file mode 100644
index 113405e..0000000
--- a/erpnext/docs/user/setting-up/sms-setting.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# SMS Setting
-
-To integrate SMS in ERPNext, approach a SMS Gateway Provider who provides HTTP
-API. They will create an account for you and will provide an unique username
-and password.
-
-To configure SMS Settings in ERPNext, find out their HTTP API (a document
-which describes the method of accessing their SMS interface from 3rd party
-applications). In this document, you will get an URL which is used to send the
-SMS using HTTP request. Using this URL, you can configure SMS Settings in
-ERPNext.
-
-Example URL:  
-
-    
-    
-    http://instant.smses.com/web2sms.php?username=<USERNAME>&password;=<PASSWORD>&to;=<MOBILENUMBER>&sender;=<SENDERID>&message;=<MESSAGE>
-    
-
-![SMS Settings](/assets/manual_erpnext_com/old_images/erpnext/sms-setting2.jpg)
-
-> Note: the string up to the "?" is the SMS Gateway URL
-
-Example:
-
-    
-    
-    http://instant.smses.com/web2sms.php?username=abcd&password;=abcd&to;=9900XXXXXX&sender;
-    =DEMO&message;=THIS+IS+A+TEST+SMS
-
-The above URL will send SMS from account abcd to mobile number 9900XXXXXX with
-sender ID as DEMO with text message as "THIS IS A TEST SMS"
-
-Note that some parameters in the URL are static.You will get static values
-from your SMS Provider like username, password etc. These static values should
-be entered in the Static Parameters table.
-
-![SMS Setting](/assets/manual_erpnext_com/old_images/erpnext/sms-settings1.png)
-
-{next}
diff --git a/erpnext/docs/user/setting-up/stock-reconciliation-for-non-serialized-item.md b/erpnext/docs/user/setting-up/stock-reconciliation-for-non-serialized-item.md
deleted file mode 100644
index 5c4effe..0000000
--- a/erpnext/docs/user/setting-up/stock-reconciliation-for-non-serialized-item.md
+++ /dev/null
@@ -1,158 +0,0 @@
-Stock Reconciliation is the process of counting and evaluating stock-in-trade,
-usually at an organisations year end in order to value the total stock for
-preparation of the accounts. In this process actual physical stocks are
-checked and recorded in the system. The actual stocks and the stock in the system should be in agreement and accurate. If they are not, you can
-use the stock reconciliation tool to reconcile stock balance and value with actuals.
-
-**Difference between Serialized and Non-serialized Items.**
-
-A serial number is a unique, identifying number or group of numbers and
-letters assigned to an individual Item. Serialized items are generally high value items for which you need to warranty's and service agreements. Mostly items as machinery, equipments and high-value electronics (computers, printers etc.) are serialized.
-
-Non Serialized items are generally fast moving and low value item, hence doesn't need tracking for each unit. Items like screw, cotton waste, other consumables, stationary products can be categorized as non-serialized.
-
-> Stock Reconciliation option is available for the non serialized Items only. For seriazlized and batch items, you should create Material Receipt entry in Stock Entry form.
-
-### Opening Stocks
-
-You can upload your opening stock balance in the system using Stock Reconciliation.
-Stock Reconciliation will update your stock for a given Item on a given date
-for a given Warehouse to the given quantity.
-
-To perform Stock Reconciliation, go to:
-
-> Stock > Tools > Stock Reconciliation > New
-
-#### Step 1: Download Template
-
-A predefined template of an spreadsheet file should be followed for importing item's stock levels and valuations. Open new Stock Reconciliation form to see download option.
-
-<img class="screenshot" alt="Stock Reconciliation" src="/assets/manual_erpnext_com/img/setup/stock-recon-1.png">
-
-#### Step 2: Enter Data in csv file.
-
-![Stock Reco Data](/assets/manual_erpnext_com/old_images/erpnext/stock-reco-data.png)
-
-The csv format is case-sensitive. Do not edit the headers which are preset in the template. In the Item Code and Warehouse column, enter exact Item Code and Warehouse as created in your ERPNext account. For quatity, enter stock level you wish to set for that item, in a specific warehouse. If you do not want to change the quantity or valuation rate of an Item, you should leave it blank.
-
-Note: Make sure you do not put zero if you do not want to change the quantity
-amount or valuation amount. The system will calculate zero as zero quantity.
-So leave the field blank.
-
-#### **Step 3: Upload file and Enter Values in Stock Reconciliation Form
-
-<img class="screenshot" alt="Stock Reconciliation" src="/assets/manual_erpnext_com/img/setup/stock-recon-2.png">
-
-**Posting Date**
-
-Posting Date will be date when you want uploaded stock to reflect in the report. Posting Date selection option allows you making back dated stock reconcialiation as well.
-
-**Difference Account:**
-
-When making Stock Reconciliation for updating **opening balance**, then you should select Balance Sheet account. By default **Temporary Opening** is created in the chart of account which can be used here.
-
-If you are making Stock Reconciliation for **correcting stock level or valuation of an item**, then you can select any expense account in which you would want difference amount (derived from difference of valuation of item) should be booked. If Expense Account is selected as Difference Account, you will also need to select Cost Center as it is mandatory with any income and expense account selection.
-
-After reviewing saved Reconciliation Data, submit the Stock Reconciliation. On
-successful submission, the data will be updated in the system. To check the
-submitted data go to stock and view stock level report.
-
-Note: While filling the valuation rates of Items, if you wish to find out the
-valuation rates of all items, you can go to stock and click on Item Prices
-report. The report will show you all types of rates.
-
-#### Step 4: Review the reconciliation data
-
-![Stock Reco Review](/assets/manual_erpnext_com/old_images/erpnext/stock-reco-upload.png)
-
-### Stock Ledger Report
-
-![Stock Reco Ledger](/assets/manual_erpnext_com/old_images/erpnext/stock-reco-ledger.png)
-
-**How Stock Reconciliation Works**
-
-Stock Reconciliation on a specific date means balance quantity frozen for that item on reconciliation date, and shall not get affected due to stock entries made before its date.
-
-Example:
-
-Item Code: ABC001
-Warehouse: Mumbai
-Let's assume stock as on 10th January is 100 nos.
-Stock Reconciliation is made on 12th January to bring stock balance to 150 nos.
-Existing Stock Ledger:
-<html>
-<style>
-    td {
-    padding:5px 10px 5px 5px;
-    };
-    img {
-    align:center;
-    };
-	table, th, td {
-    border: 1px solid black;
-    border-collapse: collapse;
-	}
-</style>
- <table border="1" cellspacing="0px">
-            <tbody>
-                <tr align="center" bgcolor="#EEE">
-                    <td><b>Posting Date</b>
-                    </td>
-                    <td><b>Qty</b>
-                    </td>
-                    <td><b>Balance Qty</b>
-                    </td>
-                    <td><b>Voucher Type</b>
-                    </td>
-                </tr>
-                <tr>
-                    <td>10/01/2014</td>
-                    <td align="center">100</td>
-                    <td>100&nbsp;</td>
-                    <td>Purchase Receipt</td>
-                </tr>
-                <tr>
-                    <td>12/01/2014</td>
-                    <td align="center">50</td>
-                    <td>150</td>
-                    <td>Stock Reconciliation</td>
-                </tr>
-            </tbody>
-        </table>
-</html>
-Let's assume Purchase Receipt entry is made on 5th January, 2014, that is on date before Stock Reconciliation entry.
-<html>
-	<table border="1" cellspacing="0px">
-        <tbody>
-            <tr align="center" bgcolor="#EEE">
-                <td><b>Posting Date</b></td>
-                <td><b>Qty</b></td>
-                <td><b>Balance Qty</b></td>
-                <td><b>Voucher Type</b></td>
-            </tr>
-            <tr>
-                <td>05/01/2014</td>
-                <td align="center">20</td>
-                <td style="text-align: center;">20</td>
-                <td>Purchase Receipt</td>
-            </tr>
-            <tr>
-                <td>10/01/2014</td>
-                <td align="center">100</td>
-                <td style="text-align: center;">120</td>
-                <td>Purchase Receipt</td>
-            </tr>
-            <tr>
-                <td>12/01/2014</td>
-                <td align="center"><br></td>
-                <td style="text-align: center;"><b>150</b></td>
-                <td>Stock Reconciliation<br></td>
-            </tr>
-        </tbody>
-	</table>
-</html>
-As per the updated logic, irrespective of receipt/issue entry made for an item, balance quantity as set via Stock Reconciliation will not be affected.
-
-> Check out the video tutorial at https://www.youtube.com/watch?v=0yPgrtfeCTs
-
-{next}
diff --git a/erpnext/docs/user/setting-up/territory.md b/erpnext/docs/user/setting-up/territory.md
deleted file mode 100644
index 007542a..0000000
--- a/erpnext/docs/user/setting-up/territory.md
+++ /dev/null
@@ -1,10 +0,0 @@
-If your business operates in multiple Territories (could be countries, states
-or cities) it is usually a great idea to build your structure in the system.
-Once you group your Customers by Territories, you can set annual targets for
-each Item Group and get reports that will show your actual performance in the
-territory v/s what you had planned.
-You can also set different pricing for the same product sold across different territories.
-
-<img class="screenshot" alt="Territory Tree" src="/assets/manual_erpnext_com/img/crm/territory-tree.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/setting-up/third-party-backups.md b/erpnext/docs/user/setting-up/third-party-backups.md
deleted file mode 100644
index 0a93b36..0000000
--- a/erpnext/docs/user/setting-up/third-party-backups.md
+++ /dev/null
@@ -1,54 +0,0 @@
-If you wish to store your backups on a periodic basis,on Dropbox, you can do
-it directly through ERPNext.
-
-> Setup > Manage 3rd Party Backups
-
-__Step 1:__ Click on Setup.
-
-__Step 2:__ Click on Manage Third Party Backup
-
-#### Figure 1: Manage Third Party Backup
-
-![Third Party Backups](/assets/manual_erpnext_com/old_images/erpnext/third-party-backups.png)
-
-On the Backup Manager page, enter the email addresses of those people whom you
-wish to notify about the upload status. Under the topic 'Sync with Dropbox',
-select whether you wish to upload Daily, Weekly or Never. 
-
-__Step 3__ Click on **Allow Dropbox Access**.
-
-> Tip: In future, if you wish to discontinue uploading backups to dropbox,
-then select the Never option.
-
-#### Figure 2: Allow Dropbox Access
-
-![Backup Manager](/assets/manual_erpnext_com/old_images/erpnext/backup-manager.png)
-
-You need to login to your dropbox account, with your user id and password.
-
-![Dropbox Access](/assets/manual_erpnext_com/old_images/erpnext/dropbox-access.png)
-
-## Open Source Users
-
-Installing Pre-Requisites
-
-    
-    
-    pip install dropbox
-    pip install google-api-python-client
-    
-
-  
-
-#### Create an App in Dropbox
-
-First create your Dropbox account and create a new app (https://www.dropbox.com/developers/apps).
-After successful creation of account you will receive `app_key`, `app_secret` and `access_type`. Now edit `site_config.json` of your site (/frappe-bench/sites/your-site/) and add the following lines:
-- `"dropbox_access_key": "app_key",` and 
-- `"dropbox_secret_key": "app_secret"`
-
-Then you can go to the "Integrations" module and Allow Dropbox Access.
-
-> Note: Please ensure Allow Pop-ups are enabled in your browser.
-
-{next}
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/adding-users.md b/erpnext/docs/user/setting-up/users-and-permissions/adding-users.md
deleted file mode 100644
index a4201cd..0000000
--- a/erpnext/docs/user/setting-up/users-and-permissions/adding-users.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Adding Users
-
-Users can be added by the System Manager. If you are a System Manager, you can add Users via
-
-> Setup > User
-
-### 1. List of Users
-
-<img class="screenshot" src="/assets/manual_erpnext_com/img/setup/users/user-1.png" alt="User List">
-
-
-To add a new user, click on "New"
-
-### 2. Add the user details
-
-Add user details such as First Name, Last Name, Email etc.
-
-The user's Email will become the user id.
-
-After adding these details, save the user.
-
-### 3. Setting Roles
-
-After saving, you will see a list of roles and a checkbox next to it. Just check the roles you want the
-the user to have and save the document. To click on what permissions translate into roles, click on the role
-name.
-
-<img class="screenshot" src="/assets/manual_erpnext_com/img/setup/users/user-2.png" alt="User Roles">
-
-### 4. Setting Module Access
-
-Users will have access to all modules for which they have role based access. If you want to block certain modules for certain users, un-check the module from the list.
-
-<img class="screenshot" src="/assets/manual_erpnext_com/img/setup/users/user-3.png" alt="User Block Module">
-
-### 5. Security Settings
-
-If you wish to give the user access to the system only between office hours,
-or during weekends, mention it under security settings.
-
-<img class="screenshot" src="/assets/manual_erpnext_com/img/setup/users/user-4.png" alt="User Security">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/role-based-permissions.md b/erpnext/docs/user/setting-up/users-and-permissions/role-based-permissions.md
deleted file mode 100644
index bbbc4da..0000000
--- a/erpnext/docs/user/setting-up/users-and-permissions/role-based-permissions.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Role Based Permissions
-
-ERPNext has a role-based permission system. It means that you can assign Roles to Users, and set Permissions on Roles. The permission structure also allows you to define different permission rules for different fields, using a concept called **Permission "Level"** of a field. Once roles are assigned to a user, it gives you the ability to limit access for a user to only specific documents.
-
-To start with, go to:
-> Setup > Permissions > Role Permissions Manager
-
-<img alt="Manage Read, Write, Create, Submit, Amend access using the Role Permissions Manager" class="screenshot" src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-leave-application.png">
-
-Permissions are applied on a combination of:
-
-  * **Roles:** As we saw earlier, Users are assigned to Roles and it is on these Roles that permission rules are applied.
-
-  *Examples of Roles include Accounts Manager, Employee, HR User.*
-
-  * **Document Types:** Each type of document, master or transaction, has a separate list of Role based permissions.
-
-  *Examples of Document Types are Sales Invoice, Leave Application, Stock Entry, etc.*
-
-  * **Permission "Levels":** In each document, you can group fields by "levels". Each group of field is denoted by a unique number (0, 1, 2, 3, etc.). A separate set of permission rules can be applied to each field group. By default all fields are of level 0.
-
-    *Permission "Level" connects the group of fields with level X to a permission rule with level X.*
-
-  * **Document Stages:** Permissions are applied on each stage of the document like on Creation, Saving, Submission, Cancellation and Amendment. A role can be permitted to Print, Email, Import or Export data, access Reports, or define User Permissions.
-
-  * **Apply User Permissions:** This switch decides whether User Permissions should be applied for the role on selected Document Stages.
-
-	If enabled, a user with that role will be able to access only specific Documents for that Document Type. Such specific Document access is defined in the list of User Permissions. Additionally, User Permissions defined for other Document Types also get applied if they are related to the current Document Type through Link Fields.
-
-	To set, User Permissions go to:
-    > Setup > Permissions > [User Permissions Manager](/contents/setting-up/users-and-permissions/user-permissions)
-
----
-
-**To add a new rule**, click on "Add a New Rule" button and a pop-up box will ask you to select a Role and a Permission Level. Once you select this and click on "Add", this will add a new row to your rules table.
-
----
-
-Leave Application is a good **example** that encompasses all areas of Permission System.
-
-<img class="screenshot" alt="Leave Application Form should be created by an Employee, and approved by Leave Approver or HR User" src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-leave-application-form.png">
-
-   1. **It should be created by an Employee.**
-     For this, Employee Role should be given Read, Write, Create permissions.
-
-<img class="screenshot" alt="Giving Read, Write and Create Permissions to Employee for Leave Application"  src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-employee-role.png">
-
-   1. **An Employee should only be able to access his/her Leave Application.**
-     Hence, Apply User Permissions should be enabled for Employee Role, and a User Permission record should be created for each User Employee combination. (This effort is reduced for Employee Document Type, by programmatically creating User Permission records.)
-
-<img class="screenshot" alt="Limiting access to Leave Applications for a user with Employee Role via User Permissions Manager" src="/assets/manual_erpnext_com/old_images/erpnext/setting-up-permissions-employee-user-permissions.png">
-
-   1. **HR Manager should be able to see all Leave Applications.**
-     Create a Permission Rule for HR Manager at Level 0, with Read permissions. Apply User Permissions should be disabled.
-
-<img class="screenshot" alt="Giving Submit and Cancel permissions to HR Manager for Leave Applications. 'Apply User Permissions' is unchecked to give full access." src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-hr-manager-role.png">
-
-   2. **Leave Approver should be able to see and update Leave Applications applicable to him/her.**
-     Leave Approver is given Read and Write access at Level 0, with Apply User Permissions enabled. Relevant Employee Documents should be enlisted in the User Permissions of Leave Approvers. (This effort is reduced for Leave Approvers mentioned in Employee Documents, by programmatically creating User Permission records.)
-
-<img class="screenshot" alt="Giving Read, Write and Submit permissions to Leave Approver for Leave Applications.'Apply User Permissions' is checked to limit access based on Employee." src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-leave-approver-role.png">
-
-   3. **It should be Approved / Rejected only by HR User or Leave Approver.**
-     The Status field of Leave Application is set at Level 1. HR User and Leave Approver are given Read and Write permissions for Level 1, while everyone else (All) are given Read permission for Level 1.
-
-<img class="screenshot" alt="Limiting read access for a set of fields to certain Roles" src="/assets/manual_erpnext_com/old_images/erpnext/setting-up-permissions-level-1.png">
-
-
-   4. **HR User should be able to delegate Leave Applications to his/her subordinates**
-     HR User is given the right to Set User Permissions. A User with HR User role would be able to defined User Permissions on Leave Application for other users.
-
-<img class="screenshot" alt="Let HR User delegate access to Leave Applications by checking 'Set User Permissions'. This will allow HR User to access User Permissions Manager for 'Leave Application'" src="/assets/manual_erpnext_com/img/users-and-permissions/setting-up-permissions-hr-user-role.png">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/sharing.md b/erpnext/docs/user/setting-up/users-and-permissions/sharing.md
deleted file mode 100644
index 76b162e..0000000
--- a/erpnext/docs/user/setting-up/users-and-permissions/sharing.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Sharing
-
-In addition to user and role permissions, you can also Share a document with another user if you have sharing rights.
-
-To share a document, open the document, click on the "+" icon under sharing and select the user
-
-<img class="screenshot" src="/assets/manual_erpnext_com/img/setup/users/share.gif">
-
-{next}
diff --git a/erpnext/docs/user/setting-up/users-and-permissions/user-permissions.md b/erpnext/docs/user/setting-up/users-and-permissions/user-permissions.md
deleted file mode 100644
index 640c6f9..0000000
--- a/erpnext/docs/user/setting-up/users-and-permissions/user-permissions.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# User Permissions
-
-Limit access for a User to a set of documents using User Permissions Manager
-
-Role Base Permissions define the periphery of document types within which a user with a set of Roles can move around in. However, you can have an even finer control by defining User Permissions for a User. By setting specific documents in User Permissions list, you can limit access for that User to specific documents of a particular DocType, on the condition that "Apply User Permissions" is checked in Role Permissions Manager.
-
-To start with, go to:
-> Setup > Permissions > User Permissions Manager
-
-<figure>
-	<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-company.png"
-		class="img-responsive" alt="User Permissions Manager">
-	<figcaption>User Permissions Manager displaying how users can access only a specific Company.</figcaption>
-</figure>
-
-#### Example
-
-User 'aromn@example.com' has Sales User role and we want to limit the user to access records for only a specific Company 'Wind Power LLC'.
-
-  1. We add a User Permissions row for Company.
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permission-user-limited-by-company.png"
-			class="img-responsive" alt="User Permissions For Company">
-		<figcaption>Add User Permissions row for a combination of User 'aromn@example.com' and Company 'Wind Power LLC'.</figcaption>
-	</figure>
-
-  1. Also Role "All" has only Read permission for Company, with 'Apply User Permissions' checked.
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-company-role-all.png"
-			class="img-responsive" alt="Role Permissions for All on Company">
-		<figcaption>Read Permission with Apply User Permissions checked for DocType Company.</figcaption>
-	</figure>
-
-  1. The combined effect of the above two rules lead to User 'aromn@example.com' having only Read access to Company 'Wind Power LLC'.
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-company-wind-power-llc.png"
-			class="img-responsive" alt="Effect of Role and User Permissions on Company">
-		<figcaption>Access is limited to Company 'Wind Power LLC'.</figcaption>
-	</figure>
-
-  1. We want this User Permission on Company to get applied on other documents like Quotation, Sales Order, etc.
-These forms have a **Link Field based on Company**. As a result, User Permissions on Company also get applied on these documents, which leads to User 'aromn@example.com' to acces these documents having Company 'Wind Power LLC'.
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-quotation-sales-user.png"
-			class="img-responsive" alt="Sales User Role Permissions for Quotation">
-		<figcaption>Users with Sales User Role can Read, Write, Create, Submit and Cancel Quotations based on their User Permissions, since 'Apply User Permissions' is checked.</figcaption>
-	</figure>
-	<figure>
-		<img src="/assets/manual_erpnext_com/old_images/erpnext/user-permissions-quotation-list.png"
-			class="img-responsive" alt="Quotation List limited to results for Company 'Wind Power LLC'">
-		<figcaption>Quotation List is limited to results for Company 'Wind Power LLC' for User 'aromn@example.com'.</figcaption>
-	</figure>
-
-  1. User Permissions get applied automatically based on Link Fields, just like how it worked for Quotation. But, Lead Form has 4 Link fields: Territory, Company, Lead Owner and Next Contact By. Say, you want Leads to limit access to Users based only on Territory, even though you have defined User Permissions for DocTypes User, Territory and Company. You can do this by setting 'Ignore User Permissions' for Link fields: Company, Lead Owner and Next Contact By.
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-lead-role-permissions.png"
-			class="img-responsive" alt="Role Permissions on Lead for Sales User Role">
-		<figcaption>Sales User can Read, Write and Create Leads limited by User Permissions.</figcaption>
-	</figure>
-	<figure>
-		<img src="/assets/manual_erpnext_com/img/users-and-permissions/user-permissions-ignore-user-permissions.png"
-			class="img-responsive" alt="Set Ingore User Permissions from Setup > Customize > Customize Form">
-		<figcaption>Check 'Ingore User Permissions' for Company, Lead Owner and Next Contact By fields using Setup > Customize > Customize Form for Lead.</figcaption>
-	</figure>
-	<figure>
-		<img src="/assets/manual_erpnext_com/old_images/erpnext/user-permissions-lead-based-on-territory.png"
-			class="img-responsive" alt="Lead List is limited to records with Territory 'United States'">
-		<figcaption>Due to the effect of the above combination, User 'aromn@example.com' can only access Leads with Territory 'United States'.</figcaption>
-	</figure>
-
-{next}
-
diff --git a/erpnext/docs/user/setting-up/workflows.md b/erpnext/docs/user/setting-up/workflows.md
deleted file mode 100644
index 5ae4bae..0000000
--- a/erpnext/docs/user/setting-up/workflows.md
+++ /dev/null
@@ -1,66 +0,0 @@
-In order to allow multiple people to submit multiple requests, for approvals,
-by multiple users, ERPNext requires you to fill the workflow conditions.
-ERPNext tracks the multiple permissions before submission.
-
-Example of a leave application workflow is given below:
-
-If an user applies for a leave, then his request will be sent to the HR
-department. The HR department(HR User) will either reject or approve this
-request. Once this process is completed, the user's Manager(leave approver)
-will get an indication that the HR department has Accepted or Rejected. The
-Manager, who is the approving authority, will either Approve or Reject this
-request. Accordingly,the user will get his Approved or Rejected status.
-
-![Workflow](/assets/manual_erpnext_com/old_images/erpnext/workflow-leave-fl.jpg)
-
-To make this Workflow and transition rules go to :
-
-> Setup > Workflow > New Workflow
-
-#### Step 1: Enter the different states of Leave Approval Process.
-
-<img class="screenshot" alt="Workflow" src="/assets/manual_erpnext_com/img/setup/workflow-1.png">
-
-#### Step 2: Enter Transition Rules.
-
-<img class="screenshot" alt="Workflow" src="/assets/manual_erpnext_com/img/setup/workflow-2.png">
-
-#### Notes:
-
-> Note 1: When you make a workflow you essentially overwrite the code that is
-written for that document. Thus the document will function based on your
-workflow and not based on the pre-set code settings. Hence there might be no
-submit button / option if you have not specified it in the workflow.
-
-> Note 2: Document status of saved is 0, of submitted is 1, and of cancelled is
-2.
-
-> Note 3: A document cannot be cancelled unless it is submitted.
-
-> Note 4: If you wish to give the option to cancel, you will have to write a
-workflow transition step that says from submitted you can cancel.
-
-  
-
-#### Example of a Leave Application Process:  
-
-Go to the Human Resources Module and click on Leave Application. Apply for a
-Leave.
-
-When a Leave Application is submitted, the status on the right hand corner of
-the page shows as "Applied"
-
-![Workflow Employee LA](/assets/manual_erpnext_com/old_images/erpnext/workflow-employee-la.png)
-
-When the HR User logs in, he can either Approve or Reject. If approved the
-status on the right hand corner of the page shows as Approved. However, a blue
-band of information is displayed saying approval is pending by leave approver.
-
-![Leave Approver](/assets/manual_erpnext_com/old_images/erpnext/workflow-hr-user-la.png)
-
-When the leave approver opens the Leave Application page, he should select the
-status and convert to Approved or Rejected.
-
-![Workflow Leave Approver](/assets/manual_erpnext_com/old_images/erpnext/workflow-leave-approver-la.png)
-
-{next}
diff --git a/erpnext/docs/user/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md b/erpnext/docs/user/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md
deleted file mode 100644
index 0e64fce..0000000
--- a/erpnext/docs/user/stock/accounting-of-inventory-stock/migrate-to-perpetual-inventory.md
+++ /dev/null
@@ -1,38 +0,0 @@
-Existing Users, need to follow some steps to activate the new Perpetual
-Inventory system. As Perpetual Inventory always maintains a sync between stock
-and account balance, it is not possible to enable it with existing Warehouse
-setup. You have to create a whole new set of Warehouses, each linked to
-relevant account.
-
-Steps:
-
-  * Nullify the balance of account heads (stock-in-hand / fixed-asset) which you are using to maintain available stock value, through a Journal Entry.
-
-  * As existing warehouses are linked to stock transactions which does not have corresponding accounting entries, those warehouses can not be used for perpetual inventory. You have to create new warehouses for the future stock transactions which will be linked to their respective accounts. While creating new warehouses, select an account group under which the child account for the warehouse will be created.
-
-  * Setup the following default accounts for each Company 
-
-    * Stock Received But Not Billed
-    * Stock Adjustment Account
-    * Expenses Included In Valuation
-    * Cost Center
-  * Activate Perpetual Inventory
-
-> Setup > Accounts Settings > Make Accounting Entry For Every Stock Movement
-
-![Activation](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-1.png)  
-  
-
-  * Create Stock Entry (Material Transfer) to transfer available stock from existing warehouse to new warehouse. As stock will be available in the new warehouse, you should select the new warehouse for all the future transactions.
-
-System will not post any accounting entries for existing stock transactions
-submitted prior to the activation of Perpetual Inventory as those old
-warehouses will not be linked to any account. If you create any new
-transaction or modify/amend existing transactions, with old warehouse, there
-will be no corresponding accounting entries. You have to manually sync stock
-and account balance through Journal Entry.
-
-> Note: If you are already using old Perpetual Inventory system, it will be
-deactivated automatically. You need to follow the above steps to reactivate
-it.
-
diff --git a/erpnext/docs/user/stock/accounting-of-inventory-stock/perpetual-inventory.md b/erpnext/docs/user/stock/accounting-of-inventory-stock/perpetual-inventory.md
deleted file mode 100644
index 870bc98..0000000
--- a/erpnext/docs/user/stock/accounting-of-inventory-stock/perpetual-inventory.md
+++ /dev/null
@@ -1,371 +0,0 @@
-In perpetual inventory, system creates accounting entries for each stock
-transactions, so that stock and account balance will always remain same. The
-account balance will be posted against their respective account heads for each
-Warehouse. On saving of a Warehouse, the system will automatically create an
-account head with the same name as warehouse. As account balance is maintained
-for each Warehouse, you should create Warehouses, based on the type of items
-(Current / Fixed Assets) it stores.
-
-At the time of items received in a particular warehouse, the balance of asset
-account (linked to that warehouse) will be increased. Similarly when you
-deliver some items from that warehouse, an expense will be booked and the
-asset account will be reduced, based on the valuation amount of those items.
-
-## **Activation**
-
-  1. Setup the following default accounts for each Company 
-
-    * Stock Received But Not Billed
-    * Stock Adjustment Account
-    * Expenses Included In Valuation
-    * Cost Center
-  2. In perpetual inventory, the system will maintain seperate account balance for each warehouse under separate account head. To create that account head, enter "Create Account Under" in Warehouse master.
-
-  3. Activate Perpetual Inventory
-
-> Setup > Accounts Settings > Make Accounting Entry For Every Stock Movement
-
-* * *
-
-## **Example**
-
-Consider following Chart of Accounts and Warehouse setup for your company:
-
-#### Chart of Accounts
-
-  * Assets (Dr) 
-    * Current Assets
-    * Accounts Receivable 
-      * Jane Doe
-    * Stock Assets 
-      * Stores
-      * Finished Goods
-      * Work In Progress
-    * Tax Assets 
-      * VAT
-    * Fixed Assets
-    * Fixed Asset Warehouse
-  * Liabilities (Cr) 
-    * Current Liabilities
-    * Accounts Payable 
-      * East Wind Inc.
-    * Stock Liabilities 
-      * Stock Received But Not Billed
-    * Tax Liabilities 
-      * Service Tax
-  * Income (Cr) 
-    * Direct Income
-    * Sales Account
-  * Expenses (Dr) 
-    * Direct Expenses
-    * Stock Expenses 
-      * Cost of Goods Sold
-      * Expenses Included In Valuation
-      * Stock Adjustment
-      * Shipping Charges
-      * Customs Duty
-
-#### Warehouse - Account Configuration
-
-  * Stores
-  * Work In Progress
-  * Finished Goods
-  * Fixed Asset Warehouse
-
-### **Purchase Receipt**
-
-Suppose you have purchased _10 nos_ of item "RM0001" at _$200_ and _5 nos_ of
-item "Desktop" at **$100** from supplier "East Wind Inc". Following are the
-details of Purchase Receipt:
-
-**Supplier:** East Wind Inc.
-
-**Items:**
-
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Item</th>
-            <th>Warehouse</th>
-            <th>Qty</th>
-            <th>Rate</th>
-            <th>Amount</th>
-            <th>Valuation Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>RM0001</td>
-            <td>Stores</td>
-            <td>10</td>
-            <td>200</td>
-            <td>2000</td>
-            <td>2200</td>
-        </tr>
-        <tr>
-            <td>Desktop</td>
-            <td>Fixed Asset Warehouse</td>
-            <td>5</td>
-            <td>100</td>
-            <td>500</td>
-            <td>550</td>
-        </tr>
-    </tbody>
-</table>
-<p><strong>Taxes:</strong>
-</p>
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Account</th>
-            <th>Amount</th>
-            <th>Category</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>Shipping Charges</td>
-            <td>100</td>
-            <td>Total and Valuation</td>
-        </tr>
-        <tr>
-            <td>VAT</td>
-            <td>120</td>
-            <td>Total</td>
-        </tr>
-        <tr>
-            <td>Customs Duty</td>
-            <td>150</td>
-            <td>Valuation</td>
-        </tr>
-    </tbody>
-</table>
-<p><strong>Stock Ledger</strong>
-</p>
-
-![pr<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-2.png)
-
-**General Ledger**
-
-![pr<em>general</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-3.png)
-
-As stock balance increases through Purchase Receipt, "Store" and "Fixed Asset
-Warehouse" accounts are debited and a temporary account "Stock Receipt But Not
-Billed" account is credited, to maintain double entry accounting system. At the same time, negative expense is booked in account "Expense included in Valuation" for the amount added for valuation purpose, to avoid double expense booking.
-
-* * *
-
-### **Purchase Invoice**
-
-On receiving Bill from supplier, for the above Purchase Receipt, you will make
-Purchase Invoice for the same. The general ledger entries are as follows:
-
-**General Ledger**
-
-![pi<em>general</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-4.png)
-
-Here "Stock Received But Not Billed" account is debited and nullified the
-effect of Purchase Receipt.
-
-* * *
-
-### **Delivery Note**
-
-Lets say, you have an order from "Jane Doe" to deliver 5 nos of item "RM0001"
-at $300. Following are the details of Delivery Note:
-
-**Customer:** Jane Doe
-
-**Items:**
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Item</th>
-            <th>Warehouse</th>
-            <th>Qty</th>
-            <th>Rate</th>
-            <th>Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>RM0001</td>
-            <td>Stores</td>
-            <td>5</td>
-            <td>300</td>
-            <td>1500</td>
-        </tr>
-    </tbody>
-</table>
-<p><strong>Taxes:</strong>
-</p>
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Account</th>
-            <th>Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>Service Tax</td>
-            <td>150</td>
-        </tr>
-        <tr>
-            <td>VAT</td>
-            <td>100</td>
-        </tr>
-    </tbody>
-</table>
-
-**Stock Ledger**
-
-![dn<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-5.png)
-
-**General Ledger**
-
-![dn<em>general</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-6.png)
-
-As item is delivered from "Stores" warehouse, "Stores" account is credited and
-equal amount is debited to the expense account "Cost of Goods Sold". The
-debit/credit amount is equal to the total valuation amount (buying cost) of
-the selling items. And valuation amount is calculated based on your prefferred
-valuation method (FIFO / Moving Average) or actual cost of serialized items.
-
-    
-    
-        
-    In this example, we have considered valuation method as FIFO. 
-    Valuation Rate  = Purchase Rate + Charges Included in Valuation 
-                    = 200 + (250 * (2000 / 2500) / 10) 
-                    = 220
-    Total Valuation Amount  = 220 * 5 
-                            = 1100
-        
-    
-
-* * *
-
-### **Sales Invoice with Update Stock**
-
-Lets say, you did not make Delivery Note against the above order and instead
-you have made Sales Invoice directly, with "Update Stock" options. The details
-of the Sales Invoice are same as the above Delivery Note.
-
-**Stock Ledger**
-
-![si<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-7.png)
-
-**General Ledger**
-
-![si<em>general</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-8.png)
-
-Here, apart from normal account entries for invoice, "Stores" and "Cost of
-Goods Sold" accounts are also affected based on the valuation amount.
-
-* * *
-
-### **Stock Entry (Material Receipt)**
-
-**Items:**
-
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Item</th>
-            <th>Target Warehouse</th>
-            <th>Qty</th>
-            <th>Rate</th>
-            <th>Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>RM0001</td>
-            <td>Stores</td>
-            <td>50</td>
-            <td>220</td>
-            <td>11000</td>
-        </tr>
-    </tbody>
-</table>
-
-**Stock Ledger**
-
-![mr<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-9.png)
-
-**General Ledger**
-
-![mr<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-10.png)
-
-* * *
-
-### **Stock Entry (Material Issue)**
-
-**Items:**
-
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Item</th>
-            <th>Source Warehouse</th>
-            <th>Qty</th>
-            <th>Rate</th>
-            <th>Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>RM0001</td>
-            <td>Stores</td>
-            <td>10</td>
-            <td>220</td>
-            <td>2200</td>
-        </tr>
-    </tbody>
-</table>
-
-**Stock Ledger**
-
-![mi<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-11.png)
-
-**General Ledger**
-
-![mi<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-12.png)
-
-* * *
-
-### **Stock Entry (Material Transfer)**
-
-**Items:**
-
-<table class="table table-bordered">
-    <thead>
-        <tr>
-            <th>Item</th>
-            <th>Source Warehouse</th>
-            <th>Target Warehouse</th>
-            <th>Qty</th>
-            <th>Rate</th>
-            <th>Amount</th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>RM0001</td>
-            <td>Stores</td>
-            <td>Work In Progress</td>
-            <td>10</td>
-            <td>220</td>
-            <td>2200</td>
-        </tr>
-    </tbody>
-</table>
-
-**Stock Ledger**
-
-![mtn<em>stock</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-13.png)
-
-**General Ledger**
-
-![mtn<em>general</em>ledger](/assets/manual_erpnext_com/old_images/erpnext/accounting-for-stock-14.png)
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/batch.md b/erpnext/docs/user/stock/batch.md
deleted file mode 100644
index 20ff42d..0000000
--- a/erpnext/docs/user/stock/batch.md
+++ /dev/null
@@ -1,25 +0,0 @@
-Batch inventory feature in ERPNext allows you to group multiple units of an item, 
-and assign them a unique value/number/tag called Batch No.
-
-The practise of stocking based on batch is mainly followed in the pharmaceutical industry. 
-Medicines/drugs produced in a particular batched is assigned a unique id. 
-This helps them updating and tracking manufacturing and expiry date for all the units produced under specific batch.
-
-> Note: To set item as a batch item, "Has Batch No" field should be updated as Yes in the Item master.
-
-On every stock transaction (Purchase Receipt, Delivery Note, POS Invoice) made for batch item, 
-you should provide item's Batch No. To create new Batch No. master for an item, go to:
-
-> Stock > Setup > Batch > New
-
-Batch master is created before creation of Purchase Receipt. 
-Hence eveytime there is Purchase Receipt or Production entry being made for a batch item, 
-you will first create its Batch No, and then select it in Purcase order or Production Entry.
-
-<img class="screenshot" alt="batch" src="/assets/manual_erpnext_com/img/stock/batch.png">
-
-> Note: In stock transactions, Batch IDs will be filtered based on Item Code, Warehouse, 
-Batch Expiry Date (compared with Posting date of a transaction) and Actual Qty in Warehouse. 
-While searching for Batch ID  without value in Warehouse field, then Actual Qty filter won't be applied.
-
-{next}
diff --git a/erpnext/docs/user/stock/delivery-note.md b/erpnext/docs/user/stock/delivery-note.md
deleted file mode 100644
index c5c19d6..0000000
--- a/erpnext/docs/user/stock/delivery-note.md
+++ /dev/null
@@ -1,56 +0,0 @@
-A Delivery Note is made when a shipment is shipped from the company’s
-Warehouse.
-
-A copy of the Delivery Note is usually sent with the transporter. The Delivery
-Note contains the list of Items that are sent in the shipment and updates the
-inventory.
-
-The entry of the Delivery Note is very similar to a Purchase Receipt. You can
-create a new Delivery Note from:
-
-> Stock > Delivery Note > New
-
-or from a “Submitted” Sales Order (that is not already shipped) by clicking on
-“Make Delivery Note”.
-
-<img class="screenshot" alt="Delivery Note" src="/assets/manual_erpnext_com/img/stock/delivery-note.png">
-
-You can also “fetch” the details from an unshipped Sales Order.
-
-You will notice that all the information about unshipped Items and other
-details are carried over from your Sales Order.
-
-### Shipping Packets or Items with Product Bundle
-
-If you are shipping Items that have a [Product Bundle](/contents/selling/setup/sales-bom), ERPNext will automatically
-create a “Packing List” table for you based on the sub-Items in that Item.
-
-If your Items are serialized, then for Product Bundle type of Items, you will have
-to update the Serial Number in the “Packing List” table.
-
-### Packing Items in to Cases, for Container Shipment
-
-If you are doing container shipment or by weight, then you can use the Packing
-Slip to breakup your Delivery Note into smaller units. To make a Packing Slip
-go to:
-
-> Stock > Packing Slip > New Packing Slip
-
-You can create multiple Packing Slips for your Delivery Note and ERPNext will
-ensure that the quantities in the Packing Slip do not exceed the quantities in
-the Delivery Note.
-
-* * *
-
-#### Q. How to Print Without Amounts?
-
-If you want to print your Delivery Notes without the amount (this might be
-useful if you are shipping high value items), just check the “Print without
-Amount” box in the “More Info” section.
-
-#### What happens when the Delivery Note is “Submitted”?
-
-A Stock Ledger Entry is made for each Item and stock is updated. Pending
-Quantity in the Sales Order is updated (if applicable).
-
-{next}
diff --git a/erpnext/docs/user/stock/installation-note.md b/erpnext/docs/user/stock/installation-note.md
deleted file mode 100644
index 514f287..0000000
--- a/erpnext/docs/user/stock/installation-note.md
+++ /dev/null
@@ -1,5 +0,0 @@
-You can use installation note to record the instalation of a product having a serial number.
-
-<img class="screenshot" alt="Installation Note" src="/assets/manual_erpnext_com/img/stock/installation-note.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/item-price.md b/erpnext/docs/user/stock/item-price.md
deleted file mode 100644
index eea33ea..0000000
--- a/erpnext/docs/user/stock/item-price.md
+++ /dev/null
@@ -1,43 +0,0 @@
-Item Price is the record in which you can log sellig and buying rate of an item.
-
-There are two ways to reach to new Item Price form.
-
-> Selling/Buying/Stock >> Setup >> Item Price >> New Item Price
-
-Or
-
-> Item >> Add/Edit Prices >> Click on "+"  >> New Item Price
-
-Following are the steps to create new Item Price.
-
-Step 1: Select Price List
-
-You can create multiple Price List in ERPNext to track Selling and Buying Price List of an item separtely. Also if item's selling prices id changing based on territory, or due to other criteria, you can create multiple selling Price List for it.
-
-![Item Price list](/assets/manual_erpnext_com/old_images/erpnext/item-price-list.png)
-
-On selection of Price List, its currency and for selling or buying property will be fetched as well.
-
-To have Item Price fetching in the sales or purchase transaction, you should have Price List id selected in the transaction, just above Item table.
-
-Step 2: Select Item
-
-Select item for which Item Price record is to be created. On selection of Item Code, Item Name and Description will be fetched as well.
-
-![Item Price Item](/assets/manual_erpnext_com/old_images/erpnext/item-price-item.png)
-
-Step 3: Enter Rate
-
-Enter selling/buying rate of an item in Price List currency.
-
-![Item Price Rate](/assets/manual_erpnext_com/old_images/erpnext/item-price-rate.png)
-
-Step 4: Save Item Price
-
-To check all Item Price together, go to:
-
-Stock >> Main Report >> Itemwise Price List Rate
-
-You will find option to create new Item Price record (+) in this report as well.
-
-{next}
diff --git a/erpnext/docs/user/stock/item-valuation-fifo-and-moving-average.md b/erpnext/docs/user/stock/item-valuation-fifo-and-moving-average.md
deleted file mode 100644
index ef0a413..0000000
--- a/erpnext/docs/user/stock/item-valuation-fifo-and-moving-average.md
+++ /dev/null
@@ -1,28 +0,0 @@
-### How are Items Valued?
-
-One of the major features of any inventory system is that you can find out the
-value of any item based on its historic or average price. You can also find
-the value of all your items for your balance sheet.
-
-Valuation is important because:
-
-  * The buying price may fluctuate.
-  * The value may change because of some process (value add).
-  * The value may change because of decay, loss etc.
-
-You may encounter these terms, so lets clarify:
-
-  * Rate: Rate at which the transaction takes place.
-  * Valuation Rate: Rate at which the items value is set for your valuation.
-
-There are two major ways in which ERPNext values your items.
-
-  * **FIFO (First In First Out):** In this system, ERPNext assumes that you will consume / sell those Items first which you bought first. For example, if you buy an Item at price X and then after a few days at price Y, whenever you sell your Item, ERPNext will reduce the quantity of the Item priced at X first and then Y.
-
-![FIFO](/assets/manual_erpnext_com/old_images/erpnext/fifo.png)
-
-  * **Moving Average:** In this method, ERPNext assumes that the value of the item at any point is the average price of the units of that Item in stock. For example, if the value of an Item is X in a Warehouse with quantity Y and another quantity Y1 is added to the Warehouse at cost X1, the new value X2 would be:
-
-> New Value X2 = (X * Y + X1 * Y1) / (Y + Y1)
-
-{next}
diff --git a/erpnext/docs/user/stock/item/index.md b/erpnext/docs/user/stock/item/index.md
deleted file mode 100644
index 5db91e5..0000000
--- a/erpnext/docs/user/stock/item/index.md
+++ /dev/null
@@ -1,91 +0,0 @@
-An Item is your companys' product or a service. The term Item is applicable to your core products as well as your raw materials. It can be a product or service that you buy/sell from your customers/ suppliers. ERPNext allows you to manage all sorts of items like raw-materials, sub-assemblies, finished goods, item variants and service items.
-
-ERPNext is optimized for itemized management of your sales and purchase. If you are in services, you can create an Item for each services that your offer. Completing the Item Master is very essential for successful implementation of ERPNext.
-
-## Item Properties
-
-  * **Item Name:** Item name is the actual name of your product or service.
-  * **Item Code:** Item Code is a short-form to denote your Item. If you have very few Items, it is advisable to keep the Item Name and the Item Code same. This helps new users to recognise and update Item details in all transactions. In case you have lot of Items with long names and the list runs in hundreds, it is advisable to code. To understand naming Item codes see [Item Codification](/contents/stock/item/item-codification)
-  * **Item Group:** Item Group is used to categorize an Item under various criterias like products, raw materials, services, sub-assemblies, consumables or all Item groups. Create your default Item Group list under Setup> Item Group and pre-select the option while filling your New Item details under [Item Group](/contents/stock/setup/item-group)
-  * **Default Unit of Measure:** This is the default measuring unit that you will use for your product. It could be in nos, kgs, meters, etc. You can store all the UOM’s that your product will require under Set Up> Master Data > UOM. These can be preselected while filling New Item by using % sign to get a pop up of the UOM list.
-  * **Brand:** If you have more than one brand save them under Set Up> Master Data> Brand and pre-select them while filling a New Item.
-  * **Variant:** A Item Variant is a different version of a Item.To learn more about managing varaints see [Item Variants](/contents/stock/item/item-variants)
-  
-### Upload an Image
-
-To upload an image for your icon that will appear in all transactions, save
-the partially filled form. Only after your file is saved  the 'upload' button will
-work above the Image icon. Click on this sign and upload the image.
-
-### Inventory : Warehouse and Stock Setting
-
-In ERPNext, you can select different type of Warehouses to stock your
-different Items. This can be selected based on Item types. It could be Fixed
-Asset Item, Stock Item or even Manufacturing Item.
-
-  * **Stock Item:** If you are maintaining stock of this Item in your Inventory, ERPNext will make a stock ledger entry for each transaction of this item.
-  * **Default Warehouse:** This is the Warehouse that is automatically selected in your transactions. 
-  * **Allowance Percentage:** This is the percent by which you will be allowed to over-bill or over-deliver this Item. If not set, it will select from the Global Defaults. 
-  * **Valuation Method:** There are two options to maintain valuation of stock. FIFO (first in - first out) and Moving Average. To understand this topic in detail please visit “ Item Valuation, FIFO and Moving Average”.
-
-### Serialized and Batched Inventory
-
-These numbers help to track individual units or batches of Items which you sell. It also tracks warranty and returns. In case any individual Item is recalled by the supplier the number system helps to track individual Item. The numbering system also manages expiry dates. Please note that if you sell your items in thousands, and if the items are very small like pens or erasers, you need not serialize them. In ERPNext, you will have to mention the serial number in some accounting entries. To create serial numbers you will have to manually create all the numbers in your entries. If your product is not a big consumer durable Item, if it has no warranty and has no chances of being recalled, avoid giving serial numbers.
-
-> Important: Once you mark an item as serialized or batched or neither, you cannot change it after you have made any stock entry.
-
-  * [Discussion on Serialized Inventory](/contents/setting-up/stock-reconciliation-for-non-serialized-item)  
-
-### Re Ordering
-
-  * **Re-order level** suggests the amount of stock balance in the Warehouse. 
-  * **Re-order Qty** suggests the amount of stock to be ordered to maintain minimum stock levels.
-  * **Minimum Order Qty** is the minimum quantity for which a Material Request / Purchase Order must be made.
-
-### Item Tax
-
-These settings are required only if a particular Item has a different tax rate
-than the rate defined in the standard tax Account. For example, If you have a
-tax Account, “VAT 10%” and this particular Item is exempted from tax, then you
-select “VAT 10%” in the first column, and set “0” as the tax rate in the
-second column.
-
-Go to [Setting Up Taxes](/contents/setting-up/setting-up-taxes) to understand this topic in detail.
-
-### Inspection
-
-Inspection Required: If an incoming inspection (at the time of delivery from
-the Supplier) is mandatory for this Item, mention “Inspection Required” as
-“Yes”. The system will ensure that a Quality Inspection will be prepared and
-approved before a Purchase Receipt is submitted.
-
-Inspection Criteria: If a Quality Inspection is prepared for this Item, then
-this template of criteria will automatically be updated in the Quality
-Inspection table of the Quality Inspection. Examples of Criteria are: Weight,
-Length, Finish etc.
-
-### Purchase Details
-
-![Purchase Details](/assets/manual_erpnext_com/old_images/erpnext/item-purchase.png)
-
-**Lead time days:** Lead time days are the number of days required for the Item to reach the warehouse.
-
-**Default Expense Account:** It is the account in which cost of the Item will be debited.
-
-**Default Cost Centre:** It is used for tracking expense for this Item.
-
-### Sales Details
-
-![Sales Details](/assets/manual_erpnext_com/old_images/erpnext/item-sales.png)
-
-**Default Income Account:** Income account selected here will be fetched automatically in sales invoice for this item.
-
-**Cost Centre:** Cost center selected here will be fetched automatically in sales invoice for this item.
-
-### Manufacturing And Website
-
-![Manufacturing](/assets/manual_erpnext_com/old_images/erpnext/item-manufacturing-website.png)
-
-Visit [Manufacturing](/contents/manufacturing) and [Website ](/contents/website)to understand these topics in detail.
-
-{next}
diff --git a/erpnext/docs/user/stock/item/item-variants.md b/erpnext/docs/user/stock/item/item-variants.md
deleted file mode 100644
index 149e0b5..0000000
--- a/erpnext/docs/user/stock/item/item-variants.md
+++ /dev/null
@@ -1,24 +0,0 @@
-A Item Variant is a different version of a Item, such as differing sizes or differing colours.
-Without Item variants, you would have to treat the small, medium and large versions of a t-shirt as three separate Items; 
-Item variants let you treat the small, medium and large versions of a t-shirt as variations of the same Item.
-
-To use Item Variants in ERPNext, create an Item and check 'Has Variants'
-
-* The Item shall then be referred as a 'Template'
-
-<img class="screenshot" alt="Has Variants" src="/assets/manual_erpnext_com/img/stock/item-has-variants.png">
-
-On selecting 'Has Variants' a table shall appear. Specify the variant attributes for the Item in the table.
-In case the attribute has Numeric Values, you can specify the range and increment values here. 
-
-<img class="screenshot" alt="Valid Attributes" src="/assets/manual_erpnext_com/img/stock/item-attributes.png">
-
-> Note: You cannot make Transactions against a 'Template'
-
-To create 'Item Variants' against a 'Template' select 'Make Variants'
-
-<img class="screenshot" alt="Make Variants" src="/assets/manual_erpnext_com/img/stock/make-variant.png">
-
-<img class="screenshot" alt="Make Variants" src="/assets/manual_erpnext_com/img/stock/make-variant-1.png">
-
-To learn more about setting Attributes Master check [Item Attributes](/contents/stock/setup/item-attribute)
diff --git a/erpnext/docs/user/stock/item/purchase-details.md b/erpnext/docs/user/stock/item/purchase-details.md
deleted file mode 100644
index ce3cbd6..0000000
--- a/erpnext/docs/user/stock/item/purchase-details.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# purchase details
-
-# How Do I Track Warranty Status?
-
-To track a warranty period, it is necessary that the Item is a serialized Item.
-When this Item is delivered, the delivery date and the expiry period is saved in the serial number master. Through the serial number master you can track the warranty status.
-
-A warranty means a guarantee or a promise which provides assurance by one party to the other party which allows for a legal remedy if that promise is not true or followed. A warranty period is a time period in which a purchased product may be returned or exchanged.
-
-![Warranty](/assets/manual_erpnext_com/old_images/erpnext/faq-warranty.png)
-
-# How To Name A Manufacturer Part Number?
-
-Go to the purchase details section of the Item form, and enter the number on the right hand side in the field ‘Manufacturer Part Number’
-
-> Stock > Item
-
-A manufacturer part number is a series of numbers and /or letters that has been given to a part by the manufacturer. The manufacturer part number belongs to the manufacturer and helps distinguish the part from other manufacturers. If two parts come from different manufacturers, they will have different MPNs. This allows businesses to identify which company made the part.
-
-![Part No](/assets/manual_erpnext_com/old_images/erpnext/faq-manufacturer-part-no.png)
-
-__For Example:__ A refrigerator will have different parts which will have manufacturer part number. Thus, when any part fails and you want to replace it, you can simply order that part based on its part number.
diff --git a/erpnext/docs/user/stock/item/reorder.md b/erpnext/docs/user/stock/item/reorder.md
deleted file mode 100644
index 7ae57cf..0000000
--- a/erpnext/docs/user/stock/item/reorder.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Re-Order 
-
-# How To Setup Re-order Level?
-
-Go to the Re-order section of the Item form in the Stock module.
-
-> Stock > Item
-
-The Re-order level is the point at which stock on a particular item has diminished to a point where it needs to be replenished. To order based on Re-order level can avoid shortages. Re-order level can be determined based on the lead time and the average daily consumption.
-
-![Reorder Level](/assets/manual_erpnext_com/old_images/erpnext/faq-reorder-level.png)
-
-__For example:__ You can set your reorder level of bath towels at 10. When there are only 10 towels remaining in stock, the system will either send a mail or take action depending upon what you have selected in global settings.
-
-# How To Setup Reorder Quantity?
-
-To setup Reorder quantity, go to the Re-order section of the Item form. In the field ‘Re-order Qty’ type the amount that is needed.
-
-> Stock> Item
-
-Re-order quantity is the quantity to order, so that the sum of ordering cost and holding cost is at its minimum.The re-order quantity is based on the minimum order quantity specified by the supplier and many other factors.
-
-![Reorder Quantity](/assets/manual_erpnext_com/old_images/erpnext/faq-reorder-qty.png)
-
-__For example:__ If reorder level is 100 items, your reorder quantity may not necessarily be 100 items. The Reorder quantity can be greater than or equal to reorder level. It may depend upon lead time, discount, transportation and average daily consumption.
-
diff --git a/erpnext/docs/user/stock/material-request.md b/erpnext/docs/user/stock/material-request.md
deleted file mode 100644
index b886a0b..0000000
--- a/erpnext/docs/user/stock/material-request.md
+++ /dev/null
@@ -1,30 +0,0 @@
-A Material Request is a simple document identifying a requirement of a set of
-Items (products or services) for a particular reason.
-
-![Workflow](/assets/manual_erpnext_com/old_images/erpnext/material-request-workflow.jpg)
-
-To generate a Material Request manually go to:
-
-> Stock > Documents > Material Request > New
-
-#### Creating Material Request 
-
-<img class="screenshot" alt="Material Request" src="/assets/manual_erpnext_com/img/buying/material-request.png">
-
-A Material Request can be generated:
-
-  * Automatically from a Sales Order.
-  * Automatically when the Projected Quantity of an Item in stores reaches a particular level.
-  * Automatically from your Bill of Materials if you use Production Plan to plan your manufacturing activities.
-  * If your Items are inventory items, you must also mention the Warehouse where you expect these Items to be delivered. This helps to keep track of the [Projected Quantity](/contents/stock/projected-quantity) for this Item.
-
-A Material Request can be of type:
-
-* Purchase - If the request material is to be purchased.
-* Material Transfer - If the requested material is to be shifted from one warehouse to another.
-* Material Issue - If the requested material is to be Issued.
-
-> Info: Material Request is not mandatory. It is ideal if you have centralized
-buying so that you can collect this information from various departments.
-
-{next}
diff --git a/erpnext/docs/user/stock/projected-quantity.md b/erpnext/docs/user/stock/projected-quantity.md
deleted file mode 100644
index 0d7bd38..0000000
--- a/erpnext/docs/user/stock/projected-quantity.md
+++ /dev/null
@@ -1,26 +0,0 @@
-Projected Quantity is the level of stock that is predicted for a particular
-Item, based on the current stock levels and other requirements. It is the
-quantity of gross inventory that includes supply and demand in the past which
-is done as part of the planning process.
-
-The projected inventory is used by the planning system to monitor the reorder
-point and to determine the reorder quantity. The projected Quantity is used by
-the planning engine to monitor the safety stock levels. These levels are
-maintained to serve unexpected demands.
-
-Having a tight control of the projected inventory is crucial to determine
-shortages and to calculate the right order quantity.
-
-![Projected Quantity Stock Report](/assets/manual_erpnext_com/old_images/erpnext/projected-quantity-stock-report.png)
-
-
-> Projected Qty = Actual Qty + Planned Qty + Requested Qty + Ordered Qty -
-Reserved Qty
-
-  * Actual Qty: Quantity available in the warehouse.
-  * Planned Qty: Quantity, for which, Production Order has been raised, but is pending to be manufactured.
-  * Requested Qty: Quantity requested for purchase, but not ordered.
-  * Ordered Qty: Quantity ordered for purchase, but not received.
-  * Reserved Qty: Quantity ordered for sale, but not delivered.
-
-{next}
diff --git a/erpnext/docs/user/stock/purchase-receipt.md b/erpnext/docs/user/stock/purchase-receipt.md
deleted file mode 100644
index ff7c8ef..0000000
--- a/erpnext/docs/user/stock/purchase-receipt.md
+++ /dev/null
@@ -1,78 +0,0 @@
-Purchase Receipts are made when you accept material from your Supplier usually
-against a Purchase Order.
-
-You can also accept Purchase Receipts directly ( Set Purchase Order
-Required as “No” in Global Defaults).
-
-You can make a Purchase Receipt directly from:
-
-> Stock > Purchase Receipt > New Purchase Receipt
-
-or from a “Submitted” Purchase Order, by clicking on “Make Purchase Receipt”.
-
-<img class="screenshot" alt="Purchase Receipt" src="/assets/manual_erpnext_com/img/stock/purchase-receipt.png">
-
-### Rejections
-
-In the Purchase Receipt, you are required to enter whether all the materials
-you receive are of acceptable quality (in case you check). If you have any
-rejections, update the “Rejected Quantity” column in the Items table.
-
-If you reject, you are required to enter a “Rejected Warehouse” to indicate
-where you are storing the rejected Items.
-
-### Quality Inspections
-
-If for certain Items, it is mandatory to record Quality Inspections (if you
-have set it in your Item master), you will need to update the “Quality
-Inspection No” (QA No) column. The system will only allow you to “Submit” the
-Purchase Receipt if you update the “Quality Inspection No”.
-
-### UOM Conversions
-
-If your Purchase Order for an Item is in a different Unit of Measure (UOM)
-than what you stock (Stock UOM), then you will need to update the “UOM
-Conversion Factor”. 
-
-### Currency Conversions
-
-Since the incoming Item affects the value of your inventory, it is important
-to convert it into your base Currency, if you have ordered in another
-Currency. You will need to update the Currency Conversion Rate if applicable.
-
-### Taxes and Valuation
-
-Some of your taxes and charges may affect your Items value. For example, a Tax
-may not be added to your Item’s valuation, because if you sell the Item, you
-will have to add the tax at that time. So make sure to mark all your taxes in
-the Taxes and Charges table correctly for accurate valuation.
-
-### Serial Numbers and Batches
-
-If your Item is serialized or batched, you will have to enter Serial Number
-and Batch in the Item's table. You are allowed to enter multiple Serial Numbers
-in one row (each on a separate line) and you must enter the same number of
-Serial Numbers as the quantity. You must enter each Batch number on a separate
-line.
-
-* * *
-
-#### What happens when the Purchase Receipt is “Submitted”?
-
-A Stock Ledger Entry is created for each Item adding the Item in the Warehouse
-by the “Accepted Quantity” If you have rejections, a Stock Ledger Entry is
-made for each Rejection. The “Pending Quantity” is updated in the Purchase
-Order.
-
-* * *
-
-#### Adding value to your Items post Purchase Receipt:
-
-Some times, certain expenses that add value to your purchased Items are known
-only after a while. Common example is, if you are importing the Items, you
-will come to know of Customs Duty etc only when your “Clearing Agent” sends
-you a bill. If you want to attribute this cost to your purchased Items, you
-will have to use the Landed Cost Wizard. Why “Landed Cost”? Because it
-represents the charges that you paid when it landed in your possession.
-
-{next}
diff --git a/erpnext/docs/user/stock/purchase-return.md b/erpnext/docs/user/stock/purchase-return.md
deleted file mode 100644
index 1feb813..0000000
--- a/erpnext/docs/user/stock/purchase-return.md
+++ /dev/null
@@ -1,21 +0,0 @@
-ERPNext has an option for products that are need to be returned to the
-supplier. This may be on account of a number of reasons like defects in goods,
-quality not matching, the buyer not needing the stock, etc.
-
-You can create a Purchase Return by simply making a Purchase Receipt with negative quantity.
-
-First open the original Purchase Receipt, against which supplier delivered the items.
-
-<img class="screenshot" alt="Original Purchase Receipt" src="/assets/manual_erpnext_com/img/stock/purchase-return-original-purchase-receipt.png">
-
-Then click on "Make Purchase Return", it will open a new Purchase Receipt with "Is Return" checked, items and taxes with negative amount.
-
-<img class="screenshot" alt="Return Against Purchase Receipt" src="/assets/manual_erpnext_com/img/stock/purchase-return-against-purchase-receipt.png">
-
-On submission of Return Purchase Return, system will decrease item qty from the mentioned warehouse. To maintain correct stock valuation, stock balance will also go up according to the original purchase rate of the returned items.
-
-<img class="screenshot" alt="Return Stock Ledger" src="/assets/manual_erpnext_com/img/stock/purchase-return-stock-ledger.png">
-
-If Perpetual Inventory enabled, system will also post accounting entry against warehouse account to sync warehouse account balance with stock balance as per Stock Ledger.
-
-<img class="screenshot" alt="Return Stock Ledger" src="/assets/manual_erpnext_com/img/stock/purchase-return-general-ledger.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/sales-return.md b/erpnext/docs/user/stock/sales-return.md
deleted file mode 100644
index 83c7fbe..0000000
--- a/erpnext/docs/user/stock/sales-return.md
+++ /dev/null
@@ -1,27 +0,0 @@
-Goods sold being returned is quite a common practice in business. They could
-be returned by the customer on quality issues, non-delivery on agreed date, or
-any other reason. 
-
-In ERPNext, you can create a Sales Return by simply making a Delivery Note / Sales Invoice with negative quantity.
-
-First open the original Delivery Note / Sales Invoice, against which customer returned the items.
-
-<img class="screenshot" alt="Original Delivery Note" src="/assets/manual_erpnext_com/img/stock/sales-return-original-delivery-note.png">
-
-Then click on "Make Sales Return", it will open a new Delivery Note with "Is Return" checked, items and taxes with negative amount.
-
-<img class="screenshot" alt="Return Against Delivery Note" src="/assets/manual_erpnext_com/img/stock/sales-return-against-delivery-note.png">
-
-You can also create the return entry against original Sales Invoice, to return stock along with credit note, check "Update Stock" option in Return Sales Invoice.
-
-<img class="screenshot" alt="Return Against Sales Invoice" src="/assets/manual_erpnext_com/img/stock/sales-return-against-sales-invoice.png">
-
-On submission of Return Delivery Note / Sales Invoice, system will increase stock balance in the mentioned warehouse. To maintain correct stock valuation, stock balance will go up according to the original purchase rate of the returned items.
-
-<img class="screenshot" alt="Return Stock Ledger" src="/assets/manual_erpnext_com/img/stock/sales-return-stock-ledger.png">
-
-In case of Return Sales Invoice, Customer account will be credited and associated income and tax account will be debited.
-
-If Perpetual Inventory enabled, system will also post accounting entry against warehouse account to sync warehouse account balance with stock balance as per Stock Ledger.
-
-<img class="screenshot" alt="Return Stock Ledger" src="/assets/manual_erpnext_com/img/stock/sales-return-general-ledger.png">
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/serial-no.md b/erpnext/docs/user/stock/serial-no.md
deleted file mode 100644
index d714d25..0000000
--- a/erpnext/docs/user/stock/serial-no.md
+++ /dev/null
@@ -1,33 +0,0 @@
-As we discussed in the **Item** section, if an **Item** is _serialized_, a
-**Serial Number** (Serial No) record is maintained for each quantity of that
-**Item**. This information is helpful in tracking the location of the Serial
-No, its warranty and end-of-life (expiry) information.
-
-**Serial Nos** are also useful to maintain fixed assets. **Maintenance Schedules** can also be created against serial numbers for planning and scheduling maintenance activity for these assets (if they require maintenance).
-
-You can also track from which **Supplier** you purchased the **Serial No** and
-to which **Customer** you have sold it. The **Serial No** status will tell you
-its current inventory status.
-
-If your Item is _serialized_ you will have to enter the Serial Nos in the
-related column with each Serial No in a new line.
-You can maintain single units of serialized items using Serial Number.
-
-### Serial Nos and Inventory
-
-Inventory of an Item can only be affected if the Serial No is transacted via a
-Stock transaction (Stock Entry, Purchase Receipt, Delivery Note, Sales
-Invoice). When a new Serial No is created directly, its warehouse cannot be
-set.
-
-<img class="screenshot" alt="Serial Number" src="/assets/manual_erpnext_com/img/stock/serial-no.png">
-
-* The Status is set based on Stock Entry.
-
-* Only Serial Numbers with status 'Available' can be delivered.
-
-* Serial Nos can automatically be created from a Stock Entry or Purchase Receipt. If you mention Serial No in the Serial Nos column, it will automatically create those serial Nos.
-
-* If in the Item Master, the Serial No Series is mentioned, you can leave the Serial No column blank in a Stock Entry / Purchase Receipt and Serial Nos will automatically be set from that series.
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/setup/item-attribute.md b/erpnext/docs/user/stock/setup/item-attribute.md
deleted file mode 100644
index fc7ea2d..0000000
--- a/erpnext/docs/user/stock/setup/item-attribute.md
+++ /dev/null
@@ -1,16 +0,0 @@
-You can define Attributes and attribute values for your Item Variants here.
-
-<img class="screenshot" alt="Attribute Master" src="/assets/manual_erpnext_com/img/stock/item-attribute.png">
-
-#### Non Numeric Attributes
-
-* For Non Numeric Attributes, specify attributes values along with its abbreviation in the Attribute Value Table.
-
-<img class="screenshot" alt="Attribute Master" src="/assets/manual_erpnext_com/img/stock/item-attribute-non-numeric.png">
-
-#### Numeric Attributes
-
-* If your attribute is Numeric, select Numeric Values
-* Specify the Range and the Increment Value
-
-<img class="screenshot" alt="Attribute Master" src="/assets/manual_erpnext_com/img/stock/item-attribute-numeric.png">
diff --git a/erpnext/docs/user/stock/setup/item-group.md b/erpnext/docs/user/stock/setup/item-group.md
deleted file mode 100644
index 5a56ec1..0000000
--- a/erpnext/docs/user/stock/setup/item-group.md
+++ /dev/null
@@ -1,26 +0,0 @@
-Item Group is the classification category. Depending on the type of product,
-categorise it under its respective field. If the product is
-service oriented, name it under the group head - service. If the
-product is used as a raw-material, you have to name it under the Raw-material
-category. In case, your product is used only in trading, you can categorise it
-under Trading.
-
-<img class="screenshot" alt="Item Group Tree" src="/assets/manual_erpnext_com/img/stock/item-group-tree.png">
-
-### Create a Item Group
-
-* Select an Item Group under which you wish to create the group.
-
-* Select 'Add Child'
-
-<img class="screenshot" alt="Add Item Group" src="/assets/manual_erpnext_com/img/stock/item-group-new.gif">
-
-### Delete an Item Group
-
-* Select the Item Group you want to delete.
-
-* Select 'delete'
-
-<img class="screenshot" alt="Add Item Group" src="/assets/manual_erpnext_com/img/stock/item-group-del.gif">
-
-{next}
diff --git a/erpnext/docs/user/stock/setup/stock-settings.md b/erpnext/docs/user/stock/setup/stock-settings.md
deleted file mode 100644
index b2f7635..0000000
--- a/erpnext/docs/user/stock/setup/stock-settings.md
+++ /dev/null
@@ -1,5 +0,0 @@
-You can set default settings for your stock related transactions here.
-
-<img class="screenshot" alt="Stock Settings" src="/assets/manual_erpnext_com/img/stock/stock-settings.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/stock-entry.md b/erpnext/docs/user/stock/stock-entry.md
deleted file mode 100644
index 113163c..0000000
--- a/erpnext/docs/user/stock/stock-entry.md
+++ /dev/null
@@ -1,43 +0,0 @@
-A Stock Entry is a simple document that lets you record Item movement from a
-Warehouse, to a Warehouse and between Warehouses.
-
-To make a Stock Entry you have to go to:
-
-> Stock > Stock Entry > New
-
-<img class="screenshot" alt="Stock Entry" src="/assets/manual_erpnext_com/img/stock/stock-entry.png">
-
-Stock Entries can be made for the following purposes:
-
-* Material Issue - If the material is being issued. (Outgoing Material)
-* Material Receipt - If the material is being received. (Incoming Material)
-* Material Transfer - If the material is being moved from one warehouse to another.
-* Material Transfer for Manufacturing - If the material being transfered is for Manufacturing Process.
-* Manufacture - If the Material is being received from a Manufacturing/Production Operation.
-* Repack - If the Original item/items is being repacked into new item/items.
-* Subcontract - If the Material is being issued for a sub-contract activity.
-
-In the Stock Entry you have to update the Items table with all your
-transactions. For each row, you must enter a “Source Warehouse” or a “Target
-Warehouse” or both (if you are recording a movement).
-
-**Additional Costs:**
-
-If the stock entry is an incoming entry i.e any item is receiving at a target warehouse, you can add related additional costs (like Shipping Charges, Customs Duty, Operating Costs etc) assotiated with the process. The additional costs will be considered to calculate valuation rate of the items.
-
-To add additional costs, enter the description and amount of the cost in the Additional Costs table.
-
-<img class="screenshot" alt="Stock Entry Additional Costs" src="/assets/manual_erpnext_com/img/stock/additional-costs-table.png">
-
-The added additional costs will be distributed among the receiving items (where the target warehouse mentioned) proportionately based on Basic Amount of the items. And the distributed additional cost will be added to the basic rate of the item, to calculate valuation rate.
-
-<img class="screenshot" alt="Stock Entry Item Valuation Rate" src="/assets/manual_erpnext_com/img/stock/stock-entry-item-valuation-rate.png">
-
-If perpetual inventory system is enabled, additional costs will be booked in "Expense Included In Valuation" account.
-
-<img class="screenshot" alt="Additional Costs General Ledger" src="/assets/manual_erpnext_com/img/stock/additional-costs-general-ledger.png">
-
-
-> **Note:** To update Stock from a spreadsheet, see Stock Reconciliation.
-
-{next}
diff --git a/erpnext/docs/user/stock/tools/landed-cost-voucher.md b/erpnext/docs/user/stock/tools/landed-cost-voucher.md
deleted file mode 100644
index 211011a..0000000
--- a/erpnext/docs/user/stock/tools/landed-cost-voucher.md
+++ /dev/null
@@ -1,33 +0,0 @@
-Landed Cost is the total cost of a product to reach the product at the buyer’s door. Landed costs include the original cost of the item, complete shipping costs, customs duties, taxes, insurance and currency conversion fees etc. All of these components might not be applicable in every shipment, but relevant components must be considered as a part of the landed cost.
-
-> To understand landed cost better, let’s take an example based on our daily lives. You need to purchase a new washing machine for your home. Before making actual purchase, you probably do some investigation to know the best price. In this process, you often found a better deal from a store which is long away from your home. But you should also consider shipping cost while buying from that store. Total cost including transportation might be more than the price you get in your nearby store. In that case you will choose to buy from  your nearest store, as landed cost of the item is cheaper in the nearest store.
-
-Similarly in business, identifying landed cost for a item / product is very crucial, as it helps to decide selling cost of that item and impacts company’s profitability. Hence all applicable landed cost charges should be included in item’s valuation rate.
-
-According to the [Third-Party Logistics Study](http://www.3plstudy.com/), only 45% of the respondents stated that they use Landed Cost extensively. The main reasons of not using Landed Cost are unavailability of necessary data (49%), lack of right tools (48%), do not have sufficient time (31%) and not sure how to apply landed cost (27%).
-
-### Landed Cost via Purchase Receipt
-
-In ERPNext, you can add landed cost related charges in “Taxes and Charges” table while creating Purchase Receipt (PR). You should add those charges for “Total and Valuation” or “Valuation”. Charges which are payable to the same supplier from whom you are buying the items, should be tagged as “Total and Valuation”. Otherwise if applicable charges are payable to a 3rd party, it should be tagged as “Valuation”. On submission of PR, system will calculate landed cost of all items, considering those charges and that landed cost will be considered to calculate item’s valuation rate (based on FIFO / Moving Average method).
-
-But in reality, while making Purchase Receipt we might not know all the charges which are applicable for landed cost. Your transporter can send the invoice after 1 month, but there is no point in waiting for booking Purchase Receipt till then. Companies who imports their products / parts, pays a huge amount as Customs Duty. And generally they get invoices from Customs Department after a period of time. In these cases, “Landed Cost Voucher” becomes handy, as it allows you to add those additional charges on a later date, and to update landed cost of purchased items.
-
-### Landed Cost Voucher
-
-You can update landed cost any time in the future via Landed Cost Voucher.
-
-> Stock > Tools > Landed Cost Voucher
-
-In the document, you can select multiple Purchase Receipts and fetch all items from those Purchase Receipts. Then you should add applicable charges in “Taxes and Charges” table. You can easily delete an item if the added charges is not applicable to that item. The added charges are proportionately distributed among all the items based their amount.
-
-<img class="screenshot" alt="Landed Cost Vouher" src="/assets/manual_erpnext_com/img/stock/landed-cost.png">
-
-### What happend on submission?
-
-1. On submission of Landed Cost Voucher, the applicable landed cost charges are updated in Purchase Receipt Item table.
-
-2. Valuation Rate of items are recalculated based on new landed cost. 
-
-3. If you are using “Perpetual Inventory”, the system will post general ledger entries to correct Stock-in-Hand balance. It will debit (increase) corresponding “warehouse account” and credit (decrease) “Expense Included in Valuation” account. If items are already delivered, the Cost-of-Goods-Sold (CoGS) value has been booked as per old valuation rate. Hence, general ledger entries are reposted for all future outgoing entries of associated items, to correct CoGS value.
-
-{next}
diff --git a/erpnext/docs/user/stock/tools/packing-slip.md b/erpnext/docs/user/stock/tools/packing-slip.md
deleted file mode 100644
index c2b0c6b..0000000
--- a/erpnext/docs/user/stock/tools/packing-slip.md
+++ /dev/null
@@ -1,7 +0,0 @@
-A packing slip is a document listing the items in a shipment. Usually attached to the goods delivered.
-While Shipping a product 'Draft' for Delivery Notes are created.
-You can make a Packing Slip from these Delivery Notes (Draft)
-
-<img class="screenshot" alt="Packing Slip" src="/assets/manual_erpnext_com/img/stock/packing-slip.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/tools/quality-inspection.md b/erpnext/docs/user/stock/tools/quality-inspection.md
deleted file mode 100644
index f76c3f2..0000000
--- a/erpnext/docs/user/stock/tools/quality-inspection.md
+++ /dev/null
@@ -1,8 +0,0 @@
-In ERPNext, you can mark your incoming or outgoing products for Quality
-Inspection. To enable ERPNext to perform this function, go to :
-
-> Stock > Quality Inspection > New
-
-<img class="screenshot" alt="Quality Inspection" src="/assets/manual_erpnext_com/img/stock/quality-inspection.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/stock/tools/stock-uom-replace-utility.md b/erpnext/docs/user/stock/tools/stock-uom-replace-utility.md
deleted file mode 100644
index 9e96b36..0000000
--- a/erpnext/docs/user/stock/tools/stock-uom-replace-utility.md
+++ /dev/null
@@ -1,10 +0,0 @@
-#Stock UOM Replace Utility
-
-This tool will help you to change the UOM (Unit of measurement) of an existing Item.
-
-You need to select an Item, system fetches the Existing UOM of that item. You can then select the new UOM for that item 
-and specify the conversion factor.
-
-<img class="screenshot" alt="Stock Uom Replace" src="/assets/manual_erpnext_com/img/stock/uom-replace.png">
-
-{next}
diff --git a/erpnext/docs/user/stock/warehouse.md b/erpnext/docs/user/stock/warehouse.md
deleted file mode 100644
index 5ec786a..0000000
--- a/erpnext/docs/user/stock/warehouse.md
+++ /dev/null
@@ -1,38 +0,0 @@
-A warehouse is a commercial building for storage of goods. Warehouses are used
-by manufacturers, importers, exporters, wholesalers, transport businesses,
-customs, etc. They are usually large plain buildings in industrial areas of
-cities, towns, and villages. They mostly have loading docks to load and unload
-goods from trucks.
-
-To go to Warehouse, click on Stock and go to Warehouse under Masters.  You
-could also go to the Setup module and click on Warehouse under Master Data.
-
-> Stock > Warehouse > New Warehouse
-
-<img class="screenshot" alt="Warehouse" src="/assets/manual_erpnext_com/img/stock/warehouse.png">
-
-In ERPNext, every Warehouse must belong to a specific company, to maintain
-company wise stock balance. The Warehouses are saved with their respective
-company’s abbreviations. This facilitates in identifying which Warehouse
-belongs to which company, at a glance.
-
-You can include user restrictions for these Warehouses. In case you do not
-wish a particular user to operate on a particular Warehouse, you can refrain
-the user from accessing that Warehouse.
-
-### Merge Warehouse
-
-In day to day transactions, duplicate entries are done by mistake, resulting
-in duplicate Warehouses. Duplicate records can be merged into a single
-Warehouse. From the top bar of the system select the File menu. Select Rename
-and Enter the correct Warehouse and check the Merge button. The system will
-replace all the links of wrong Warehouse with the correct Warehouse, in all
-transactions. Also, the available quantity (actual qty, reserved qty, ordered
-qty etc) of all items in the duplicate warehouse will be transferred to the
-correct warehouse. Once merging is done, delete the duplicate Warehouse.
-
-> Note: ERPNext system maintains stock balance for every distinct combination
-of Item and Warehouse. Thus you can get stock balance for any specific Item in
-a particular Warehouse on any particular date.
-
-{next}
diff --git a/erpnext/docs/user/support/issue.md b/erpnext/docs/user/support/issue.md
deleted file mode 100644
index 2e84952..0000000
--- a/erpnext/docs/user/support/issue.md
+++ /dev/null
@@ -1,47 +0,0 @@
-Issue is an incoming query from your Customer, usually via email or
-from the “Contact” section of your website. (To fully integrate the Support
-Ticket to email, see the Email Settings section).
-
-> Tip: A dedicated support email id is a good way to integrate incoming
-queries via email. For example, you can send support queries to ERPNext at
-support@erpnext.com and it will automatically create a Issue in the
-Frappe system.
-
-
-
-> Support > Issue > New Issue
-
-<img class="screenshot" alt="Issue" src="/assets/manual_erpnext_com/img/support/issue.png">
-
-#### Discussion Thread
-
-When a new email is fetched from your mailbox, a new Issue record is
-created and an automatic reply is sent to the sender indicating the Support
-Ticket Number. The sender can send additional information to this email. All
-subsequent emails containing this Issue number in the subject will be
-added to this Issue thread. The sender can also add attachments to
-the email.
-
-Issue maintains all the emails which are sent back and forth against
-this issue in the system so that you can track what transpired between the
-sender and the person responding.
-
-#### Status
-
-When a new Issue is created, its status is “Open”, when it is
-replied, its status becomes “Waiting for Reply”. If the sender replies back
-its status again becomes “Open”.
-
-#### Closing
-
-You can either “Close” the Issue manually by clicking on “Close
-Ticket” in the toolbar or if its status is “Waiting For Reply” . If the sender
-does not reply in 7 days, then the Issue closes automatically.
-
-#### Allocation
-
-You can allocate the Issue by using the “Assign To” feature in the
-right sidebar. This will add a new To Do to the user and also send a message
-indicating that this Issue is allocated.
-
-{next}
diff --git a/erpnext/docs/user/support/maintenance-schedule.md b/erpnext/docs/user/support/maintenance-schedule.md
deleted file mode 100644
index 09cb460..0000000
--- a/erpnext/docs/user/support/maintenance-schedule.md
+++ /dev/null
@@ -1,31 +0,0 @@
-All machines require regular maintenance, specially those that contain a lot
-of moving parts, so if you are in the business of maintaining those or have
-some of them in your own premises, this is a useful tool to plan a calendar of
-activities for its maintenance.
-
-If the Customer Issue refers to “Breakdown Maintenance”, this refers to
-“Preventive Maintenance”.
-
-To create a new Maintenance Schedule go to:
-
-> Support > Maintenance Schedule > New Maintenance Schedule
-
-<img class="screenshot" alt="Maintenance Schedule" src="/assets/manual_erpnext_com/img/support/maintenance-schedule.png">
-
-In the Maintenance Schedule, there are two sections:
-
-In the first section, you select the Items for which you want to generate the
-schedule and set how frequently you want to plan a visit or a maintenance.
-These can be optionally fetched from a Sales Order. After selecting the Items,
-“Save” the record.
-
-The second section contains the maintenance activities planned in the
-schedule. “Generate Schedule” will generate a separate row for each
-maintenance activity.
-
-Each Item in a Maintenance Schedule is allocated to a Sales Person.
-
-When the document is “Submitted” Calendar events are created in the User of
-the Sales Person for each maintenance.
-
-{next}
diff --git a/erpnext/docs/user/support/maintenance-visit.md b/erpnext/docs/user/support/maintenance-visit.md
deleted file mode 100644
index f544ead..0000000
--- a/erpnext/docs/user/support/maintenance-visit.md
+++ /dev/null
@@ -1,17 +0,0 @@
-A Maintenance Visit is a record of a visit made by an engineer to a
-Customer’s premise usually against a Customer Issue. You can create a new
-Maintenance Visit from:
-
-> Support > Maintenance Visit > New Maintenance Visit
-
-<img class="screenshot" alt="Maintenance Visit" src="/assets/manual_erpnext_com/img/support/maintenance-visit.png">
-
-The Maintenance Visit contains information about the:
-
-  * Customer.
-  * The Items that were inspected / maintenance activity was carried out on.
-  * Details of actions taken.
-  * The person who carried out the actions.
-  * Feedback from the Customer.
-
-{next}
diff --git a/erpnext/docs/user/support/warranty-claim.md b/erpnext/docs/user/support/warranty-claim.md
deleted file mode 100644
index 4b2250a..0000000
--- a/erpnext/docs/user/support/warranty-claim.md
+++ /dev/null
@@ -1,23 +0,0 @@
-If you are selling **Items** under warranty or if you have sold and extended
-service contract like the Annual Maintenance Contract (AMC), your **Customer**
-may call you about an issue or a break-down and give you the Serial No of this
-Item.
-
-To record this, you can create a new **Warranty Claim** and add the
-**Customer** and **Item** / **Serial No**. The system will then automatically
-fetch the Serial No’s details and indicate whether this is under warranty or
-AMC.
-
-You must also add a description of the **Customer**’s issue and assign it to
-the person who needs to look into solving the issue.
-
-To create a new **Warranty Claim**:
-
-> Support > Warranty Claim > New Warranty Claim
-
-![Warranty Claim](/assets/manual_erpnext_com/img/support/warranty-claim.png)
-
-If a Customer visit is required to address the issue, you can create a new
-Maintenance Visit record from this.
-
-{next}
diff --git a/erpnext/docs/user/videos/index.md b/erpnext/docs/user/videos/index.md
new file mode 100644
index 0000000..c043c13
--- /dev/null
+++ b/erpnext/docs/user/videos/index.md
@@ -0,0 +1,35 @@
+# ERPNext Videos
+
+<h3>
+	<a class="no-decoration" href="/videos/learn">Learn ERPNext</a>
+</h3>
+
+<div class="row">
+    <div class="col-sm-4">
+        <a href="/videos/learn">
+            <img src="assets/img/videos/learn.jpg" class="img-responsive" style="margin-top: 0px;">
+        </a>
+    </div>
+    <div class="col-sm-8">
+        Learn how to setup and use ERPNext in this series of videos that go through important processes step-by-step.
+    </div>
+</div>
+
+---
+
+<h3>
+	<a class="no-decoration" href="https://conf.erpnext.com/2014/videos">Conference Vidoes</a>
+</h3>
+
+<div class="row">
+    <div class="col-sm-4">
+        <a href="https://conf.erpnext.com/2014/videos">
+            <img src="assets/img/videos/conf-2014.jpg" class="img-responsive" style="margin-top: 0px;">
+        </a>
+    </div>
+    <div class="col-sm-8">
+        Watch video presentations from the ERPNext team and users from the 2014 ERPNext Conference.
+        <br><br>
+		<a href="https://conf.erpnext.com">Join us at the ERPNext Conference on October 9th 2015 in Mumbai</a>
+    </div>
+</div>
diff --git a/erpnext/docs/user/videos/learn/batch-inventory.md b/erpnext/docs/user/videos/learn/batch-inventory.md
new file mode 100644
index 0000000..9bd9229
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/batch-inventory.md
@@ -0,0 +1,9 @@
+# Batch Inventory
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/J0QKl7ABPKM" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:46**
+
+Batch inventory allows you to group multiple units of an item, and assign them a unique value/number/tag called Batch No.
+
+This video walks you through creating new Batch, and using it in stock transactions. Each batch can have certain expiry. In the stock module, you can check item's batchwise stock level.
diff --git a/erpnext/docs/user/videos/learn/bill-of-materials.md b/erpnext/docs/user/videos/learn/bill-of-materials.md
new file mode 100644
index 0000000..42695d9
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/bill-of-materials.md
@@ -0,0 +1,9 @@
+# Bill of Material
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/hDV0c1OeWLo" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:27**
+
+The BOM is a list of all materials (either bought or made) and operations that go into a finished product or sub-Item.
+
+This video walks you through creating masters (like Item, Operations, Workstation etc.) required for setting up BOM. Once you have all these masters in place, using them you can create Bill of Materials for the sub-assembly, finished and sub-contracted items.
diff --git a/erpnext/docs/user/videos/learn/chart-of-accounts.md b/erpnext/docs/user/videos/learn/chart-of-accounts.md
new file mode 100644
index 0000000..f71013f
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/chart-of-accounts.md
@@ -0,0 +1,9 @@
+# Chart of Accounts
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/DyR-DST-PyA" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:26**
+
+This tutorial walks you through setting up Accounts in the Chart of Account master. This is the most crucial master for getting your financial statement and other accounting reports correct.
+
+Chart of Account is a tree structure master which allows user to define parent and child relationship between accounts. Also there are various account types (like Income a/c, Expense a/c, Bank a/c, Tax a/c etc.) which helps you segregate and filter out other accounts while creating transactions.
diff --git a/erpnext/docs/user/videos/learn/customer-and-supplier.md b/erpnext/docs/user/videos/learn/customer-and-supplier.md
new file mode 100644
index 0000000..ba0c5b8
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/customer-and-supplier.md
@@ -0,0 +1,7 @@
+# Customer and Supplier
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/anoGi_RpQ20" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:21**
+
+This video demonstrate creating Customer and Suppliers in ERPNext. It also covers setting up masters required for creating Customer and Supplier like Customer Group, Territory and Supplier Type.
diff --git a/erpnext/docs/user/videos/learn/data-import-tool.md b/erpnext/docs/user/videos/learn/data-import-tool.md
new file mode 100644
index 0000000..10cd00f
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/data-import-tool.md
@@ -0,0 +1,8 @@
+# Data Import Tool
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/6wiriRKPhmg" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:24**
+
+This video walks you through on importing data in ERPNext from spreadsheet files. This tools allows you in faster migration of masters and transactions from legacy system into ERPNext. You can also use this tool to export data from ERPNext, and keep it as a backup
+of specific document type.
diff --git a/erpnext/docs/user/videos/learn/email-account.md b/erpnext/docs/user/videos/learn/email-account.md
new file mode 100644
index 0000000..0ac4e98
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/email-account.md
@@ -0,0 +1,7 @@
+# Email Account
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/YFYe0DrB95o" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:27**
+
+This video walks you through setting up Email Account for incoming and outgoing emails. For hosted users, outgoing email gateway is set by default. Based on incoming email, you can have new document (like Issue, Lead etc.) auto-created, and have email received on these id's appended to specified document.
diff --git a/erpnext/docs/user/videos/learn/employee.md b/erpnext/docs/user/videos/learn/employee.md
new file mode 100644
index 0000000..e7f78a3
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/employee.md
@@ -0,0 +1,7 @@
+# Employee
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/USfIUdZlUhw" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 1:59**
+
+This video walks you through adding Employee in ERPNext.
diff --git a/erpnext/docs/user/videos/learn/expense-claim.md b/erpnext/docs/user/videos/learn/expense-claim.md
new file mode 100644
index 0000000..296a678
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/expense-claim.md
@@ -0,0 +1,7 @@
+# Expense Claim
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/5SZHJF--ZFY" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:51**
+
+This tutorial walks you through managing Expense Claims in ERPNext. Employee create first draft of Expense Claim. User with Expense Claim Approver role review Expense Claim submitted by Employee, and update sanctioned amount in it. After Expense Claim is approved/submitted, Journal Entry is created Expense Claim.
diff --git a/erpnext/docs/user/videos/learn/field-customization.md b/erpnext/docs/user/videos/learn/field-customization.md
new file mode 100644
index 0000000..36e2a9e
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/field-customization.md
@@ -0,0 +1,9 @@
+# Field Customization
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/pJhL9mmxV_U" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:10**
+
+This video walks you through various field level customization options.
+
+Using Customize Form tool, you can insert custom field in the forms. Also you can change the property of standard fields like visibility in print format, should field be a mandatory or non-mandatory, should this field always carry unique value etc. Also you can customize location of a field on form.
diff --git a/erpnext/docs/user/videos/learn/index.css b/erpnext/docs/user/videos/learn/index.css
new file mode 100644
index 0000000..025e938
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/index.css
@@ -0,0 +1,17 @@
+.hero-and-content .page-container {
+	max-width: 100%;
+}
+
+.video-list li {
+	margin: 0px;
+	padding: 10px 0px;
+	border-bottom: 1px solid #d1d8dd;
+}
+
+.video-list li:last-child {
+	border-bottom: 0px;
+}
+
+.manual-feedback {
+	display: none;
+}
diff --git a/erpnext/docs/user/videos/learn/index.html b/erpnext/docs/user/videos/learn/index.html
new file mode 100644
index 0000000..70343a2
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/index.html
@@ -0,0 +1,217 @@
+<!-- no-sidebar -->
+<!-- no-breadcrumbs -->
+<!-- title: Learn ERPNext -->
+<div style="max-width: 700px; margin: auto;">
+    <div class="row hero" style="padding-top: 50px; border-bottom: 0px;">
+        <div class="col-sm-12 hero-content">
+            <h1>ERPNext Video Tutorials</h1>
+            <p>Step-by-step guides to setting up and using ERPNext</p>
+        </div>
+    </div>
+    <br>
+    <h3>Using ERPNext</h3>
+    <ul class="list-unstyled video-list">
+        <li>
+            <a href="/videos/learn/navigation">
+              User Interface and Navigation</a>
+            <span class="text-muted pull-right">1:17</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Setting Up</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/setup-wizard">
+            The Setup Wizard</a>
+            <span class="text-muted pull-right">2:28</span>
+        </li>
+        <li><a href="/videos/learn/user-and-permission">
+            User and Permissions</a>
+            <span class="text-muted pull-right">4:20</span>
+        </li>
+        <li><a href="/videos/learn/data-import-tool">
+            Data Import Tool</a>
+            <span class="text-muted pull-right">3:24</span>
+    </li>
+        <li><a href="/videos/learn/printing-and-branding">
+            Printing and Branding</a>
+            <span class="text-muted pull-right">4:00</span>
+        </li>
+        <li><a href="/videos/learn/customer-and-supplier">
+            Customer and Supplier</a>
+            <span class="text-muted pull-right">3:21</span>
+        </li>
+        <li><a href="/videos/learn/item">
+            Item and Pricing</a>
+            <span class="text-muted pull-right">3:17</span>
+        </li>
+        <li><a href="/videos/learn/opening-stock">
+            Opening Stock</a>
+            <span class="text-muted pull-right">2:06</span>
+        </li>
+        <li><a href="/videos/learn/opening-account-balances">
+            Opening Account Balances</a>
+            <span class="text-muted pull-right">3:46</span>
+        </li>
+        <li><a href="/videos/learn/email-account">
+            Email Account</a>
+            <span class="text-muted pull-right">2:27</span>
+        </li>
+    </ul>
+    <br>
+    <h3>CRM and Sales</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/lead-to-quotation">
+            Lead to Quotation</a>
+            <span class="text-muted pull-right">2:00</span>
+        </li>
+        <li><a href="/videos/learn/sales-cycle">
+            Sales Order to Payment</a>
+              <span class="text-muted pull-right">4:28</span>
+        </li>
+        <li><a href="/videos/learn/product-bundle">
+            Product Bundle</a>
+            <span class="text-muted pull-right">2:31</span>
+        </li>
+        <li><a href="/videos/learn/newsletter">
+            Newsletter</a>
+            <span class="text-muted pull-right">2:04</span>
+        </li>
+        <li><a href="/videos/learn/taxes">
+            Taxes</a>
+            <span class="text-muted pull-right">3:00</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Buying</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/material-request-to-purchase-order">
+            Material Request to Purchase Order</a>
+            <span class="text-muted pull-right">2:25</span>
+        </li>
+        <li><a href="/videos/learn/purchase-cycle">
+            Purchase Order to Payment</a>
+              <span class="text-muted pull-right">3:16</span>
+        </li>
+        <li><a href="/videos/learn/taxes">
+            Taxes</a>
+            <span class="text-muted pull-right">3:00</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Stock</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/item">
+            Item and Pricing</a>
+            <span class="text-muted pull-right">3:17</span>
+        </li>
+        <li><a href="/videos/learn/item-variant">
+            Item Variant</a>
+            <span class="text-muted pull-right">2:38</span>
+        </li>
+        <li><a href="/videos/learn/opening-stock">
+            Opening Stock</a>
+            <span class="text-muted pull-right">2:06</span>
+        </li>
+        <li><a href="/videos/learn/stock-entries">
+            Stock Entries</a>
+              <span class="text-muted pull-right">3:46</span>
+        </li>
+        <li><a href="/videos/learn/serialized-inventory">
+            Seriralized Inventory</a>
+            <span class="text-muted pull-right">4:12</span>
+        </li>
+        <li><a href="/videos/learn/batch-inventory">
+            Batch Inventory</a>
+            <span class="text-muted pull-right">3:46</span>
+        </li>
+        <li><a href="/videos/learn/subcontracting">
+            Managing Subcontracting</a>
+            <span class="text-muted pull-right">4:37</span>
+        </li>
+        <li><a href="/videos/learn/quality-inspection">
+            Quality Inspection</a>
+            <span class="text-muted pull-right">2:36</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Accounts</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/chart-of-accounts">
+            Chart of Accounts</a>
+            <span class="text-muted pull-right">2:26</span>
+        </li>
+        <li><a href="/videos/learn/opening-account-balances">
+            Opening Account Balances</a>
+            <span class="text-muted pull-right">3:46</span>
+        </li>
+        <li><a href="/videos/learn/taxes">
+            Taxes</a>
+              <span class="text-muted pull-right">3:00</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Manufacturing</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/bill-of-materials">
+            Bill of Materials</a>
+            <span class="text-muted pull-right">3:27</span>
+        </li>
+        <li><a href="/videos/learn/production-planning">
+            Production Planning Tool</a>
+              <span class="text-muted pull-right">1:41</span>
+        </li>
+        <li><a href="/videos/learn/production-order">
+            Production Order</a>
+            <span class="text-muted pull-right">2:24</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Human Resource</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/employee">
+            Employee</a>
+            <span class="text-muted pull-right">1:59</span>
+        </li>
+        <li><a href="/videos/learn/processing-payroll">
+            Processing Payroll</a>
+              <span class="text-muted pull-right">4:00</span>
+        </li>
+        <li><a href="/videos/learn/leave-management">
+            Leave Management</a>
+            <span class="text-muted pull-right">2:50</span>
+        </li>
+        <li><a href="/videos/learn/expense-claim">
+            Expense Claim</a>
+            <span class="text-muted pull-right">2:52</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Retail</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/point-of-sale">
+            Point of Sale</a>
+            <span class="text-muted pull-right">2:34</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Project</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/project-and-task">
+            Project and Task</a>
+            <span class="text-muted pull-right">3:52</span>
+        </li>
+    </ul>
+    <br>
+    <h3>Customization</h3>
+    <ul class="list-unstyled video-list">
+        <li><a href="/videos/learn/field-customization">
+            Field Customization</a>
+            <span class="text-muted pull-right">3:10</span>
+        </li>
+        <li><a href="/videos/learn/workflow">
+            Workflow</a>
+            <span class="text-muted pull-right">3:38</span>
+        </li>
+    </ul>
+</div>
+<div style="height: 70px;"></div>
diff --git a/erpnext/docs/user/videos/learn/item-variant.md b/erpnext/docs/user/videos/learn/item-variant.md
new file mode 100644
index 0000000..c171b9d
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/item-variant.md
@@ -0,0 +1,7 @@
+# Item Variant
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/kogIricF40I" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:38**
+
+This video tutorial helps you in setting up Item Attributes (like Size, Lenthg etc.) and creating item variants using these attributes.
diff --git a/erpnext/docs/user/videos/learn/item.md b/erpnext/docs/user/videos/learn/item.md
new file mode 100644
index 0000000..79d5caf
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/item.md
@@ -0,0 +1,7 @@
+# Item and Pricing
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/qXaEwld4_Ps" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:17**
+
+This tutorial walks you through managing stock and service item in ERPNext. For each item, you can track its standard selling and buying price using Price List.
diff --git a/erpnext/docs/user/videos/learn/lead-to-quotation.md b/erpnext/docs/user/videos/learn/lead-to-quotation.md
new file mode 100644
index 0000000..dcfef68
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/lead-to-quotation.md
@@ -0,0 +1,8 @@
+# Lead to Quotation
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/TxYX4r4JAKA" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:00**
+
+This video walks you through creating Lead in the CRM module. You can convert Lead into Opportunity, one which has good probability of conversion. When customer ask for the Quotation,
+you can fetch Lead and item details from Opportunity to Quotation.
diff --git a/erpnext/docs/user/videos/learn/leave-management.md b/erpnext/docs/user/videos/learn/leave-management.md
new file mode 100644
index 0000000..d4f64b7
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/leave-management.md
@@ -0,0 +1,7 @@
+# Leave Management
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/fc0p_AXebc8" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:49**
+
+This tutorial walks you through leave processing in ERPNext. Firstly, various leaves are allocated to Employees for a year. As and when needed, Employees apply for leave. Their application is reviewed and approved or rejected by Leave Approver. On approval/submission of Leave Application, leave allocated to Employee is reduced.
diff --git a/erpnext/docs/user/videos/learn/material-request-to-purchase-order.md b/erpnext/docs/user/videos/learn/material-request-to-purchase-order.md
new file mode 100644
index 0000000..506a99a
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/material-request-to-purchase-order.md
@@ -0,0 +1,7 @@
+# Material Request to Purchase Order
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/4TN9kPyfIqM" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:25**
+
+This video walks you through creating Material Request. To request quotation from Supplier, you can forward Material Request to them. On receipt of quotation from supplier, Material Request's data will be fetched into Supplier Quotation. After evaluating multiple supplier quotations, favorable quotation's is converted into Purchase Order.
diff --git a/erpnext/docs/user/videos/learn/navigation.md b/erpnext/docs/user/videos/learn/navigation.md
new file mode 100644
index 0000000..40adb82
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/navigation.md
@@ -0,0 +1,7 @@
+# User Interface and Navigation
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/YDoI2DF4Lmc?list=PL3lFfCEoMxvxDHtYyQFJeUYkWzQpXwFM9" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 1:17**
+
+This video walks you through using the ERPNext "Desk" interface. The ERPNext User Interface is very web friendly and if you have used a website or mobile app before, the navigation should be very intuitive.
diff --git a/erpnext/docs/user/videos/learn/newsletter.md b/erpnext/docs/user/videos/learn/newsletter.md
new file mode 100644
index 0000000..9896309
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/newsletter.md
@@ -0,0 +1,9 @@
+# Newsletter
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/muLKsCrrDRo" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:04**
+
+A newsletter is a short written report that tells about the recent activities of an organization. It is generally sent to members of the organization, potential clients, customers or potential leads.
+
+This video walks you through managing Newsletter List, master containing email id's to whom Newsletter will be sent. You can compose Newsletter using rich text editor, and also in HTML editor.
diff --git a/erpnext/docs/user/videos/learn/opening-account-balances.md b/erpnext/docs/user/videos/learn/opening-account-balances.md
new file mode 100644
index 0000000..518b892
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/opening-account-balances.md
@@ -0,0 +1,7 @@
+# Opening Account Balances
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/kdgM20Q-q68" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:46**
+
+This video walks you through step to update opening account balances in ERPNext. Before updating opening balance for accounts, you should close your financial statements in the previous system. Closing balance of your legacy system should be updated as opening balance in ERPNext.
diff --git a/erpnext/docs/user/videos/learn/opening-stock.md b/erpnext/docs/user/videos/learn/opening-stock.md
new file mode 100644
index 0000000..9715b88
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/opening-stock.md
@@ -0,0 +1,9 @@
+# Opening Stock
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/0yPgrtfeCTs" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:06**
+
+This tutorial demonstrates updating opening stock balance of an item. Following same steps, you can also reconcile stock of an item with respect to physical stock in a warehouse.
+
+If you maintain serialized inventory, [click here](https://erpnext.com/manual/videos/learn/serialized-inventory) for the tutorial on updating it's opening stock in ERPNext.
diff --git a/erpnext/docs/user/videos/learn/point-of-sale.md b/erpnext/docs/user/videos/learn/point-of-sale.md
new file mode 100644
index 0000000..5f6f229
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/point-of-sale.md
@@ -0,0 +1,9 @@
+# Point of Sale
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/4WkelWkbP_c" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:34**
+
+Retail transaction has sales, goods delivery and payment happening at the same time. POS (Point of Sale) module in ERPNext allow you creating POS Invoices which manages all the functions involved in retail sales.
+
+This tutorial walks you through setting up POS profile and creating POS invoice in ERPNext. Each billing station can have separate POS profile. This allows in faster and efficient billing at the sales counters.
diff --git a/erpnext/docs/user/videos/learn/printing-and-branding.md b/erpnext/docs/user/videos/learn/printing-and-branding.md
new file mode 100644
index 0000000..555697d
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/printing-and-branding.md
@@ -0,0 +1,9 @@
+# Printing and Branding
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/cKZHcx1znMc" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:59**
+
+This video walks you through setting up of masters like your companies Letterhead and Logo.
+This tutorial also covers using tools to customize standard print formats, creating new print
+format, and setting up print headings (Quotation to Proposal) as per your requirement.
diff --git a/erpnext/docs/user/videos/learn/processing-payroll.md b/erpnext/docs/user/videos/learn/processing-payroll.md
new file mode 100644
index 0000000..e858ba6
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/processing-payroll.md
@@ -0,0 +1,7 @@
+# Processing Payroll
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/apgE-f25Rm0" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 4:00**
+
+This video walks you through processing payroll for Employees. You can maintain Salary Structure for each Employee. Based on it, you can create Salary Slips individually, or in bulk for all the Employees.
diff --git a/erpnext/docs/user/videos/learn/product-bundle.md b/erpnext/docs/user/videos/learn/product-bundle.md
new file mode 100644
index 0000000..c17456a
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/product-bundle.md
@@ -0,0 +1,9 @@
+# Product Bundle
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/yk3kPrRyRRc" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:31**
+
+Product Bundle (aka Sales Bill of Material) is a master where you can list items which are bundled together and sold as one item.
+
+This video walks you through setting up items, and creating Product Bundle master using them.
diff --git a/erpnext/docs/user/videos/learn/production-order.md b/erpnext/docs/user/videos/learn/production-order.md
new file mode 100644
index 0000000..dd2e30f
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/production-order.md
@@ -0,0 +1,9 @@
+# Production Order
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/ZotgLyp2YFY" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:24**
+
+Production Order (also called as Work Order) is a document that is given to the manufacturing shop floor by the Production Planner as a signal to produce a certain quantity of a certain Item.
+
+This video walks you through creating Production Order in ERPNext. There will be several entries made against Production Order (like Material Transfer, Manufacture entry, Time Log) to track progress against Production Order.
diff --git a/erpnext/docs/user/videos/learn/production-planning.md b/erpnext/docs/user/videos/learn/production-planning.md
new file mode 100644
index 0000000..6ed409b
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/production-planning.md
@@ -0,0 +1,9 @@
+# Production Planning Tool
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/CzatSl4zJ2Y" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 1:41**
+
+Production Planning Tool helps you plan production and purchase of Items for a period.
+
+This video walks you through production planning for Sales Order item. Material Planning allows you to check required quantity of raw materials for manufacturing. You can create Material Request for the raw-material items for which sufficient stock is not available. From Production Planning Tool, you can also create Production Order for the finished items.
diff --git a/erpnext/docs/user/videos/learn/project-and-task.md b/erpnext/docs/user/videos/learn/project-and-task.md
new file mode 100644
index 0000000..6be77db
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/project-and-task.md
@@ -0,0 +1,9 @@
+# Project and Task
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/egxIGwtoKI4" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:52**
+
+This is the tutorial on managing Projects and Task in ERPNext.
+
+Project can be divided into multiple assignable Task. Based on Tasks of a Project, you can check its Gantt Chart view. To track actual time spent on Project or Task, user can create Time Logs.
diff --git a/erpnext/docs/user/videos/learn/purchase-cycle.md b/erpnext/docs/user/videos/learn/purchase-cycle.md
new file mode 100644
index 0000000..acf7642
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/purchase-cycle.md
@@ -0,0 +1,7 @@
+# Purchase Cycle
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/EK65tLdVUDk" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:16**
+
+This video walks you through purchase cycle in ERPNext. Purchase Order can be created directly, or by fetching data from Material Request or Supplier Quotation. When ordered items are received from Supplier, Purchase Receipt is created against Purchase Order. You can create Purchase Invoice from Purchase Order or Purchase Receipt. When making payment to Supplier, Journal Entry will be created against Purchase Invoice.
diff --git a/erpnext/docs/user/videos/learn/quality-inspection.md b/erpnext/docs/user/videos/learn/quality-inspection.md
new file mode 100644
index 0000000..b00a1c0
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/quality-inspection.md
@@ -0,0 +1,7 @@
+# Quality Inspection
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/WmtcF3Y40Fs" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:36**
+
+This video walks you through quality testing and reporting procedure for purchased, manufactured and item which are being delivered.
diff --git a/erpnext/docs/user/videos/learn/sales-cycle.md b/erpnext/docs/user/videos/learn/sales-cycle.md
new file mode 100644
index 0000000..d9b8e13
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/sales-cycle.md
@@ -0,0 +1,9 @@
+# Sales Cycle
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/7AMq4lqkN4A" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 4:28**
+
+This video walks you through sales cycle in ERPNext. On receipt of confirmation of order from Customer, Sales Order will be directly. When sales items is shipped to customer, Delivery Note is created against Sales Order. You can create Sales Invoice from Sales Order or Delivery Note.
+
+From Sales Order, you can track complete order like %delivered, %billed and payment status of Sales Invoice.
diff --git a/erpnext/docs/user/videos/learn/serialized-inventory.md b/erpnext/docs/user/videos/learn/serialized-inventory.md
new file mode 100644
index 0000000..e3b97e1
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/serialized-inventory.md
@@ -0,0 +1,9 @@
+# Serialized Inventory
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/gvOVlEwFDAk" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 4:11**
+
+If an Item is serialized, a Serial Number (Serial No) record is maintained for each unit of that Item. This information is helpful in tracking the location of the Serial No, its warranty and end-of-life (expiry) information.
+
+This video walks you through setting item as serialized item, and creating stock transaction for it. Mostly a high value items are set as serialized item which requires close tracking of its location and warranty expiry.
diff --git a/erpnext/docs/user/videos/learn/setup-wizard.md b/erpnext/docs/user/videos/learn/setup-wizard.md
new file mode 100644
index 0000000..378cc32
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/setup-wizard.md
@@ -0,0 +1,8 @@
+# Setup Wizard
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/oIOf_zCFWKQ" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 2:28**
+
+After successful setup of ERPNext account, on the first login, you will see Setup Wizard. The Setup Wizard helps you quickly setup your masters like your company, Items, Customer,
+Suppliers and will also setup a basic website with this data.
diff --git a/erpnext/docs/user/videos/learn/stock-entries.md b/erpnext/docs/user/videos/learn/stock-entries.md
new file mode 100644
index 0000000..2d31ec9
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/stock-entries.md
@@ -0,0 +1,7 @@
+# Stock Entries
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/Njt107hlY3I" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:46**
+
+Stock Entry is a stock transaction, used for multiple purposes like inter-warehouse Material Transfer, Material Receipt for updating balance, Material Issue etc.
diff --git a/erpnext/docs/user/videos/learn/subcontracting.md b/erpnext/docs/user/videos/learn/subcontracting.md
new file mode 100644
index 0000000..331e892
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/subcontracting.md
@@ -0,0 +1,9 @@
+# Subcontracting
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/ThiMCC2DtKo" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 4:36**
+
+Subcontracting is a type of job contract that seeks to outsource certain types of work to other companies.
+
+There are warehouses masters created in order to carryout subcontracting transaction. This video walks you through various steps involved like creating BOM, transfer raw-material to subcontractor, receiving processed goods from subcontractor.
diff --git a/erpnext/docs/user/videos/learn/taxes.md b/erpnext/docs/user/videos/learn/taxes.md
new file mode 100644
index 0000000..992aa1d
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/taxes.md
@@ -0,0 +1,7 @@
+# Taxes
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/nQ1zZdPgdaQ" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:00**
+
+This video walks you through setting up tax accounts in the Chart of Account. Based on the taxation rules, you can create multiple sales and purchase tax templates in ERPNext.
diff --git a/erpnext/docs/user/videos/learn/user-and-permission.md b/erpnext/docs/user/videos/learn/user-and-permission.md
new file mode 100644
index 0000000..62d728d
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/user-and-permission.md
@@ -0,0 +1,7 @@
+# User and Permissions
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/fnBoRhBrwR4" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 4:20**
+
+This video tutorial walks you through setting up User and their permissions in ERPNext. Role Permission Manager tool allows you to define restricted access for the user, based on various criterion like, value in the specific field on the form, creator of the document etc.
diff --git a/erpnext/docs/user/videos/learn/workflow.md b/erpnext/docs/user/videos/learn/workflow.md
new file mode 100644
index 0000000..a0e0e21
--- /dev/null
+++ b/erpnext/docs/user/videos/learn/workflow.md
@@ -0,0 +1,9 @@
+# Workflow
+
+<iframe width="660" height="371" src="https://www.youtube.com/embed/yObJUg9FxFs" frameborder="0" allowfullscreen></iframe>
+
+**Duration: 3:37**
+
+This video walks you through setting up Workflow for a document type.
+
+Bydefault, ERPNext has two level verification system for documents, Save and Submit. If you have more than one authority approving document, you can manage it via Workflow. Workflow allow you do define multiple stages through which document will be review and finally get approved, and who will be the approver at each stage.
diff --git a/erpnext/docs/user/website/add-products-to-website.md b/erpnext/docs/user/website/add-products-to-website.md
deleted file mode 100644
index 66e27f4..0000000
--- a/erpnext/docs/user/website/add-products-to-website.md
+++ /dev/null
@@ -1,69 +0,0 @@
-### Add Products to the Website
-
-To list your Item on the Website, fill the Item details and save the file.
-Once the file is saved, a plus (+) button will appear next to the Image icon.
-Click on the plus button and add your Item image. The html code will be
-generated automatically.
-
-##### Step 1: Save Image
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage.png)
-
-  
-
-##### Step 2: Check the 'Show in Website' box.
-
-Under the Website section, please check the box that says 'show in Website'.
-Once the box is checked, the page will display other fields for entering
-information.
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage-1.png)
-
-  
-
-##### Step 3: Enter Website Details
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage-2.png)
-
-The page name will be generated automatically. Mention the Item-Group under
-which the Item will be displayed.
-
-#### Item Groups
-
-Mention the Item Group under this column. If you wish to list your Item under
-the broad category products, name your Item Group as Products. In case you
-have various varieties of Item and want to classify them under different
-names, make Item Groups with those names and check the box that says 'show in
-Website'. For Example, if you wish to create a category called 'Bags', create
-a Item Group named Bags.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-webimage-bags.png)
-
-Once the Item Group is created go to the Website Settings page under Website.
-Enter the Label, Url, and Parent Label.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-website-settings.png)
-
-  
-
-#### Webpage labels
-
-![Webpage](/assets/manual_erpnext_com/old_images/erpnext/webpage-labels.png)
-
-Add more Items under a particular Item Group.
-
-To add more Items under a certain Label, mention the Item Group on the Item
-Page. The Items will be added automatically on the Webpage, under the Item
-Group Label. For Example, To add Item-Kiddies Bag and Butterfly Print Bag,
-check the 'Show in Website'box. The Items will be placed under the Label Bags
-on the Webpage.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-websettings.png)
-
-  
-
-Item Group Display
-
-![Item Group Display](/assets/manual_erpnext_com/old_images/erpnext/webpage-itemgroup-display.png)
-
-{next}
diff --git a/erpnext/docs/user/website/blog-post.md b/erpnext/docs/user/website/blog-post.md
deleted file mode 100644
index 619c173..0000000
--- a/erpnext/docs/user/website/blog-post.md
+++ /dev/null
@@ -1,20 +0,0 @@
-Blogs are a great way to share your thoughts about your business and keep your
-customers and readers updated of what you are up to.
-
-In the age of internet, writing assumes a lot of significance because when
-people come to your website, they want to read about you and your product.
-
-To create a new blog, just create a new Blog from:
-
-> Website > Blog > New Blog
-
-<img class="screenshot" alt="Blog Post" src="/assets/manual_erpnext_com/img/website/blog-post.png">
-
-You can format a blog using the Markdown format.You can also access your blog
-by going to the page “blog.html”.
-
-#### A sample blog-page.
-
-<img class="screenshot" alt="Blog Sample" src="/assets/manual_erpnext_com/img/website/blog-sample.png">
-
-{next}
diff --git a/erpnext/docs/user/website/blogger.md b/erpnext/docs/user/website/blogger.md
deleted file mode 100644
index 1d6b40e..0000000
--- a/erpnext/docs/user/website/blogger.md
+++ /dev/null
@@ -1,6 +0,0 @@
-Blogger is a user who can post blogs. 
-You can mention a shori bio about the blogger and also set a avatar here.
-
-<img class="screenshot" alt="Blogger" src="/assets/manual_erpnext_com/img/website/blogger.png">
-
-{next}
\ No newline at end of file
diff --git a/erpnext/docs/user/website/product-listing-on-website.md b/erpnext/docs/user/website/product-listing-on-website.md
deleted file mode 100644
index cc5ca6d..0000000
--- a/erpnext/docs/user/website/product-listing-on-website.md
+++ /dev/null
@@ -1,68 +0,0 @@
-### Listing Item on Website
-
-To list your Item on the Website, fill the Item details and save the file.
-Once the file is saved, a plus (+) button will appear next to the Image icon.
-Click on the plus button and add your Item image. The html code will be
-generated automatically.
-
-##### Step 1: Save Image
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage.png)
-
-  
-
-##### Step 2: Check the 'Show in Website' box.
-
-Under the Website section, please check the box that says 'show in Website'.
-Once the box is checked, the page will display other fields for entering
-information.
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage-1.png)
-
-  
-
-##### Step 3: Enter Website Details
-
-![Webimage](/assets/manual_erpnext_com/old_images/erpnext/item-webimage-2.png)
-
-The page name will be generated automatically. Mention the Item-Group under
-which the Item will be displayed.
-
-#### Item Groups
-
-Mention the Item Group under this column. If you wish to list your Item under
-the broad category products, name your Item Group as Products. In case you
-have various varieties of Item and want to classify them under different
-names, make Item Groups with those names and check the box that says 'show in
-Website'. For Example, if you wish to create a category called 'Bags', create
-a Item Group named Bags.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-webimage-bags.png)
-
-Once the Item Group is created go to the Website Settings page under Website.
-Enter the Label, Url, and Parent Label.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-website-settings.png)
-
-  
-
-#### Webpage labels
-
-![Webpage](/assets/manual_erpnext_com/old_images/erpnext/webpage-labels.png)
-
-Add more Items under a particular Item Group.
-
-To add more Items under a certain Label, mention the Item Group on the Item
-Page. The Items will be added automatically on the Webpage, under the Item
-Group Label. For Example, To add Item-Kiddies Bag and Butterfly Print Bag,
-check the 'Show in Website'box. The Items will be placed under the Label Bags
-on the Webpage.
-
-![Item Group](/assets/manual_erpnext_com/old_images/erpnext/itemgroup-websettings.png)
-
-  
-
-Item Group Display
-
-![Item Group Display](/assets/manual_erpnext_com/old_images/erpnext/webpage-itemgroup-display.png)
-
diff --git a/erpnext/docs/user/website/setup/website-settings.md b/erpnext/docs/user/website/setup/website-settings.md
deleted file mode 100644
index 541d98a..0000000
--- a/erpnext/docs/user/website/setup/website-settings.md
+++ /dev/null
@@ -1,45 +0,0 @@
-Most of the website related settings can be defined here.
-
-<img class="screenshot" alt="Website Settings" src="/assets/manual_erpnext_com/img/website/website-settings.png">
-
-####Landing Page
-
-* Home Page: You can specify which [Web Page](/contents/website/web-page) must be the homepage of the website
-
-* Home Page is Products: if Checked, the Home page will be the default Item Group for the website.
-
-* Title Prefix: Set the browser title.
-
-####Website Theme
-
-Select the theme for the website. You can create new Theme for you website also.
-
-<img class="screenshot" alt="Website Theme" src="/assets/manual_erpnext_com/img/website/website-theme.png">
-
-* Select 'create new website theme' if you wish to customize the default website theme.
-
-####Banner
-
-You can add a banner/ logo to your website here. Attach the image and click on set banner from Image.
-An HTML code will be generated by the system under Banner HTML.
-
-<img class="screenshot" alt="Banner" src="/assets/manual_erpnext_com/img/website/banner.png">
-
-####Top Bar
-
-You can set the menus items in the Top Bar here.
-
-<img class="screenshot" alt="Top Bar" src="/assets/manual_erpnext_com/img/website/top-bar.png">
-
- * Similarlly you can also set sidebar and footer links.
- 
-####Integrations & Miscellaneous Settings
-
-You can integrate the website using Google Analytics and enable social media sharing for post shared on the website.
-
-<img class="screenshot" alt="Integrations" src="/assets/manual_erpnext_com/img/website/integrations.png">
-
-* You can disable public signup to your ERPNext account by checking 'disable signup'
-
-{next}
-
diff --git a/erpnext/docs/user/website/shopping-cart.md b/erpnext/docs/user/website/shopping-cart.md
deleted file mode 100644
index 20be819..0000000
--- a/erpnext/docs/user/website/shopping-cart.md
+++ /dev/null
@@ -1,41 +0,0 @@
-On the Webpage, a shopping cart is an icon that allows you to store all the
-things that you have earmarked for purchasing. It is a graphical
-representation of a shopping basket or a shopping cart that allows you to save
-the items you intend to buy.
-
-This software displays the price of the product . It also displays shipping
-and handling charges, along with taxes, if applicable.
-
-To set up a shopping cart, go to the selling module.
-
-> Selling > Shopping Cart Settings
-
-#### Step 1: Enter Company Details and Default Territory.
-
-![Shopping Cart](/assets/manual_erpnext_com/old_images/erpnext/shopping-cart-1.png)
-
-  
-
-#### Step 2: Enter Price List, Tax Master and Shipping Rule.
-
-![Shopping Cart](/assets/manual_erpnext_com/old_images/erpnext/shopping-cart-2.png)
-
-  
-
-#### Shopping Cart Display
-
-On the Website, the shopping cart image will be seen below the Item price.
-Customers can click on the cart and enter the amount of quantity they wish to
-buy. The Item number will be stored on the right hand corner of the page, next
-to the flower sign.
-
-![Shopping Cart](/assets/manual_erpnext_com/old_images/erpnext/shopping-cart-display-1.png)
-
-  
-
-Click on the flower sign on the right hand side to see the cart details. Click
-on the cart to get the final amount details.
-
-![Shopping Cart](/assets/manual_erpnext_com/old_images/erpnext/shopping-cart-display-amount.png)
-
-{next}
diff --git a/erpnext/docs/user/website/web-form.md b/erpnext/docs/user/website/web-form.md
deleted file mode 100644
index 3eb432a..0000000
--- a/erpnext/docs/user/website/web-form.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Web Forms
-
-<p class="lead">Add forms to the website that will add / update data in your tables. Allow users to edit / manage multiple web forms</p>
-
-You can add forms in your website for example, Contact Us, Inquiry, Complaint etc. Data from these can fill up records like Lead, Opportunity, Issue etc. The user can also be allowed manage multiple records (like Complaints etc.)
-
----
-
-### Creating
-
-To create a new **Web Form** go to:
-
-> Website > Web Form > New
-
-1. Set the Web Form title and url.
-1. Select the **DocType** in which you want the user to store the records.
-1. Select if you require the user to login, edit records, manage multiple records etc.
-1. Add the fields you want in the record.
-
-<img class="screenshot" alt="Web Form" src="/assets/manual_erpnext_com/img/website/web-form.png">
-
----
-
-### Viewing
-
-Once you create the web form, you can view it on the url and test it out!
-
-<img class="screenshot" alt="Web form" src="/assets/manual_erpnext_com/img/website/web-form-view.png">
-
----
-
-### Results
-
-Your data will be stored in the table you have selected
-
-{next}
diff --git a/erpnext/docs/user/website/web-page.md b/erpnext/docs/user/website/web-page.md
deleted file mode 100644
index 103b1cb..0000000
--- a/erpnext/docs/user/website/web-page.md
+++ /dev/null
@@ -1,32 +0,0 @@
-<p class="lead">Static Content like your Home Page, About Us, Contact Us, Terms pages can be created using the Web Page. </p>
-
-To create a new Web Page, go to:
-
-> Website > Web Page > New
-
-<img class="screenshot" alt="Web Page" src="/assets/manual_erpnext_com/img/website/web-page.png">
-
-#### Title
-
-The first thing to set is the title of your page. The title has the maximum
-weight for search engines so choose a title that reflects the keywords that
-you are targeting for your audience.
-
-#### Content
-
-After selecting your layout, you can add content (text, images, etc) to each
-of your content boxes. You can add content in Markdown or HTML format. Read
-the section on how to format using Markdown, for more details.
-
-#### Page Link
-
-The web link to your page will be the value of the “Page Name” field +
-“.html”. For example if your page name is contact-us, the web link of your
-page will be yoursite.com/contact-us.html.
-
-#### Images
-
-You can attach images to your web page and show them using the  HTML tag or
-using markdown format. the link to your file will be assets/manual_erpnext_com/old_images/erpnext/filename
-
-{next}