What is the best seo solution for deep linking a flex app/site? - flex3

There are several quality solutions for deep linking a flex application or site. For seo purposes which one produces the best indexing results?
Asual's SWFAddress, Adobe's BrowserManager or urlKit. All three of which seem viable and easy to implement.
Update
This guy at unitedmindset seems to have pulled it off using the BrowserManager and SWFObject.

The deep-linking libraries would not affect page rank or any SEO result directly. It mostly depends on how you put your alternative content.
It is because most search engine do not run JavaScript, which the deep-linking libraries built on, so they wouldn't see the deep-links.
But one thing worth mentioning is, Google can detect and index Flash contents (deep-linked or not), when the swf is embedded by Adobe's solution (AC_OETags.js) or the more standard SWFObject.
You may see Google's Webmaster Central Blog.

Related

Why does Google obscure HTML/CSS classes on Google+?

The attachment is a screenshot of Chrome Developer Tools when looking at Google+ HTML. Note the ~random classnames:
The source for unreadable identifiers can be:
minification
obfuscation
random Id generation
Google Plus is probably implemented as a GWT (or similar framework) application with minified resources (javascript and css files) and automatically generated identifiers. Minification is also widely used as a tool for obfuscating the code so the unreadability is partly intentional too.
Obfuscation can be used to reduce code size, as well as reduce code readability for an "unauthorized" user to make it harder to reverse-engineer a product/program or steal ideas. Someone asked a pretty similar question here, that should answer any more questions that you have.

What Rich text editor should I use for a custom CMS

I want to build a custom CMS where users a Rich text editor is the main way to create content rather than wiki markup.
Besides stability and performance, I want the RTE to be easily extensible. The latter point is very important because I intend to extend it to my needs.
For example I want the users to be able to embed OpenSocial gadgets and whiteboard (based on canvas) into the page. I also the want the users to embed media source like (youtube, slideshare etc).
My preliminary investigation shows that Dojo's (dijit) RTE and TinyMCE are pretty good. How would you compare the two in terms of stability, performance and extensibility. Any other RTE's I should be looking at that fit the bill?
PS: I am using dojo as the main js library.
Hava a look here (blog post with some very helpfull informations).
My own opinion is that there are two free available rtes that are close to each other in comparison. Those are CKEditor and Tinymce. My experience lies on the tinymce side and i can say that the extensibility using own plugins is great with it. Some independent tests have shown that tinymce seems to be more adavanced than CKEditor, others claim CKEditor is better. You will have to decide on your own (development is advancing further each day and new functionality has been developed since those tests).
You may also have a look here for comparisons and discussions:
http://verens.com/2007/09/27/fckeditor-vs-tinymce-vs-everything-else/
http://verens.com/2007/09/27/fckeditor-vs-tinymce-vs-everything-else/
http://www.mediacurrent.com/blog/wysiwyg-shootout-and-winner

Where are the docs for the Chromium Embedded Framework?

I downloaded and started playing with CEF, but there doesn't seem to be any docs for it. Not even a working wiki… Am I missing something?
Most of the documentation is in CEF's header files. The binary distribution comes with docs generated from those files. It's well documented in terms of amount of content written, but I had a lot of trouble while learning to use it. The project's Wiki page contains a lot of useful content as does the cefclient sample program.
The CEF3 API documentation can be found at http://magpcss.org/ceforum/apidocs3/
and CEF1 API docuemntation can be found at http://magpcss.org/ceforum/apidocs/. These two links can be found on the Chromium Embedded framework (CEF) wiki home page: https://bitbucket.org/chromiumembedded/cef/wiki/Home
You didn't provide a link to CEF, so I Googled it, and found the project's Web site, which features a prominent link to their wiki.
The wiki has several pages, but the first one that jumped out at me is the General Usage page that shows how to create a "fully functional embedded browser window using CEF".
So I'm not sure where you were looking, but yes, it looks like you were missing something (grin). The wiki documentation is right there.

Automated content creation for the web?

I see a lot of new websites lately which create automated content, most notable SiteGuruji and 7zoom:
http://www.siteguruji.com/site/youtube.com
Is there an application framework or text analysis framework available to create such sites? SiteGuruji is doing full SEO analysis of the sites as well. Is there an SEO analysis library available? How do I do such an analysis?
Sorry for the noobish question, but i am new to programming and thus I am not sure which direction to start in.
By SEO did you mean this section of the page?
http://www.siteguruji.com/site/youtube.com#seo_status ?
I don't think any frameworks are available for SEO... however you can check out NLTK for text analysis and natural language processing:
http://www.nltk.org/book
You basically need to write your own classes to scrape content from the site and third party sites and analyse it. I have not found something ready for this. Bits fom here and there, you can use.
Personally, I have created everything from scratch using zend framework as basis.

How does Javascript use affect 508 Compliance?

As background, I currently develop for a university, and we have problems with departments demanding "web 2.0 content" and accessibility requirements.
How do really big sites that are JavaScript based deal with 508 Compliance? Some sites degrade, and others require enabling JavaScript. How much impact does one decision have versus the other?
Also, in a realistic sense, how much development time should be devoted the accessible versions of sites versus the "main" versions?
I'm a blind developer and find it possible to use many Web 2.0 sites - this is most certainly possible.
Firstly, I strongly advise against making a separae accessible site, regardless of how many people advise you to do this. This is bad practice and will end up being more work, even if it initialy seems simpler.
Next, try to use progressive enhancement (particularly if this is a new site). Code the site without any Javascript; it's not just accessibility which benefits. Then, in your OnLoad() go through and attach Click events to the anchor tags; this way if you have Javascript you'll see the Ajax version, otherwise you will have a full page refresh and see another HTML page.
Luckily, there is a new standard, WAI-Aria (www.w3.org/WAI/intro/aria.php) which makes this much simpler. You attach attributes to HTML tags to identify the semantics of an Ajax control, for example. The only problem with Aria is that it only works with newer screen readers and web browsers. The university may well require the site be accessible to people running older software.
I'm a screen reader user and often use Javascript enabled sites. Javascript is not an accessibility issue, the way it is used can be. For example if the site uses javascript that requires the use of a mouse and doesn't have keyboard alternatives it will not be 508 compliant. An example of a site that uses Javascript and is accessible is stackoverflow.com. The only feature that isn't accessible is the ability to determine if you have accepted an answer to a question. I would take a look at the links in Annie's answer. All the blind college students I know use a fairly modern browser with Javascript enabled, Lynx is no longer popular in the blind community. If you want to try using a screen reader a good open source one for windows can be found at
http://www.nvda-project.org/
and it works well with firefox. If you want to try using the web with out Javascript install the Noscript addin.
Sites don't have to disable JavaScript to be accessible. Many sites use ARIA roles to work better with screen readers. There's a giant list of articles on accessible AJAX applications here. You could try something like AxsJAX.