Initial checkin

Believe this structure will work, but it lacks style. Also need to add a listing page. Going to try and use categories to loop through pages.
WillSullivan · Jun 12, 2017 · 28966a0 · 28966a0
1 parent 503241e
commit 28966a0
Show file tree

Hide file tree

Showing 13 changed files with 233 additions and 0 deletions.
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,2 @@
+_site/
+.sass-cache/
diff --git a/_config.yml b/_config.yml
@@ -0,0 +1,27 @@
+# Site settings
+title: I Downvoted because...
+email: willsullivan@live.com
+url: http://idownvotedbecause.com
+description: "A website designed to help you help others"
+
+# Build settings
+markdown: kramdown
+permalink: pretty
+baseurl: /idownvotedbecause
+
+gems:
+  - jekyll-redirect-from
+  - jekyll-feed
+
+defaults:
+  - scope: 
+      path: ""
+    values:
+      layout: default
+  - scope:
+      path: "images"
+    values:
+      image: true
+
+sass:
+    sass_dir: _sass
diff --git a/_includes/footer.html b/_includes/footer.html
@@ -0,0 +1,8 @@
+<footer>
+    <section class="call-to-action">
+        <bold>Did this page help you?</bold> If not, or if you would like to leave feedback, please <b><a href="https://github.com/WillSullivan/IDownvotedBecause/issues/new">create an Issue regarding this page on GitHub.</a></b>
+    </section>
+    <section class="who-to-downvote">        
+        Project maintained primarily by <a href="https://github.com/WillSullivan">WillSullivan</a> with the help of people like you!
+    </section>
+</footer>
diff --git a/_includes/header.html b/_includes/header.html
@@ -0,0 +1,5 @@
+<header>
+    <h1>I downvoted because...</h1>
+    <h2 class="page-byline">...{{ page.byline }}</h2>
+    <a href="https://github.com/WillSullivan/IDownvotedYouBecause" class="logo" title="View the website repository on GitHub"></a>
+</header>
diff --git a/_layouts/default.html b/_layouts/default.html
@@ -0,0 +1,16 @@
+<!DOCTYPE HTML>
+<html>
+  <head>
+    <title>{{ page.title }}</title>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width,initial-scale=1">
+    <link rel="stylesheet" href="css/default.css">
+  </head>
+  <body>
+    {% include header.html %}
+    <section class="content">
+      {{content}}
+    </section>
+    {% include footer.html %}
+  </body>
+</html>
diff --git a/_sass/reset.scss b/_sass/reset.scss
@@ -0,0 +1,47 @@
+/* http://meyerweb.com/eric/tools/css/reset/ 
+   v2.0 | 20110126
+   License: none (public domain)
+*/
+html, body, div, span, applet, object, iframe,
+h1, h2, h3, h4, h5, h6, p, blockquote, pre,
+a, abbr, acronym, address, big, cite, code,
+del, dfn, em, img, ins, kbd, q, s, samp,
+small, strike, strong, sub, sup, tt, var,
+b, u, i, center,
+dl, dt, dd, ol, ul, li,
+fieldset, form, label, legend,
+table, caption, tbody, tfoot, thead, tr, th, td,
+article, aside, canvas, details, embed, 
+figure, figcaption, footer, header, hgroup, 
+menu, nav, output, ruby, section, summary,
+time, mark, audio, video {
+	margin: 0;
+	padding: 0;
+	border: 0;
+	font-size: 100%;
+	font: inherit;
+	vertical-align: baseline;
+}
+/* HTML5 display-role reset for older browsers */
+article, aside, details, figcaption, figure, 
+footer, header, hgroup, menu, nav, section {
+	display: block;
+}
+body {
+	line-height: 1;
+}
+ol, ul {
+	list-style: none;
+}
+blockquote, q {
+	quotes: none;
+}
+blockquote:before, blockquote:after,
+q:before, q:after {
+	content: '';
+	content: none;
+}
+table {
+	border-collapse: collapse;
+	border-spacing: 0;
+}
diff --git a/css/default.scss b/css/default.scss
@@ -0,0 +1,84 @@
+// @import 'reset';
+
+// $primary-color: #1e1e1e;
+// $primary-background-color: #c1c1c1;
+// $primary-font: 'Open Sans', sans-serif; 
+// $special-font: 'Helvetica Neue', sans-serif;
+// $padding: 18px;
+
+// body{    
+//     font-family: $primary-font;
+//     color: $primary-color; 
+// }
+
+// h1 { 
+//     font-family: $special-font;
+//     font-size: 96px; 
+//     font-weight: bold; 
+//     letter-spacing: -1px; 
+//     line-height: 1; 
+// }
+
+// h2 { 
+//     font-size: 30px; 
+//     font-weight: 300; 
+//     line-height: 32px; 
+// }
+// h3 { 
+//     font-size: 24px; 
+//     font-weight: 300; 
+//     line-height: 32px; 
+//     text-decoration: underline;
+// }
+// h4 { 
+//     font-size: 18px; 
+//     font-style: italic;
+//     font-weight: 300; 
+//     line-height: 32px; 
+// }
+
+// p { 
+//     background-color: $primary-background-color;
+//     font-family: 'Helvetica Neue', sans-serif; 
+//     font-size: 14px; 
+//     line-height: 24px; 
+//     margin: 0 0 24px; 
+//     text-align: justify; 
+//     text-justify: inter-word; 
+// }
+
+// .block{
+//   background-color: $primary-background-color;
+//   padding: $padding; 
+// }
+// header{
+//   @extend .block;
+// }
+// .page-byline{
+
+// }
+// .logo {
+//   position: absolute;
+//   height: 36px;
+//   width: 36px;
+//   right: $padding;
+//   top: $padding;
+//   display: block;
+//   background: url(images/octocat-logo.png);  
+// }
+// .content{
+
+// }
+// footer{
+//   @extend .block;
+//   position:absolute;
+//   bottom: 0px;
+//   right:0px;
+//   left:0px;
+// }
+// .call-to-action{
+
+// }
+// .who-to-downvote{
+
+// }
diff --git a/css/images/octocat-logo.png b/css/images/octocat-logo.png
diff --git a/images/stackoverflow/exceptionimage1.PNG b/images/stackoverflow/exceptionimage1.PNG
diff --git a/images/stackoverflow/exceptionimage2.PNG b/images/stackoverflow/exceptionimage2.PNG
diff --git a/images/stackoverflow/exceptionimage3.PNG b/images/stackoverflow/exceptionimage3.PNG
diff --git a/index.md b/index.md
@@ -0,0 +1,6 @@
+---
+title: I downvoted because...
+byline: a website designed to help you help others!
+---
+
+Main page content goes here, hopefully
diff --git a/stackoverflow/imageofanexception.md b/stackoverflow/imageofanexception.md
@@ -0,0 +1,38 @@
+---
+title: ...a picture of your exception isn't helpful
+permalink: imageofanexception/
+categories: stackoverflow
+---
+##Pictures of exceptions are not helpful 
+In your question, you indicated that there was an exception thrown when your code executes. That's good information that we need to help you find a solution. However, in order to find that solution, we need to know the details that can be found within the exception. If your question lacks this detailed exception information, it becomes harder for us to help you.
+
+###Why this is a problem
+Pasting a picture of your exception is not helpful. You do not have to prove your code threw an Exception with a picture of it--we trusted you when you stated this fact within your question.
+
+![The exception dialog](images/stackoverflow/exceptionimage1.PNG)
+
+Pictures of Exceptions that shows some of the detail contained within the exception *are also not helpful.*
+
+![Viewing the details of the exception](images/stackoverflow/exceptionimage2.PNG)
+
+###Why this is worth a downvote
+One of the first things people do when trying to help someone with an exception is *they copy text from the exception and paste it into their favorite search engine*. When you put an image of the exception into your question, you force people who are trying to help you--*for free*--**to transcribe the exception from your image**. Not only is this an annoying waste of time, but also it can result in transcription errors and reduce the chance that the search is successful.
+
+No image can contain **all of the details** from your exception. Exceptions contain [stack traces](https://en.wikipedia.org/wiki/Stack_trace) which are often very long and won't fit in an image. Exceptions also can contain *inner exceptions* which have stack traces of their own, and they can have inner exceptions as well. We need all that information to answer your question. Your image isn't giving us this necessary information!
+
+In addition, text in images isn't indexed. This makes it very hard, if not impossible, to find your question via search engines. It reduces the visibility of your question and prevents future readers from finding it. It also prevents people who use screen readers from being able to answer your question.
+
+###Capturing exception details
+Instead of taking a picture of the exception, **get a text report of all of the contents within it.** This can usually be accomplished very easy, depending on what language and tools you are using. Here are some examples of capturing these details. 
+
+####Visual Studio and .NET
+If you are debugging in Visual Studio, the Exception Helper Dialog contains a link that will copy all exception details to the clipboard 
+
+![The link to copy exception details to the clipboard on the exception helper dialog](images/stackoverflow/exceptionimage3.PNG)
+
+If you are experiencing the Exception at runtime, you can [catch the exception](http://stackoverflow.com/questions/9526139/how-to-catch-exceptions) and call 'ToString()' on it. Log the result, using whatever method is most convenient for you.
+
+###What to do next
+Once you have gathered all the details from the exception, you can paste it into your question in an edit. **This is important**--do not try to paste the exception details into a comment, as there is not enough room for all the of details. There is an "edit" link at the bottom of your question, click it and paste the details into your question. And don't forget to format it!
+
+Once you have done this, leave a comment to the person who sent you this link. They will be happy to retract their downvote.