Volunteer github guru for documentation submissions?
J. Landman Gay
jacque at hyperactivesw.com
Tue Apr 12 15:17:25 EDT 2016
On 4/12/2016 5:19 AM, Ali Lloyd wrote:
> The viewer stack was something I quickly knocked up so that there was
> *some* way of viewing the document in context - the links indeed don't work
> as it doesn't rebuild the whole dictionary. I'm sorry about that- I can
> probably make it work properly at some point.
I wouldn't make it a priority, the problem for me wasn't with the viewer
itself. I only needed to know whether I should ignore the terms that
didn't display. Your blog mentioned that links don't work, but I hadn't
yet seen the markdown document so I didn't know what you meant by
"link." I thought you meant URLs.
> The line
> *Navigate to the file you want to modify in the dictionary folder of the
> community-docs branch
> with a link to the correct branch/folder was there before, but I've
> submitted a PR to reinforce the fact that the community-docs branch should
> be the base branch to modify the file:
Thanks. I know you want the best for us, and you're responsiveness is
terrific. I may not be typical because my eyesight is poor and I don't
always notice things. If I need to read through a lot of text to find
links, I'll miss some. A straightforward list would have helped a lot:
Contribution overview: <link to blog post>
Joining github: <link>
The documentation files: <link to community docs>
Using the web interface: <link to
Using Git GUI software: <link #git software>
Using the command line: <link #command line>
Linking to your LC account: <link>
Signing the CLA: <link>
Documentation Format Reference: <link>
For me, this thread would have been a whole lot shorter if that had been
available on github, or at least a link to it.
Thanks again for your dedication Ali.
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the Use-livecode