You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2019/10/01 09:55:41 UTC
About Royale Docs Improvements over latest months
Hi,
about latest changes in docs done is latest months. This is a summary of
the work done (still in progress at some points):
About layout, search and usability:
* Now we have a more polished layout that should work right on desktop,
tablet and mobile, making more easy for new users coming to Royale learn
about it
* The sidebar menu will show on the right as normal in tablet and desktop.
In mobile shows a button on the right side that make the menu slide from
the right
* Now we have search functionality implemented thanks to Algolia search.
The index is crawled every 24h. Take into account if you make some change
and don't see it when searching as you upload the change.
* Main menu now turns to dropdown if there's no enough room to show it
horizontally
About content:
* Added global styles for better readability and support of most of the
markdown options and highlighting of code (specially for AS3 and MXML)
* Now all pages has "description" and "permalink" in the head section to
improve sharing and searching on internet. Remember to add this lines so we
make all navigation consistent with the rest of pages. If someone notice a
page without this, please add it or report it.
* Added metadata for sharing in social networks more easily capturing the
previous point plus screenshot and name.
* I tried to bring pages to the index that was still missing so we have
most of the overall structure in place. I'm pretty sure there's still
missing concepts and things to bring to the docs, so keep your eyes open to
see what could still be missing and report it or add yourself.
* Notice that some of that content is still a page mostly empty and waiting
to be filled. You're all invited to do so, just let others know about it to
avoid duplicate efforts.
* For Component Sets, I started to create a page per component where we add
the most needed info to start with the component. It then refers to ASDocs
for a full spec and access to all classes. I'm working on Jewel. Others are
invited to use Jewel finished pages and use it as template for Basic,
MXRoyale and other sets, and/or create new ones for components that are not
similar and there's no counterpart on Jewel.
* I added live content on Jewel components, since visual running examples
are very powerful.
* I added live example on the GitHub tutorial app.
* I added many cross link references between Royale-docs, blog examples and
ASDocs pages. Content must be in only one place but that content should be
linked with the rest of royale contents in our network.
* I tried to format all the pages I could to get most of the new visuals
created, but I'm sure threr's still content to format, we can do this
between all here, and anyone coming to Royale and browse content is invited
to help in this point as well to submit more content to be reviewed and
added.
* I refactored all license pages to make all consistent with one style.
To Help:
I think there's many content already done and formatted in the right way to
make others be able to add content that aligns to the rest of the doc
pages. Andrew and I are here to help to give the finished results that
conform to actual specs.
There's still many things to do to get a full docs site. This is the list
of things I see:
* Fill Features and concepts pages still empty (View States, Data Binding,
RPC methods pages, ....). I think this can be the most important ones since
are core concepts in Royale.
* Complete Jewel and other sets reference pages. Very important for people
coming. Here I plan to add for Jewel "style specs" too as someone mentioned
some days ago, and I think this will be a very good idea.
* Add Crux documentation, that should come in part from swiz framework docs
What more things you still think are missing?
Thanks
--
Carlos Rovira
http://about.me/carlosrovira
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Great Harbs!
hope to hear from you soon :)
El vie., 18 oct. 2019 a las 15:28, Harbs (<ha...@gmail.com>) escribió:
> I hope to do it after the Jewish holidays.
>
> > On Oct 18, 2019, at 12:26 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi Piotr,
> > that's great. Hope Harbs, Yishay, Pashmina, Josh, Greg and others could
> > give some word about it.
> > I think 3-4 will be ok to start that page.
> > Thanks
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Harbs <ha...@gmail.com>.
I hope to do it after the Jewish holidays.
> On Oct 18, 2019, at 12:26 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Piotr,
> that's great. Hope Harbs, Yishay, Pashmina, Josh, Greg and others could
> give some word about it.
> I think 3-4 will be ok to start that page.
> Thanks
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
that's great. Hope Harbs, Yishay, Pashmina, Josh, Greg and others could
give some word about it.
I think 3-4 will be ok to start that page.
Thanks
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Piotr Zarzycki <pi...@gmail.com>.
My plate is full, but I promise to mention that to Prominic so they can put
some words about Royale usage. They are pretty happy with the port result
so far, so this should be very very positive :)
śr., 16 paź 2019 o 23:33 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi folks,
>
> please remember we have this request open. It's very few time for you you
> all, just invest 5 minutes in send a phrase, name, job and picture to
> appear in out testimonials page :)
>
> This can sum to the rest of things that will make others want to use Royale
>
>
> El vie., 4 oct. 2019 a las 10:19, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Thanks Andrew!
> >
> > I look forward to at least 2 more (better 3) to be able to mount the
> > page. We look forward to your help in this regard! :)
> >
> >
> > El jue., 3 oct. 2019 a las 22:40, Andrew Wetmore (<co...@gmail.com>)
> > escribió:
> >
> >> "Apache Royale captures the best of Apache Flex and the best of new
> trends
> >> in web development, so it's the best of both worlds. We migrated a Flex
> >> application to JavaScript in significantly less time than it would have
> >> taken using the most popular JavaScript frameworks. The productivity,
> >> programming model and combination of OOP and declarative languages make
> >> Apache Royale a very solid development environment and a lot of fun to
> >> work
> >> with! :)"
> >>
> >> On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira <ca...@apache.org>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > Here's main that could serve as well as example (@Andrew if you can
> fix
> >> any
> >> > grammar disaster I could make, please go ahead! :D) :
> >> >
> >> > -------------
> >> >
> >> > "Apache Royale captures the best of Apache Flex and the best of new
> >> trends
> >> > in web development, so it's best of both worlds. We migrated a Flex
> >> > application to javascript in significant less time than using the
> >> current
> >> > top notch javascript frameworks out there. The productivity, the
> >> programing
> >> > model and the combination of OOP and declarative languages makes it a
> >> very
> >> > solid tech and very fun to work with! :)"
> >> >
> >> > Carlos Rovira
> >> > Executive Chairman at Codeoscopic
> >> >
> >> > profile img to use: EB6igxEXYAE-PvU
> >> > <https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg&name=large>
> >> >
> >> > --------------
> >> >
> >> > I think is a small contribution that could be of help in our site.
> >> Harbs,
> >> > Yishay, Piotr, and the rest...please take this request into
> >> consideration
> >> > so we can fill the page with at least 4+ of this.
> >> >
> >> > thanks
> >> >
> >> > El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<
> >> carlosrovira@apache.org
> >> > >)
> >> > escribió:
> >> >
> >> > > Hi all,
> >> > >
> >> > > we are talking about add a new "Testimonials" page were people could
> >> > share
> >> > > "How ApacheRoyale has helped" (you, your project, your company...)
> >> with a
> >> > > new app, or a migration from Flex.
> >> > >
> >> > > Please submit to this thread a phrase or a paragraph that will
> capture
> >> > > that topic for you and help us to fill that page with useful
> >> information
> >> > > for others that come to Apache Royale.
> >> > > (Note: Take into account that anyone that do this contribution is
> >> under
> >> > > the assumption that allows us to use his phrase, name and info
> >> submitted
> >> > in
> >> > > out website as a Testimonial in that page and submitting implies
> give
> >> us
> >> > > permission to do that :))
> >> > >
> >> > > Please provide an image as well for the profile. It can be your
> >> portrait,
> >> > > or if you don't want your photo in our website, you can send us
> other
> >> > > image(photo, logo or graphic) that represents you, to enhance the
> >> > > testimonial. We reserve the option to use it or not depending on the
> >> > image
> >> > > provided if we think is not appropriate or could infringe some
> >> copyright
> >> > or
> >> > > rule. For this reason, please try to use original content and
> nothing
> >> > that
> >> > > could be offensive or problematic with any of the Apache rules or
> the
> >> > > common sense :)
> >> > >
> >> > > This will help others to decide to join us or use Royale since
> others
> >> had
> >> > > success in using it.
> >> > >
> >> > > Thanks all for your contribution to this page!! That will be of
> great
> >> > > help! :)
> >> > >
> >> > > Carlos
> >> > >
> >> > >
> >> > >
> >> > > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
> >> > carlosrovira@apache.org>)
> >> > > escribió:
> >> > >
> >> > >> Hi,
> >> > >> we can add testimonials page (as an additional page a part from
> >> showcase
> >> > >> page). The actual theme has that integrated that will be easy to
> do.
> >> > >> Will start a thread so others can write its own testimonial to be
> >> added.
> >> > >>
> >> > >> Thanks for the suggestion :)
> >> > >>
> >> > >>
> >> > >>
> >> > >> El mar., 1 oct. 2019 a las 19:37, Alex Harui
> >> (<aharui@adobe.com.invalid
> >> > >)
> >> > >> escribió:
> >> > >>
> >> > >>> The showcase would be great, but if it is easier/faster to simply
> >> have
> >> > a
> >> > >>> page of links to blogs of our committers like you and Harbs that
> >> just
> >> > >>> contain a paragraph or two about how Royale has helped, that might
> >> be a
> >> > >>> good place to start.
> >> > >>>
> >> > >>> -Alex
> >> > >>>
> >> > >>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org>
> >> > wrote:
> >> > >>>
> >> > >>> Hi Alex,
> >> > >>>
> >> > >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
> >> > >>> (<ah...@adobe.com.invalid>)
> >> > >>> escribió:
> >> > >>>
> >> > >>> > Thanks for working on the docs.
> >> > >>> >
> >> > >>> > Beyond the docs, what I would most like to see is "success
> >> > >>> stories". I
> >> > >>> > keep thinking it would help if it was easier for folks to
> read
> >> > >>> about how
> >> > >>> > Royale has helped.
> >> > >>> >
> >> > >>>
> >> > >>> You refer to "showcase" page?
> >> > >>>
> >> > >>>
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> >> > >>> I still has that on my plate. I have to plan the info to
> >> showcase
> >> > >>> and post
> >> > >>> so people can submit about it
> >> > >>> But yes is one of the important pieces to work on. I'll try to
> >> get
> >> > >>> over it
> >> > >>> soon.
> >> > >>>
> >> > >>> thanks
> >> > >>>
> >> > >> --
> >> > > Carlos Rovira
> >> > > http://about.me/carlosrovira
> >> > >
> >> > >
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >>
> >
> >
> > --
> > 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: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Hi folks,
please remember we have this request open. It's very few time for you you
all, just invest 5 minutes in send a phrase, name, job and picture to
appear in out testimonials page :)
This can sum to the rest of things that will make others want to use Royale
El vie., 4 oct. 2019 a las 10:19, Carlos Rovira (<ca...@apache.org>)
escribió:
> Thanks Andrew!
>
> I look forward to at least 2 more (better 3) to be able to mount the
> page. We look forward to your help in this regard! :)
>
>
> El jue., 3 oct. 2019 a las 22:40, Andrew Wetmore (<co...@gmail.com>)
> escribió:
>
>> "Apache Royale captures the best of Apache Flex and the best of new trends
>> in web development, so it's the best of both worlds. We migrated a Flex
>> application to JavaScript in significantly less time than it would have
>> taken using the most popular JavaScript frameworks. The productivity,
>> programming model and combination of OOP and declarative languages make
>> Apache Royale a very solid development environment and a lot of fun to
>> work
>> with! :)"
>>
>> On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira <ca...@apache.org>
>> wrote:
>>
>> > Hi,
>> >
>> > Here's main that could serve as well as example (@Andrew if you can fix
>> any
>> > grammar disaster I could make, please go ahead! :D) :
>> >
>> > -------------
>> >
>> > "Apache Royale captures the best of Apache Flex and the best of new
>> trends
>> > in web development, so it's best of both worlds. We migrated a Flex
>> > application to javascript in significant less time than using the
>> current
>> > top notch javascript frameworks out there. The productivity, the
>> programing
>> > model and the combination of OOP and declarative languages makes it a
>> very
>> > solid tech and very fun to work with! :)"
>> >
>> > Carlos Rovira
>> > Executive Chairman at Codeoscopic
>> >
>> > profile img to use: EB6igxEXYAE-PvU
>> > <https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg&name=large>
>> >
>> > --------------
>> >
>> > I think is a small contribution that could be of help in our site.
>> Harbs,
>> > Yishay, Piotr, and the rest...please take this request into
>> consideration
>> > so we can fill the page with at least 4+ of this.
>> >
>> > thanks
>> >
>> > El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<
>> carlosrovira@apache.org
>> > >)
>> > escribió:
>> >
>> > > Hi all,
>> > >
>> > > we are talking about add a new "Testimonials" page were people could
>> > share
>> > > "How ApacheRoyale has helped" (you, your project, your company...)
>> with a
>> > > new app, or a migration from Flex.
>> > >
>> > > Please submit to this thread a phrase or a paragraph that will capture
>> > > that topic for you and help us to fill that page with useful
>> information
>> > > for others that come to Apache Royale.
>> > > (Note: Take into account that anyone that do this contribution is
>> under
>> > > the assumption that allows us to use his phrase, name and info
>> submitted
>> > in
>> > > out website as a Testimonial in that page and submitting implies give
>> us
>> > > permission to do that :))
>> > >
>> > > Please provide an image as well for the profile. It can be your
>> portrait,
>> > > or if you don't want your photo in our website, you can send us other
>> > > image(photo, logo or graphic) that represents you, to enhance the
>> > > testimonial. We reserve the option to use it or not depending on the
>> > image
>> > > provided if we think is not appropriate or could infringe some
>> copyright
>> > or
>> > > rule. For this reason, please try to use original content and nothing
>> > that
>> > > could be offensive or problematic with any of the Apache rules or the
>> > > common sense :)
>> > >
>> > > This will help others to decide to join us or use Royale since others
>> had
>> > > success in using it.
>> > >
>> > > Thanks all for your contribution to this page!! That will be of great
>> > > help! :)
>> > >
>> > > Carlos
>> > >
>> > >
>> > >
>> > > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
>> > carlosrovira@apache.org>)
>> > > escribió:
>> > >
>> > >> Hi,
>> > >> we can add testimonials page (as an additional page a part from
>> showcase
>> > >> page). The actual theme has that integrated that will be easy to do.
>> > >> Will start a thread so others can write its own testimonial to be
>> added.
>> > >>
>> > >> Thanks for the suggestion :)
>> > >>
>> > >>
>> > >>
>> > >> El mar., 1 oct. 2019 a las 19:37, Alex Harui
>> (<aharui@adobe.com.invalid
>> > >)
>> > >> escribió:
>> > >>
>> > >>> The showcase would be great, but if it is easier/faster to simply
>> have
>> > a
>> > >>> page of links to blogs of our committers like you and Harbs that
>> just
>> > >>> contain a paragraph or two about how Royale has helped, that might
>> be a
>> > >>> good place to start.
>> > >>>
>> > >>> -Alex
>> > >>>
>> > >>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org>
>> > wrote:
>> > >>>
>> > >>> Hi Alex,
>> > >>>
>> > >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
>> > >>> (<ah...@adobe.com.invalid>)
>> > >>> escribió:
>> > >>>
>> > >>> > Thanks for working on the docs.
>> > >>> >
>> > >>> > Beyond the docs, what I would most like to see is "success
>> > >>> stories". I
>> > >>> > keep thinking it would help if it was easier for folks to read
>> > >>> about how
>> > >>> > Royale has helped.
>> > >>> >
>> > >>>
>> > >>> You refer to "showcase" page?
>> > >>>
>> > >>>
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
>> > >>> I still has that on my plate. I have to plan the info to
>> showcase
>> > >>> and post
>> > >>> so people can submit about it
>> > >>> But yes is one of the important pieces to work on. I'll try to
>> get
>> > >>> over it
>> > >>> soon.
>> > >>>
>> > >>> thanks
>> > >>>
>> > >> --
>> > > Carlos Rovira
>> > > http://about.me/carlosrovira
>> > >
>> > >
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>>
>>
>> --
>> Andrew Wetmore
>>
>> http://cottage14.blogspot.com/
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Thanks Andrew!
I look forward to at least 2 more (better 3) to be able to mount the
page. We look forward to your help in this regard! :)
El jue., 3 oct. 2019 a las 22:40, Andrew Wetmore (<co...@gmail.com>)
escribió:
> "Apache Royale captures the best of Apache Flex and the best of new trends
> in web development, so it's the best of both worlds. We migrated a Flex
> application to JavaScript in significantly less time than it would have
> taken using the most popular JavaScript frameworks. The productivity,
> programming model and combination of OOP and declarative languages make
> Apache Royale a very solid development environment and a lot of fun to work
> with! :)"
>
> On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi,
> >
> > Here's main that could serve as well as example (@Andrew if you can fix
> any
> > grammar disaster I could make, please go ahead! :D) :
> >
> > -------------
> >
> > "Apache Royale captures the best of Apache Flex and the best of new
> trends
> > in web development, so it's best of both worlds. We migrated a Flex
> > application to javascript in significant less time than using the current
> > top notch javascript frameworks out there. The productivity, the
> programing
> > model and the combination of OOP and declarative languages makes it a
> very
> > solid tech and very fun to work with! :)"
> >
> > Carlos Rovira
> > Executive Chairman at Codeoscopic
> >
> > profile img to use: EB6igxEXYAE-PvU
> > <https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg&name=large>
> >
> > --------------
> >
> > I think is a small contribution that could be of help in our site. Harbs,
> > Yishay, Piotr, and the rest...please take this request into consideration
> > so we can fill the page with at least 4+ of this.
> >
> > thanks
> >
> > El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<
> carlosrovira@apache.org
> > >)
> > escribió:
> >
> > > Hi all,
> > >
> > > we are talking about add a new "Testimonials" page were people could
> > share
> > > "How ApacheRoyale has helped" (you, your project, your company...)
> with a
> > > new app, or a migration from Flex.
> > >
> > > Please submit to this thread a phrase or a paragraph that will capture
> > > that topic for you and help us to fill that page with useful
> information
> > > for others that come to Apache Royale.
> > > (Note: Take into account that anyone that do this contribution is under
> > > the assumption that allows us to use his phrase, name and info
> submitted
> > in
> > > out website as a Testimonial in that page and submitting implies give
> us
> > > permission to do that :))
> > >
> > > Please provide an image as well for the profile. It can be your
> portrait,
> > > or if you don't want your photo in our website, you can send us other
> > > image(photo, logo or graphic) that represents you, to enhance the
> > > testimonial. We reserve the option to use it or not depending on the
> > image
> > > provided if we think is not appropriate or could infringe some
> copyright
> > or
> > > rule. For this reason, please try to use original content and nothing
> > that
> > > could be offensive or problematic with any of the Apache rules or the
> > > common sense :)
> > >
> > > This will help others to decide to join us or use Royale since others
> had
> > > success in using it.
> > >
> > > Thanks all for your contribution to this page!! That will be of great
> > > help! :)
> > >
> > > Carlos
> > >
> > >
> > >
> > > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
> > carlosrovira@apache.org>)
> > > escribió:
> > >
> > >> Hi,
> > >> we can add testimonials page (as an additional page a part from
> showcase
> > >> page). The actual theme has that integrated that will be easy to do.
> > >> Will start a thread so others can write its own testimonial to be
> added.
> > >>
> > >> Thanks for the suggestion :)
> > >>
> > >>
> > >>
> > >> El mar., 1 oct. 2019 a las 19:37, Alex Harui
> (<aharui@adobe.com.invalid
> > >)
> > >> escribió:
> > >>
> > >>> The showcase would be great, but if it is easier/faster to simply
> have
> > a
> > >>> page of links to blogs of our committers like you and Harbs that just
> > >>> contain a paragraph or two about how Royale has helped, that might
> be a
> > >>> good place to start.
> > >>>
> > >>> -Alex
> > >>>
> > >>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org>
> > wrote:
> > >>>
> > >>> Hi Alex,
> > >>>
> > >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
> > >>> (<ah...@adobe.com.invalid>)
> > >>> escribió:
> > >>>
> > >>> > Thanks for working on the docs.
> > >>> >
> > >>> > Beyond the docs, what I would most like to see is "success
> > >>> stories". I
> > >>> > keep thinking it would help if it was easier for folks to read
> > >>> about how
> > >>> > Royale has helped.
> > >>> >
> > >>>
> > >>> You refer to "showcase" page?
> > >>>
> > >>>
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> > >>> I still has that on my plate. I have to plan the info to showcase
> > >>> and post
> > >>> so people can submit about it
> > >>> But yes is one of the important pieces to work on. I'll try to
> get
> > >>> over it
> > >>> soon.
> > >>>
> > >>> thanks
> > >>>
> > >> --
> > > 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: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Andrew Wetmore <co...@gmail.com>.
"Apache Royale captures the best of Apache Flex and the best of new trends
in web development, so it's the best of both worlds. We migrated a Flex
application to JavaScript in significantly less time than it would have
taken using the most popular JavaScript frameworks. The productivity,
programming model and combination of OOP and declarative languages make
Apache Royale a very solid development environment and a lot of fun to work
with! :)"
On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira <ca...@apache.org>
wrote:
> Hi,
>
> Here's main that could serve as well as example (@Andrew if you can fix any
> grammar disaster I could make, please go ahead! :D) :
>
> -------------
>
> "Apache Royale captures the best of Apache Flex and the best of new trends
> in web development, so it's best of both worlds. We migrated a Flex
> application to javascript in significant less time than using the current
> top notch javascript frameworks out there. The productivity, the programing
> model and the combination of OOP and declarative languages makes it a very
> solid tech and very fun to work with! :)"
>
> Carlos Rovira
> Executive Chairman at Codeoscopic
>
> profile img to use: EB6igxEXYAE-PvU
> <https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg&name=large>
>
> --------------
>
> I think is a small contribution that could be of help in our site. Harbs,
> Yishay, Piotr, and the rest...please take this request into consideration
> so we can fill the page with at least 4+ of this.
>
> thanks
>
> El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<carlosrovira@apache.org
> >)
> escribió:
>
> > Hi all,
> >
> > we are talking about add a new "Testimonials" page were people could
> share
> > "How ApacheRoyale has helped" (you, your project, your company...) with a
> > new app, or a migration from Flex.
> >
> > Please submit to this thread a phrase or a paragraph that will capture
> > that topic for you and help us to fill that page with useful information
> > for others that come to Apache Royale.
> > (Note: Take into account that anyone that do this contribution is under
> > the assumption that allows us to use his phrase, name and info submitted
> in
> > out website as a Testimonial in that page and submitting implies give us
> > permission to do that :))
> >
> > Please provide an image as well for the profile. It can be your portrait,
> > or if you don't want your photo in our website, you can send us other
> > image(photo, logo or graphic) that represents you, to enhance the
> > testimonial. We reserve the option to use it or not depending on the
> image
> > provided if we think is not appropriate or could infringe some copyright
> or
> > rule. For this reason, please try to use original content and nothing
> that
> > could be offensive or problematic with any of the Apache rules or the
> > common sense :)
> >
> > This will help others to decide to join us or use Royale since others had
> > success in using it.
> >
> > Thanks all for your contribution to this page!! That will be of great
> > help! :)
> >
> > Carlos
> >
> >
> >
> > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
> carlosrovira@apache.org>)
> > escribió:
> >
> >> Hi,
> >> we can add testimonials page (as an additional page a part from showcase
> >> page). The actual theme has that integrated that will be easy to do.
> >> Will start a thread so others can write its own testimonial to be added.
> >>
> >> Thanks for the suggestion :)
> >>
> >>
> >>
> >> El mar., 1 oct. 2019 a las 19:37, Alex Harui (<aharui@adobe.com.invalid
> >)
> >> escribió:
> >>
> >>> The showcase would be great, but if it is easier/faster to simply have
> a
> >>> page of links to blogs of our committers like you and Harbs that just
> >>> contain a paragraph or two about how Royale has helped, that might be a
> >>> good place to start.
> >>>
> >>> -Alex
> >>>
> >>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >>>
> >>> Hi Alex,
> >>>
> >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
> >>> (<ah...@adobe.com.invalid>)
> >>> escribió:
> >>>
> >>> > Thanks for working on the docs.
> >>> >
> >>> > Beyond the docs, what I would most like to see is "success
> >>> stories". I
> >>> > keep thinking it would help if it was easier for folks to read
> >>> about how
> >>> > Royale has helped.
> >>> >
> >>>
> >>> You refer to "showcase" page?
> >>>
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> >>> I still has that on my plate. I have to plan the info to showcase
> >>> and post
> >>> so people can submit about it
> >>> But yes is one of the important pieces to work on. I'll try to get
> >>> over it
> >>> soon.
> >>>
> >>> thanks
> >>>
> >> --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
Here's main that could serve as well as example (@Andrew if you can fix any
grammar disaster I could make, please go ahead! :D) :
-------------
"Apache Royale captures the best of Apache Flex and the best of new trends
in web development, so it's best of both worlds. We migrated a Flex
application to javascript in significant less time than using the current
top notch javascript frameworks out there. The productivity, the programing
model and the combination of OOP and declarative languages makes it a very
solid tech and very fun to work with! :)"
Carlos Rovira
Executive Chairman at Codeoscopic
profile img to use: EB6igxEXYAE-PvU
<https://pbs.twimg.com/media/EB6igxEXYAE-PvU?format=jpg&name=large>
--------------
I think is a small contribution that could be of help in our site. Harbs,
Yishay, Piotr, and the rest...please take this request into consideration
so we can fill the page with at least 4+ of this.
thanks
El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi all,
>
> we are talking about add a new "Testimonials" page were people could share
> "How ApacheRoyale has helped" (you, your project, your company...) with a
> new app, or a migration from Flex.
>
> Please submit to this thread a phrase or a paragraph that will capture
> that topic for you and help us to fill that page with useful information
> for others that come to Apache Royale.
> (Note: Take into account that anyone that do this contribution is under
> the assumption that allows us to use his phrase, name and info submitted in
> out website as a Testimonial in that page and submitting implies give us
> permission to do that :))
>
> Please provide an image as well for the profile. It can be your portrait,
> or if you don't want your photo in our website, you can send us other
> image(photo, logo or graphic) that represents you, to enhance the
> testimonial. We reserve the option to use it or not depending on the image
> provided if we think is not appropriate or could infringe some copyright or
> rule. For this reason, please try to use original content and nothing that
> could be offensive or problematic with any of the Apache rules or the
> common sense :)
>
> This will help others to decide to join us or use Royale since others had
> success in using it.
>
> Thanks all for your contribution to this page!! That will be of great
> help! :)
>
> Carlos
>
>
>
> El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<ca...@apache.org>)
> escribió:
>
>> Hi,
>> we can add testimonials page (as an additional page a part from showcase
>> page). The actual theme has that integrated that will be easy to do.
>> Will start a thread so others can write its own testimonial to be added.
>>
>> Thanks for the suggestion :)
>>
>>
>>
>> El mar., 1 oct. 2019 a las 19:37, Alex Harui (<ah...@adobe.com.invalid>)
>> escribió:
>>
>>> The showcase would be great, but if it is easier/faster to simply have a
>>> page of links to blogs of our committers like you and Harbs that just
>>> contain a paragraph or two about how Royale has helped, that might be a
>>> good place to start.
>>>
>>> -Alex
>>>
>>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>>>
>>> Hi Alex,
>>>
>>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
>>> (<ah...@adobe.com.invalid>)
>>> escribió:
>>>
>>> > Thanks for working on the docs.
>>> >
>>> > Beyond the docs, what I would most like to see is "success
>>> stories". I
>>> > keep thinking it would help if it was easier for folks to read
>>> about how
>>> > Royale has helped.
>>> >
>>>
>>> You refer to "showcase" page?
>>>
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
>>> I still has that on my plate. I have to plan the info to showcase
>>> and post
>>> so people can submit about it
>>> But yes is one of the important pieces to work on. I'll try to get
>>> over it
>>> soon.
>>>
>>> thanks
>>>
>> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Testimonials Page (Was: Re: About Royale Docs Improvements over
latest months)
Posted by Carlos Rovira <ca...@apache.org>.
Hi all,
we are talking about add a new "Testimonials" page were people could share
"How ApacheRoyale has helped" (you, your project, your company...) with a
new app, or a migration from Flex.
Please submit to this thread a phrase or a paragraph that will capture that
topic for you and help us to fill that page with useful information for
others that come to Apache Royale.
(Note: Take into account that anyone that do this contribution is under the
assumption that allows us to use his phrase, name and info submitted in out
website as a Testimonial in that page and submitting implies give us
permission to do that :))
Please provide an image as well for the profile. It can be your portrait,
or if you don't want your photo in our website, you can send us other
image(photo, logo or graphic) that represents you, to enhance the
testimonial. We reserve the option to use it or not depending on the image
provided if we think is not appropriate or could infringe some copyright or
rule. For this reason, please try to use original content and nothing that
could be offensive or problematic with any of the Apache rules or the
common sense :)
This will help others to decide to join us or use Royale since others had
success in using it.
Thanks all for your contribution to this page!! That will be of great help!
:)
Carlos
El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<ca...@apache.org>)
escribió:
> Hi,
> we can add testimonials page (as an additional page a part from showcase
> page). The actual theme has that integrated that will be easy to do.
> Will start a thread so others can write its own testimonial to be added.
>
> Thanks for the suggestion :)
>
>
>
> El mar., 1 oct. 2019 a las 19:37, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
>> The showcase would be great, but if it is easier/faster to simply have a
>> page of links to blogs of our committers like you and Harbs that just
>> contain a paragraph or two about how Royale has helped, that might be a
>> good place to start.
>>
>> -Alex
>>
>> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>>
>> Hi Alex,
>>
>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
>> (<ah...@adobe.com.invalid>)
>> escribió:
>>
>> > Thanks for working on the docs.
>> >
>> > Beyond the docs, what I would most like to see is "success
>> stories". I
>> > keep thinking it would help if it was easier for folks to read
>> about how
>> > Royale has helped.
>> >
>>
>> You refer to "showcase" page?
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
>> I still has that on my plate. I have to plan the info to showcase and
>> post
>> so people can submit about it
>> But yes is one of the important pieces to work on. I'll try to get
>> over it
>> soon.
>>
>> thanks
>>
> --
Carlos Rovira
http://about.me/carlosrovira
Re: About Royale Docs Improvements over latest months
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
we can add testimonials page (as an additional page a part from showcase
page). The actual theme has that integrated that will be easy to do.
Will start a thread so others can write its own testimonial to be added.
Thanks for the suggestion :)
El mar., 1 oct. 2019 a las 19:37, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> The showcase would be great, but if it is easier/faster to simply have a
> page of links to blogs of our committers like you and Harbs that just
> contain a paragraph or two about how Royale has helped, that might be a
> good place to start.
>
> -Alex
>
> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> El mar., 1 oct. 2019 a las 17:50, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > Thanks for working on the docs.
> >
> > Beyond the docs, what I would most like to see is "success
> stories". I
> > keep thinking it would help if it was easier for folks to read about
> how
> > Royale has helped.
> >
>
> You refer to "showcase" page?
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> I still has that on my plate. I have to plan the info to showcase and
> post
> so people can submit about it
> But yes is one of the important pieces to work on. I'll try to get
> over it
> soon.
>
> thanks
>
>
> > My 2 cents,
> > -Alex
> >
> > On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
> >
> > This is great progress!
> >
> > I think one other area where we are still very thin is on using
> > RoyaleUnit
> > for testing.
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> carlosrovira@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > about latest changes in docs done is latest months. This is a
> > summary of
> > > the work done (still in progress at some points):
> > >
> > > About layout, search and usability:
> > >
> > > * Now we have a more polished layout that should work right on
> > desktop,
> > > tablet and mobile, making more easy for new users coming to
> Royale
> > learn
> > > about it
> > > * The sidebar menu will show on the right as normal in tablet
> and
> > desktop.
> > > In mobile shows a button on the right side that make the menu
> slide
> > from
> > > the right
> > > * Now we have search functionality implemented thanks to
> Algolia
> > search.
> > > The index is crawled every 24h. Take into account if you make
> some
> > change
> > > and don't see it when searching as you upload the change.
> > > * Main menu now turns to dropdown if there's no enough room to
> show
> > it
> > > horizontally
> > >
> > > About content:
> > >
> > > * Added global styles for better readability and support of
> most of
> > the
> > > markdown options and highlighting of code (specially for AS3
> and
> > MXML)
> > > * Now all pages has "description" and "permalink" in the head
> > section to
> > > improve sharing and searching on internet. Remember to add this
> > lines so we
> > > make all navigation consistent with the rest of pages. If
> someone
> > notice a
> > > page without this, please add it or report it.
> > > * Added metadata for sharing in social networks more easily
> > capturing the
> > > previous point plus screenshot and name.
> > > * I tried to bring pages to the index that was still missing
> so we
> > have
> > > most of the overall structure in place. I'm pretty sure
> there's still
> > > missing concepts and things to bring to the docs, so keep your
> eyes
> > open to
> > > see what could still be missing and report it or add yourself.
> > > * Notice that some of that content is still a page mostly
> empty and
> > waiting
> > > to be filled. You're all invited to do so, just let others know
> > about it to
> > > avoid duplicate efforts.
> > > * For Component Sets, I started to create a page per component
> where
> > we add
> > > the most needed info to start with the component. It then
> refers to
> > ASDocs
> > > for a full spec and access to all classes. I'm working on
> Jewel.
> > Others are
> > > invited to use Jewel finished pages and use it as template for
> Basic,
> > > MXRoyale and other sets, and/or create new ones for components
> that
> > are not
> > > similar and there's no counterpart on Jewel.
> > > * I added live content on Jewel components, since visual
> running
> > examples
> > > are very powerful.
> > > * I added live example on the GitHub tutorial app.
> > > * I added many cross link references between Royale-docs, blog
> > examples and
> > > ASDocs pages. Content must be in only one place but that
> content
> > should be
> > > linked with the rest of royale contents in our network.
> > > * I tried to format all the pages I could to get most of the
> new
> > visuals
> > > created, but I'm sure threr's still content to format, we can
> do this
> > > between all here, and anyone coming to Royale and browse
> content is
> > invited
> > > to help in this point as well to submit more content to be
> reviewed
> > and
> > > added.
> > > * I refactored all license pages to make all consistent with
> one
> > style.
> > >
> > > To Help:
> > >
> > > I think there's many content already done and formatted in the
> right
> > way to
> > > make others be able to add content that aligns to the rest of
> the doc
> > > pages. Andrew and I are here to help to give the finished
> results
> > that
> > > conform to actual specs.
> > >
> > > There's still many things to do to get a full docs site. This
> is the
> > list
> > > of things I see:
> > >
> > > * Fill Features and concepts pages still empty (View States,
> Data
> > Binding,
> > > RPC methods pages, ....). I think this can be the most
> important
> > ones since
> > > are core concepts in Royale.
> > > * Complete Jewel and other sets reference pages. Very
> important for
> > people
> > > coming. Here I plan to add for Jewel "style specs" too as
> someone
> > mentioned
> > > some days ago, and I think this will be a very good idea.
> > > * Add Crux documentation, that should come in part from swiz
> > framework docs
> > >
> > > What more things you still think are missing?
> > >
> > > Thanks
> > >
> > >
> > > --
> > > Carlos Rovira
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=kYfh67uUCVIqPA%2FD6YIV%2FpyVOgOg5dyr0p8hCq1TBY4%3D&reserved=0
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=a%2BX%2F%2BlO242%2BqVeUDd7CsUOCqyoPeyc2bwiL3xjFpM4g%3D&reserved=0
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=QMLoJ4WGOdDHq24JEMJekkMwEuXT1A5Y8lDkXzB%2F07k%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: About Royale Docs Improvements over latest months
Posted by Carlos Rovira <ca...@apache.org>.
Yeah! that would be great Andrew :)
Other things I have planned to is to go over ASDoc visuals to make it more
near to Royale Docs and more mobile friendly when possible.
I think we're getting a really good product with all the current efforts in
progress :D
El mar., 1 oct. 2019 a las 20:40, Andrew Wetmore (<co...@gmail.com>)
escribió:
> I have not forgotten "Royale in a Week", the reworking of "Flex in a Week"
> which I undertook to do. Will be working on that.
>
> On Tue, Oct 1, 2019 at 2:37 PM Alex Harui <ah...@adobe.com.invalid>
> wrote:
>
> > The showcase would be great, but if it is easier/faster to simply have a
> > page of links to blogs of our committers like you and Harbs that just
> > contain a paragraph or two about how Royale has helped, that might be a
> > good place to start.
> >
> > -Alex
> >
> > On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
> >
> > Hi Alex,
> >
> > El mar., 1 oct. 2019 a las 17:50, Alex Harui
> (<aharui@adobe.com.invalid
> > >)
> > escribió:
> >
> > > Thanks for working on the docs.
> > >
> > > Beyond the docs, what I would most like to see is "success
> > stories". I
> > > keep thinking it would help if it was easier for folks to read
> about
> > how
> > > Royale has helped.
> > >
> >
> > You refer to "showcase" page?
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> > I still has that on my plate. I have to plan the info to showcase and
> > post
> > so people can submit about it
> > But yes is one of the important pieces to work on. I'll try to get
> > over it
> > soon.
> >
> > thanks
> >
> >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
> > >
> > > This is great progress!
> > >
> > > I think one other area where we are still very thin is on using
> > > RoyaleUnit
> > > for testing.
> > >
> > > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> > carlosrovira@apache.org>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > about latest changes in docs done is latest months. This is a
> > > summary of
> > > > the work done (still in progress at some points):
> > > >
> > > > About layout, search and usability:
> > > >
> > > > * Now we have a more polished layout that should work right
> on
> > > desktop,
> > > > tablet and mobile, making more easy for new users coming to
> > Royale
> > > learn
> > > > about it
> > > > * The sidebar menu will show on the right as normal in tablet
> > and
> > > desktop.
> > > > In mobile shows a button on the right side that make the menu
> > slide
> > > from
> > > > the right
> > > > * Now we have search functionality implemented thanks to
> > Algolia
> > > search.
> > > > The index is crawled every 24h. Take into account if you make
> > some
> > > change
> > > > and don't see it when searching as you upload the change.
> > > > * Main menu now turns to dropdown if there's no enough room
> to
> > show
> > > it
> > > > horizontally
> > > >
> > > > About content:
> > > >
> > > > * Added global styles for better readability and support of
> > most of
> > > the
> > > > markdown options and highlighting of code (specially for AS3
> > and
> > > MXML)
> > > > * Now all pages has "description" and "permalink" in the head
> > > section to
> > > > improve sharing and searching on internet. Remember to add
> this
> > > lines so we
> > > > make all navigation consistent with the rest of pages. If
> > someone
> > > notice a
> > > > page without this, please add it or report it.
> > > > * Added metadata for sharing in social networks more easily
> > > capturing the
> > > > previous point plus screenshot and name.
> > > > * I tried to bring pages to the index that was still missing
> > so we
> > > have
> > > > most of the overall structure in place. I'm pretty sure
> > there's still
> > > > missing concepts and things to bring to the docs, so keep
> your
> > eyes
> > > open to
> > > > see what could still be missing and report it or add
> yourself.
> > > > * Notice that some of that content is still a page mostly
> > empty and
> > > waiting
> > > > to be filled. You're all invited to do so, just let others
> know
> > > about it to
> > > > avoid duplicate efforts.
> > > > * For Component Sets, I started to create a page per
> component
> > where
> > > we add
> > > > the most needed info to start with the component. It then
> > refers to
> > > ASDocs
> > > > for a full spec and access to all classes. I'm working on
> > Jewel.
> > > Others are
> > > > invited to use Jewel finished pages and use it as template
> for
> > Basic,
> > > > MXRoyale and other sets, and/or create new ones for
> components
> > that
> > > are not
> > > > similar and there's no counterpart on Jewel.
> > > > * I added live content on Jewel components, since visual
> > running
> > > examples
> > > > are very powerful.
> > > > * I added live example on the GitHub tutorial app.
> > > > * I added many cross link references between Royale-docs,
> blog
> > > examples and
> > > > ASDocs pages. Content must be in only one place but that
> > content
> > > should be
> > > > linked with the rest of royale contents in our network.
> > > > * I tried to format all the pages I could to get most of the
> > new
> > > visuals
> > > > created, but I'm sure threr's still content to format, we can
> > do this
> > > > between all here, and anyone coming to Royale and browse
> > content is
> > > invited
> > > > to help in this point as well to submit more content to be
> > reviewed
> > > and
> > > > added.
> > > > * I refactored all license pages to make all consistent with
> > one
> > > style.
> > > >
> > > > To Help:
> > > >
> > > > I think there's many content already done and formatted in
> the
> > right
> > > way to
> > > > make others be able to add content that aligns to the rest of
> > the doc
> > > > pages. Andrew and I are here to help to give the finished
> > results
> > > that
> > > > conform to actual specs.
> > > >
> > > > There's still many things to do to get a full docs site. This
> > is the
> > > list
> > > > of things I see:
> > > >
> > > > * Fill Features and concepts pages still empty (View States,
> > Data
> > > Binding,
> > > > RPC methods pages, ....). I think this can be the most
> > important
> > > ones since
> > > > are core concepts in Royale.
> > > > * Complete Jewel and other sets reference pages. Very
> > important for
> > > people
> > > > coming. Here I plan to add for Jewel "style specs" too as
> > someone
> > > mentioned
> > > > some days ago, and I think this will be a very good idea.
> > > > * Add Crux documentation, that should come in part from swiz
> > > framework docs
> > > >
> > > > What more things you still think are missing?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=kYfh67uUCVIqPA%2FD6YIV%2FpyVOgOg5dyr0p8hCq1TBY4%3D&reserved=0
> > > >
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=a%2BX%2F%2BlO242%2BqVeUDd7CsUOCqyoPeyc2bwiL3xjFpM4g%3D&reserved=0
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=QMLoJ4WGOdDHq24JEMJekkMwEuXT1A5Y8lDkXzB%2F07k%3D&reserved=0
> >
> >
> >
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: About Royale Docs Improvements over latest months
Posted by Andrew Wetmore <co...@gmail.com>.
I have not forgotten "Royale in a Week", the reworking of "Flex in a Week"
which I undertook to do. Will be working on that.
On Tue, Oct 1, 2019 at 2:37 PM Alex Harui <ah...@adobe.com.invalid> wrote:
> The showcase would be great, but if it is easier/faster to simply have a
> page of links to blogs of our committers like you and Harbs that just
> contain a paragraph or two about how Royale has helped, that might be a
> good place to start.
>
> -Alex
>
> On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Alex,
>
> El mar., 1 oct. 2019 a las 17:50, Alex Harui (<aharui@adobe.com.invalid
> >)
> escribió:
>
> > Thanks for working on the docs.
> >
> > Beyond the docs, what I would most like to see is "success
> stories". I
> > keep thinking it would help if it was easier for folks to read about
> how
> > Royale has helped.
> >
>
> You refer to "showcase" page?
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
> I still has that on my plate. I have to plan the info to showcase and
> post
> so people can submit about it
> But yes is one of the important pieces to work on. I'll try to get
> over it
> soon.
>
> thanks
>
>
> > My 2 cents,
> > -Alex
> >
> > On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
> >
> > This is great progress!
> >
> > I think one other area where we are still very thin is on using
> > RoyaleUnit
> > for testing.
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> carlosrovira@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > about latest changes in docs done is latest months. This is a
> > summary of
> > > the work done (still in progress at some points):
> > >
> > > About layout, search and usability:
> > >
> > > * Now we have a more polished layout that should work right on
> > desktop,
> > > tablet and mobile, making more easy for new users coming to
> Royale
> > learn
> > > about it
> > > * The sidebar menu will show on the right as normal in tablet
> and
> > desktop.
> > > In mobile shows a button on the right side that make the menu
> slide
> > from
> > > the right
> > > * Now we have search functionality implemented thanks to
> Algolia
> > search.
> > > The index is crawled every 24h. Take into account if you make
> some
> > change
> > > and don't see it when searching as you upload the change.
> > > * Main menu now turns to dropdown if there's no enough room to
> show
> > it
> > > horizontally
> > >
> > > About content:
> > >
> > > * Added global styles for better readability and support of
> most of
> > the
> > > markdown options and highlighting of code (specially for AS3
> and
> > MXML)
> > > * Now all pages has "description" and "permalink" in the head
> > section to
> > > improve sharing and searching on internet. Remember to add this
> > lines so we
> > > make all navigation consistent with the rest of pages. If
> someone
> > notice a
> > > page without this, please add it or report it.
> > > * Added metadata for sharing in social networks more easily
> > capturing the
> > > previous point plus screenshot and name.
> > > * I tried to bring pages to the index that was still missing
> so we
> > have
> > > most of the overall structure in place. I'm pretty sure
> there's still
> > > missing concepts and things to bring to the docs, so keep your
> eyes
> > open to
> > > see what could still be missing and report it or add yourself.
> > > * Notice that some of that content is still a page mostly
> empty and
> > waiting
> > > to be filled. You're all invited to do so, just let others know
> > about it to
> > > avoid duplicate efforts.
> > > * For Component Sets, I started to create a page per component
> where
> > we add
> > > the most needed info to start with the component. It then
> refers to
> > ASDocs
> > > for a full spec and access to all classes. I'm working on
> Jewel.
> > Others are
> > > invited to use Jewel finished pages and use it as template for
> Basic,
> > > MXRoyale and other sets, and/or create new ones for components
> that
> > are not
> > > similar and there's no counterpart on Jewel.
> > > * I added live content on Jewel components, since visual
> running
> > examples
> > > are very powerful.
> > > * I added live example on the GitHub tutorial app.
> > > * I added many cross link references between Royale-docs, blog
> > examples and
> > > ASDocs pages. Content must be in only one place but that
> content
> > should be
> > > linked with the rest of royale contents in our network.
> > > * I tried to format all the pages I could to get most of the
> new
> > visuals
> > > created, but I'm sure threr's still content to format, we can
> do this
> > > between all here, and anyone coming to Royale and browse
> content is
> > invited
> > > to help in this point as well to submit more content to be
> reviewed
> > and
> > > added.
> > > * I refactored all license pages to make all consistent with
> one
> > style.
> > >
> > > To Help:
> > >
> > > I think there's many content already done and formatted in the
> right
> > way to
> > > make others be able to add content that aligns to the rest of
> the doc
> > > pages. Andrew and I are here to help to give the finished
> results
> > that
> > > conform to actual specs.
> > >
> > > There's still many things to do to get a full docs site. This
> is the
> > list
> > > of things I see:
> > >
> > > * Fill Features and concepts pages still empty (View States,
> Data
> > Binding,
> > > RPC methods pages, ....). I think this can be the most
> important
> > ones since
> > > are core concepts in Royale.
> > > * Complete Jewel and other sets reference pages. Very
> important for
> > people
> > > coming. Here I plan to add for Jewel "style specs" too as
> someone
> > mentioned
> > > some days ago, and I think this will be a very good idea.
> > > * Add Crux documentation, that should come in part from swiz
> > framework docs
> > >
> > > What more things you still think are missing?
> > >
> > > Thanks
> > >
> > >
> > > --
> > > Carlos Rovira
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=kYfh67uUCVIqPA%2FD6YIV%2FpyVOgOg5dyr0p8hCq1TBY4%3D&reserved=0
> > >
> >
> >
> > --
> > Andrew Wetmore
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=a%2BX%2F%2BlO242%2BqVeUDd7CsUOCqyoPeyc2bwiL3xjFpM4g%3D&reserved=0
> >
> >
> >
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=QMLoJ4WGOdDHq24JEMJekkMwEuXT1A5Y8lDkXzB%2F07k%3D&reserved=0
>
>
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
Re: About Royale Docs Improvements over latest months
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The showcase would be great, but if it is easier/faster to simply have a page of links to blogs of our committers like you and Harbs that just contain a paragraph or two about how Royale has helped, that might be a good place to start.
-Alex
On 10/1/19, 10:02 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Alex,
El mar., 1 oct. 2019 a las 17:50, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Thanks for working on the docs.
>
> Beyond the docs, what I would most like to see is "success stories". I
> keep thinking it would help if it was easier for folks to read about how
> Royale has helped.
>
You refer to "showcase" page?
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3D&reserved=0
I still has that on my plate. I have to plan the info to showcase and post
so people can submit about it
But yes is one of the important pieces to work on. I'll try to get over it
soon.
thanks
> My 2 cents,
> -Alex
>
> On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
>
> This is great progress!
>
> I think one other area where we are still very thin is on using
> RoyaleUnit
> for testing.
>
> On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi,
> >
> > about latest changes in docs done is latest months. This is a
> summary of
> > the work done (still in progress at some points):
> >
> > About layout, search and usability:
> >
> > * Now we have a more polished layout that should work right on
> desktop,
> > tablet and mobile, making more easy for new users coming to Royale
> learn
> > about it
> > * The sidebar menu will show on the right as normal in tablet and
> desktop.
> > In mobile shows a button on the right side that make the menu slide
> from
> > the right
> > * Now we have search functionality implemented thanks to Algolia
> search.
> > The index is crawled every 24h. Take into account if you make some
> change
> > and don't see it when searching as you upload the change.
> > * Main menu now turns to dropdown if there's no enough room to show
> it
> > horizontally
> >
> > About content:
> >
> > * Added global styles for better readability and support of most of
> the
> > markdown options and highlighting of code (specially for AS3 and
> MXML)
> > * Now all pages has "description" and "permalink" in the head
> section to
> > improve sharing and searching on internet. Remember to add this
> lines so we
> > make all navigation consistent with the rest of pages. If someone
> notice a
> > page without this, please add it or report it.
> > * Added metadata for sharing in social networks more easily
> capturing the
> > previous point plus screenshot and name.
> > * I tried to bring pages to the index that was still missing so we
> have
> > most of the overall structure in place. I'm pretty sure there's still
> > missing concepts and things to bring to the docs, so keep your eyes
> open to
> > see what could still be missing and report it or add yourself.
> > * Notice that some of that content is still a page mostly empty and
> waiting
> > to be filled. You're all invited to do so, just let others know
> about it to
> > avoid duplicate efforts.
> > * For Component Sets, I started to create a page per component where
> we add
> > the most needed info to start with the component. It then refers to
> ASDocs
> > for a full spec and access to all classes. I'm working on Jewel.
> Others are
> > invited to use Jewel finished pages and use it as template for Basic,
> > MXRoyale and other sets, and/or create new ones for components that
> are not
> > similar and there's no counterpart on Jewel.
> > * I added live content on Jewel components, since visual running
> examples
> > are very powerful.
> > * I added live example on the GitHub tutorial app.
> > * I added many cross link references between Royale-docs, blog
> examples and
> > ASDocs pages. Content must be in only one place but that content
> should be
> > linked with the rest of royale contents in our network.
> > * I tried to format all the pages I could to get most of the new
> visuals
> > created, but I'm sure threr's still content to format, we can do this
> > between all here, and anyone coming to Royale and browse content is
> invited
> > to help in this point as well to submit more content to be reviewed
> and
> > added.
> > * I refactored all license pages to make all consistent with one
> style.
> >
> > To Help:
> >
> > I think there's many content already done and formatted in the right
> way to
> > make others be able to add content that aligns to the rest of the doc
> > pages. Andrew and I are here to help to give the finished results
> that
> > conform to actual specs.
> >
> > There's still many things to do to get a full docs site. This is the
> list
> > of things I see:
> >
> > * Fill Features and concepts pages still empty (View States, Data
> Binding,
> > RPC methods pages, ....). I think this can be the most important
> ones since
> > are core concepts in Royale.
> > * Complete Jewel and other sets reference pages. Very important for
> people
> > coming. Here I plan to add for Jewel "style specs" too as someone
> mentioned
> > some days ago, and I think this will be a very good idea.
> > * Add Crux documentation, that should come in part from swiz
> framework docs
> >
> > What more things you still think are missing?
> >
> > Thanks
> >
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142&sdata=kYfh67uUCVIqPA%2FD6YIV%2FpyVOgOg5dyr0p8hCq1TBY4%3D&reserved=0
> >
>
>
> --
> Andrew Wetmore
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=a%2BX%2F%2BlO242%2BqVeUDd7CsUOCqyoPeyc2bwiL3xjFpM4g%3D&reserved=0
>
>
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576191136&sdata=QMLoJ4WGOdDHq24JEMJekkMwEuXT1A5Y8lDkXzB%2F07k%3D&reserved=0
Re: About Royale Docs Improvements over latest months
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
El mar., 1 oct. 2019 a las 17:50, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Thanks for working on the docs.
>
> Beyond the docs, what I would most like to see is "success stories". I
> keep thinking it would help if it was easier for folks to read about how
> Royale has helped.
>
You refer to "showcase" page?
https://royale.apache.org/showcase/
I still has that on my plate. I have to plan the info to showcase and post
so people can submit about it
But yes is one of the important pieces to work on. I'll try to get over it
soon.
thanks
> My 2 cents,
> -Alex
>
> On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
>
> This is great progress!
>
> I think one other area where we are still very thin is on using
> RoyaleUnit
> for testing.
>
> On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi,
> >
> > about latest changes in docs done is latest months. This is a
> summary of
> > the work done (still in progress at some points):
> >
> > About layout, search and usability:
> >
> > * Now we have a more polished layout that should work right on
> desktop,
> > tablet and mobile, making more easy for new users coming to Royale
> learn
> > about it
> > * The sidebar menu will show on the right as normal in tablet and
> desktop.
> > In mobile shows a button on the right side that make the menu slide
> from
> > the right
> > * Now we have search functionality implemented thanks to Algolia
> search.
> > The index is crawled every 24h. Take into account if you make some
> change
> > and don't see it when searching as you upload the change.
> > * Main menu now turns to dropdown if there's no enough room to show
> it
> > horizontally
> >
> > About content:
> >
> > * Added global styles for better readability and support of most of
> the
> > markdown options and highlighting of code (specially for AS3 and
> MXML)
> > * Now all pages has "description" and "permalink" in the head
> section to
> > improve sharing and searching on internet. Remember to add this
> lines so we
> > make all navigation consistent with the rest of pages. If someone
> notice a
> > page without this, please add it or report it.
> > * Added metadata for sharing in social networks more easily
> capturing the
> > previous point plus screenshot and name.
> > * I tried to bring pages to the index that was still missing so we
> have
> > most of the overall structure in place. I'm pretty sure there's still
> > missing concepts and things to bring to the docs, so keep your eyes
> open to
> > see what could still be missing and report it or add yourself.
> > * Notice that some of that content is still a page mostly empty and
> waiting
> > to be filled. You're all invited to do so, just let others know
> about it to
> > avoid duplicate efforts.
> > * For Component Sets, I started to create a page per component where
> we add
> > the most needed info to start with the component. It then refers to
> ASDocs
> > for a full spec and access to all classes. I'm working on Jewel.
> Others are
> > invited to use Jewel finished pages and use it as template for Basic,
> > MXRoyale and other sets, and/or create new ones for components that
> are not
> > similar and there's no counterpart on Jewel.
> > * I added live content on Jewel components, since visual running
> examples
> > are very powerful.
> > * I added live example on the GitHub tutorial app.
> > * I added many cross link references between Royale-docs, blog
> examples and
> > ASDocs pages. Content must be in only one place but that content
> should be
> > linked with the rest of royale contents in our network.
> > * I tried to format all the pages I could to get most of the new
> visuals
> > created, but I'm sure threr's still content to format, we can do this
> > between all here, and anyone coming to Royale and browse content is
> invited
> > to help in this point as well to submit more content to be reviewed
> and
> > added.
> > * I refactored all license pages to make all consistent with one
> style.
> >
> > To Help:
> >
> > I think there's many content already done and formatted in the right
> way to
> > make others be able to add content that aligns to the rest of the doc
> > pages. Andrew and I are here to help to give the finished results
> that
> > conform to actual specs.
> >
> > There's still many things to do to get a full docs site. This is the
> list
> > of things I see:
> >
> > * Fill Features and concepts pages still empty (View States, Data
> Binding,
> > RPC methods pages, ....). I think this can be the most important
> ones since
> > are core concepts in Royale.
> > * Complete Jewel and other sets reference pages. Very important for
> people
> > coming. Here I plan to add for Jewel "style specs" too as someone
> mentioned
> > some days ago, and I think this will be a very good idea.
> > * Add Crux documentation, that should come in part from swiz
> framework docs
> >
> > What more things you still think are missing?
> >
> > Thanks
> >
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C3c71205762e0405e770108d7465dbeb5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055240758594242&sdata=eS3bng5TzHplex9tuk4212G4u8jTz3QAh0PKbSSJnt8%3D&reserved=0
> >
>
>
> --
> Andrew Wetmore
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C3c71205762e0405e770108d7465dbeb5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055240758594242&sdata=owUz09O3UlXfX8OcLJoqwGjSvOmbiYfrQIYiQs3H19M%3D&reserved=0
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: About Royale Docs Improvements over latest months
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Thanks for working on the docs.
Beyond the docs, what I would most like to see is "success stories". I keep thinking it would help if it was easier for folks to read about how Royale has helped.
My 2 cents,
-Alex
On 10/1/19, 3:54 AM, "Andrew Wetmore" <co...@gmail.com> wrote:
This is great progress!
I think one other area where we are still very thin is on using RoyaleUnit
for testing.
On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <ca...@apache.org>
wrote:
> Hi,
>
> about latest changes in docs done is latest months. This is a summary of
> the work done (still in progress at some points):
>
> About layout, search and usability:
>
> * Now we have a more polished layout that should work right on desktop,
> tablet and mobile, making more easy for new users coming to Royale learn
> about it
> * The sidebar menu will show on the right as normal in tablet and desktop.
> In mobile shows a button on the right side that make the menu slide from
> the right
> * Now we have search functionality implemented thanks to Algolia search.
> The index is crawled every 24h. Take into account if you make some change
> and don't see it when searching as you upload the change.
> * Main menu now turns to dropdown if there's no enough room to show it
> horizontally
>
> About content:
>
> * Added global styles for better readability and support of most of the
> markdown options and highlighting of code (specially for AS3 and MXML)
> * Now all pages has "description" and "permalink" in the head section to
> improve sharing and searching on internet. Remember to add this lines so we
> make all navigation consistent with the rest of pages. If someone notice a
> page without this, please add it or report it.
> * Added metadata for sharing in social networks more easily capturing the
> previous point plus screenshot and name.
> * I tried to bring pages to the index that was still missing so we have
> most of the overall structure in place. I'm pretty sure there's still
> missing concepts and things to bring to the docs, so keep your eyes open to
> see what could still be missing and report it or add yourself.
> * Notice that some of that content is still a page mostly empty and waiting
> to be filled. You're all invited to do so, just let others know about it to
> avoid duplicate efforts.
> * For Component Sets, I started to create a page per component where we add
> the most needed info to start with the component. It then refers to ASDocs
> for a full spec and access to all classes. I'm working on Jewel. Others are
> invited to use Jewel finished pages and use it as template for Basic,
> MXRoyale and other sets, and/or create new ones for components that are not
> similar and there's no counterpart on Jewel.
> * I added live content on Jewel components, since visual running examples
> are very powerful.
> * I added live example on the GitHub tutorial app.
> * I added many cross link references between Royale-docs, blog examples and
> ASDocs pages. Content must be in only one place but that content should be
> linked with the rest of royale contents in our network.
> * I tried to format all the pages I could to get most of the new visuals
> created, but I'm sure threr's still content to format, we can do this
> between all here, and anyone coming to Royale and browse content is invited
> to help in this point as well to submit more content to be reviewed and
> added.
> * I refactored all license pages to make all consistent with one style.
>
> To Help:
>
> I think there's many content already done and formatted in the right way to
> make others be able to add content that aligns to the rest of the doc
> pages. Andrew and I are here to help to give the finished results that
> conform to actual specs.
>
> There's still many things to do to get a full docs site. This is the list
> of things I see:
>
> * Fill Features and concepts pages still empty (View States, Data Binding,
> RPC methods pages, ....). I think this can be the most important ones since
> are core concepts in Royale.
> * Complete Jewel and other sets reference pages. Very important for people
> coming. Here I plan to add for Jewel "style specs" too as someone mentioned
> some days ago, and I think this will be a very good idea.
> * Add Crux documentation, that should come in part from swiz framework docs
>
> What more things you still think are missing?
>
> Thanks
>
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C3c71205762e0405e770108d7465dbeb5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055240758594242&sdata=eS3bng5TzHplex9tuk4212G4u8jTz3QAh0PKbSSJnt8%3D&reserved=0
>
--
Andrew Wetmore
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7C3c71205762e0405e770108d7465dbeb5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055240758594242&sdata=owUz09O3UlXfX8OcLJoqwGjSvOmbiYfrQIYiQs3H19M%3D&reserved=0
Re: About Royale Docs Improvements over latest months
Posted by Andrew Wetmore <co...@gmail.com>.
This is great progress!
I think one other area where we are still very thin is on using RoyaleUnit
for testing.
On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <ca...@apache.org>
wrote:
> Hi,
>
> about latest changes in docs done is latest months. This is a summary of
> the work done (still in progress at some points):
>
> About layout, search and usability:
>
> * Now we have a more polished layout that should work right on desktop,
> tablet and mobile, making more easy for new users coming to Royale learn
> about it
> * The sidebar menu will show on the right as normal in tablet and desktop.
> In mobile shows a button on the right side that make the menu slide from
> the right
> * Now we have search functionality implemented thanks to Algolia search.
> The index is crawled every 24h. Take into account if you make some change
> and don't see it when searching as you upload the change.
> * Main menu now turns to dropdown if there's no enough room to show it
> horizontally
>
> About content:
>
> * Added global styles for better readability and support of most of the
> markdown options and highlighting of code (specially for AS3 and MXML)
> * Now all pages has "description" and "permalink" in the head section to
> improve sharing and searching on internet. Remember to add this lines so we
> make all navigation consistent with the rest of pages. If someone notice a
> page without this, please add it or report it.
> * Added metadata for sharing in social networks more easily capturing the
> previous point plus screenshot and name.
> * I tried to bring pages to the index that was still missing so we have
> most of the overall structure in place. I'm pretty sure there's still
> missing concepts and things to bring to the docs, so keep your eyes open to
> see what could still be missing and report it or add yourself.
> * Notice that some of that content is still a page mostly empty and waiting
> to be filled. You're all invited to do so, just let others know about it to
> avoid duplicate efforts.
> * For Component Sets, I started to create a page per component where we add
> the most needed info to start with the component. It then refers to ASDocs
> for a full spec and access to all classes. I'm working on Jewel. Others are
> invited to use Jewel finished pages and use it as template for Basic,
> MXRoyale and other sets, and/or create new ones for components that are not
> similar and there's no counterpart on Jewel.
> * I added live content on Jewel components, since visual running examples
> are very powerful.
> * I added live example on the GitHub tutorial app.
> * I added many cross link references between Royale-docs, blog examples and
> ASDocs pages. Content must be in only one place but that content should be
> linked with the rest of royale contents in our network.
> * I tried to format all the pages I could to get most of the new visuals
> created, but I'm sure threr's still content to format, we can do this
> between all here, and anyone coming to Royale and browse content is invited
> to help in this point as well to submit more content to be reviewed and
> added.
> * I refactored all license pages to make all consistent with one style.
>
> To Help:
>
> I think there's many content already done and formatted in the right way to
> make others be able to add content that aligns to the rest of the doc
> pages. Andrew and I are here to help to give the finished results that
> conform to actual specs.
>
> There's still many things to do to get a full docs site. This is the list
> of things I see:
>
> * Fill Features and concepts pages still empty (View States, Data Binding,
> RPC methods pages, ....). I think this can be the most important ones since
> are core concepts in Royale.
> * Complete Jewel and other sets reference pages. Very important for people
> coming. Here I plan to add for Jewel "style specs" too as someone mentioned
> some days ago, and I think this will be a very good idea.
> * Add Crux documentation, that should come in part from swiz framework docs
>
> What more things you still think are missing?
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Andrew Wetmore
http://cottage14.blogspot.com/