Issue 6210 - Implement Subscription (Double-opt-in) template for newsletter

src/scss/_content.scss

Index: src/scss/_content.scss
===================================================================
new file mode 100644
--- /dev/null
+++ b/src/scss/_content.scss
@@ -0,0 +1,19 @@
+/*******************************************************************************
+ * Content
+ ******************************************************************************/
+
+.content
+{
+  p { margin: 1em 0em; }
+  
+  a,
+  a:visited
+  {
+    color: $secondary;
+    text-decoration: underline;
+  }
+
+  abbr { text-decoration: none; }

[juliandoucette, 2018/01/22 19:47:53]

NIT: This is a very general rule for a very specific use case.

[ire, 2018/01/23 08:48:09]

I didn't think it was necessary to introduce a class in this case since we don't
have any other use cases for the abbr element. If/when we do, we can add that
extra specificity.

[juliandoucette, 2018/01/23 17:00:46]

I think we should take the opposite approach.

ID: Expectation of a unique use case
Class: Expectation of multiple use cases
HTML Tag: Expectation of most use cases (exceptions are exceptions)

In this case, I think that we are not expecting all abbrs to have no text
decoration. I think that we are expecting the one or more abbr of a specific
type (required asterisk) to have no text decoration (hence I think class is more
appropriate).

It is true that it doesn't matter here (hence NIT). But I think we should fix
this if we prefer to optimize for maintainability[1].

[1]: If we define maintainability as the ease in which issues can be fixed when
they occur. And the potential issue as the addition of an <abbr> tag to this
page that should have text decoration. Assuming most use cases for abbr should
have text decoration on this page and that none of such cases have occurred yet.

+
+  .color-secondary { color: $secondary; }
+}