Replaced external confluence smile gif with font-awesome fa-smile-o

tzvatot · Oct 25, 2016 · 0764b3e · 0764b3e
1 parent 81835fe
commit 0764b3e
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 2 deletions.
diff --git a/10-minute-tutorial.md.vtl b/10-minute-tutorial.md.vtl
@@ -33,7 +33,7 @@ In practical terms, it achieves to manage all facets of your application's secur
 
 What can Apache Shiro do?
 
-A lot ![](https://cwiki.apache.org/confluence/images/icons/emoticons/smile.png). But we don't want to bloat the QuickStart. Please check out our [Features](features.html "Features") page if you'd like to see what it can do for you. Also, if you're curious on how we got started and why we exist, please see the [Shiro History and Mission](what-is-shiro.html "What is Shiro") page.
+A lot <i class="fa fa-smile-o" aria-hidden="true"></i>. But we don't want to bloat the QuickStart. Please check out our [Features](features.html "Features") page if you'd like to see what it can do for you. Also, if you're curious on how we got started and why we exist, please see the [Shiro History and Mission](what-is-shiro.html "What is Shiro") page.
 
 Ok. Now let's actually do something!
 

diff --git a/assets/css/style.css b/assets/css/style.css
@@ -362,4 +362,18 @@ ul.navigation a {
 .editThisPage {
 	position:absolute; bottom:2%; right:2%;
 	font-size:16px;
+}
+
+/* Yello smiles! */
+.fa-smile-o {
+	position: relative;
+}
+.fa-smile-o:before {
+	content: "\f111";
+	color: #f1c40f;
+}
+.fa-smile-o:after {
+	left: 0;
+	position: absolute;
+	content: "\f118";
 }
diff --git a/how-to-contribute.md b/how-to-contribute.md
@@ -164,7 +164,7 @@ This is a collection of tips for contributing to the project in a manner that is
 *   Start new threads with new Subject for new topics, rather than reusing the previous Subject line.
 *   Keep each topic focused. If some new topic arises then start a new discussion. This leaves the original topic to continue uncluttered.  
     Whenever you decide to start a new topic, then start with a fresh new email message window. Do not use the "Reply to" button, because threaded mail-readers get confused (they utilise the In-reply-to header). If so, then your new topic will get lost in the previous thread and go unanswered.
-*   Prepend your email subject line with a marker when that is appropriate, e.g. [Proposal], [RT] (Random Thought which quickly blossom into research topics ![](https://cwiki.apache.org/confluence/images/icons/emoticons/smile.png), [STATUS] (development status of a certain facility).
+*   Prepend your email subject line with a marker when that is appropriate, e.g. [Proposal], [RT] (Random Thought which quickly blossom into research topics <i class="fa fa-smile-o" aria-hidden="true"></i>, [STATUS] (development status of a certain facility).
 *   Remember that most people are participating in development on a volunteer basis and in their "spare time". These enthusiasts will attempt to respond to issues. It may take a little while to get your answers.
 *   Research your topic thoroughly before beginning to discuss a new development issue. Search and browse through the email archives - your issue may have been discussed before. Do not just perceive a problem and then rush out with a question - instead, delve.
 *   Try to at least offer a partial solution and not just a problem statement.