[wp-meta] [Making WordPress.org] #1113: Site Cloner: Add support for Remote CSS plugin

Making WordPress.org noreply at wordpress.org
Thu Jul 9 14:15:43 UTC 2015


#1113: Site Cloner: Add support for Remote CSS plugin
------------------------+--------------------------
Reporter:  iandunn      |      Owner:
    Type:  enhancement  |     Status:  new
Priority:  normal       |  Component:  wordcamp.org
Keywords:  needs-patch  |
------------------------+--------------------------
 In the near future, [https://make.wordpress.org/community/2015/06/16
 /editing-wordcamp-css-locally-with-git/ WordCamp.org will be able to
 import CSS from remote Git repositories], to allow organizing teams to use
 a traditional development workflow instead of Jetpack's CSS editor.

 When that launches, the Site Cloner will need to be able to import the CSS
 that the site uses.

 I think most teams who use the Site Cloner will be doing so because they
 don't have the resources to build a new design from scratch, which makes
 it unlikely that they'd want to use a remote repository, and will probably
 be using the Jetpack editor.

 I also don't see a good way to support the Remote CSS approach directly;
 we wouldn't want to use the source site's repository, because any changes
 to it would cause unintended changes to the new site.

 So, I think it's probably best to just copy the cached/sanitized CSS from
 the source site, and then add that to Jetpack's CSS on the new site.

 It should be prepended to any Jetpack CSS that's also being pulled in, to
 maintain the same cascading order that the Remote CSS plugin implements.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1113>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list