Saying you shouldn't use Flex for content-focused website is going a little bit over the edge IMHO. I think we all definitely agree that for 100% content-focused sites, you should use HTML, and for 100% data-focused sites, you should use Flex. However in between those extremes, you can still use Flex and get your data indexed. For example, if you're going to create a blog in Flex, you are probably going to use some sort of ready-made blogging engine and plug it into a Flex front-end, using whatever means you feel are right (for example, using XML-RPC if you're using WordPress). Well, blogging engines create RSS feeds, and Google will index an RSS feed just fine. Then it's a matter of adding a link to the RSS feed in the HTML for the Flex app. Similarly if you create a message board. While I'm not convinced creating a blog or a message board interface in Flex is smart (I would advise against it personally), if you want to do it, you have options for getting it indexed.
You don't have to sound angry when you're talking about it. It just sounds like you're trying to say "PEOPLE, DON'T USE SCREWDRIVERS, YOU CAN'T DRIVE NAILS WITH THEM!!!!". Dude, that's why we have hammers. Patrick Doug McCune a écrit : > > How about this one as an example: the Adobe Restaurant Finder sample > app, with the "Recent Reviews" page in particular. The app is here: > http://examples. adobe.com/ flex2/inproduct/ sdk/restaurant/ > recentReviews. html > <http://examples.adobe.com/flex2/inproduct/sdk/restaurant/recentReviews.html> > > If you look at that app you can see user submitted reviews of > restaurants. For example, there's a review of Addis Red Sea and the > reviewer mentions E. Coli in the review. If anyone did a search for > "Addis Red Sea" and "E Coli" this page would never come up. The only > possible way to get the site to appear in search results would be to > publish an alternative HTML version of all the reviews. > > And in fact a complete Google search for everything on examples.adobe. > com shows that you can't find anything useful: http://www.google. > com/search? q=site:examples. adobe.com+&hl=en&lr=&filter=0 > <http://www.google.com/search?q=site:examples.adobe.com+&hl=en&lr=&filter=0> > > Yes, the Restaurant Finder app wrapper HTML page is indexed, but > that's useless. > > Now, a Google search for "ecoli" on Yelp turns up tons of > user-submitted results: http://www.google. com/search? > hl=en&lr=&q=site%3Ayelp. com+ecoli > <http://www.google.com/search?hl=en&lr=&q=site%3Ayelp.com+ecoli> > > The Yelp team would never give that up. They simply can't do Yelp in > Flex because they'd lose the search engine indexing. Now, I'm not > saying that this is a huge problem. All it means is that at the moment > Flex is not the answer for many websites. That's OK, Flex is still > great at what it does well. But if you want any of your dynamic > content indexed by search engines Flex is not the way to go. And it's > not a matter of just thinking about how to include keywords. Flex just > simply isn't an option, nor does it need to be, for websites like > this. Use Flex for what it does, but trying to make a website in Flex > that needs to be indexed by a search engine simply isn't an option at > the moment. > > And this "example" of the restaurant review stuff is a typical example > of tons of other types of websites that shouldn't be done in Flex. > Blogs, news sites, message boards, the list goes on and on. But if > you're doing some stuff that needs data visualization or you can do > without search engine indexing, then by all means use Flex. And I say > this as a HUGE fan of Flex. People just need to use it for what it's > good at. > > Doug > > John Dowdell wrote: > >> dougmccune wrote: >> > While I know Adobe employees don't like to admit this, the answer is >> > very simple: It is often impossible, and if not impossible then at >> > least extremely difficult, to get your Flex content indexed by search >> > engines. That's the straight answer. No more no less. >> >> A particular concrete example might help bring this conversation back to >> ground. >> >> Work using Flex as the creation tool can certainly be found by search >> engines. Identifying your reasonable target search terms is the first >> step. >> >> jd >> >> -- >> John Dowdell . Adobe Developer Support . San Francisco CA USA >> Weblog: http://weblogs. macromedia. com/jd >> <http://weblogs.macromedia.com/jd> >> Aggregator: http://weblogs. macromedia. com/mxna >> <http://weblogs.macromedia.com/mxna> >> Technotes: http://www.macromed ia.com/support/ >> <http://www.macromedia.com/support/> >> Spam killed my private email -- public record is best, thanks. >> > >
