On 12/16/16, 1:36 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
<omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

>
>IMO, this problem
>> needs to be made easy for all FlexJS applications and that's one reason
>>to
>> make ASDoc a RIA.  So we can show folks how to do it.  Are there really
>> static pages behind Home Depot and Amazon's stores?
>>
>
>
>But then you need something like phantom.js that runs our SPA, renders the
>html and stores/serves it on demand.  When a search bot hits the server,
>we
>need to figure that out and redirect it to the phantom.js server instead
>of
>serving up the JS and CSS filese required to render the web application.
>Here is an overview of one way of adding search engine optimization for a
>single page app [1]
>
>My point is: it is quite a bit of unnecessary work when you can simply
>generate html from asdocs using XSLT.

My point is, that most RIAs may not easily translate to html using XSLT.
We need to provide the reference for how to make a FlexJS RIA available to
search engines.  If you have an hour to contribute to FlexJS, I would much
rather have you work on that than on XSLT.  But of course, you are free to
do what you want.

I am surprised by the complexity of [1].  But because we have a tool
chain, I wonder if the tool chain should somehow help.  Should we have a
tool that calls PhantomJS or some equivalent?

Thoughts?
-Alex

>
>Google can probably just handle a SPA without any special work needed from
>us [1], but not sure about other search engines.
>
>[1]
>https://lawsonry.com/2014/05/diy-angularjs-seo-with-phantomjs-the-easy-way
>/
>[2]
>https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.h
>tml
>
>
>
>
>>
>> -Alex
>>
>>
>>

Reply via email to