[Website] Getting content ready to publish

[Carlos Rovira <ca...@apache.org>]

Hi,

I'm working on setting up real content on the website preview.

I think I'll be posting in this thread finished pages for you to review.

For example the first one:

http://royale.codeoscopic.com/mailing-lists/

Here, you could check if we have all expected content, if content is ok, if
no errors are found (spelling, links, ...). Let me know.

As others commented, we need a website ready as soon as we can, but some
parts are still on the works (renaming, first release...) and maybe it will
not be ready before website is launched. That's not a problem since we can
add things at a later time. Some of that things I see are:

* NPM info (@Om will make npm when we make first release)
* Try it now (@Olaf will work on that when he come back from vacation)
* Download (Until release, there are no binaries to post)
* Showcase (I think this is a section for the future, we need some apps
here: Harbs printui, and at least one or two more right?)
...

So the first website release, will not be as huge as I'd like, but we'll
need to add things as those are ready.

I think we still need to continue working in the shadows without making too
much noise to finish things so we can have all things ready to spread the
word in all possible ways to get eyes on us. At that time we should make
lot of noise in all available channels.
But this must be at proper time, if try to do that before time, that could
be our worst movement and maybe a suicide. People coming must see a
finished product that they could use at a minimun. If people start to test
Apache Royale and finds many flaws, they would never come back, and they
will generate bad press.

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

Re: [Website] Getting content ready to publish

[Carlos Rovira <ca...@apache.org>]

Hi Alex,

I checked it, thanks for letting me know


2017-11-10 9:49 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:

> Hi Carlos,
>
> Looks good as always.  Thank you so much for doing this.
>
> I want to remind you of this document [1].  IMO, if the top banner is
> consistent between the home page and other pages, that might be where we
> have to hang the required links to License, Sponsorship/Donate, Thanks,
> Security, and Apache.
>

the page talks about "top level pages" and not "top banner". We have all
this links in all pages thanks
to the footer menu. Remember that I worked in the most easy and modern
navigation menus that uses most of the
products like us:

1.- in top main menu, there's one level menus (no submenus at all!) with
the most important links (here I put what I though more important, some of
the links must be removed on first version like "Try it now" since we don't
have the content, or left we some text that let people know that we're
working on it)

2.- in footer main menu, there's all site menus available, again one level,
since we want to expose o the user all available options so they can know
at first sight without the need to hover or click menus.

IMHO, I think we are conforming to the apache policies.


> There seems to be another requirement in [1] about a "brief one sentence
> description".
>
> And another requirement about the "tm" symbol.
>
>
I'll try to introduce "tm" in page title (so even in browser window will
appear, and in the logo to conform with this) as I get time.

About the "brief one sentence description", a part from the main section in
the home we have it as the other point, in the footer
right available for all pages. Here doesn't mention that it must be on top,
so I think we are doing right in that page position.

Thanks Alex!

Carlos


> There is a checklist in [1].  See [2].
>
> [1] http://www.apache.org/foundation/marks/pmcs.html
> [2] http://www.apache.org/foundation/marks/pmcs.html#checklist
>
> Thanks,
> -Alex
>
>

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

Re: [Website] Getting content ready to publish

[Alex Harui <ah...@adobe.com.INVALID>]

Hi Carlos,

Looks good as always.  Thank you so much for doing this.

I want to remind you of this document [1].  IMO, if the top banner is
consistent between the home page and other pages, that might be where we
have to hang the required links to License, Sponsorship/Donate, Thanks,
Security, and Apache.

There seems to be another requirement in [1] about a "brief one sentence
description".

And another requirement about the "tm" symbol.

There is a checklist in [1].  See [2].

[1] http://www.apache.org/foundation/marks/pmcs.html
[2] http://www.apache.org/foundation/marks/pmcs.html#checklist

Thanks,
-Alex

On 11/9/17, 1:48 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:

>Hi,
>
>I'm working on setting up real content on the website preview.
>
>I think I'll be posting in this thread finished pages for you to review.
>
>For example the first one:
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.cod
>eoscopic.com%2Fmailing-lists%2F&data=02%7C01%7C%7Caacf4bf96d7b4a53774508d5
>27bc9f92%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636458613435472177&s
>data=LG3JnjaxdTRtXaa%2BSLnR%2FNTUzin2LNWi1HNwdW6%2BxY0%3D&reserved=0
>
>Here, you could check if we have all expected content, if content is ok,
>if
>no errors are found (spelling, links, ...). Let me know.
>
>As others commented, we need a website ready as soon as we can, but some
>parts are still on the works (renaming, first release...) and maybe it
>will
>not be ready before website is launched. That's not a problem since we can
>add things at a later time. Some of that things I see are:
>
>* NPM info (@Om will make npm when we make first release)
>* Try it now (@Olaf will work on that when he come back from vacation)
>* Download (Until release, there are no binaries to post)
>* Showcase (I think this is a section for the future, we need some apps
>here: Harbs printui, and at least one or two more right?)
>...
>
>So the first website release, will not be as huge as I'd like, but we'll
>need to add things as those are ready.
>
>I think we still need to continue working in the shadows without making
>too
>much noise to finish things so we can have all things ready to spread the
>word in all possible ways to get eyes on us. At that time we should make
>lot of noise in all available channels.
>But this must be at proper time, if try to do that before time, that could
>be our worst movement and maybe a suicide. People coming must see a
>finished product that they could use at a minimun. If people start to test
>Apache Royale and finds many flaws, they would never come back, and they
>will generate bad press.
>
>-- 
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7C%7Caacf4bf96d7b4a53774508d527bc9f92%7Cfa7b1b5
>a7b34438794aed2c178decee1%7C0%7C0%7C636458613435472177&sdata=SlO5jUUkNkRy0
>9qC63cO4LeiuJpVtWLIZhurwOgIyDc%3D&reserved=0

Re: [Website] Getting content ready to publish

[Harbs <ha...@gmail.com>]

We’re not tied. It just needs to be on a different page to avoid users downloading nightly versions by mistake.

There needs to be two download pages:

1. For “normal” users who only want to use stable releases.
2. Framework developers and users who want to use the latest.

Right now, we don’t have content for #1.

Harbs

> On Nov 10, 2017, at 12:31 PM, Carlos Rovira <ca...@apache.org> wrote:
> 
> Hi Piotr, Justin,
> 
> as Justin, comments, I think we are tied until we get our first release.
> It really doesn't matter to me since "downloads" page is something
> currently not widely used is project like us.
> As always, I like to refer to competence, and they use to point to NPM or
> Github and not post releases.
> We can do it, but for me this is to conform with old habits. We should
> expect that "young devs" will go directly to NPM
> to get Apache Royale ;)
> 
> 
> 2017-11-10 0:30 GMT+01:00 Justin Mclean <ju...@classsoftware.com>:
> 
>> Hi,
>> 
>>> Great job. I think we have all links on the mailing list web page. The
>> one
>>> thing which I really really miss is place on the download site where I
>> will
>>> be able to download Nightly Build -
>> 
>> Please read this [1] about linking to nightly builds.
>> 
>> Justin
>> 
>> 1. http://www.apache.org/legal/release-policy.html#host-rc <
>> http://www.apache.org/legal/release-policy.html#host-rc>
> 
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [Website] Getting content ready to publish

[Carlos Rovira <ca...@apache.org>]

Hi Piotr, Justin,

as Justin, comments, I think we are tied until we get our first release.
It really doesn't matter to me since "downloads" page is something
currently not widely used is project like us.
As always, I like to refer to competence, and they use to point to NPM or
Github and not post releases.
We can do it, but for me this is to conform with old habits. We should
expect that "young devs" will go directly to NPM
to get Apache Royale ;)


2017-11-10 0:30 GMT+01:00 Justin Mclean <ju...@classsoftware.com>:

> Hi,
>
> > Great job. I think we have all links on the mailing list web page. The
> one
> > thing which I really really miss is place on the download site where I
> will
> > be able to download Nightly Build -
>
> Please read this [1] about linking to nightly builds.
>
> Justin
>
> 1. http://www.apache.org/legal/release-policy.html#host-rc <
> http://www.apache.org/legal/release-policy.html#host-rc>




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

Re: [Website] Getting content ready to publish

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Great job. I think we have all links on the mailing list web page. The one
> thing which I really really miss is place on the download site where I will
> be able to download Nightly Build - 

Please read this [1] about linking to nightly builds.

Justin

1. http://www.apache.org/legal/release-policy.html#host-rc <http://www.apache.org/legal/release-policy.html#host-rc>

Re: [Website] Getting content ready to publish

[Harbs <ha...@gmail.com>]

I do think we want to make it clear on how to get the nightly for those who want, but there needs to be a clear separation between “stable user” information, and “consenting developer” information. Although I’m not sure we have any “stable users” as of yet… ;-)

One idea is we can have a “bleeding edge” page. There we can have information on how to get the nightly along with info on how to build from source locally, etc.

Harbs

> On Nov 10, 2017, at 12:40 AM, Piotr Zarzycki <pi...@gmail.com> wrote:
> 
> Hi Carlos,
> 
> Great job. I think we have all links on the mailing list web page. The one
> thing which I really really miss is place on the download site where I will
> be able to download Nightly Build - Which can rotate from time to time. -
> For now such place would fill the gap before release of 0.9.0.
> 
> Thanks, Piotr
> 
> 
> 2017-11-09 22:48 GMT+01:00 Carlos Rovira <ca...@apache.org>:
> 
>> Hi,
>> 
>> I'm working on setting up real content on the website preview.
>> 
>> I think I'll be posting in this thread finished pages for you to review.
>> 
>> For example the first one:
>> 
>> http://royale.codeoscopic.com/mailing-lists/
>> 
>> Here, you could check if we have all expected content, if content is ok, if
>> no errors are found (spelling, links, ...). Let me know.
>> 
>> As others commented, we need a website ready as soon as we can, but some
>> parts are still on the works (renaming, first release...) and maybe it will
>> not be ready before website is launched. That's not a problem since we can
>> add things at a later time. Some of that things I see are:
>> 
>> * NPM info (@Om will make npm when we make first release)
>> * Try it now (@Olaf will work on that when he come back from vacation)
>> * Download (Until release, there are no binaries to post)
>> * Showcase (I think this is a section for the future, we need some apps
>> here: Harbs printui, and at least one or two more right?)
>> ...
>> 
>> So the first website release, will not be as huge as I'd like, but we'll
>> need to add things as those are ready.
>> 
>> I think we still need to continue working in the shadows without making too
>> much noise to finish things so we can have all things ready to spread the
>> word in all possible ways to get eyes on us. At that time we should make
>> lot of noise in all available channels.
>> But this must be at proper time, if try to do that before time, that could
>> be our worst movement and maybe a suicide. People coming must see a
>> finished product that they could use at a minimun. If people start to test
>> Apache Royale and finds many flaws, they would never come back, and they
>> will generate bad press.
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*

Re: [Website] Getting content ready to publish

[Piotr Zarzycki <pi...@gmail.com>]

Hi Carlos,

Great job. I think we have all links on the mailing list web page. The one
thing which I really really miss is place on the download site where I will
be able to download Nightly Build - Which can rotate from time to time. -
For now such place would fill the gap before release of 0.9.0.

Thanks, Piotr


2017-11-09 22:48 GMT+01:00 Carlos Rovira <ca...@apache.org>:

> Hi,
>
> I'm working on setting up real content on the website preview.
>
> I think I'll be posting in this thread finished pages for you to review.
>
> For example the first one:
>
> http://royale.codeoscopic.com/mailing-lists/
>
> Here, you could check if we have all expected content, if content is ok, if
> no errors are found (spelling, links, ...). Let me know.
>
> As others commented, we need a website ready as soon as we can, but some
> parts are still on the works (renaming, first release...) and maybe it will
> not be ready before website is launched. That's not a problem since we can
> add things at a later time. Some of that things I see are:
>
> * NPM info (@Om will make npm when we make first release)
> * Try it now (@Olaf will work on that when he come back from vacation)
> * Download (Until release, there are no binaries to post)
> * Showcase (I think this is a section for the future, we need some apps
> here: Harbs printui, and at least one or two more right?)
> ...
>
> So the first website release, will not be as huge as I'd like, but we'll
> need to add things as those are ready.
>
> I think we still need to continue working in the shadows without making too
> much noise to finish things so we can have all things ready to spread the
> word in all possible ways to get eyes on us. At that time we should make
> lot of noise in all available channels.
> But this must be at proper time, if try to do that before time, that could
> be our worst movement and maybe a suicide. People coming must see a
> finished product that they could use at a minimun. If people start to test
> Apache Royale and finds many flaws, they would never come back, and they
> will generate bad press.
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*