We have separate repository here [1]. Whatever you push there it will be automatically deployed here [2]. In what format it should be - well I always thought that it can be bunch of github pages - Which we later display it somehow.
If you look into some of the page in Olaf's starting point repository [3] - You can change each of that page as an file for example "Hello-world.md" with exactly the same markers as it is on the wiki. In whatever direction you will go it will be good I think so, we can later change all of that to most suitable way. [1] https://github.com/apache/royale-docs [2] https://apache.github.io/royale-docs/ [3] https://github.com/olafkrueger/flexjs-docs/wiki/Hello-world Thanks, Piotr 2018-01-14 21:54 GMT+01:00 Andrew Wetmore <[email protected]>: > Yes, that's an excellent beginning and structure. > > Royale will need a branded knowledge base. Will that be integrated in the > website, or a wiki hosted on github or somewhere else? > > a > > On Sun, Jan 14, 2018 at 3:53 PM, Piotr Zarzycki <[email protected] > > > wrote: > > > Hi, > > > > We have started that effort here [1]. That was quite good starting point. > > > > [1] https://github.com/olafkrueger/flexjs-docs/wiki > > > > Thanks, Piotr > > > > 2018-01-14 20:42 GMT+01:00 Carlos Rovira <[email protected]>: > > > > > Changing subject > > > > > > About Github documentation, I think we should start migrating what we > > have > > > already at Apache Wiki in FlexJS. > > > > > > For Example this: > > > https://cwiki.apache.org/confluence/display/FLEX/ > FlexJS+Basic+components > > > > > > Would be a great start > > > > > > About the documentation tag, I see you already introduced a bug report, > > > Maybe others want to comment as well regarding this issue > > > > > > thanks! > > > > > > > > > > > > > 2018-01-14 16:04 GMT+01:00 Andrew Wetmore <[email protected]>: > > > >> > > > >> > > > >> I am thinking about where to record and track tasks for future > > > >> documentation. I see that our project in GitHub has a > "documentation" > > > tag > > > >> with no active bug reports. Is that where I should enter, not just > > > >> documentation bug issues, but to-do stuff like "create a blog entry > on > > > >> TOPIC X"? Or is there some other system for tracking stuff like > that? > > > >> > > > >> -- > > > Carlos Rovira > > > http://about.me/carlosrovira > > > > > > > > > > > -- > > > > Piotr Zarzycki > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > <https://www.patreon.com/piotrzarzycki>* > > > > > > -- > Andrew Wetmore > > http://cottage14.blogspot.com/ > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
