Hi Andrew,

I think "royale-docs" is a separated repository itself (from the main
project) that should have all the learning material. That's docs, for now,
but your "Royale in a Week" project is ok for me in that place. Maybe is
more about to expose/highlight it better in that royale-docs page with a
banner or something as we have it and storing all of it in a concrete and
organized subfolder of royale-docs repo.

Royale docs could be as well hosting other tutorials and even the blog
examples, so website turns to just a marketing face for the project.

As you probably know, I'm investing some free time in looking to how to
create a Royale App for it so we use our own, and was trying to make royale
load markdown from github, but it's turning a bit complicated, due to
github using Kramdown and many other things. So maybe this is the solution:
migrate blog examples to royale-docs converting to mark-down and make
website just center the website in trying to create a Royale web that
centers in marketing and presentation of the technology.

Another thing I expect for the future is decrease the repositories we have,
since I think we have many and that could be a bit cumbersome to people
interested in Royale. One of the things I'd like before 1.0 is just 1 repo
instead of 3 for (compiler,typedefs and framework), that will make for sure
a difference for people coming to Royale and will streamline lots of things
like builds and releases).

Thanks


El dom., 19 abr. 2020 a las 23:52, Andrew Wetmore (<cottag...@gmail.com>)
escribió:

> Hi:
>
> Hi: I see that flink.apache.org has requested a separate git repository
> for
> the self-directed learning modules they hope to deploy. As we move closer
> to Royale 1.0 it will become more important to have a suite of tutorials to
> extends the excellent how-tos @carlos has been posting on the blog..
>
> I have committed to creating Royale in a Week, which will have lots of
> stuff to store: scripts, videos, code samples, transcripts, and so on. Can
> we fit that all into the existing documentation repository? Or should we
> request a separate one?
>
> A
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to