I’m always interested in the development details of other products, particularly their styleguides and approach to CSS. Given my penchant for the otherwise inane CSS details, I decided to write a bit about GitHub’s CSS.
You're minding your own business, casually browsing around on the World Wide Web. You navigate to a page that begins to load and render, but suddenly it stalls. For a few seconds you stare at a partial white screen, appalled at the hiatus your device has placed on your browsing flow. Finally, the page yields and loads the remainder of the content. What just happened? It's likely that you've fallen prey to a poorly implemented Facebook, Twitter, or Google Plus share button.
Social Networking widgets are a digital blot on the beautiful canvas we call the web. They often do not (with intent) blend with a site's design or with each other.
If you don't already know, GitHub is an incredibly effective way to collaborate on development projects. Providing a place for anyone with an internet connection to have an avenue where they can share code with the world for free (not to mention the robust supporting tools for source inspection and easy viewing of commit histories). GitHub has been adopted by many large open-source projects as their primary home for collaboration and contribution.
But how do you join in and contribute to a project? Sure, you know how to use Git to track changes to files and push those files to a server. But there are major benefits to getting involved in larger open-source projects, and GitHub is arguably the best place to start. Today, we will discuss a few rules of the road for collaborating on open source projects, and give you the knowledge and intuition you will need to get involved.
Une question que je me pose en ce moment… Comment, en PHP, comparer deux version d’un même texte et n’en faire plus qu’une contenant les différentes modifications. Basiquement : diff + merge. C’est ce qui est utilisé couramment dans les systèmes de Wiki (dont Wikipédia) et je vois quelques applications à cela qui pourraient être très sympathiques.
Après une petite recherche, voilà ce que je retiens de ce qui existe.
GitHub has become the corner stone for all things open source software. Developers love it, collaborate on it and are constantly building awesome projects through it. Apart from hosting our code, GitHub’s main attraction is using it as a collaborative tool. In this tutorial, let’s explore some of the most useful GitHub features, especially for working in teams, making it all the more efficient, productive and, most importantly, fun!
All that's needed to use the button is an a link to a specific repository (such as http://github.com/h5bp/html5-boilerplate)
. It doesn't need to be on your account, it can belong to anyone (which is particularly useful for groups and organizations that share repositories) and it's flexible, so it should work regardless of whether you have 8 watchers or 8,000.
Clears the junk out of your CSS by finding out which selectors are actually not used in your HTML.
With the onslaught of Twitter Bootstrap upon the world it's very tempting to just download their whole fat 80+Kb CSS and serve it up even though you're not using half of the HTML that it styles.
There's also the case of websites that have changed over time but without the CSS getting the same amount of love refactoring. Then it's very likely that you get CSS selectors that you're no longer or never using.
This tool can help you get started reducing all those selectors that you're not using.
No, that's a separate concern. This tool works independent of whitespace compression/optimization.
For example, if you have a build step or a runtime step that converts all your CSS files into one (concatenation) and trims away all the excess whitespace (compression) then the output CSS can still contain selectors that are never actually used.
Repo.js is a jQuery plugin that lets you easily embed a Github repo onto your site. This is great for other plugin or library authors that want to showcase the contents of a repo on their project pages.
Repo.js uses Markus Ekwall's jQuery Vangogh plugin for styling of file contents. Vangogh, subsequently, utilizes highlight.js, written by Ivan Sagalaev for syntax highlighting.
Stash n’est juste cool parceque ça veut dire joint en anglais, c’est aussi une fabuleuse fonctionalité de Git.
Quand vous devez faire un merge ou un checkout mais qu’il y a des modifications non sauvegardées en cours sur vos fichiers, Git va vous demander d’y remedier. Soit vous commitez les changements, soit vous les annulez, sans quoi pas de merge ni de checkout possible.
Dans d’autres cas vous travaillez sur un truc à moitié fini que vous ne voulez pas commiter encore (parceque c’est moche). Mais un bug est découvert qui prendra une seconde à corriger. Ca fait chier de mettre à l’eau toute les modifs ou de créer une branche pour ça.
Je sais, vous faites tous git add . comme Max des gros bourrins. Mais je vais partir du principe que certains d’entre vous font leurs commits avec amour, en prenant uniquement les fichiers dont ils ont besoin.
Et ces certains-d-entre-vous-qui-font-leurs-commits-avec-amour sont frustrés de devoir manuellement ajouter chaque fichier ou dossier.
Ceci est un message d’espoir pour notre minorité bafouée aux cris étouffés par la répression grondante des… Mais je m’égare.
La révolution s’appelle SCM Breeze, camarade
Ca s’installe les doigts dans le goulag:
There is now an "organization" on GitHub for CSS-Tricks. This is a great feature of GitHub and a perfect fit for us.
Git has come a long way since its introduction, and has become significantly easier to work with in a Windows environment. In this tutorial, we are going to get setup with Git on Windows.
As a web designer or web developer, you’ve probably heard of Git before, a version control system that has had a swift ascension to ubiquity due in part to GitHub, a social code repository site.
If you’d like to learn how to use Git, check out my top 10 favorite Git tutorials for beginners. At the end, you’ll also see a list of other educational Git resources.
One of the problems hacktivists ran into when trying to disseminate useful information to people in Syria and Egypt was how to get through to people when DNS and web access are being filtered or outright blocked. Putting up web pages containing phone numbers of ISPs volunteering dialup access was something of a crapshoot because there was no guarantee that people would be able to view them. Someone (I don't remember whom) hit on the idea of contacting sysadmins in the Middle East by leaving messages in the access and error logs of their web servers. This works but pumping an entire list of phone numbers, usernames, and passwords by hand over HTTP requests gets old fast, to say the least.