blog-rekahsoft-ca/sass/default.sass

151 lines
3.4 KiB
Sass
Raw Normal View History

Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
// (C) Copyright Collin Doering @!@YEAR@!@
//
// This program is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program. If not, see <http://www.gnu.org/licenses/>.
// File: default.sass
// Author: Collin J. Doering <rekahsoft@gmail.com>
// Date: Dec 5, 2013
//
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
// Use Bourbon
@import 'sass/bourbon/bourbon'
@import 'sass/fonts'
@import 'sass/util'
@import 'sass/header'
@import 'sass/home-page'
@import 'sass/blog-page'
@import 'sass/contact-page'
@import 'sass/tag-page'
@import 'sass/post-page'
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
@import 'sass/src-highlight'
//-------------------------------------------------------------------------------------
// General
//-------------------------------------------------------------------------------------
body
background: #efe
font: 14px/21px FreeMono, monospace, Helvetica, Arial, sans-serif
h1,h2,h3,h4,h5,h6
font-family: FreeMono
h1
font-size: 2.5em
h2
font-size: 2em
h3
font-size: 1.75em
h4
font-size: 1.5em
h5
font-size: 1.25em
h6
font-size: 1em
ul, ol
padding-left: 1em
hr
margin-bottom: 0.5em
sup
vertical-align: super
sub
vertical-align: sub
#noscript-alert
@include border-box(0, #FCD4D4)
text-align: center
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
#page-content
opacity: 1
@include transition(opacity 250ms ease-out)
margin-top: 1em
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
overflow: hidden
ul > li:before
content: "\2192"
padding-right: 0.5em
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
font-size: 1.5em
ul > li
margin-bottom: 0.02em
ol > li
margin-bottom: 0.02em
#page-content.loading
opacity: 0.35
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
#page-content.loading-done
@include transition(opacity 1s ease-in 0.5s)
opacity: 1
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
#page-content.loading-error p
background: #fd6f6f url('/images/error-loading.png') no-repeat 50%
height: 200px
font-weight: bold
line-height: 200px
text-align: center
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
#page-content.init.loading
background: url('/images/init-loading.gif') no-repeat 50%
height: 125px
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
#footer-left
padding-left: 1em
#footer-right
text-align: right
.border-box
Major changes! See full log. * Changes ** Hakyll "site.hs" *** Added the ability to have per-page templates (for all "pages/*") *** "pages/*" can now be sectioned off into blocks A section is a logical division of a page. It removes the requirement for pages that have multiple sections to have some html in the markdown for the page or to move some of the markdown content to the template. Both of which are un-maintainable. There are two types of sections, both with slightly different syntax's. A _global section_ is a section who's content will be included in all sections (regardless of ordering). This is handy for including links and footnotes that might be needed in more then one section or non-section . It is not accessible from the Context obtained from genSectionContext. To indicate where a global section begins and ends use "$section$" and "$endsection$" respectively (without quotes). Formally: $section$ <body> $endsection$ A _named section_ is a section of a document that can be accessed by a given name from the context obtained from the function genSectionContext. To specify a named section use the following syntax: $section("<name>")$ <body> $endsection$ where <name> is the name of the section (any character except \") and <body> is the section body Anything that is not a section is referred to as a non-section. These are still important as they will include all content of the global sections of the document as well as the non-section itself. To be a little more formal a non-section is everything between "$end-section$" and ("$section$ or $section("<name>")$"). **** Example: mypage.markdown page title ========== $section("column-one")$ This is text that can be formatted in the individual page template located at "templates/pages/mypage.haml". Here is a link from a global section. See [Home][]. $endsection$ This is some text in between two sections or a section and the top or bottom of the page. It can be accessed by $body<n>$ where <n> its position from the top of all non-sections starting from 0. Here i can also use $section$ [Home]: http://blog.rekahsoft.ca $endsection$ ***** To see more visit - "pages/<name>" where the sectioned page markdown is written - "templates/pages/<name>.haml" where the individual page template is stored/loaded from - "templates/page.haml" the generic page wrapper ** Miscellaneous *** Reorganized the file structure - created folder "image-src" for image-sources - created folder "lib" for libraries that will be needed on the server - moved jQuery and Skeleton to lib and made appropriate - created folder "fonts" for FreeMono and FreeSans font files which are now used via css @font-face - create folder "css" and setup "site.hs" to minimize all css files and publish them to idRoute - created folder "sass" which contains a variety of s[ac]ss files along with a file named "default.s[ax]ss" which will be processed by sass to include any other s[ac]ss files that are needed and output "default.css" to the site root *** cleaned up .gitmodules ** Javascript - fixed processing of urls - temporarily disabled nojs version of site as its under heavy development Note: still need to merge changes made to default version into the nojs one; specifically having "templates/pages/*.haml" be applied to there respective page before "templates/page.haml" is applied to the result ** Styling - switched to using sass (with a side bourbon) instead of css leaving css folder and processing for convenience - slimmed the site of the nav-loading image - updated favicon (rounded corders, preparing to support more sizes) - updated the logo-banner - added new images for tab page ** Templates - converted all "templates/**" to haml and made the apropriate adjustments in site.hs - added "templates/pages/*" which contains individual templates per page in "pages/*" ** Known Issues **** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser) **** pagination has been attempted but no solution yet **** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version **** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2013-12-11 04:31:48 +00:00
@include border-box()
//-------------------------------------------------------------------------------------
// @media selectors
//-------------------------------------------------------------------------------------
// Smaller than standard 960 (devices and browsers)
@media only screen and (max-width: 959px)
// Tablet Portrait size to standard 960 (devices and browsers)
@media only screen and (min-width: 768px) and (max-width: 959px)
// All Mobile Sizes (devices and browser)
@media only screen and (max-width: 767px)
#footer-left, #footer-right
text-align: center
#logo
height: 130px
// Mobile Landscape Size to Tablet Portrait (devices and browsers)
@media only screen and (min-width: 480px) and (max-width: 767px)
#logo-background
padding: 0.5em 0
#nav-menu li
padding: 10px 1.5em
#footer-left
padding-left: 0
// Mobile Portrait Size to Mobile Landscape Size (devices and browsers)
@media only screen and (max-width: 479px)
#logo-background
padding: 0
#nav-menu li
padding: 10px 5px