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 <carlosrov...@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 (<cottag...@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 <carlosrov...@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 (< > > carlosrov...@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 (< > > > carlosrov...@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 (< > > > >> adrianszuszkiew...@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>*
