Title: Git – Make WordPress Community --- # Tag Archives: Git [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 7:22 pm _on_ November 24, 2015 Tags: Git, [Improving WordCamp.org ( 17 )](https://make.wordpress.org/community/tag/improving-wordcamp-org/), [Jetpack CSS Editor ( 4 )](https://make.wordpress.org/community/tag/jetpack-css-editor/), [wordcamp.org ( 34 )](https://make.wordpress.org/community/tag/wordcamp-org/)    # 󠀁[Remote CSS Plugin Launched on WordCamp.org](https://make.wordpress.org/community/2015/11/24/remote-css-plugin-launched-on-wordcamp-org/)󠁿 [The Remote CSS tool](https://make.wordpress.org/community/2015/06/16/editing-wordcamp-css-locally-with-git/) is now available on WordCamp.org. It’s one of the ideas that came out of last year’s Community Summit, and it allows WordCamp.org site developers to work with whatever tools they want, instead of Jetpack’s CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. editor. [⌊remote-css-basic⌉⌊remote-css-basic⌉[ ## What You Can Do For instance, you can: * Work in a local development environment, like Varying Vagrant Vagrants. * Use your favorite IDE or text-editor, like PhpStorm or Sublime Text. * Use SASS or LESS instead of vanilla CSS. * Use tools like Grunt to automate your workflow. * Manage your CSS in a version control system like GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. [https://git-scm.com/](https://git-scm.com/). * Collaborate with others on a social coding platform like GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/). You can use all of those tools, only some of them, or completely different ones. It’s up to you how you choose to work. ## How It Works Remote CSS works by downloading your CSS file from a remote server (like GitHub. com), sanitizing it to remove security threats, minifying it, and then storing a local copy on WordCamp.org. The local copy is then enqueued as a stylesheet, either in addition to your theme’s stylesheet, or as a replacement for it. The local copy of the CSS is synchronized with the remote file whenever you press the _Update_ button, and you can also setup webhook notifications for automatic synchronization when the remote file changes. Because of security concerns, it can only support specific hosting platforms, but it currently supports GitHub, and we can add others if there’s interest. If you  want to use Beanstalk, Bitbucket, CodeForge, or something else, let me know. ## Contextual Help The pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. also contains detailed setup instructions inside wp-admin; just open the Help tab. [⌊remote-css-help⌉⌊remote-css-help⌉[ It plays nicely with Jetpack, so you can test it out today without losing any of your current CSS. If you’re looking for something simpler, though, Jetpack’s CSS Editor is still a great option. If you have any feedback or ideas to improve it, please leave a comment. If you’d like to check out the source code, it’s [available in the Meta repository](https://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-remote-css). [#git](https://make.wordpress.org/community/tag/git/), [#improving-wordcamp-org](https://make.wordpress.org/community/tag/improving-wordcamp-org/), [#jetpack-css-editor](https://make.wordpress.org/community/tag/jetpack-css-editor/), [#wordcamp-org](https://make.wordpress.org/community/tag/wordcamp-org/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcommunity%2F2015%2F11%2F24%2Fremote-css-plugin-launched-on-wordcamp-org%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 7:32 pm _on_ June 16, 2015 Tags: Git, [Improving WordCamp.org ( 17 )](https://make.wordpress.org/community/tag/improving-wordcamp-org/), [Jetpack CSS Editor ( 4 )](https://make.wordpress.org/community/tag/jetpack-css-editor/), [official websites ( 44 )](https://make.wordpress.org/community/tag/official-websites/), [wordcamp.org ( 34 )](https://make.wordpress.org/community/tag/wordcamp-org/)    # 󠀁[Editing WordCamp CSS Locally with Git](https://make.wordpress.org/community/2015/06/16/editing-wordcamp-css-locally-with-git/)󠁿 One of the [Improving WordCamp.org projects](https://make.wordpress.org/community/2015/06/10/wordcamp-org-tools-survey-results/) is to let organizers develop their CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. locally, and then commit it to a version control system like GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. [https://git-scm.com/](https://git-scm.com/), and have it automatically updated on their WordCamp.org site. This is the project that I think will make the most impact for organizing teams with experienced developers. The benefits are that: * You avoid all of [the pain points](https://make.wordpress.org/community/2015/03/05/improving-wordcamp-org-user-experience-of-the-css-editor/) of editing CSS in a browser. * You can use whatever IDE and other tools that you normally use. * You get all the benefits of a version control system, like easier/safer collaboration, history, and a structured approach. So, I’d like to discuss the best way to implement a system like that. ### Implementing a solution After thinking about it for awhile, this is the best approach I’ve come up with: _(Note: This process has been updated since it was originally published, to incorporate feedback from the comments.)_ 1. Add a new wp-admin screen under the Appearance menu, called something like “Remote CSS”. It will have a field where you can enter the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress. org for a CSS file, and a button to pull CSS from that repository and enqueue it locally. The CSS file can be in a source control repository like Git, but it doesn’t have to be. 2. The CSS file can be named anything, and it can be built from supporting SASS/LESS/ etc files, but only the CSS file will be used by WordCamp.org; everything else will be ignored. 3. The contents of CSS file will be passed through Jetpack’s CSS sanitization functions, and if there’s anything left, the safe CSS will be cached. If there are any errors while fetching the file, the process will abort to avoid overriding the known-good version that’s already stored on WordCamp.org. 4. When front-end pages are loaded, the cached CSS will be enqueued as a extra stylesheet, similar to how Jetpack’s Custom CSS is enqueued. 5. To automate updates, there will also be an endpoint listening for [webhook](https://developer.github.com/webhooks/) notifications of pushes to source control repositories. If the files changed in the pushed commits include the CSS file, the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. will automatically fetch the latest version, sanitize it, and cache it. Updates will be limited to once every 3 minutes, to prevent abuse. Rate-limited notifications should be queued and acted on once the limit has expired. 6. If the fieldon the Remote CSS screen for the CSS file is empty, we’ll display step- by-step instructions for setting up the CSS file, webhook, and a [local WordCamp.org sandbox](https://plan.wordcamp.org/first-steps/web-presence/using-the-wordcamp-theme/setting-up-a-local-wordcamp-org-sandbox/). If the file is hosted on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/), we’ll also recommend [enabling two factor authentication](https://help.github.com/articles/about-two-factor-authentication/), to mitigate the risk of a compromised account leading to CSS defacement or other malicious changes. 7. A new metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. box could be added to the _Appearance > Custom CSS_ page to advertise the option of using a remote repository. Does anybody see any problems with that approach, have a different idea, or have any other feedback?   [#git](https://make.wordpress.org/community/tag/git/), [#improving-wordcamp-org](https://make.wordpress.org/community/tag/improving-wordcamp-org/), [#jetpack-css-editor](https://make.wordpress.org/community/tag/jetpack-css-editor/), [#official-websites](https://make.wordpress.org/community/tag/official-websites/), [#wordcamp-org](https://make.wordpress.org/community/tag/wordcamp-org/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcommunity%2F2015%2F06%2F16%2Fediting-wordcamp-css-locally-with-git%2F%23respond&locale=en_US)