You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Adrian Szuszkiewicz <ad...@gmail.com> on 2019/05/07 15:47:56 UTC
Royale Docs Changes Proposal
Hi all :)
Introduction
My name is Adrian and together with Piotr I am preparing a set of video
tutorials about Moonshine IDE, Royale and ActionScript. I am completely new
to this technology stack and a few days ago I was reading Royale Docs for
the first time. There were a couple of things I found confusing about the
structure of the documentation. I believe that with a few minor changes to
the docs we can achieve more clarity. If the Team agrees I volunteer to do
the changes. Here’s what I propose:
Merging Getting Started
There are two pages with awfully similar titles and responsibilities:
-
Getting Started [https://royale.apache.org/getting-started/] reachable
from "Get Started" button on main Royale page
-
Get started with Royale [
https://apache.github.io/royale-docs/Get%20Started.html] reachable from
"Get Started" item in doc’s table of content.
In my opinion, the existence of two Get Started pages is very confusing. If
you agree I’d like to:
1.
Move all the content of Getting Started page to Get started with Royale in
the docs
2.
Make Get Started button on main Royale page point to Get started with
Royale in the docs.
Renaming Links with Instructions
On "Getting Started" page there are four links with instructions about how
to install and configure Royale in different editors. When I was reading
the docs for the first time I skipped those links because I thought they
only point to download locations, not the instructions. I’d like to rename
them as follows:
-
“Moonshine IDE” -> “Instructions for Moonshine IDE”
-
“Visual Studio Code” -> “Instructions for Visual Studio Code”
-
“Adobe Flash Builder” -> “Instructions for Adobe Flash Builder”
-
“IntelliJ IDEA” -> “Instructions for IntelliJ IDEA” [this link is empty
but I’d keep it anyway]
Changing Menu Behavior
The Table of Content menu on the right side in the docs behaves in a weird
way. When you click on an item it doesn't automatically expand. But when
you select your topic from the main text then it expands correctly showing
all its children. At first, I thought the menu was incomplete and
disjointed but then I realized it just doesn’t expand at right times. It
made me feel a little bit lost in the docs and track my journey through
them in the notepad. If you agree I’d like to fix expanding behavior.
It's easier to conceptualize this in a video:
https://www.youtube.com/watch?v=GHzDnH8h6gE&feature=youtu.be
Have a great day,
Adrian
Re: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Alex,
In ASDoc application we have similar header as it is in main website page
(Features, Get Started). Get Started has currently wrong link - how this
header is being generated ? It is not part of that Application as I see ?
Thanks,
Piotr
pt., 17 maj 2019 o 14:35 Andrew Wetmore <co...@gmail.com> napisał(a):
> @Piotr: yes, that is correct. If I use the menu, it is like I am using the
> table of contents of a physical book. If I follow a link within the text,
> it is as if I am picking up a different physical book.
>
> On Fri, May 17, 2019 at 7:18 AM Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
> > Andrew,
> >
> > By saying that:
> >
> > "If I am starting from the help
> > docs I do not want the window to suddenly be focusing on something else;
> I
> > would prefer a new window to appear with whatever I clicked on so I can
> go
> > back to the first window easily and continue my studies."
> >
> > Do you mean when you are being in doc [1] - above apply on anything what
> > you click inside text - Am I right ? Above new window rule do not apply
> > when you navigating trough menu on the right sight in doc [1]?
> >
> > [1] https://apache.github.io/royale-docs/
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 maj 2019 o 12:12 Andrew Wetmore <co...@gmail.com>
> napisał(a):
> >
> > > I agree with @Piotr that context is key. If I am starting from the help
> > > docs I do not want the window to suddenly be focusing on something
> else;
> > I
> > > would prefer a new window to appear with whatever I clicked on so I can
> > go
> > > back to the first window easily and continue my studies. Similarly, if
> my
> > > context is the website, then I am thinking about the get-started stuff
> as
> > > part of the website, and I am happy for the material I click on to take
> > > over the current screen.
> > >
> > > On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > wrote:
> > >
> > > > Let's see whether Andrew have different thoughts. He is an expert in
> > case
> > > > of documentation ;) Adrian is working on 1 or 2 small pull requests
> > more.
> > > > ;)
> > > >
> > > > pt., 17 maj 2019 o 10:11 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Ok Piotr,
> > > > >
> > > > > so I think we have all set as you said, and we just need to worry
> > about
> > > > the
> > > > > content created to follow that guidelines
> > > > >
> > > > > :)
> > > > >
> > > > > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > > > > piotrzarzycki21@gmail.com>) escribió:
> > > > >
> > > > > > In my opinion it depends where you are clicking on Get Started.
> If
> > > you
> > > > > are
> > > > > > clicking on Get Started on main page (main menu or footer) you
> > should
> > > > > stay
> > > > > > in the same window. I think it should be true for whatever option
> > in
> > > > main
> > > > > > menu you are clicking.
> > > > > >
> > > > > > However if you are in Docs already and click on "Apache Royale
> > > > > > Documentation
> > > > > > <https://apache.github.io/royale-docs/>" - it would can go to
> > > separate
> > > > > > window where you can easy navigate.
> > > > > >
> > > > > > My 2 cents ;)
> > > > > >
> > > > > >
> > > > > > pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Andrew,
> > > > > > >
> > > > > > > ok, so website navigation happens on the same window and docs
> in
> > > its
> > > > > own
> > > > > > > window. That's ok for me too.
> > > > > > >
> > > > > > > What to do with the case of pages like "Get Started"? The link
> is
> > > in
> > > > > > > website, but goes to royale docs
> > > > > > >
> > > > > > > thanks
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > > > > cottage14@gmail.com
> > > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > I think "target=_blank" should be for links to location
> outside
> > > of
> > > > > > Royale
> > > > > > > > docs. To me, that includes the Royale website. I would want
> it
> > to
> > > > > open
> > > > > > > in a
> > > > > > > > new window rather than taking over the window I am using to
> > read
> > > > the
> > > > > > > docs.
> > > > > > > >
> > > > > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > > > > carlosrovira@apache.org
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Adrian,
> > > > > > > > >
> > > > > > > > > I read the Get Started page. Good work! :)
> > > > > > > > >
> > > > > > > > > just added a link that I think was missed, change it if you
> > > think
> > > > > it
> > > > > > > > should
> > > > > > > > > point to other page.
> > > > > > > > >
> > > > > > > > > I want to ask about the links strategy. I see some of them
> > that
> > > > > > refers
> > > > > > > to
> > > > > > > > > the same Royale-docs part has target blank while other not.
> > > > > > > > > We talked about this when launched the website: In the
> > website
> > > we
> > > > > put
> > > > > > > all
> > > > > > > > > links to be loaded on the same page, while external links
> to
> > > the
> > > > > site
> > > > > > > > load
> > > > > > > > > in a blank page. I think we should do the same for
> > Royale-docs.
> > > > We
> > > > > > just
> > > > > > > > > need to consider if website and Royale-docs must load in
> the
> > > same
> > > > > > page.
> > > > > > > > For
> > > > > > > > > example in website, a link to NPM will load in another page
> > > while
> > > > > > > mailing
> > > > > > > > > list info will load in the current one.
> > > > > > > > >
> > > > > > > > > thanks!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > > > > > carlosrovira@apache.org
> > > > > > > > > >)
> > > > > > > > > escribió:
> > > > > > > > >
> > > > > > > > > > Hi
> > > > > > > > > >
> > > > > > > > > > I tried various plugin solutions for WP and no one seems
> to
> > > fit
> > > > > > what
> > > > > > > we
> > > > > > > > > > need. So I changed the url to the docs page as suggested.
> > > Going
> > > > > to
> > > > > > > > > publish
> > > > > > > > > > the site.
> > > > > > > > > >
> > > > > > > > > > I see the styles in headers and other things are not
> > matching
> > > > the
> > > > > > > site
> > > > > > > > > > styles. I'll try to fix that soon.
> > > > > > > > > >
> > > > > > > > > > Thanks
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > > > > > > carlosrovira@apache.org>)
> > > > > > > > > > escribió:
> > > > > > > > > >
> > > > > > > > > >> Hi, I'm looking into this now: How to make website
> render
> > > the
> > > > > > > content
> > > > > > > > of
> > > > > > > > > >> a GitHub page.
> > > > > > > > > >> About Menu I'll change to "Get Started" as Piotr
> suggested
> > > > > > > > > >>
> > > > > > > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz
> (<
> > > > > > > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > > > > > > >>
> > > > > > > > > >>> My pull request
> > > > > > > > > >>>
> > > > > > > > > >>> #17: Move Getting Started to Docs
> > > > > > > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > > > > > > >>>
> > > > > > > > > >>> has just been merged. Now I would like to ask someone
> > with
> > > > > > > WordPress
> > > > > > > > > >>> access
> > > > > > > > > >>> to change the link on header's "GET STARTED" button and
> > > > > footer's
> > > > > > > > > "Getting
> > > > > > > > > >>> Started"
> > > > > > > > > >>>
> > > > > > > > > >>> from: https://royale.apache.org/getting-started/
> > > > > > > > > >>> to:
> > > https://apache.github.io/royale-docs/Get%20Started.html
> > > > > > > > > >>>
> > > > > > > > > >>> Thanks,
> > > > > > > > > >>> Adrian
> > > > > > > > > >>>
> > > > > > > > > >>>
> > > > > > > > > >>>
> > > > > > > > > >>> --
> > > > > > > > > >>> Sent from:
> > > > > http://apache-royale-development.20373.n8.nabble.com/
> > > > > > > > > >>>
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> --
> > > > > > > > > >> Carlos Rovira
> > > > > > > > > >> http://about.me/carlosrovira
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Carlos Rovira
> > > > > > > > > > http://about.me/carlosrovira
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Carlos Rovira
> > > > > > > > > http://about.me/carlosrovira
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > 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
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > 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>*
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Royale Docs Changes Proposal
Posted by Andrew Wetmore <co...@gmail.com>.
@Piotr: yes, that is correct. If I use the menu, it is like I am using the
table of contents of a physical book. If I follow a link within the text,
it is as if I am picking up a different physical book.
On Fri, May 17, 2019 at 7:18 AM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Andrew,
>
> By saying that:
>
> "If I am starting from the help
> docs I do not want the window to suddenly be focusing on something else; I
> would prefer a new window to appear with whatever I clicked on so I can go
> back to the first window easily and continue my studies."
>
> Do you mean when you are being in doc [1] - above apply on anything what
> you click inside text - Am I right ? Above new window rule do not apply
> when you navigating trough menu on the right sight in doc [1]?
>
> [1] https://apache.github.io/royale-docs/
>
> Thanks,
> Piotr
>
> pt., 17 maj 2019 o 12:12 Andrew Wetmore <co...@gmail.com> napisał(a):
>
> > I agree with @Piotr that context is key. If I am starting from the help
> > docs I do not want the window to suddenly be focusing on something else;
> I
> > would prefer a new window to appear with whatever I clicked on so I can
> go
> > back to the first window easily and continue my studies. Similarly, if my
> > context is the website, then I am thinking about the get-started stuff as
> > part of the website, and I am happy for the material I click on to take
> > over the current screen.
> >
> > On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > wrote:
> >
> > > Let's see whether Andrew have different thoughts. He is an expert in
> case
> > > of documentation ;) Adrian is working on 1 or 2 small pull requests
> more.
> > > ;)
> > >
> > > pt., 17 maj 2019 o 10:11 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Ok Piotr,
> > > >
> > > > so I think we have all set as you said, and we just need to worry
> about
> > > the
> > > > content created to follow that guidelines
> > > >
> > > > :)
> > > >
> > > > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > > > piotrzarzycki21@gmail.com>) escribió:
> > > >
> > > > > In my opinion it depends where you are clicking on Get Started. If
> > you
> > > > are
> > > > > clicking on Get Started on main page (main menu or footer) you
> should
> > > > stay
> > > > > in the same window. I think it should be true for whatever option
> in
> > > main
> > > > > menu you are clicking.
> > > > >
> > > > > However if you are in Docs already and click on "Apache Royale
> > > > > Documentation
> > > > > <https://apache.github.io/royale-docs/>" - it would can go to
> > separate
> > > > > window where you can easy navigate.
> > > > >
> > > > > My 2 cents ;)
> > > > >
> > > > >
> > > > > pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> > > > > napisał(a):
> > > > >
> > > > > > Hi Andrew,
> > > > > >
> > > > > > ok, so website navigation happens on the same window and docs in
> > its
> > > > own
> > > > > > window. That's ok for me too.
> > > > > >
> > > > > > What to do with the case of pages like "Get Started"? The link is
> > in
> > > > > > website, but goes to royale docs
> > > > > >
> > > > > > thanks
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > > > cottage14@gmail.com
> > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > I think "target=_blank" should be for links to location outside
> > of
> > > > > Royale
> > > > > > > docs. To me, that includes the Royale website. I would want it
> to
> > > > open
> > > > > > in a
> > > > > > > new window rather than taking over the window I am using to
> read
> > > the
> > > > > > docs.
> > > > > > >
> > > > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > > > carlosrovira@apache.org
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Adrian,
> > > > > > > >
> > > > > > > > I read the Get Started page. Good work! :)
> > > > > > > >
> > > > > > > > just added a link that I think was missed, change it if you
> > think
> > > > it
> > > > > > > should
> > > > > > > > point to other page.
> > > > > > > >
> > > > > > > > I want to ask about the links strategy. I see some of them
> that
> > > > > refers
> > > > > > to
> > > > > > > > the same Royale-docs part has target blank while other not.
> > > > > > > > We talked about this when launched the website: In the
> website
> > we
> > > > put
> > > > > > all
> > > > > > > > links to be loaded on the same page, while external links to
> > the
> > > > site
> > > > > > > load
> > > > > > > > in a blank page. I think we should do the same for
> Royale-docs.
> > > We
> > > > > just
> > > > > > > > need to consider if website and Royale-docs must load in the
> > same
> > > > > page.
> > > > > > > For
> > > > > > > > example in website, a link to NPM will load in another page
> > while
> > > > > > mailing
> > > > > > > > list info will load in the current one.
> > > > > > > >
> > > > > > > > thanks!
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > > > > carlosrovira@apache.org
> > > > > > > > >)
> > > > > > > > escribió:
> > > > > > > >
> > > > > > > > > Hi
> > > > > > > > >
> > > > > > > > > I tried various plugin solutions for WP and no one seems to
> > fit
> > > > > what
> > > > > > we
> > > > > > > > > need. So I changed the url to the docs page as suggested.
> > Going
> > > > to
> > > > > > > > publish
> > > > > > > > > the site.
> > > > > > > > >
> > > > > > > > > I see the styles in headers and other things are not
> matching
> > > the
> > > > > > site
> > > > > > > > > styles. I'll try to fix that soon.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > > > > > carlosrovira@apache.org>)
> > > > > > > > > escribió:
> > > > > > > > >
> > > > > > > > >> Hi, I'm looking into this now: How to make website render
> > the
> > > > > > content
> > > > > > > of
> > > > > > > > >> a GitHub page.
> > > > > > > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > > > > > > >>
> > > > > > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > > > > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > > > > > >>
> > > > > > > > >>> My pull request
> > > > > > > > >>>
> > > > > > > > >>> #17: Move Getting Started to Docs
> > > > > > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > > > > > >>>
> > > > > > > > >>> has just been merged. Now I would like to ask someone
> with
> > > > > > WordPress
> > > > > > > > >>> access
> > > > > > > > >>> to change the link on header's "GET STARTED" button and
> > > > footer's
> > > > > > > > "Getting
> > > > > > > > >>> Started"
> > > > > > > > >>>
> > > > > > > > >>> from: https://royale.apache.org/getting-started/
> > > > > > > > >>> to:
> > https://apache.github.io/royale-docs/Get%20Started.html
> > > > > > > > >>>
> > > > > > > > >>> Thanks,
> > > > > > > > >>> Adrian
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>> --
> > > > > > > > >>> Sent from:
> > > > http://apache-royale-development.20373.n8.nabble.com/
> > > > > > > > >>>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> --
> > > > > > > > >> Carlos Rovira
> > > > > > > > >> http://about.me/carlosrovira
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Carlos Rovira
> > > > > > > > > http://about.me/carlosrovira
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Carlos Rovira
> > > > > > > > http://about.me/carlosrovira
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > 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
> > > >
> > >
> > >
> > > --
> > >
> > > 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>*
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
Andrew,
By saying that:
"If I am starting from the help
docs I do not want the window to suddenly be focusing on something else; I
would prefer a new window to appear with whatever I clicked on so I can go
back to the first window easily and continue my studies."
Do you mean when you are being in doc [1] - above apply on anything what
you click inside text - Am I right ? Above new window rule do not apply
when you navigating trough menu on the right sight in doc [1]?
[1] https://apache.github.io/royale-docs/
Thanks,
Piotr
pt., 17 maj 2019 o 12:12 Andrew Wetmore <co...@gmail.com> napisał(a):
> I agree with @Piotr that context is key. If I am starting from the help
> docs I do not want the window to suddenly be focusing on something else; I
> would prefer a new window to appear with whatever I clicked on so I can go
> back to the first window easily and continue my studies. Similarly, if my
> context is the website, then I am thinking about the get-started stuff as
> part of the website, and I am happy for the material I click on to take
> over the current screen.
>
> On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki <pi...@gmail.com>
> wrote:
>
> > Let's see whether Andrew have different thoughts. He is an expert in case
> > of documentation ;) Adrian is working on 1 or 2 small pull requests more.
> > ;)
> >
> > pt., 17 maj 2019 o 10:11 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Ok Piotr,
> > >
> > > so I think we have all set as you said, and we just need to worry about
> > the
> > > content created to follow that guidelines
> > >
> > > :)
> > >
> > > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > In my opinion it depends where you are clicking on Get Started. If
> you
> > > are
> > > > clicking on Get Started on main page (main menu or footer) you should
> > > stay
> > > > in the same window. I think it should be true for whatever option in
> > main
> > > > menu you are clicking.
> > > >
> > > > However if you are in Docs already and click on "Apache Royale
> > > > Documentation
> > > > <https://apache.github.io/royale-docs/>" - it would can go to
> separate
> > > > window where you can easy navigate.
> > > >
> > > > My 2 cents ;)
> > > >
> > > >
> > > > pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Hi Andrew,
> > > > >
> > > > > ok, so website navigation happens on the same window and docs in
> its
> > > own
> > > > > window. That's ok for me too.
> > > > >
> > > > > What to do with the case of pages like "Get Started"? The link is
> in
> > > > > website, but goes to royale docs
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > > > >
> > > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > > cottage14@gmail.com
> > > > >)
> > > > > escribió:
> > > > >
> > > > > > I think "target=_blank" should be for links to location outside
> of
> > > > Royale
> > > > > > docs. To me, that includes the Royale website. I would want it to
> > > open
> > > > > in a
> > > > > > new window rather than taking over the window I am using to read
> > the
> > > > > docs.
> > > > > >
> > > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > > carlosrovira@apache.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Adrian,
> > > > > > >
> > > > > > > I read the Get Started page. Good work! :)
> > > > > > >
> > > > > > > just added a link that I think was missed, change it if you
> think
> > > it
> > > > > > should
> > > > > > > point to other page.
> > > > > > >
> > > > > > > I want to ask about the links strategy. I see some of them that
> > > > refers
> > > > > to
> > > > > > > the same Royale-docs part has target blank while other not.
> > > > > > > We talked about this when launched the website: In the website
> we
> > > put
> > > > > all
> > > > > > > links to be loaded on the same page, while external links to
> the
> > > site
> > > > > > load
> > > > > > > in a blank page. I think we should do the same for Royale-docs.
> > We
> > > > just
> > > > > > > need to consider if website and Royale-docs must load in the
> same
> > > > page.
> > > > > > For
> > > > > > > example in website, a link to NPM will load in another page
> while
> > > > > mailing
> > > > > > > list info will load in the current one.
> > > > > > >
> > > > > > > thanks!
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > > > carlosrovira@apache.org
> > > > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > I tried various plugin solutions for WP and no one seems to
> fit
> > > > what
> > > > > we
> > > > > > > > need. So I changed the url to the docs page as suggested.
> Going
> > > to
> > > > > > > publish
> > > > > > > > the site.
> > > > > > > >
> > > > > > > > I see the styles in headers and other things are not matching
> > the
> > > > > site
> > > > > > > > styles. I'll try to fix that soon.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > >
> > > > > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > > > > carlosrovira@apache.org>)
> > > > > > > > escribió:
> > > > > > > >
> > > > > > > >> Hi, I'm looking into this now: How to make website render
> the
> > > > > content
> > > > > > of
> > > > > > > >> a GitHub page.
> > > > > > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > > > > > >>
> > > > > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > > > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > > > > >>
> > > > > > > >>> My pull request
> > > > > > > >>>
> > > > > > > >>> #17: Move Getting Started to Docs
> > > > > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > > > > >>>
> > > > > > > >>> has just been merged. Now I would like to ask someone with
> > > > > WordPress
> > > > > > > >>> access
> > > > > > > >>> to change the link on header's "GET STARTED" button and
> > > footer's
> > > > > > > "Getting
> > > > > > > >>> Started"
> > > > > > > >>>
> > > > > > > >>> from: https://royale.apache.org/getting-started/
> > > > > > > >>> to:
> https://apache.github.io/royale-docs/Get%20Started.html
> > > > > > > >>>
> > > > > > > >>> Thanks,
> > > > > > > >>> Adrian
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> --
> > > > > > > >>> Sent from:
> > > http://apache-royale-development.20373.n8.nabble.com/
> > > > > > > >>>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> Carlos Rovira
> > > > > > > >> http://about.me/carlosrovira
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > > --
> > > > > > > > Carlos Rovira
> > > > > > > > http://about.me/carlosrovira
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > 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
> > >
> >
> >
> > --
> >
> > 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>*
Re: Royale Docs Changes Proposal
Posted by Andrew Wetmore <co...@gmail.com>.
I agree with @Piotr that context is key. If I am starting from the help
docs I do not want the window to suddenly be focusing on something else; I
would prefer a new window to appear with whatever I clicked on so I can go
back to the first window easily and continue my studies. Similarly, if my
context is the website, then I am thinking about the get-started stuff as
part of the website, and I am happy for the material I click on to take
over the current screen.
On Fri, May 17, 2019 at 5:23 AM Piotr Zarzycki <pi...@gmail.com>
wrote:
> Let's see whether Andrew have different thoughts. He is an expert in case
> of documentation ;) Adrian is working on 1 or 2 small pull requests more.
> ;)
>
> pt., 17 maj 2019 o 10:11 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Ok Piotr,
> >
> > so I think we have all set as you said, and we just need to worry about
> the
> > content created to follow that guidelines
> >
> > :)
> >
> > El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > In my opinion it depends where you are clicking on Get Started. If you
> > are
> > > clicking on Get Started on main page (main menu or footer) you should
> > stay
> > > in the same window. I think it should be true for whatever option in
> main
> > > menu you are clicking.
> > >
> > > However if you are in Docs already and click on "Apache Royale
> > > Documentation
> > > <https://apache.github.io/royale-docs/>" - it would can go to separate
> > > window where you can easy navigate.
> > >
> > > My 2 cents ;)
> > >
> > >
> > > pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > > > Hi Andrew,
> > > >
> > > > ok, so website navigation happens on the same window and docs in its
> > own
> > > > window. That's ok for me too.
> > > >
> > > > What to do with the case of pages like "Get Started"? The link is in
> > > > website, but goes to royale docs
> > > >
> > > > thanks
> > > >
> > > >
> > > >
> > > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> > cottage14@gmail.com
> > > >)
> > > > escribió:
> > > >
> > > > > I think "target=_blank" should be for links to location outside of
> > > Royale
> > > > > docs. To me, that includes the Royale website. I would want it to
> > open
> > > > in a
> > > > > new window rather than taking over the window I am using to read
> the
> > > > docs.
> > > > >
> > > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> > carlosrovira@apache.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Adrian,
> > > > > >
> > > > > > I read the Get Started page. Good work! :)
> > > > > >
> > > > > > just added a link that I think was missed, change it if you think
> > it
> > > > > should
> > > > > > point to other page.
> > > > > >
> > > > > > I want to ask about the links strategy. I see some of them that
> > > refers
> > > > to
> > > > > > the same Royale-docs part has target blank while other not.
> > > > > > We talked about this when launched the website: In the website we
> > put
> > > > all
> > > > > > links to be loaded on the same page, while external links to the
> > site
> > > > > load
> > > > > > in a blank page. I think we should do the same for Royale-docs.
> We
> > > just
> > > > > > need to consider if website and Royale-docs must load in the same
> > > page.
> > > > > For
> > > > > > example in website, a link to NPM will load in another page while
> > > > mailing
> > > > > > list info will load in the current one.
> > > > > >
> > > > > > thanks!
> > > > > >
> > > > > >
> > > > > >
> > > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > > carlosrovira@apache.org
> > > > > > >)
> > > > > > escribió:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > I tried various plugin solutions for WP and no one seems to fit
> > > what
> > > > we
> > > > > > > need. So I changed the url to the docs page as suggested. Going
> > to
> > > > > > publish
> > > > > > > the site.
> > > > > > >
> > > > > > > I see the styles in headers and other things are not matching
> the
> > > > site
> > > > > > > styles. I'll try to fix that soon.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > >
> > > > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > > > carlosrovira@apache.org>)
> > > > > > > escribió:
> > > > > > >
> > > > > > >> Hi, I'm looking into this now: How to make website render the
> > > > content
> > > > > of
> > > > > > >> a GitHub page.
> > > > > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > > > > >>
> > > > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > > > >>
> > > > > > >>> My pull request
> > > > > > >>>
> > > > > > >>> #17: Move Getting Started to Docs
> > > > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > > > >>>
> > > > > > >>> has just been merged. Now I would like to ask someone with
> > > > WordPress
> > > > > > >>> access
> > > > > > >>> to change the link on header's "GET STARTED" button and
> > footer's
> > > > > > "Getting
> > > > > > >>> Started"
> > > > > > >>>
> > > > > > >>> from: https://royale.apache.org/getting-started/
> > > > > > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > > > > > >>>
> > > > > > >>> Thanks,
> > > > > > >>> Adrian
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> --
> > > > > > >>> Sent from:
> > http://apache-royale-development.20373.n8.nabble.com/
> > > > > > >>>
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Carlos Rovira
> > > > > > >> http://about.me/carlosrovira
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Rovira
> > > > > > > http://about.me/carlosrovira
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 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
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
Let's see whether Andrew have different thoughts. He is an expert in case
of documentation ;) Adrian is working on 1 or 2 small pull requests more.
;)
pt., 17 maj 2019 o 10:11 Carlos Rovira <ca...@apache.org> napisał(a):
> Ok Piotr,
>
> so I think we have all set as you said, and we just need to worry about the
> content created to follow that guidelines
>
> :)
>
> El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > In my opinion it depends where you are clicking on Get Started. If you
> are
> > clicking on Get Started on main page (main menu or footer) you should
> stay
> > in the same window. I think it should be true for whatever option in main
> > menu you are clicking.
> >
> > However if you are in Docs already and click on "Apache Royale
> > Documentation
> > <https://apache.github.io/royale-docs/>" - it would can go to separate
> > window where you can easy navigate.
> >
> > My 2 cents ;)
> >
> >
> > pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> > > Hi Andrew,
> > >
> > > ok, so website navigation happens on the same window and docs in its
> own
> > > window. That's ok for me too.
> > >
> > > What to do with the case of pages like "Get Started"? The link is in
> > > website, but goes to royale docs
> > >
> > > thanks
> > >
> > >
> > >
> > > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<
> cottage14@gmail.com
> > >)
> > > escribió:
> > >
> > > > I think "target=_blank" should be for links to location outside of
> > Royale
> > > > docs. To me, that includes the Royale website. I would want it to
> open
> > > in a
> > > > new window rather than taking over the window I am using to read the
> > > docs.
> > > >
> > > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <
> carlosrovira@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Hi Adrian,
> > > > >
> > > > > I read the Get Started page. Good work! :)
> > > > >
> > > > > just added a link that I think was missed, change it if you think
> it
> > > > should
> > > > > point to other page.
> > > > >
> > > > > I want to ask about the links strategy. I see some of them that
> > refers
> > > to
> > > > > the same Royale-docs part has target blank while other not.
> > > > > We talked about this when launched the website: In the website we
> put
> > > all
> > > > > links to be loaded on the same page, while external links to the
> site
> > > > load
> > > > > in a blank page. I think we should do the same for Royale-docs. We
> > just
> > > > > need to consider if website and Royale-docs must load in the same
> > page.
> > > > For
> > > > > example in website, a link to NPM will load in another page while
> > > mailing
> > > > > list info will load in the current one.
> > > > >
> > > > > thanks!
> > > > >
> > > > >
> > > > >
> > > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > > carlosrovira@apache.org
> > > > > >)
> > > > > escribió:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > I tried various plugin solutions for WP and no one seems to fit
> > what
> > > we
> > > > > > need. So I changed the url to the docs page as suggested. Going
> to
> > > > > publish
> > > > > > the site.
> > > > > >
> > > > > > I see the styles in headers and other things are not matching the
> > > site
> > > > > > styles. I'll try to fix that soon.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > > carlosrovira@apache.org>)
> > > > > > escribió:
> > > > > >
> > > > > >> Hi, I'm looking into this now: How to make website render the
> > > content
> > > > of
> > > > > >> a GitHub page.
> > > > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > > > >>
> > > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > > >>
> > > > > >>> My pull request
> > > > > >>>
> > > > > >>> #17: Move Getting Started to Docs
> > > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > > >>>
> > > > > >>> has just been merged. Now I would like to ask someone with
> > > WordPress
> > > > > >>> access
> > > > > >>> to change the link on header's "GET STARTED" button and
> footer's
> > > > > "Getting
> > > > > >>> Started"
> > > > > >>>
> > > > > >>> from: https://royale.apache.org/getting-started/
> > > > > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Adrian
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> Sent from:
> http://apache-royale-development.20373.n8.nabble.com/
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Carlos Rovira
> > > > > >> http://about.me/carlosrovira
> > > > > >>
> > > > > >>
> > > > > >
> > > > > > --
> > > > > > Carlos Rovira
> > > > > > http://about.me/carlosrovira
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > >
> > > >
> > > > --
> > > > 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
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Ok Piotr,
so I think we have all set as you said, and we just need to worry about the
content created to follow that guidelines
:)
El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> In my opinion it depends where you are clicking on Get Started. If you are
> clicking on Get Started on main page (main menu or footer) you should stay
> in the same window. I think it should be true for whatever option in main
> menu you are clicking.
>
> However if you are in Docs already and click on "Apache Royale
> Documentation
> <https://apache.github.io/royale-docs/>" - it would can go to separate
> window where you can easy navigate.
>
> My 2 cents ;)
>
>
> pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Andrew,
> >
> > ok, so website navigation happens on the same window and docs in its own
> > window. That's ok for me too.
> >
> > What to do with the case of pages like "Get Started"? The link is in
> > website, but goes to royale docs
> >
> > thanks
> >
> >
> >
> > El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<cottage14@gmail.com
> >)
> > escribió:
> >
> > > I think "target=_blank" should be for links to location outside of
> Royale
> > > docs. To me, that includes the Royale website. I would want it to open
> > in a
> > > new window rather than taking over the window I am using to read the
> > docs.
> > >
> > > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <carlosrovira@apache.org
> >
> > > wrote:
> > >
> > > > Hi Adrian,
> > > >
> > > > I read the Get Started page. Good work! :)
> > > >
> > > > just added a link that I think was missed, change it if you think it
> > > should
> > > > point to other page.
> > > >
> > > > I want to ask about the links strategy. I see some of them that
> refers
> > to
> > > > the same Royale-docs part has target blank while other not.
> > > > We talked about this when launched the website: In the website we put
> > all
> > > > links to be loaded on the same page, while external links to the site
> > > load
> > > > in a blank page. I think we should do the same for Royale-docs. We
> just
> > > > need to consider if website and Royale-docs must load in the same
> page.
> > > For
> > > > example in website, a link to NPM will load in another page while
> > mailing
> > > > list info will load in the current one.
> > > >
> > > > thanks!
> > > >
> > > >
> > > >
> > > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > > carlosrovira@apache.org
> > > > >)
> > > > escribió:
> > > >
> > > > > Hi
> > > > >
> > > > > I tried various plugin solutions for WP and no one seems to fit
> what
> > we
> > > > > need. So I changed the url to the docs page as suggested. Going to
> > > > publish
> > > > > the site.
> > > > >
> > > > > I see the styles in headers and other things are not matching the
> > site
> > > > > styles. I'll try to fix that soon.
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > > carlosrovira@apache.org>)
> > > > > escribió:
> > > > >
> > > > >> Hi, I'm looking into this now: How to make website render the
> > content
> > > of
> > > > >> a GitHub page.
> > > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > > >>
> > > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > > >>
> > > > >>> My pull request
> > > > >>>
> > > > >>> #17: Move Getting Started to Docs
> > > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > > >>>
> > > > >>> has just been merged. Now I would like to ask someone with
> > WordPress
> > > > >>> access
> > > > >>> to change the link on header's "GET STARTED" button and footer's
> > > > "Getting
> > > > >>> Started"
> > > > >>>
> > > > >>> from: https://royale.apache.org/getting-started/
> > > > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Adrian
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > > > >>>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Carlos Rovira
> > > > >> http://about.me/carlosrovira
> > > > >>
> > > > >>
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira
> > > > >
> > > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > > 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: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
In my opinion it depends where you are clicking on Get Started. If you are
clicking on Get Started on main page (main menu or footer) you should stay
in the same window. I think it should be true for whatever option in main
menu you are clicking.
However if you are in Docs already and click on "Apache Royale Documentation
<https://apache.github.io/royale-docs/>" - it would can go to separate
window where you can easy navigate.
My 2 cents ;)
pt., 17 maj 2019 o 09:59 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Andrew,
>
> ok, so website navigation happens on the same window and docs in its own
> window. That's ok for me too.
>
> What to do with the case of pages like "Get Started"? The link is in
> website, but goes to royale docs
>
> thanks
>
>
>
> El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<co...@gmail.com>)
> escribió:
>
> > I think "target=_blank" should be for links to location outside of Royale
> > docs. To me, that includes the Royale website. I would want it to open
> in a
> > new window rather than taking over the window I am using to read the
> docs.
> >
> > On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <ca...@apache.org>
> > wrote:
> >
> > > Hi Adrian,
> > >
> > > I read the Get Started page. Good work! :)
> > >
> > > just added a link that I think was missed, change it if you think it
> > should
> > > point to other page.
> > >
> > > I want to ask about the links strategy. I see some of them that refers
> to
> > > the same Royale-docs part has target blank while other not.
> > > We talked about this when launched the website: In the website we put
> all
> > > links to be loaded on the same page, while external links to the site
> > load
> > > in a blank page. I think we should do the same for Royale-docs. We just
> > > need to consider if website and Royale-docs must load in the same page.
> > For
> > > example in website, a link to NPM will load in another page while
> mailing
> > > list info will load in the current one.
> > >
> > > thanks!
> > >
> > >
> > >
> > > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> > carlosrovira@apache.org
> > > >)
> > > escribió:
> > >
> > > > Hi
> > > >
> > > > I tried various plugin solutions for WP and no one seems to fit what
> we
> > > > need. So I changed the url to the docs page as suggested. Going to
> > > publish
> > > > the site.
> > > >
> > > > I see the styles in headers and other things are not matching the
> site
> > > > styles. I'll try to fix that soon.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > > carlosrovira@apache.org>)
> > > > escribió:
> > > >
> > > >> Hi, I'm looking into this now: How to make website render the
> content
> > of
> > > >> a GitHub page.
> > > >> About Menu I'll change to "Get Started" as Piotr suggested
> > > >>
> > > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > > >> adrianszuszkiewicz@gmail.com>) escribió:
> > > >>
> > > >>> My pull request
> > > >>>
> > > >>> #17: Move Getting Started to Docs
> > > >>> URL: https://github.com/apache/royale-docs/pull/17
> > > >>>
> > > >>> has just been merged. Now I would like to ask someone with
> WordPress
> > > >>> access
> > > >>> to change the link on header's "GET STARTED" button and footer's
> > > "Getting
> > > >>> Started"
> > > >>>
> > > >>> from: https://royale.apache.org/getting-started/
> > > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > > >>>
> > > >>> Thanks,
> > > >>> Adrian
> > > >>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Carlos Rovira
> > > >> http://about.me/carlosrovira
> > > >>
> > > >>
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> > 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: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi Andrew,
ok, so website navigation happens on the same window and docs in its own
window. That's ok for me too.
What to do with the case of pages like "Get Started"? The link is in
website, but goes to royale docs
thanks
El jue., 16 may. 2019 a las 20:41, Andrew Wetmore (<co...@gmail.com>)
escribió:
> I think "target=_blank" should be for links to location outside of Royale
> docs. To me, that includes the Royale website. I would want it to open in a
> new window rather than taking over the window I am using to read the docs.
>
> On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi Adrian,
> >
> > I read the Get Started page. Good work! :)
> >
> > just added a link that I think was missed, change it if you think it
> should
> > point to other page.
> >
> > I want to ask about the links strategy. I see some of them that refers to
> > the same Royale-docs part has target blank while other not.
> > We talked about this when launched the website: In the website we put all
> > links to be loaded on the same page, while external links to the site
> load
> > in a blank page. I think we should do the same for Royale-docs. We just
> > need to consider if website and Royale-docs must load in the same page.
> For
> > example in website, a link to NPM will load in another page while mailing
> > list info will load in the current one.
> >
> > thanks!
> >
> >
> >
> > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> carlosrovira@apache.org
> > >)
> > escribió:
> >
> > > Hi
> > >
> > > I tried various plugin solutions for WP and no one seems to fit what we
> > > need. So I changed the url to the docs page as suggested. Going to
> > publish
> > > the site.
> > >
> > > I see the styles in headers and other things are not matching the site
> > > styles. I'll try to fix that soon.
> > >
> > > Thanks
> > >
> > >
> > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > carlosrovira@apache.org>)
> > > escribió:
> > >
> > >> Hi, I'm looking into this now: How to make website render the content
> of
> > >> a GitHub page.
> > >> About Menu I'll change to "Get Started" as Piotr suggested
> > >>
> > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > >> adrianszuszkiewicz@gmail.com>) escribió:
> > >>
> > >>> My pull request
> > >>>
> > >>> #17: Move Getting Started to Docs
> > >>> URL: https://github.com/apache/royale-docs/pull/17
> > >>>
> > >>> has just been merged. Now I would like to ask someone with WordPress
> > >>> access
> > >>> to change the link on header's "GET STARTED" button and footer's
> > "Getting
> > >>> Started"
> > >>>
> > >>> from: https://royale.apache.org/getting-started/
> > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > >>>
> > >>> Thanks,
> > >>> Adrian
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >>
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Royale Docs Changes Proposal
Posted by Andrew Wetmore <co...@gmail.com>.
I think "target=_blank" should be for links to location outside of Royale
docs. To me, that includes the Royale website. I would want it to open in a
new window rather than taking over the window I am using to read the docs.
On Thu, May 16, 2019 at 7:11 AM Carlos Rovira <ca...@apache.org>
wrote:
> Hi Adrian,
>
> I read the Get Started page. Good work! :)
>
> just added a link that I think was missed, change it if you think it should
> point to other page.
>
> I want to ask about the links strategy. I see some of them that refers to
> the same Royale-docs part has target blank while other not.
> We talked about this when launched the website: In the website we put all
> links to be loaded on the same page, while external links to the site load
> in a blank page. I think we should do the same for Royale-docs. We just
> need to consider if website and Royale-docs must load in the same page. For
> example in website, a link to NPM will load in another page while mailing
> list info will load in the current one.
>
> thanks!
>
>
>
> El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Hi
> >
> > I tried various plugin solutions for WP and no one seems to fit what we
> > need. So I changed the url to the docs page as suggested. Going to
> publish
> > the site.
> >
> > I see the styles in headers and other things are not matching the site
> > styles. I'll try to fix that soon.
> >
> > Thanks
> >
> >
> > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> carlosrovira@apache.org>)
> > escribió:
> >
> >> Hi, I'm looking into this now: How to make website render the content of
> >> a GitHub page.
> >> About Menu I'll change to "Get Started" as Piotr suggested
> >>
> >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> >> adrianszuszkiewicz@gmail.com>) escribió:
> >>
> >>> My pull request
> >>>
> >>> #17: Move Getting Started to Docs
> >>> URL: https://github.com/apache/royale-docs/pull/17
> >>>
> >>> has just been merged. Now I would like to ask someone with WordPress
> >>> access
> >>> to change the link on header's "GET STARTED" button and footer's
> "Getting
> >>> Started"
> >>>
> >>> from: https://royale.apache.org/getting-started/
> >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> >>>
> >>> Thanks,
> >>> Adrian
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
yes! I changed it, but still is in pre wp site, still didn't push it to
live. Will push in the next hours! :)
El jue., 16 may. 2019 a las 12:15, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hi Carlos,
>
> What about my proposal, cause you seems to missing that:
>
> ""Get Started" in the main menu on the website and "Getting Started" in the
> footer are pointing us to the same page, However words are different - What
> do you think to align them and have in footer "Get Started" as well?"
>
> Do you in favor of that ?
>
> czw., 16 maj 2019 o 12:11 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Adrian,
> >
> > I read the Get Started page. Good work! :)
> >
> > just added a link that I think was missed, change it if you think it
> should
> > point to other page.
> >
> > I want to ask about the links strategy. I see some of them that refers to
> > the same Royale-docs part has target blank while other not.
> > We talked about this when launched the website: In the website we put all
> > links to be loaded on the same page, while external links to the site
> load
> > in a blank page. I think we should do the same for Royale-docs. We just
> > need to consider if website and Royale-docs must load in the same page.
> For
> > example in website, a link to NPM will load in another page while mailing
> > list info will load in the current one.
> >
> > thanks!
> >
> >
> >
> > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> carlosrovira@apache.org
> > >)
> > escribió:
> >
> > > Hi
> > >
> > > I tried various plugin solutions for WP and no one seems to fit what we
> > > need. So I changed the url to the docs page as suggested. Going to
> > publish
> > > the site.
> > >
> > > I see the styles in headers and other things are not matching the site
> > > styles. I'll try to fix that soon.
> > >
> > > Thanks
> > >
> > >
> > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > carlosrovira@apache.org>)
> > > escribió:
> > >
> > >> Hi, I'm looking into this now: How to make website render the content
> of
> > >> a GitHub page.
> > >> About Menu I'll change to "Get Started" as Piotr suggested
> > >>
> > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > >> adrianszuszkiewicz@gmail.com>) escribió:
> > >>
> > >>> My pull request
> > >>>
> > >>> #17: Move Getting Started to Docs
> > >>> URL: https://github.com/apache/royale-docs/pull/17
> > >>>
> > >>> has just been merged. Now I would like to ask someone with WordPress
> > >>> access
> > >>> to change the link on header's "GET STARTED" button and footer's
> > "Getting
> > >>> Started"
> > >>>
> > >>> from: https://royale.apache.org/getting-started/
> > >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> > >>>
> > >>> Thanks,
> > >>> Adrian
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >>
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > 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: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Carlos,
What about my proposal, cause you seems to missing that:
""Get Started" in the main menu on the website and "Getting Started" in the
footer are pointing us to the same page, However words are different - What
do you think to align them and have in footer "Get Started" as well?"
Do you in favor of that ?
czw., 16 maj 2019 o 12:11 Carlos Rovira <ca...@apache.org>
napisał(a):
> Hi Adrian,
>
> I read the Get Started page. Good work! :)
>
> just added a link that I think was missed, change it if you think it should
> point to other page.
>
> I want to ask about the links strategy. I see some of them that refers to
> the same Royale-docs part has target blank while other not.
> We talked about this when launched the website: In the website we put all
> links to be loaded on the same page, while external links to the site load
> in a blank page. I think we should do the same for Royale-docs. We just
> need to consider if website and Royale-docs must load in the same page. For
> example in website, a link to NPM will load in another page while mailing
> list info will load in the current one.
>
> thanks!
>
>
>
> El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Hi
> >
> > I tried various plugin solutions for WP and no one seems to fit what we
> > need. So I changed the url to the docs page as suggested. Going to
> publish
> > the site.
> >
> > I see the styles in headers and other things are not matching the site
> > styles. I'll try to fix that soon.
> >
> > Thanks
> >
> >
> > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> carlosrovira@apache.org>)
> > escribió:
> >
> >> Hi, I'm looking into this now: How to make website render the content of
> >> a GitHub page.
> >> About Menu I'll change to "Get Started" as Piotr suggested
> >>
> >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> >> adrianszuszkiewicz@gmail.com>) escribió:
> >>
> >>> My pull request
> >>>
> >>> #17: Move Getting Started to Docs
> >>> URL: https://github.com/apache/royale-docs/pull/17
> >>>
> >>> has just been merged. Now I would like to ask someone with WordPress
> >>> access
> >>> to change the link on header's "GET STARTED" button and footer's
> "Getting
> >>> Started"
> >>>
> >>> from: https://royale.apache.org/getting-started/
> >>> to: https://apache.github.io/royale-docs/Get%20Started.html
> >>>
> >>> Thanks,
> >>> Adrian
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi Adrian,
I read the Get Started page. Good work! :)
just added a link that I think was missed, change it if you think it should
point to other page.
I want to ask about the links strategy. I see some of them that refers to
the same Royale-docs part has target blank while other not.
We talked about this when launched the website: In the website we put all
links to be loaded on the same page, while external links to the site load
in a blank page. I think we should do the same for Royale-docs. We just
need to consider if website and Royale-docs must load in the same page. For
example in website, a link to NPM will load in another page while mailing
list info will load in the current one.
thanks!
El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi
>
> I tried various plugin solutions for WP and no one seems to fit what we
> need. So I changed the url to the docs page as suggested. Going to publish
> the site.
>
> I see the styles in headers and other things are not matching the site
> styles. I'll try to fix that soon.
>
> Thanks
>
>
> El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> Hi, I'm looking into this now: How to make website render the content of
>> a GitHub page.
>> About Menu I'll change to "Get Started" as Piotr suggested
>>
>> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
>> adrianszuszkiewicz@gmail.com>) escribió:
>>
>>> My pull request
>>>
>>> #17: Move Getting Started to Docs
>>> URL: https://github.com/apache/royale-docs/pull/17
>>>
>>> has just been merged. Now I would like to ask someone with WordPress
>>> access
>>> to change the link on header's "GET STARTED" button and footer's "Getting
>>> Started"
>>>
>>> from: https://royale.apache.org/getting-started/
>>> to: https://apache.github.io/royale-docs/Get%20Started.html
>>>
>>> Thanks,
>>> Adrian
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi
I tried various plugin solutions for WP and no one seems to fit what we
need. So I changed the url to the docs page as suggested. Going to publish
the site.
I see the styles in headers and other things are not matching the site
styles. I'll try to fix that soon.
Thanks
El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi, I'm looking into this now: How to make website render the content of a
> GitHub page.
> About Menu I'll change to "Get Started" as Piotr suggested
>
> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> adrianszuszkiewicz@gmail.com>) escribió:
>
>> My pull request
>>
>> #17: Move Getting Started to Docs
>> URL: https://github.com/apache/royale-docs/pull/17
>>
>> has just been merged. Now I would like to ask someone with WordPress
>> access
>> to change the link on header's "GET STARTED" button and footer's "Getting
>> Started"
>>
>> from: https://royale.apache.org/getting-started/
>> to: https://apache.github.io/royale-docs/Get%20Started.html
>>
>> Thanks,
>> Adrian
>>
>>
>>
>> --
>> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi, I'm looking into this now: How to make website render the content of a
GitHub page.
About Menu I'll change to "Get Started" as Piotr suggested
El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
adrianszuszkiewicz@gmail.com>) escribió:
> My pull request
>
> #17: Move Getting Started to Docs
> URL: https://github.com/apache/royale-docs/pull/17
>
> has just been merged. Now I would like to ask someone with WordPress access
> to change the link on header's "GET STARTED" button and footer's "Getting
> Started"
>
> from: https://royale.apache.org/getting-started/
> to: https://apache.github.io/royale-docs/Get%20Started.html
>
> Thanks,
> Adrian
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Royale Docs Changes Proposal
Posted by Adrian Szuszkiewicz <ad...@gmail.com>.
My pull request
#17: Move Getting Started to Docs
URL: https://github.com/apache/royale-docs/pull/17
has just been merged. Now I would like to ask someone with WordPress access
to change the link on header's "GET STARTED" button and footer's "Getting
Started"
from: https://royale.apache.org/getting-started/
to: https://apache.github.io/royale-docs/Get%20Started.html
Thanks,
Adrian
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Royale Docs Changes Proposal
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Guys,
One small thing apart of above changes which are in progress. "Get Started"
in the main menu on the website and "Getting Started" in the footer are
pointing us to the same page. Words are different - What do you think to
align them and have in footer "Get Started" as well?
Thanks,
Piotr
śr., 8 maj 2019 o 10:04 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Andrian,
>
> thanks for joining us. I think you're right, so for me is ok to start
> helping in docs and videos since is our main focus now.
>
> Thanks and welcome to Apache Royale! :)
>
>
>
> El mié., 8 may. 2019 a las 9:16, Yishay Weiss (<yi...@hotmail.com>)
> escribió:
>
> > Hi Adrian and Welcome,
> >
> >
> >
> > These changes all sound good to me.
> >
> >
> >
> > Yishay
> >
> >
> >
> > ________________________________
> > From: Adrian Szuszkiewicz <ad...@gmail.com>
> > Sent: Tuesday, May 7, 2019 6:47:56 PM
> > To: dev@royale.apache.org
> > Subject: Royale Docs Changes Proposal
> >
> > Hi all :)
> >
> > Introduction
> >
> > My name is Adrian and together with Piotr I am preparing a set of video
> > tutorials about Moonshine IDE, Royale and ActionScript. I am completely
> new
> > to this technology stack and a few days ago I was reading Royale Docs for
> > the first time. There were a couple of things I found confusing about the
> > structure of the documentation. I believe that with a few minor changes
> to
> > the docs we can achieve more clarity. If the Team agrees I volunteer to
> do
> > the changes. Here’s what I propose:
> >
> > Merging Getting Started
> >
> > There are two pages with awfully similar titles and responsibilities:
> >
> > -
> >
> > Getting Started [https://royale.apache.org/getting-started/]
> reachable
> > from "Get Started" button on main Royale page
> > -
> >
> > Get started with Royale [
> > https://apache.github.io/royale-docs/Get%20Started.html] reachable
> from
> > "Get Started" item in doc’s table of content.
> >
> > In my opinion, the existence of two Get Started pages is very confusing.
> If
> > you agree I’d like to:
> >
> > 1.
> >
> > Move all the content of Getting Started page to Get started with
> Royale
> > in
> > the docs
> > 2.
> >
> > Make Get Started button on main Royale page point to Get started with
> > Royale in the docs.
> >
> >
> > Renaming Links with Instructions
> >
> > On "Getting Started" page there are four links with instructions about
> how
> > to install and configure Royale in different editors. When I was reading
> > the docs for the first time I skipped those links because I thought they
> > only point to download locations, not the instructions. I’d like to
> rename
> > them as follows:
> >
> > -
> >
> > “Moonshine IDE” -> “Instructions for Moonshine IDE”
> > -
> >
> > “Visual Studio Code” -> “Instructions for Visual Studio Code”
> > -
> >
> > “Adobe Flash Builder” -> “Instructions for Adobe Flash Builder”
> > -
> >
> > “IntelliJ IDEA” -> “Instructions for IntelliJ IDEA” [this link is
> empty
> > but I’d keep it anyway]
> >
> >
> > Changing Menu Behavior
> >
> > The Table of Content menu on the right side in the docs behaves in a
> weird
> > way. When you click on an item it doesn't automatically expand. But when
> > you select your topic from the main text then it expands correctly
> showing
> > all its children. At first, I thought the menu was incomplete and
> > disjointed but then I realized it just doesn’t expand at right times. It
> > made me feel a little bit lost in the docs and track my journey through
> > them in the notepad. If you agree I’d like to fix expanding behavior.
> >
> > It's easier to conceptualize this in a video:
> > https://www.youtube.com/watch?v=GHzDnH8h6gE&feature=youtu.be
> >
> >
> > Have a great day,
> >
> > Adrian
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Royale Docs Changes Proposal
Posted by Carlos Rovira <ca...@apache.org>.
Hi Andrian,
thanks for joining us. I think you're right, so for me is ok to start
helping in docs and videos since is our main focus now.
Thanks and welcome to Apache Royale! :)
El mié., 8 may. 2019 a las 9:16, Yishay Weiss (<yi...@hotmail.com>)
escribió:
> Hi Adrian and Welcome,
>
>
>
> These changes all sound good to me.
>
>
>
> Yishay
>
>
>
> ________________________________
> From: Adrian Szuszkiewicz <ad...@gmail.com>
> Sent: Tuesday, May 7, 2019 6:47:56 PM
> To: dev@royale.apache.org
> Subject: Royale Docs Changes Proposal
>
> Hi all :)
>
> Introduction
>
> My name is Adrian and together with Piotr I am preparing a set of video
> tutorials about Moonshine IDE, Royale and ActionScript. I am completely new
> to this technology stack and a few days ago I was reading Royale Docs for
> the first time. There were a couple of things I found confusing about the
> structure of the documentation. I believe that with a few minor changes to
> the docs we can achieve more clarity. If the Team agrees I volunteer to do
> the changes. Here’s what I propose:
>
> Merging Getting Started
>
> There are two pages with awfully similar titles and responsibilities:
>
> -
>
> Getting Started [https://royale.apache.org/getting-started/] reachable
> from "Get Started" button on main Royale page
> -
>
> Get started with Royale [
> https://apache.github.io/royale-docs/Get%20Started.html] reachable from
> "Get Started" item in doc’s table of content.
>
> In my opinion, the existence of two Get Started pages is very confusing. If
> you agree I’d like to:
>
> 1.
>
> Move all the content of Getting Started page to Get started with Royale
> in
> the docs
> 2.
>
> Make Get Started button on main Royale page point to Get started with
> Royale in the docs.
>
>
> Renaming Links with Instructions
>
> On "Getting Started" page there are four links with instructions about how
> to install and configure Royale in different editors. When I was reading
> the docs for the first time I skipped those links because I thought they
> only point to download locations, not the instructions. I’d like to rename
> them as follows:
>
> -
>
> “Moonshine IDE” -> “Instructions for Moonshine IDE”
> -
>
> “Visual Studio Code” -> “Instructions for Visual Studio Code”
> -
>
> “Adobe Flash Builder” -> “Instructions for Adobe Flash Builder”
> -
>
> “IntelliJ IDEA” -> “Instructions for IntelliJ IDEA” [this link is empty
> but I’d keep it anyway]
>
>
> Changing Menu Behavior
>
> The Table of Content menu on the right side in the docs behaves in a weird
> way. When you click on an item it doesn't automatically expand. But when
> you select your topic from the main text then it expands correctly showing
> all its children. At first, I thought the menu was incomplete and
> disjointed but then I realized it just doesn’t expand at right times. It
> made me feel a little bit lost in the docs and track my journey through
> them in the notepad. If you agree I’d like to fix expanding behavior.
>
> It's easier to conceptualize this in a video:
> https://www.youtube.com/watch?v=GHzDnH8h6gE&feature=youtu.be
>
>
> Have a great day,
>
> Adrian
>
--
Carlos Rovira
http://about.me/carlosrovira
RE: Royale Docs Changes Proposal
Posted by Yishay Weiss <yi...@hotmail.com>.
Hi Adrian and Welcome,
These changes all sound good to me.
Yishay
________________________________
From: Adrian Szuszkiewicz <ad...@gmail.com>
Sent: Tuesday, May 7, 2019 6:47:56 PM
To: dev@royale.apache.org
Subject: Royale Docs Changes Proposal
Hi all :)
Introduction
My name is Adrian and together with Piotr I am preparing a set of video
tutorials about Moonshine IDE, Royale and ActionScript. I am completely new
to this technology stack and a few days ago I was reading Royale Docs for
the first time. There were a couple of things I found confusing about the
structure of the documentation. I believe that with a few minor changes to
the docs we can achieve more clarity. If the Team agrees I volunteer to do
the changes. Here’s what I propose:
Merging Getting Started
There are two pages with awfully similar titles and responsibilities:
-
Getting Started [https://royale.apache.org/getting-started/] reachable
from "Get Started" button on main Royale page
-
Get started with Royale [
https://apache.github.io/royale-docs/Get%20Started.html] reachable from
"Get Started" item in doc’s table of content.
In my opinion, the existence of two Get Started pages is very confusing. If
you agree I’d like to:
1.
Move all the content of Getting Started page to Get started with Royale in
the docs
2.
Make Get Started button on main Royale page point to Get started with
Royale in the docs.
Renaming Links with Instructions
On "Getting Started" page there are four links with instructions about how
to install and configure Royale in different editors. When I was reading
the docs for the first time I skipped those links because I thought they
only point to download locations, not the instructions. I’d like to rename
them as follows:
-
“Moonshine IDE” -> “Instructions for Moonshine IDE”
-
“Visual Studio Code” -> “Instructions for Visual Studio Code”
-
“Adobe Flash Builder” -> “Instructions for Adobe Flash Builder”
-
“IntelliJ IDEA” -> “Instructions for IntelliJ IDEA” [this link is empty
but I’d keep it anyway]
Changing Menu Behavior
The Table of Content menu on the right side in the docs behaves in a weird
way. When you click on an item it doesn't automatically expand. But when
you select your topic from the main text then it expands correctly showing
all its children. At first, I thought the menu was incomplete and
disjointed but then I realized it just doesn’t expand at right times. It
made me feel a little bit lost in the docs and track my journey through
them in the notepad. If you agree I’d like to fix expanding behavior.
It's easier to conceptualize this in a video:
https://www.youtube.com/watch?v=GHzDnH8h6gE&feature=youtu.be
Have a great day,
Adrian