I could do that, but I'm thinking it's probably best to start with the Wiki, where I edits are easy. Also others can improve on my Wiki work. Once the work gets to a high quality product, then it'll be time to update the manual.
My basic approach right now is to begin at the point where someone has never imported by CSV, and then, eventually, build to a CSV import workflow. During the last few years, I've developed workflows so that with a few clicks, I can import many of my transactions, especially the complex transactions (some of my transactions have 10 or more splits). There is nothing wrong with entering transactions directly in GnuCash, but for some journal entries, I use various spreadsheet functions to automate my work. Combine full spreadsheet functionality with GnuCash's multi-split CSV import, saved import settings, and the automation possibilities seem endless. > On 08/16/2026 5:24 PM PDT David Cousens <[email protected]> wrote: > > > Patrick the documentation editing is decribed on the following wiki > page > https://wiki.gnucash.org/wiki/Documentation_Improvement and is more > akin to the code development. > > David > _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
