You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Andrew Wetmore <co...@gmail.com> on 2020/04/19 21:52:35 UTC
Repository for tutorials
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/
Re: Repository for tutorials
Posted by Carlos Rovira <ca...@apache.org>.
Hi Andrew,
my point is that having many repos, means people need to configure or
remember them to use any git client or from command line. Since all is
related to the same topic (lets call it "learning material or
documentation"), I think is better to reduce.
For me is something about usability and simplification. If you think in a
main menu in a website, you can see most of the actual webs use to have few
items (around 3 to 5) with no submenus or even no menu at all and just a
footer with the rest of things. All of this is trying to make things
simpler for people coming. That's different to the rest of us working many
ours in Royale and knowing all about it. Think that you go to other
project, how many time do you need to invest if info is splitted a cross
many pages and resources? for that reason I recommend streamline as
possible, reducing repos, making menus simpler and with less options and
doing our best to make any user go quicliking from a starting point of
information to the point that is trying to watch
just my 2 :)
El lun., 20 abr. 2020 a las 13:48, Andrew Wetmore (<co...@gmail.com>)
escribió:
> I am not sure how that makes more complexity for end users. I would presume
> that, once we have a set of tutorials, a site visitor would get to them
> from the website by a single click. However, I take your larger point that
> the docs repository can probably host all the tutorials we would like to
> create.
>
> a
>
> On Mon, Apr 20, 2020 at 7:47 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > I was not aware that exists.
> >
> > IMHO, and as I said before, I don't think is worth it to have more repos
> > and fronts open, we should do the opposite, since that means complexity
> for
> > end users, and that means people not coming to Royale to stay.
> >
> > El lun., 20 abr. 2020 a las 10:53, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Hi,
> > >
> > > We have also [1] - maybe this is good candidate for changes etc.
> > >
> > > [1] https://github.com/apache/royale-tourjs
> > >
> > > pon., 20 kwi 2020 o 09:19 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > 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 (<
> > cottage14@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
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Repository for tutorials
Posted by Andrew Wetmore <co...@gmail.com>.
I am not sure how that makes more complexity for end users. I would presume
that, once we have a set of tutorials, a site visitor would get to them
from the website by a single click. However, I take your larger point that
the docs repository can probably host all the tutorials we would like to
create.
a
On Mon, Apr 20, 2020 at 7:47 AM Carlos Rovira <ca...@apache.org>
wrote:
> I was not aware that exists.
>
> IMHO, and as I said before, I don't think is worth it to have more repos
> and fronts open, we should do the opposite, since that means complexity for
> end users, and that means people not coming to Royale to stay.
>
> El lun., 20 abr. 2020 a las 10:53, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Hi,
> >
> > We have also [1] - maybe this is good candidate for changes etc.
> >
> > [1] https://github.com/apache/royale-tourjs
> >
> > pon., 20 kwi 2020 o 09:19 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > 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 (<
> cottage14@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
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: Repository for tutorials
Posted by Carlos Rovira <ca...@apache.org>.
I was not aware that exists.
IMHO, and as I said before, I don't think is worth it to have more repos
and fronts open, we should do the opposite, since that means complexity for
end users, and that means people not coming to Royale to stay.
El lun., 20 abr. 2020 a las 10:53, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hi,
>
> We have also [1] - maybe this is good candidate for changes etc.
>
> [1] https://github.com/apache/royale-tourjs
>
> pon., 20 kwi 2020 o 09:19 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > 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 (<cottage14@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
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Repository for tutorials
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi,
We have also [1] - maybe this is good candidate for changes etc.
[1] https://github.com/apache/royale-tourjs
pon., 20 kwi 2020 o 09:19 Carlos Rovira <ca...@apache.org>
napisał(a):
> 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 (<co...@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
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Repository for tutorials
Posted by Carlos Rovira <ca...@apache.org>.
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 (<co...@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