PURE: SEO and accessibility?

[Nick]

I'm very impressed with what I've seen of PURE so far, and especially
love the unobtrusive nature; it's great to be rid of template code.
Good job!

Has anyone thought much about accessibility and SEO? I need to be able
to serve full pages to search engines and users without JavaScript
turned on, but can't use server-side JavaScript (I'm using PURE as
part of an Open Source CMS, and don't expect all users to be
comfortable installing Jaxer etc.).

I'm playing with two possible solutions:

1) Develop a PHP version of the PURE autoRender method that kicks in
if the user doesn't have javascript enabled. (How? Maybe send them to
the PHP version by default, then redirect them to the JavaScript-
enabled page straight away if they have it turned on. I'm not sure yet
how much a performance hit this would make, though.)

2) Store data as a series of flat, valid HTML files that the CMS
writes to directly. When they're requested by a JavaScript-enabled
browser, build the template around them. (Templating in reverse.)

Are these worthwhile approaches, or is there a better solution?

[Stephan Schmidt]

Hello,

I'm playing with server side Javascript in Java via Rhino (The Mozilla
JS Engine)
and the server DOM by John Resig. Doesn't work yet.

Best regards
Stephan

Code Monkeyism Blog at http://stephan.reposita.org - Programming is hard

[Mic Cvilic]

Hi Nick,

On 25 Nov 2008, at 10:01, Nick wrote:
> I'm playing with two possible solutions:

>
> 1) Develop a PHP version of the PURE autoRender method that kicks in
> if the user doesn't have javascript enabled. (How? Maybe send them to
> the PHP version by default, then redirect them to the JavaScript-
> enabled page straight away if they have it turned on. I'm not sure yet
> how much a performance hit this would make, though.)

There are some given things in a browser that may be hard to get in PHP:
- CSS selectors
- passing functions as directive
- JSON/XML manipulation
Feel free to contact me if you make some more research on it or need
information on how PURE is working.

> 2) Store data as a series of flat, valid HTML files that the CMS
> writes to directly. When they're requested by a JavaScript-enabled
> browser, build the template around them. (Templating in reverse.)

I do not understand this one.
You mean storing data as HTML snippets?

Do you have a link to your CMS project?
Something visible yet?

Thanks for using PURE.
Cheers,
Mic