Re: Frustration with Cordova documentation

2020-04-01 Thread Niklas Merz
I don't know if this happenend, but we could ask around Apache if someone has contacts to a technical writer available for such task to improve docs. Maybe someone knows an approiate mailing list. It looks to that we would need somebody external as the active committers are to busy or is

Re: Frustration with Cordova documentation

2020-04-01 Thread Chris Brody
Any suggestions how we can get the ball rolling with the already sponsored project? On Wed, Apr 1, 2020 at 3:49 AM Jesse wrote: > Sounds good. > I will tweet the blog post as well so we can try to stay ahead of the > questions. > > On Wed, Apr 1, 2020 at 12:44 AM julio cesar sanchez < >

Re: Frustration with Cordova documentation

2020-04-01 Thread Jesse
Sounds good. I will tweet the blog post as well so we can try to stay ahead of the questions. On Wed, Apr 1, 2020 at 12:44 AM julio cesar sanchez wrote: > Maybe we should add the error code on the blog entry (*ITMS-90809*), that > way people can end up on the blog when searching about. Right

Re: Frustration with Cordova documentation

2020-04-01 Thread julio cesar sanchez
Maybe we should add the error code on the blog entry (*ITMS-90809*), that way people can end up on the blog when searching about. Right now first entry is the ionic blog, I checked 5 pages and didn’t find anything cordova specific. El miércoles, 1 de abril de 2020, Niklas Merz escribió: > I

Re: Frustration with Cordova documentation

2020-04-01 Thread Niklas Merz
I think there is good documentation for this particular problem. I wrote a blog post {1} just two weeks ago to summarize it now that Apple is enforcing it. Most people just don't research properly and just ask and we can't do anything about it. But yes we really should get this money for

Frustration with Cordova documentation

2020-03-31 Thread Chris Brody
Improvement has already been sponsored by an anonymous donor. Repeated requests for help with getting it started have been met with no response so far. I think this recent thread is an example of how our documentation could use some improvement: