Skip to main content
replaced http://meta.webmasters.stackexchange.com/ with https://webmasters.meta.stackexchange.com/
Source Link

I asked this over on webmasters.metaover on webmasters.meta and the response was pretty clear. They stay on SF. Server-side webmastery thingies like php/apache/mysql configs are clearly Our Problem. Things like picking which packages to run, design within frameworks, increasing search-engine visibility, and suchall are Their Problem.

I asked this over on webmasters.meta and the response was pretty clear. They stay on SF. Server-side webmastery thingies like php/apache/mysql configs are clearly Our Problem. Things like picking which packages to run, design within frameworks, increasing search-engine visibility, and suchall are Their Problem.

I asked this over on webmasters.meta and the response was pretty clear. They stay on SF. Server-side webmastery thingies like php/apache/mysql configs are clearly Our Problem. Things like picking which packages to run, design within frameworks, increasing search-engine visibility, and suchall are Their Problem.

Source Link
sysadmin1138 Mod
  • 135.3k
  • 6
  • 48
  • 90

I asked this over on webmasters.meta and the response was pretty clear. They stay on SF. Server-side webmastery thingies like php/apache/mysql configs are clearly Our Problem. Things like picking which packages to run, design within frameworks, increasing search-engine visibility, and suchall are Their Problem.