Well, duh. I forgot about the royal-docs repo… 😳 They can just fork that and submit pull requests.
I do think that we should have some of this self documenting from the source code though. I’d like to explore that. Thanks! Harbs > On Jul 19, 2018, at 2:23 PM, Andrew Wetmore <[email protected]> wrote: > > Starting a page in the docs project and putting together material would be > great. Then we can link it into the published docs when it is ready. I am > not sure who grants permissions/access for that. > > a > > On Thu, Jul 19, 2018 at 8:14 AM, Harbs <[email protected]> wrote: > >> I just started some folks (my daughter and some friends) on some Royale >> work. They’re still getting into things. Hopefully as they get more into >> things, they will be able to contribute. >> >> One of the big things they are struggling with is discovering what >> components there are and what bead can work with which components. If I was >> not here to help them, it would be almost impossible to get going. One of >> them expressed interest in helping writing documentation for this as they >> are learning. >> >> What’s the best way for her to do that? It doesn’t really fit into the >> wiki. I’m not sure how to give her access to the docs. >> >> I think ideally, this should be something that the code self-documents. >> >> Thoughts? >> >> Harbs > > > > > -- > Andrew Wetmore > > http://cottage14.blogspot.com/
