The same, also has some manuals for use in the ERPNext en, she prepared for the use of our staff.
Among them are:
Access Handbook: Covering the process of introducing the user on the desktop ERPNext.
Sales Handbook: Covering the process of creating and managing Prospectus, sales orders, quotations and so on.
Support Handbook: Covering the process of care and customer support.
Financial Handbook: (Under development) covering the use of the process of accounts.
We will be studying the availability of these manuals as a Github repository, and applicable license.
She is responsible for the documentation process using ERPNext and preparation of the Manuals, and now contribute to the translation, to enable the inclusion of printscreens with a good translation.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Thanks is awesome :) I was just beginning to resign myself to the fact that open source seems to be a one-way street!
Priya is our documentation expert https://github.com/fogueri and we have made quite some progress in the manual which we are publishing at erpnext.org
Our goal is to make erpnext.org the main (and community) site for ERPNext and keep erpnext.com for cloud hosting (our bread and butter).
Right now erpnext.org is just static pages hosted on GitHub Pages, but we want to make this into a full ERPNext instance so that we (and anyone from the community) can easily manage web pages, add blog posts etc using the Website module.
I would suggest you can add / edit / update your manuals directly in the erpnext repository at the moment by sending pull request to:
The same, also has some manuals for use in the ERPNext en, she prepared for the use of our staff.
Among them are:
Access Handbook: Covering the process of introducing the user on the desktop ERPNext.
Sales Handbook: Covering the process of creating and managing Prospectus, sales orders, quotations and so on.
Support Handbook: Covering the process of care and customer support.
Financial Handbook: (Under development) covering the use of the process of accounts.
We will be studying the availability of these manuals as a Github repository, and applicable license.
She is responsible for the documentation process using ERPNext and preparation of the Manuals, and now contribute to the translation, to enable the inclusion of printscreens with a good translation.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
The
questions are related precisely to maintain, updates, documentation,
manuals, getting started guides and resources ERPNext focused on local
issues (for each country), but in such a way that it can be part of the
product ERPNext.
We would like very much to contribute more actively to ERPNext, however, have small problems like:
- Work overload
- We are under the law (idiots) in Brazil
-
We have to fight every day to keep ERPNext (as you mentioned in the
first version of the manual ERPNext - We must be champions)
Today,
we have a very high workload to keep ERPNext just a company, we are 3
developers, and we are fighting to show that ERPNext is the best way to
Perform Group, the company that we used, and we're only 3 to surportar 13 establishments.
I'm fighting against myself, because I am fighting a war to replace the first ERP company that I developed.
Currently
our manuals are in Google Docs, but soon will migrate this to Markdown,
enabling their inclusion in ERPNext, our focus is on the use of manual,
covering every step in detail.
Therefore,
we take care to present including what each feature is built of ERPNext
because here people do not have the habit of thinking outside the box,
and try to figure out on your own how things work or serving something.
...
Thanks is awesome :) I was just beginning to resign myself to the fact that open source seems to be a one-way street!
Priya is our documentation expert https://github.com/fogueri and we have made quite some progress in the manual which we are publishing at erpnext.org
Our goal is to make erpnext.org the main (and community) site for ERPNext and keep erpnext.com for cloud hosting (our bread and butter).
Right now erpnext.org is just static pages hosted on GitHub Pages, but we want to make this into a full ERPNext instance so that we (and anyone from the community) can easily manage web pages, add blog posts etc using the Website module.
I would suggest you can add / edit / update your manuals directly in the erpnext repository at the moment by sending pull request to:
The same, also has some manuals for use in the ERPNext en, she prepared for the use of our staff.
Among them are:
Access Handbook: Covering the process of introducing the user on the desktop ERPNext.
Sales Handbook: Covering the process of creating and managing Prospectus, sales orders, quotations and so on.
Support Handbook: Covering the process of care and customer support.
Financial Handbook: (Under development) covering the use of the process of accounts.
We will be studying the availability of these manuals as a Github repository, and applicable license.
She is responsible for the documentation process using ERPNext and preparation of the Manuals, and now contribute to the translation, to enable the inclusion of printscreens with a good translation.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Amazing to see that you have supported 13 estabilishments! It might help just to document your experience so that it can motivate other users. Good luck with your struggles - It will really take ERPNext to a next level to have an experienced developer like yourself.
Replying to your other issues via GitHub.
best,
Rushabh
ps. Happy to note the "Champions" page was actually read :)
The
questions are related precisely to maintain, updates, documentation,
manuals, getting started guides and resources ERPNext focused on local
issues (for each country), but in such a way that it can be part of the
product ERPNext.
We would like very much to contribute more actively to ERPNext, however, have small problems like:
- Work overload
- We are under the law (idiots) in Brazil
-
We have to fight every day to keep ERPNext (as you mentioned in the
first version of the manual ERPNext - We must be champions)
Today,
we have a very high workload to keep ERPNext just a company, we are 3
developers, and we are fighting to show that ERPNext is the best way to
Perform Group, the company that we used, and we're only 3 to surportar 13 establishments.
I'm fighting against myself, because I am fighting a war to replace the first ERP company that I developed.
Currently
our manuals are in Google Docs, but soon will migrate this to Markdown,
enabling their inclusion in ERPNext, our focus is on the use of manual,
covering every step in detail.
Therefore,
we take care to present including what each feature is built of ERPNext
because here people do not have the habit of thinking outside the box,
and try to figure out on your own how things work or serving something.
...
Thanks is awesome :) I was just beginning to resign myself to the fact that open source seems to be a one-way street!
Priya is our documentation expert https://github.com/fogueri and we have made quite some progress in the manual which we are publishing at erpnext.org
Our goal is to make erpnext.org the main (and community) site for ERPNext and keep erpnext.com for cloud hosting (our bread and butter).
Right now erpnext.org is just static pages hosted on GitHub Pages, but we want to make this into a full ERPNext instance so that we (and anyone from the community) can easily manage web pages, add blog posts etc using the Website module.
I would suggest you can add / edit / update your manuals directly in the erpnext repository at the moment by sending pull request to:
The same, also has some manuals for use in the ERPNext en, she prepared for the use of our staff.
Among them are:
Access Handbook: Covering the process of introducing the user on the desktop ERPNext.
Sales Handbook: Covering the process of creating and managing Prospectus, sales orders, quotations and so on.
Support Handbook: Covering the process of care and customer support.
Financial Handbook: (Under development) covering the use of the process of accounts.
We will be studying the availability of these manuals as a Github repository, and applicable license.
She is responsible for the documentation process using ERPNext and preparation of the Manuals, and now contribute to the translation, to enable the inclusion of printscreens with a good translation.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to a topic in the Google Groups “ERPNext Developer Forum” group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Wiki update contribution will help lot more enterprises to migrate and not just manufacutring outfits.
Mitul
On Friday, September 27, 2013, Rushabh Mehta wrote:
Max,
Amazing to see that you have supported 13 estabilishments! It might help just to document your experience so that it can motivate other users. Good luck with your struggles - It will really take ERPNext to a next level to have an experienced developer like yourself.
Replying to your other issues via GitHub.
best,
Rushabh
ps. Happy to note the "Champions" page was actually read :)
The
questions are related precisely to maintain, updates, documentation,
manuals, getting started guides and resources ERPNext focused on local
issues (for each country), but in such a way that it can be part of the
product ERPNext.
We would like very much to contribute more actively to ERPNext, however, have small problems like:
- Work overload
- We are under the law (idiots) in Brazil
-
We have to fight every day to keep ERPNext (as you mentioned in the
first version of the manual ERPNext - We must be champions)
Today,
we have a very high workload to keep ERPNext just a company, we are 3
developers, and we are fighting to show that ERPNext is the best way to
Perform Group, the company that we used, and we're only 3 to surportar 13 establishments.
I'm fighting against myself, because I am fighting a war to replace the first ERP company that I developed.
Currently
our manuals are in Google Docs, but soon will migrate this to Markdown,
enabling their inclusion in ERPNext, our focus is on the use of manual,
covering every step in detail.
Therefore,
we take care to present including what each feature is built of ERPNext
because here people do not have the habit of thinking outside the box,
and try to figure out on your own how things work or serving something.
...
Thanks is awesome :) I was just beginning to resign myself to the fact that open source seems to be a one-way street!
Priya is our documentation expert https://github.com/fogueri and we have made quite some progress in the manual which we are publishing at erpnext.org
Our goal is to make erpnext.org the main (and community) site for ERPNext and keep erpnext.com for cloud hosting (our bread and butter).
Right now erpnext.org is just static pages hosted on GitHub Pages, but we want to make this into a full ERPNext instance so that we (and anyone from the community) can easily manage web pages, add blog posts etc using the Website module.
I would suggest you can add / edit / update your manuals directly in the erpnext repository at the moment by sending pull request to:
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
End of Note
—
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
