we maintain a separate one note for each of our contract support customers. its the best centralized documentation for those we ever had. and we can give them visibility or export it for them. the only issue is if your offline making edits and someone else is you have to do conflict mitigation when they sync, but thats with anything
On Sat, Jan 20, 2018 at 11:21 AM, Steve Jones <[email protected]> wrote: > OneNote is WAY better for that. thats where I maintain all our > documentation. try it out, not the App, the actual program. ive stayed with > 2013 because it flows better. It like a digital binder, less restrictive > than any wiki i ever met. drag and drop stuff. i embed alot of excel files, > they view-able directly and then editable outside the page but save right > back. its sexy for ip space management. the only drawback is you can only > go like 4 sub pages deep per section. i do job orders for contractors in it > and export them as pdf, sexy, all sexy > > On Sat, Jan 20, 2018 at 11:16 AM, <[email protected]> wrote: > >> I want it to be in wiki format. An ongoing knowledge base. We had one >> at a former company and it was great. But I was not the one that installed >> it so I don’t know what is involved in that. >> >> *From:* Steve Jones >> *Sent:* Saturday, January 20, 2018 10:14 AM >> *To:* [email protected] >> *Subject:* Re: [AFMUG] OT tech wiki >> >> if its not public, i use OneNote >> its not in the wiki format but it logs changes, logs who made changes and >> allows multiuser access >> >> On Sat, Jan 20, 2018 at 11:06 AM, <[email protected]> wrote: >> >>> What is the most pain free way to create a wiki? >>> >> >> > >
