This can be a question to proxy and wordpress plugin designers.

The typical mindset if this involves specific sites is "They create changes which breaks our wordpress plugin we alter the logic to really make it work again".

But, let's say sleep issues worries relating to this too? To compile some recommendations and finest practices for site development for any proxy-friendly site, exactly what do you suggest is going into it? Think about the challenging nuts you've needed to crack. Remember individuals moments you wanted the website developer tried a particular feature in a different way? How?

As this is worried about coding, I do not think it will visit serverfault.

Edit: After reading through Pekka's comment Personally i think I ought to add more history.

You will find web proxy scripts available for example glype and PHProxy. Because the script should deal with many unknown conditions it does not serve many sites. Because the amount of websites like these has me overwhelmed it doesn't seem sensible to try and result in the proxy's internal logic sophisticated enough additional huge variety. This is when plug ins prove useful. The primary or base script implements a mechanism to invoke wordpress plugin code on the per site bases.

So, when the proxy does not serve let us say facebook.com, the situation incidentally, a coder thinking about the task does some investigation and debugging, to locate where and why the chain is damaged and what ought to be done to solve the problem. The coder implements his fix like a wordpress plugin for your particular site and customers could drop the wordpress plugin to their plug ins directory.

It happens that something on the website changes, which change causes the wordpress plugin to interrupt again. So it's a continuing match to meet up with the newest changes of the site. The irony of everything is that lots of site designers neither know, nor worry about the impact their design choices might have on proxy serve-ability from the content. However, many sites have valid reason of looking after about ale site visitors to gain access to their content through proxies. Don't wish to enter into politics here, and so i allow you to definitely guess why this can be vital that you some sites.

This is definitely an make an effort to take advantage of the collective understanding and connection with proxy and wordpress plugin authors to create a group of recommendations to make a website proxy-friendly.

I did not tag the question php initially because it mostly concerns creation of a website, not the way you generate it. But made the decision to tag it so, since it will improve visibility from the question and also the tag might be justified on audience basis too. I am causeing this to be community wiki also, so if you're php tag ought to be removed, simply do so.

It is really an interesting question and that i don't believe there's a great general solution. Essentially you would like your site's content to become transformable by some 3rd party over that you've no control and perhaps no understanding from the changes.

The standard way this issue is solved is as simple as getting a released API which enables organizations to question the information they need inside a controlled manner which does not depend on the watch's screen-scraping. The API frequently is only going to expose a subset from the functionality, usually since the site requires customers viewing pages to create ad revenue (as well as other type of revenue).

You can generate quite simple pages, essentially utilizing an HTML API, and employ Javascript and CSS to create the web pages more user-friendly. This is probably not right for most sites, however. However the "progressive enhancement" approach trumpeted by jQuery yet others is across the same lines: serve fundamental, semantic content and add functionality and style through JS and CSS.

You could utilize microformats to make sure page content more accessible. You need to use semantic HTML and set plenty of classes and ids on-page elements to ensure that wordpress plugin authors will find the appropriate content they require.

It strikes me it does not matter what these proxies will need to learn to parse your website at least one time. You can document the procedure (maybe to produce wordpress plugin or two).

I do not think you'll have the ability to avoid forcing wordpress plugin authors to re-code whenever you release new versions of the site. You can institute an insurance policy of getting a beta period, where both old and new versions from the site can be found, which gives wordpress plugin authors an opportunity to update their plug ins without any service disruptions for his or her customers.