swiftfire-jekyll-theme 0.2.0

data/pages/account/email-verification-failed.sf.md

@@ -0,0 +1,11 @@
+---
+layout: page
+title: Email verification failed
+---
+Unfortunately an error occurred.
+
+If a typo or copy/paste error was made, you can try to visit the link in the email again.
+
+It could also be that you inadvertently visited the link twice (or more) and the corresponding account is already verified.
+
+If you think this is a server error you can contact the administrator to speed up the processing of this fault (the information was already recorded). See the contact page for details.

data/pages/account/email-verification-success.sf.md

@@ -0,0 +1,7 @@
+---
+layout: page
+title: Email verification completed
+---
+Thanks for completing the registration process.
+
+Your account can now be used: [Login](/pages/login.sf.html)

data/pages/account/error.sf.md

@@ -0,0 +1,13 @@
+---
+layout: page
+title: Error
+---
+An error occurred that prevented completion of your request.
+
+If this is a recoverable error, you can try again.
+
+If this is a non-recoverable error a log entry was made and will be investigated in due time. You can speed up error investigation by alerting the admin through the contact page. 
+
+The following error message was generated:
+
+.show($service.error-message)

data/pages/account/forgot-password-continue.sf.md

@@ -0,0 +1,9 @@
+---
+layout: page
+title: An email was send
+---
+An email has been sent to the email address associated with the account.
+
+If you do not receive an email, either the account does not exist, the email was mistakenly classified as spam, or you do not have access (anymore) to the old email account. In these cases please contact an administrator.
+
+Please visit the link in that email within the next 24 hours to set a new password.

data/pages/account/forgot-password.sf.md

@@ -0,0 +1,25 @@
+---
+layout: page
+title: New Password?
+---
+If you forgot your password, you can use this page to set a new password.
+
+Step 1: Fill in the name of the account
+
+Step 2: Click 'Set New Password'
+
+Step 3: Wait for the email to arrive and visit the link in the email
+
+Step 4: Set a new password
+
+The link in the mail is valid for 24 hours. The account remains usable with the old password up until a new password is set.
+
+<form action="/command/forgot-password" method="post">
+	<div style="display:flex; flex-direction:column; justify-content:center; margin-bottom:50px;">
+		<div style="margin-left:auto; margin-right:auto;">
+			<p style="margin-bottom:0px">Name:</p>
+			<input style="width:100%; color:black;" type="text" name="forgot-password-account-id" value="" autofocus><br><br>
+			<input style="width:100%; color:black;" type="submit" value="Set New Password">
+		</div>
+	</div>
+</form>

data/pages/account/login.sf.md

@@ -0,0 +1,19 @@
+---
+layout: page
+title: Login
+---
+<form action="/command/login" method="post">
+	<div style="display:flex; flex-direction:column; justify-content:center; margin-bottom:50px;">
+		<div style="margin-left:auto; margin-right:auto;">
+			<p>.show($request.previous-attempt-message!)</p>
+		</div>
+		<div style="margin-left:auto; margin-right:auto;">
+			<p style="margin-bottom:0px">Name:</p>
+			<input style="width:100%; color:black;" type="text" name="login-name" value=".show($request.login-name!)" autofocus><br>
+			<p style="margin-bottom:0px">Password:</p>
+			<input style="width:100%; color:black;" type="password" name="login-password" value=".show($request.login-password!)"><br><br>
+			<input style="width:100%; color:black;" type="submit" value="Login">
+			<p><a href="/pages/register.sf.html">Register</a> - <a href="/pages/forgot-password.sf.html">Forgot password?</a></p>
+		</div>
+	</div>
+</form>

data/pages/account/not-allowed.sf.md

@@ -0,0 +1,7 @@
+---
+layout: page
+title: Not allowed
+---
+You seem to have tried something which is not allowed.
+
+For example doing something twice that has an explicit one-off authorization.

data/pages/account/register-continue.sf.md

@@ -0,0 +1,11 @@
+---
+layout: page
+title: Complete registration
+---
+Thanks for registering.
+
+An email has been sent to .show($request.register-email)
+
+Please wait for this email and visit the confirmation link in it to complete the registration process.
+
+Your account can be used after that link has been visited.

data/pages/account/register.sf.md

@@ -0,0 +1,30 @@
+---
+layout: page
+title: Register
+---
+To register, fill out the fields below and click the 'Register' button. Upon verification of the fields values, an email will be sent to the given address containing a verification link. Visit that link to complete the registration process.
+
+<form action="/command/register" method="post">
+	<div style="display:flex; flex-direction:column; justify-content:center; margin-bottom:50px;">
+		<div style="margin-left:auto; margin-right:auto;">
+			<p>.show($request.previous-attempt-message!)</p>
+		</div>
+		<div style="margin-left:auto; margin-right:auto;">
+			<br>
+			<p style="margin-bottom:0px">Name:</p>
+			<input style="color:black;" type="text" name="register-name" value=".show($request.register-name!)" autofocus>
+			<br>
+			<p style="margin-bottom:0px">Password:</p>
+			<input style="color:black;" type="password" name="register-password-1" value=".show($request.RegisterPassword1!)">
+			<br>
+			<p style="margin-bottom:0px">Password:</p>
+			<input style="color:black;" type="password" name="register-password-2" value=".show($request.RegisterPassword2!)">
+			<br>
+			<p style="margin-bottom:0px">Email:</p>
+			<input style="color:black;" type="text" name="register-email" value=".show($request.register-email!)">
+			<br>
+			<br>
+			<input style="width:100%; color:black;" type="submit" value="Register">
+		</div>
+	</div>
+</form>

data/pages/account/request-new-password-failed.sf.md

@@ -0,0 +1,13 @@
+---
+layout: page
+title: Request failed
+---
+Unfortunately an error occurred.
+
+If a typo or copy/paste error was made, you can try to visit the link in the email again.
+
+If you waited more than 24 hours before using the link, then the link has expired.
+
+It could also be that you inadvertently visited the link twice (or more) and the password was already changed.
+
+Either way, you can always [try again](/pages/forgot-password.sf.html).

data/pages/account/set-new-password-success.sf.md

@@ -0,0 +1,7 @@
+---
+layout: page
+title: Success
+---
+Your password was updated.
+
+Your account can now be used: [Login](/pages/login.sf.html)

data/pages/account/set-new-password.sf.md

@@ -0,0 +1,25 @@
+---
+layout: page
+title: Set New Password
+---
+If you requested to set a new password for your account, you can do so here. If not, simply ignore this page.
+
+<form action="/command/set-new-password" method="post">
+	<input type="hidden" name="set-new-pwd-acc-id" value=".show($request.set-new-pwd-acc-id)">
+	<div style="display:flex; flex-direction:column; justify-content:center; margin-bottom:50px;">
+		<div style="margin-left:auto; margin-right:auto;">
+			<p>.show($request.previous-attempt-message!)</p>
+		</div>
+		<div style="margin-left:auto; margin-right:auto;">
+			<br>
+			<p style="margin-bottom:0px">Password:</p>
+			<input style="color:black;" type="password" name="set-new-password-1" value=".show($request.set-new-password-1!)">
+			<br>
+			<p style="margin-bottom:0px">Password:</p>
+			<input style="color:black;" type="password" name="set-new-password-2" value=".show($request.set-new-password-2!)">
+			<br>
+			<br>
+			<input style="width:100%; color:black;" type="submit" value="Set New Password">
+		</div>
+	</div>
+</form>

data/pages/categories/classic.md

@@ -0,0 +1,10 @@
+---
+layout: category-page
+title: classic
+---
+
+This file is only used to initiate the compilation of a category page for the category shown as title.
+
+Duplicate this file with a different name and title for each category you want included in the list of category pages.
+
+Note: title and category are case sensitive!

data/pages/categories/example.md

@@ -0,0 +1,10 @@
+---
+layout: category-page
+title: example
+---
+
+This file is only used to initiate the compilation of a category page for the category shown as title.
+
+Duplicate this file with a different name and title for each category you want included in the list of category pages.
+
+Note: title and category are case sensitive!

data/pages/categories/jekyll.md

@@ -0,0 +1,10 @@
+---
+layout: category-page
+title: jekyll
+---
+
+This file is only used to initiate the compilation of a category page for the category shown as title.
+
+Duplicate this file with a different name and title for each category you want included in the list of category pages.
+
+Note: title and category are case sensitive!

data/pages/categories/update.md

@@ -0,0 +1,10 @@
+---
+layout: category-page
+title: update
+---
+
+This file is only used to initiate the compilation of a category page for the category shown as title.
+
+Duplicate this file with a different name and title for each category you want included in the list of category pages.
+
+Note: title and category are case sensitive!

data/pages/classic/01-features.md

@@ -0,0 +1,36 @@
+---
+layout: page
+title: The Classic Jekyll Theme
+date: 2017-12-20
+menuInclude: yes
+menuLink: yes
+menuTopTitle: Classic
+menuTopIndex: 2
+menuSubs:
+- title: Features
+  index: 1
+excerpt: Landing page for the Classic menu topics with a list of the main features.
+---
+The main features of this theme are as follows:
+
+- RWD design (automatic reordering of the content to fit the width of the device it is viewed on)
+- Integrated menubar generator with drop-down menu (the drop-down aspect can be disabled)
+- Menu items can be three levels deep (Item, subitem, sub-subitem)
+- Automatic vertical menu when disabling the drop-down aspect of the menubar
+- Integrated categories page generator
+- Page by page override of layout and secondary/tertiary column content
+- Extensive configuration of visible elements (font, color, background, padding, size etc)
+- Banner & menubar may be fixed to the top of the browser window
+- Release date for pages
+- Includes several widgets:
+	- Recent posts
+	- Older posts
+	- Categories
+- Includes cookies warning (can be disabled)
+- Includes disqus & google analytics
+- Language customization (not multi-langage)
+- Pure HTML5/CSS3 possible (a few features need Javascript but these can be disabled)
+- Supports block layout
+- Fast rebuild option for content creation
+- Documented source code
+- Generated HTML is quite readable

data/pages/classic/02-setup.md

@@ -0,0 +1,113 @@
+---
+layout: page
+title: Installation & Setup
+date: 2017-12-20
+tertiary-column: none
+menuInclude: yes
+menuTopTitle: Classic
+menuSubs:
+- title: Installation & Setup
+  index: 2
+excerpt: Installation and initial setup of the Classic Jekyll Theme
+---
+## Installation
+
+The two most common ways of installing this theme is either using the git _clone_ command, or the gem-based approach.
+
+Either way will work just fine.
+
+If this theme is the basis for your own theme, then it seems prudent to use the _clone_ command. The cloned repository can then serve as the _master_ repository for your websites.
+
+If the only purpose is to create a website, then the gem command will result in less clutter in the website directory.
+
+This installation description presupposes that Jekyll is already installed. If not, please check out the [Jekyll](https://jekyllrb.com) website for more information.
+
+No matter which installation method is chosen it is always prudent to make sure the Jekyll environment is up to date by updating the gems:
+
+    gem update
+
+### Using the Git clone command
+
+#### Preparing for Installation
+
+The theme uses a pluging called 'jekyll-data'.
+
+This is installed with the command:
+
+    gem install jekyll-data
+    
+At the time of writing jekyll-data is at version 1.0.0. The developper of jekyll-data has announced that all versions below 2.0.0 should be compatible.
+
+#### Install
+
+Create a new repository with:
+
+    git clone https://github.com/Balancingrock/classic-jekyll-theme repository-name
+
+of course the _repository-name_ should be replaced with the name of new local repository.
+
+If the theme will be modified and used in more than one website, it may be advantageous to use the local repository only for theme related work. And use the local repository as the master repository for other website development. If you know your way around git, we would even advise to create a separate branch for your own development efforts. That makes it more manageable to merge future changes from the classic theme.
+
+#### Setup
+
+There is 1 change that _should_ be made first: in `_config.yml` __and__ `_sass/classic-jekyll-theme.scss` change the definition of `baseurl` from _"classic-jekyll-theme"_ to _""_.
+
+Now start the jekyll server with the command:
+
+    bundle exec jekyll serve
+
+Next point your browser to: _localhost:4000_ and you will see the same site as this one, but hosted on your own computer.
+
+If the `baseurl` was not changed, then point the browser to _localhost:4000/classic-jekyll-theme/index.html_.
+
+To stop the jekyll server use the key combination: _CTRL-C_. 
+
+It is recommended to explore the files `_config.yml`, `_data/setup.yml` and `_sass/classic-jekyll-theme.scss` before making changes to the theme itself. In general it is save to change any setting in these files and check the results of a modification in the browser. Note that any changes to `_config.yml` require a restart of the server as above. Changes to setup and classic-jekyll-theme can be seen bij saving the file and reloading the browser. Note that some changes may require a few seconds before the compilation is ready.
+
+Always check the output of the compilation in the terminal (command line) window! Error messages will appear in that window, not the browser!
+
+And finally: When using _git clone_ you will end up with files in the pages and _posts directory that you don't need (or want!) Simply delete what you cannot use from any of these directories (the `pages` directory can be deleted completely)
+ 
+### Gem based
+
+Install the theme with the command:
+
+    gem install classic-jekyll-theme
+
+Since you will need to copy some files from the gem directory, check where that directory is with:
+
+    bundle show classic-jekyll-theme
+
+For convenience you can create an alias to the gem directory at the same level as the root of your website directory.
+
+#### Create a new site & Setup
+
+Create a new website with:
+
+    jekyll new mysite
+
+Change to the new directory `mysite`.
+
+Copy the file `_sass/classic-jekyll-theme.scss` from the gem directory to `mysite/_sass/classic-jekyll-theme.scss`
+Copy the file `_data/setup.yml` from the gem directory to `mysite/_data/setup.yml`
+
+In the file `mysite/_config.yml` change _theme: minima_ to _theme: classic-jekyll-theme_.
+In the file `mysite/Gemfile` change _gem "minima", "~> 2.0"_ to _gem "classic-jekyll-theme"_.
+In the file `mysite/_sass/classic-jekyll-theme.scss` change _$baseurl: "classic-jekyll-theme"_ to _$baseurl: ""_.
+
+Optional:
+- Remove the `mysite/about.md` file.
+- Copy the folder `icons` from the gem directory to `mysite/icons` (to be used as examples, replace them later with icons of your own)
+- Copy the file `banner-area.md` from the gem directory to `mysite/banner-area.md` (needed when using a separate banner file, which is _not_ used by default)
+
+Now you are ready to start the jekyll server:
+
+    bundle exec jekyll serve
+    
+(Note: depending on what was done before, the `Gemfile.lock` may cause problems. If so, simply delete that file. Anytime the _bundle_ command is run it will be recreated when its is not present, and on recreation it will also be filled with the correct data)
+
+It is recommended to explore the files `_config.yml`, `_data/setup.yml` and `_sass/classic-jekyll-theme.scss` before making changes to the theme itself. In general it is save to change any setting in these files and check the results of a modification in the browser. Note that any changes to `_config.yml` require a restart of the server as above. Changes to setup and classic-jekyll-theme can be seen bij saving the file and reloading the browser. Note that some changes may require a few seconds before the compilation is ready.
+
+Always check the output of the compilation in the terminal (command line) window! Error messages will appear in that window, not the browser!
+
+To stop the jekyll server use the key combination: _CTRL-C_. 

data/pages/classic/03-pages-and-posts.md

@@ -0,0 +1,25 @@
+---
+layout: page
+title: Pages and Posts in classic
+date: 2017-12-20
+menuInclude: yes
+menuTopTitle: Classic
+menuSubs:
+- title: Pages and Posts
+  index: 3
+excerpt: "An excerpt is used as the page description and can be up to 160 characters long..."
+---
+Pages and Posts in Classic are created as is standard for Jekyll.
+
+Additional YAML front matter:
+
+- __comments__: When a disqus account is available, setting the `comments` to _yes_ will enable the disqus comment section.
+- __secondary-column__: This is an override setting of the general parameter in `site.data.setup.secondary-column`. Set this to either _none_, _right_ or _left_ to affect the placing of the secondary column for this page/post only. Note that disabling the secondary column when the drop-down menu is disabled (i.e. `site.data.setup.drop-down-menu` is set to _no_) will result in the loss of the vertical menu.
+- __tertiary-column__: This is an override setting of the general parameter in `site.data.setup.tertiary-column`. Set to either _none_ or _present_ to affect placing of the tertiary column for this page/post only.
+- __secondary-column-content__: By default the content for the secondary column is taken from _\_includes/secondary-column.html_. Assigning it a different file here will override this default for this page/post only. However if the vertical menu is used (i.e. `site.data.setup.drop-down-menu` is set to _no_), it will remain visible at the top of the content of the secondary column.
+- __tertiary-column-content__: By default the content for the tertiary column is taken from _\_includes/tertiary-column.html_. Assigning it a different file here will override this default for this page/post only.
+- __banner-position__: The position of the banner area. Use _top_ to place the banner across all three columns, _main_ to place the banner only above the primary column and _top-fixed_ to have the banner pinned at the top of the browser window. This setting is fro this page only.
+
+## For Pages
+
+- __date__: When present, the page will only be included in the website if this date is earlier than the build time. 

data/pages/classic/04-posts.md

@@ -0,0 +1,18 @@
+---
+layout: page
+title: Posts in classic
+date: 2017-12-20
+menuInclude: yes
+menuTopTitle: Classic
+menuSubs:
+- title: Posts
+  index: 4
+excerpt: "An excerpt is used as the page description and can be up to 160 characters long..."
+---
+Also see: [Pages and Posts](/pages/classic/pages.html).
+
+The home page shows a number of full posts. The number of posts shown can be set in `site.data.setup.number-of-posts-on-home-page`. By default this is set to _5_.
+
+There is also a widget called _recent-posts_ which can be used to show date & titles of the most recent posts. The number of posts show can be configured in `site.data.setup.number-of-recent-posts-in-widget`.
+
+Then there is a widget called _older-posts_ which can be used to show all previous posts in a summary/detail construction. I.e. with disclosure triangles that drill down from year to month.

data/pages/classic/05-menus.md

@@ -0,0 +1,118 @@
+---
+layout: page
+title: Menus in Classic
+date: 2017-12-15
+tertiary-column: none
+menuInclude: yes
+menuTopTitle: Classic
+menuSubs:
+- title: About Menu Items
+  index: 5
+excerpt: "An excerpt is used as the page description and can be up to 160 characters long..."
+---
+Menu items are created through YAML front matter, except for the `Home` and the `Categories` items.
+
+### Home and Categories
+
+The `Home` item is always present. The `Categories` item can be disabled by setting the parameter `site.data.setup.generate-categories-menu` to _no_.
+
+The Categories menu item is automatically suppressed when the `site.data.setup.drop-down-menu` parameter is set to _no_. This is done because the categories menu itself has no landing page and hence category selection would not be possible. There is categories widget available to make the categories accessable from any other place. By default that widget is included in the secondary-column.
+
+### Frontmatter
+
+There are several front matter parameters that can be used to configure the menu.
+
+To create a top menu item (shown in the menubar below the banner):
+
+- __menuTopTitle__: This is the name of the item that will appear in the menubar when `menuInclude` is set to _yes_.
+- __menuInclude__: Set to _yes_ to include the menu items that are defined in this front matter.
+- __menuTopIndex__: A number that is used to sort the menu items from left to right. Lower numbers appear to the left of higher numbers. But the `Home` item always appears at the very left. When `Categories` are included, they always appear at the very right. Make sure not to use duplicate numbers as that will lead to odd effects.
+- __menuLink__: Set to _no_ to disable the creation of a link from the menu item. This can be useful to create dividers or when a top item itself has no landing page. Note that when the drop down menu is disabled top items without links become unusable.
+
+While the old syntax for creating sub-menu items still works, it is no longer mentioned here. Its use is discouraged.
+
+To create sub menu items and sub-sub menu items use the new frontmatter:
+
+- __menuSubs__: This is the initiation of the new frontmatter used to create sub and sub-sub menu items.
+
+After the initiation use a `-` symbol to start a new sub menu item like this:
+
+    ---
+    ... other stuff
+    menuTopTitle: Classic
+    menuSubs:
+    - title: sub-item-1
+      index: 1
+      link: yes
+      url: http://example.com/anypage.html
+      anchorId: id-of-anchored-html-item
+	- title: "----"
+	  index: 2
+	  link: no
+	- title: sub-item-3
+	---
+
+This example is discussed below.
+	
+#### menuTopTitle
+
+The top title links the page to the proper top level menu item. It is mandatory, without it no sub menu item can be created.
+
+Note that when the drop down menu is used there does not need to be a page for the top menu item itself. However without the drop down menu and without a page linked to the top title, the menu item would simply sit in the menubar without any connections. It is therefore recommended to always provide a landing page for the top title. Even if it just tells the user to "select a subject from the menu".
+
+#### title
+
+This is the only mandatory item, it is the text used for the sub menu item.
+
+Unless overriden by other frontmatter it will have:
+
+- a link to the page in which it is defined.
+- the sub-menu item ordering is random, though often alphabetically (Seems to depends on the file system).
+- the url will be the page url of the page in which it is created.
+- no anchor id will be used.
+
+#### index
+
+This determines the ordering of the sub-menu items. Lower numbers will appear above higher numbers. Make sure not to use duplicate numbers as that will lead to odd effects. (i.e. always check the menu!)
+
+#### link
+
+By default _yes_ is assumed. This controls the creation of a link from the sub-menu item. It can be useful to have a separator sub-menu item without a link.
+
+#### url
+
+If another page (or even site) must be linked to a sub-menu item, this tag can be used.
+
+#### anchorId
+
+Use this to anchor the sub-menu item to a specific HTML element.
+
+When using the banner position “top-fixed” (see `_data/_setup.yml`) be sure to set an appropriate value for the $anchor-top-fixed-offset-xxxxx properties in the classic-jekyll-theme.scss file. This will prevent the anchored item from appearing behind the banner area. 
+
+### Sub-sub menu items
+
+Sub-sub-menu items are created in the same way the sub-items are created, but using the `sub` parameter inside `menuSubs`:
+
+    ---
+    ... other stuff
+    menuTopTitle: Classic
+    menuSubs:
+    - title: sub-item-1
+      index: 1
+      link: yes
+      url: http://example.com/anypage.html
+      anchorId: id-of-anchored-html-item
+	- title: cattle
+	  index: 2
+	  link: no
+	  sub:
+	  - title: sub-sub-item-1
+	    anchorId: horses
+	  - title: sub-sub-item-2
+	    anchorId: cows
+	- title: sub-item-3
+	---
+
+This will create two sub-sub menu items under the _cattle_ entry.
+
+For the sub-sub menu entries the same tags as for the sub-menus can be used. (`link`, `index`, `url` and `anchorId`)