http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/old_site_migration/old_site/users/basics/principal-components-analysis.md ---------------------------------------------------------------------- diff --git a/website/old_site_migration/old_site/users/basics/principal-components-analysis.md b/website/old_site_migration/old_site/users/basics/principal-components-analysis.md deleted file mode 100644 index 5a9383f..0000000 --- a/website/old_site_migration/old_site/users/basics/principal-components-analysis.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -layout: default -title: Principal Components Analysis -theme: - name: retro-mahout ---- - -<a name="PrincipalComponentsAnalysis-PrincipalComponentsAnalysis"></a> -# Principal Components Analysis - -PCA is used to reduce high dimensional data set to lower dimensions. PCA -can be used to identify patterns in data, express the data in a lower -dimensional space. That way, similarities and differences can be -highlighted. It is mostly used in face recognition and image compression. -There are several flaws one has to be aware of when working with PCA: - -* Linearity assumption - data is assumed to be linear combinations of some -basis. There exist non-linear methods such as kernel PCA that alleviate -that problem. -* Principal components are assumed to be orthogonal. ICA tries to cope with -this limitation. -* Mean and covariance are assumed to be statistically important. -* Large variances are assumed to have important dynamics. - -<a name="PrincipalComponentsAnalysis-Parallelizationstrategy"></a> -## Parallelization strategy - -<a name="PrincipalComponentsAnalysis-Designofpackages"></a> -## Design of packages
http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/old_site_migration/old_site/users/basics/svd---singular-value-decomposition.md ---------------------------------------------------------------------- diff --git a/website/old_site_migration/old_site/users/basics/svd---singular-value-decomposition.md b/website/old_site_migration/old_site/users/basics/svd---singular-value-decomposition.md deleted file mode 100644 index 4a28934..0000000 --- a/website/old_site_migration/old_site/users/basics/svd---singular-value-decomposition.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -layout: default -title: SVD - Singular Value Decomposition -theme: - name: retro-mahout ---- - -{excerpt}Singular Value Decomposition is a form of product decomposition of -a matrix in which a rectangular matrix A is decomposed into a product U s -V' where U and V are orthonormal and s is a diagonal matrix.{excerpt} The -values of A can be real or complex, but the real case dominates -applications in machine learning. The most prominent properties of the SVD -are: - - * The decomposition of any real matrix has only real values - * The SVD is unique except for column permutations of U, s and V - * If you take only the largest n values of s and set the rest to zero, -you have a least squares approximation of A with rank n. This allows SVD -to be used very effectively in least squares regression and makes partial -SVD useful. - * The SVD can be computed accurately for singular or nearly singular -matrices. For a matrix of rank n, only the first n singular values will be -non-zero. This allows SVD to be used for solution of singular linear -systems. The columns of U and V corresponding to zero singular values -define the null space of A. - * The partial SVD of very large matrices can be computed very quickly -using stochastic decompositions. See http://arxiv.org/abs/0909.4061v1 for -details. Gradient descent can also be used to compute partial SVD's and is -very useful where some values of the matrix being decomposed are not known. - -In collaborative filtering and text retrieval, it is common to compute the -partial decomposition of the user x item interaction matrix or the document -x term matrix. This allows the projection of users and items (or documents -and terms) into a common vector space representation that is often referred -to as the latent semantic representation. This process is sometimes called -Latent Semantic Analysis and has been very effective in the analysis of the -Netflix dataset. - -Dimension Reduction in Mahout: - * https://cwiki.apache.org/MAHOUT/dimensional-reduction.html - - See Also: - * http://www.kwon3d.com/theory/jkinem/svd.html - * http://en.wikipedia.org/wiki/Singular_value_decomposition - * http://en.wikipedia.org/wiki/Latent_semantic_analysis - * http://en.wikipedia.org/wiki/Netflix_Prize - * -http://www.amazon.com/Understanding-Complex-Datasets-Decompositions-Knowledge/dp/1584888326 - * http://web.mit.edu/be.400/www/SVD/Singular_Value_Decomposition.htm - * -http://www.quora.com/What-s-the-best-parallelized-sparse-SVD-code-publicly-available - * [understanding Mahout Hadoop SVD thread](http://mail-archives.apache.org/mod_mbox/mahout-user/201102.mbox/%[email protected]%3E) http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/old_site_migration/old_site/users/basics/system-requirements.md ---------------------------------------------------------------------- diff --git a/website/old_site_migration/old_site/users/basics/system-requirements.md b/website/old_site_migration/old_site/users/basics/system-requirements.md deleted file mode 100644 index 6bef40d..0000000 --- a/website/old_site_migration/old_site/users/basics/system-requirements.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: default -title: System Requirements -theme: - name: retro-mahout ---- - - -# System Requirements - -* Java 1.6.x or greater. -* Maven 3.x to build the source code. - -CPU, Disk and Memory requirements are based on the many choices made in -implementing your application with Mahout (document size, number of -documents, and number of hits retrieved to name a few.) - -Several of the Mahout algorithms are implemented to work on Hadoop -clusters. If not advertised differently, those implementations work with -Hadoop 0.20.0 or greater. http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/old_site_migration/old_site/users/basics/tf-idf---term-frequency-inverse-document-frequency.md ---------------------------------------------------------------------- diff --git a/website/old_site_migration/old_site/users/basics/tf-idf---term-frequency-inverse-document-frequency.md b/website/old_site_migration/old_site/users/basics/tf-idf---term-frequency-inverse-document-frequency.md deleted file mode 100644 index f807609..0000000 --- a/website/old_site_migration/old_site/users/basics/tf-idf---term-frequency-inverse-document-frequency.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -layout: default -title: TF-IDF - Term Frequency-Inverse Document Frequency -theme: - name: retro-mahout ---- - -{excerpt}Is a weight measure often used in information retrieval and text -mining. This weight is a statistical measure used to evaluate how important -a word is to a document in a collection or corpus. The importance increases -proportionally to the number of times a word appears in the document but is -offset by the frequency of the word in the corpus.{excerpt} In other words -if a term/word appears lots in a document but also appears lots in the -corpus/collection as a whole it will get a lower score. An example of this -would be "the", "and", "it" but depending on your source material it maybe -other words that are very common to the source matter. - - - See Also: - * http://en.wikipedia.org/wiki/Tf%E2%80%93idf - * http://nlp.stanford.edu/IR-book/html/htmledition/tf-idf-weighting-1.html http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/Gemfile.lock ---------------------------------------------------------------------- diff --git a/website/oldsite/Gemfile.lock b/website/oldsite/Gemfile.lock deleted file mode 100644 index f3aff06..0000000 --- a/website/oldsite/Gemfile.lock +++ /dev/null @@ -1,56 +0,0 @@ -GEM - remote: https://rubygems.org/ - specs: - addressable (2.5.1) - public_suffix (~> 2.0, >= 2.0.2) - colorator (1.1.0) - ffi (1.9.18) - forwardable-extended (2.6.0) - jekyll (3.4.3) - addressable (~> 2.4) - colorator (~> 1.0) - jekyll-sass-converter (~> 1.0) - jekyll-watch (~> 1.1) - kramdown (~> 1.3) - liquid (~> 3.0) - mercenary (~> 0.3.3) - pathutil (~> 0.9) - rouge (~> 1.7) - safe_yaml (~> 1.0) - jekyll-sass-converter (1.5.0) - sass (~> 3.4) - jekyll-sitemap (1.1.1) - jekyll (~> 3.3) - jekyll-watch (1.5.0) - listen (~> 3.0, < 3.1) - kramdown (1.13.2) - liquid (3.0.6) - listen (3.0.8) - rb-fsevent (~> 0.9, >= 0.9.4) - rb-inotify (~> 0.9, >= 0.9.7) - mercenary (0.3.6) - pathutil (0.14.0) - forwardable-extended (~> 2.6) - posix-spawn (0.3.6) - public_suffix (2.0.5) - pygments.rb (0.5.4) - posix-spawn (~> 0.3.6) - yajl-ruby (~> 1.1.0) - rb-fsevent (0.9.8) - rb-inotify (0.9.8) - ffi (>= 0.5.0) - rouge (1.11.1) - safe_yaml (1.0.4) - sass (3.4.23) - yajl-ruby (1.1.0) - -PLATFORMS - ruby - -DEPENDENCIES - jekyll (~> 3.1) - jekyll-sitemap - pygments.rb - -BUNDLED WITH - 1.14.6 http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/History.markdown ---------------------------------------------------------------------- diff --git a/website/oldsite/History.markdown b/website/oldsite/History.markdown deleted file mode 100644 index 5ef89c1..0000000 --- a/website/oldsite/History.markdown +++ /dev/null @@ -1,16 +0,0 @@ -## HEAD - -### Major Enhancements - -### Minor Enahncements - * Add `drafts` folder support (#167) - * Add `excerpt` support (#168) - * Create History.markdown to help project management (#169) - -### Bug Fixes - -### Site Enhancements - -### Compatibility updates - * Update `preview` task - http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/LICENSE ---------------------------------------------------------------------- diff --git a/website/oldsite/LICENSE b/website/oldsite/LICENSE deleted file mode 100644 index 01a0839..0000000 --- a/website/oldsite/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -The MIT License (MIT) - -Copyright (c) 2015 Jade Dominguez - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/README.md ---------------------------------------------------------------------- diff --git a/website/oldsite/README.md b/website/oldsite/README.md index 62fcfca..b5ef323 100644 --- a/website/oldsite/README.md +++ b/website/oldsite/README.md @@ -1,78 +1,15 @@ -# Jekyll-Bootstrap -The quickest way to start and publish your Jekyll powered blog. 100% compatible with GitHub pages -## Usage +### Original Apache Mahout Site -For all usage and documentation please see: <http://jekyllbootstrap.com> +Currently running with `mahout3` theme. To switch to old theme: + + rake theme:switch name="mahout-retro" + +Also if you want to be fun, you can use the `mahout-retro` theme on the other website parts as well. -## Version -0.3.0 - stable and versioned using [semantic versioning](http://semver.org/). +To build come to this directory and type -**NOTE:** 0.3.0 introduces a new theme which is not backwards compatible in the sense it won't _look_ like the old version. -However, the actual API has not changed at all. -You might want to run 0.3.0 in a branch to make sure you are ok with the theme design changes. + jekyll serve -## Milestones - -[0.4.0](https://github.com/plusjade/jekyll-bootstrap/milestones/v%200.4.0) - next release [ETA 03/29/2015] - -### GOALS - -* No open PRs against master branch. -* Squash some bugs. -* Add some new features (low-hanging fruit). -* Establish social media presence. - - -### Bugs - -|Bug |Description -|------|--------------- -|[#86](https://github.com/plusjade/jekyll-bootstrap/issues/86) |☑ Facebook Comments -|[#113](https://github.com/plusjade/jekyll-bootstrap/issues/113)|☑ ASSET_PATH w/ page & post -|[#144](https://github.com/plusjade/jekyll-bootstrap/issues/144)|☐ BASE_PATH w/ FQDN -|[#227](https://github.com/plusjade/jekyll-bootstrap/issues/227)|☑ Redundant JB/setup - -### Features - -|Bug |Description -|------|--------------- -|[#98](https://github.com/plusjade/jekyll-bootstrap/issues/98) |☑ GIST Integration -|[#244](https://github.com/plusjade/jekyll-bootstrap/issues/244)|☑ JB/file_exists Helper -|[#42](https://github.com/plusjade/jekyll-bootstrap/issues/42) |☑ Sort collections of Pages / Posts -|[#84](https://github.com/plusjade/jekyll-bootstrap/issues/84) |☐ Detecting production mode - -### TODOS - -Review existing pull requests against plusjake/jekyll-bootstrap:master. Merge or close each. - -* Create twitter account. Add link / icon on jekyllbootstrap.com. -* Create blog posts under plusjade/gh-pages, expose on jekyllbootstrap.com, feed to twitter account. -* Announce state of project, announce roadmap(s), announce new versions as theyâre released. - -## Contributing - - -To contribute to the framework please make sure to checkout your branch based on `jb-development`!! -This is very important as it allows me to accept your pull request without having to publish a public version release. - -Small, atomic Features, bugs, etc. -Use the `jb-development` branch but note it will likely change fast as pull requests are accepted. -Please rebase as often as possible when working. -Work on small, atomic features/bugs to avoid upstream commits affecting/breaking your development work. - -For Big Features or major API extensions/edits: -This is the one case where I'll accept pull-requests based off the master branch. -This allows you to work in isolation but it means I'll have to manually merge your work into the next public release. -Translation : it might take a bit longer so please be patient! (but sincerely thank you). - -**Jekyll-Bootstrap Documentation Website.** - -The documentation website at <http://jekyllbootstrap.com> is maintained at https://github.com/plusjade/jekyllbootstrap.com - - -## License - -[MIT](http://opensource.org/licenses/MIT) http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_drafts/jekyll-introduction-draft.md ---------------------------------------------------------------------- diff --git a/website/oldsite/_drafts/jekyll-introduction-draft.md b/website/oldsite/_drafts/jekyll-introduction-draft.md deleted file mode 100644 index 88b93f0..0000000 --- a/website/oldsite/_drafts/jekyll-introduction-draft.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: post -category : lessons -tagline: "Supporting tagline" -tags : [intro, beginner, jekyll, tutorial] ---- -{% include JB/setup %} - - -This is an example of a draft. Read more here: [http://jekyllrb.com/docs/drafts/](http://jekyllrb.com/docs/drafts/) http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_layouts/default.html ---------------------------------------------------------------------- diff --git a/website/oldsite/_layouts/default.html b/website/oldsite/_layouts/default.html index fb9c05d..ec60279 100644 --- a/website/oldsite/_layouts/default.html +++ b/website/oldsite/_layouts/default.html @@ -1,6 +1,6 @@ --- theme : - name : mahout-retro + name : mahout3 --- {% include JB/setup %} -{% include themes/mahout-retro/default.html %} +{% include themes/mahout3/default.html %} http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_layouts/page.html ---------------------------------------------------------------------- diff --git a/website/oldsite/_layouts/page.html b/website/oldsite/_layouts/page.html index fafefd2..0e123f9 100644 --- a/website/oldsite/_layouts/page.html +++ b/website/oldsite/_layouts/page.html @@ -1,7 +1,7 @@ --- theme : - name : mahout-retro + name : mahout3 layout: default --- {% include JB/setup %} -{% include themes/mahout-retro/page.html %} +{% include themes/mahout3/page.html %} http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_layouts/post.html ---------------------------------------------------------------------- diff --git a/website/oldsite/_layouts/post.html b/website/oldsite/_layouts/post.html index 44dc541..9b8f584 100644 --- a/website/oldsite/_layouts/post.html +++ b/website/oldsite/_layouts/post.html @@ -1,7 +1,7 @@ --- theme : - name : mahout-retro + name : mahout3 layout: default --- {% include JB/setup %} -{% include themes/mahout-retro/post.html %} +{% include themes/mahout3/post.html %} http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_posts/core-samples/2011-12-29-jekyll-introduction.md ---------------------------------------------------------------------- diff --git a/website/oldsite/_posts/core-samples/2011-12-29-jekyll-introduction.md b/website/oldsite/_posts/core-samples/2011-12-29-jekyll-introduction.md deleted file mode 100644 index 13fe3dc..0000000 --- a/website/oldsite/_posts/core-samples/2011-12-29-jekyll-introduction.md +++ /dev/null @@ -1,412 +0,0 @@ ---- -layout: post -category : lessons -tagline: "Supporting tagline" -tags : [intro, beginner, jekyll, tutorial] ---- -{% include JB/setup %} - -This Jekyll introduction will outline specifically what Jekyll is and why you would want to use it. -Directly following the intro we'll learn exactly _how_ Jekyll does what it does. - -## Overview - -### What is Jekyll? - -Jekyll is a parsing engine bundled as a ruby gem used to build static websites from -dynamic components such as templates, partials, liquid code, markdown, etc. Jekyll is known as "a simple, blog aware, static site generator". - -### Examples - -This website is created with Jekyll. [Other Jekyll websites](https://github.com/mojombo/jekyll/wiki/Sites). - - - -### What does Jekyll Do? - -Jekyll is a ruby gem you install on your local system. -Once there you can call `jekyll --server` on a directory and provided that directory -is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files, -compute categories, tags, permalinks, and construct your pages from layout templates and partials. - -Once parsed, Jekyll stores the result in a self-contained static `_site` folder. -The intention here is that you can serve all contents in this folder statically from a plain static web-server. - -You can think of Jekyll as a normalish dynamic blog but rather than parsing content, templates, and tags -on each request, Jekyll does this once _beforehand_ and caches the _entire website_ in a folder for serving statically. - -### Jekyll is Not Blogging Software - -**Jekyll is a parsing engine.** - -Jekyll does not come with any content nor does it have any templates or design elements. -This is a common source of confusion when getting started. -Jekyll does not come with anything you actually use or see on your website - you have to make it. - -### Why Should I Care? - -Jekyll is very minimalistic and very efficient. -The most important thing to realize about Jekyll is that it creates a static representation of your website requiring only a static web-server. -Traditional dynamic blogs like Wordpress require a database and server-side code. -Heavily trafficked dynamic blogs must employ a caching layer that ultimately performs the same job Jekyll sets out to do; serve static content. - -Therefore if you like to keep things simple and you prefer the command-line over an admin panel UI then give Jekyll a try. - -**Developers like Jekyll because we can write content like we write code:** - -- Ability to write content in markdown or textile in your favorite text-editor. -- Ability to write and preview your content via localhost. -- No internet connection required. -- Ability to publish via git. -- Ability to host your blog on a static web-server. -- Ability to host freely on GitHub Pages. -- No database required. - -# How Jekyll Works - -The following is a complete but concise outline of exactly how Jekyll works. - -Be aware that core concepts are introduced in rapid succession without code examples. -This information is not intended to specifically teach you how to do anything, rather it -is intended to give you the _full picture_ relative to what is going on in Jekyll-world. - -Learning these core concepts should help you avoid common frustrations and ultimately -help you better understand the code examples contained throughout Jekyll-Bootstrap. - - -## Initial Setup - -After [installing jekyll](/index.html#start-now) you'll need to format your website directory in a way jekyll expects. -Jekyll-bootstrap conveniently provides the base directory format. - -### The Jekyll Application Base Format - -Jekyll expects your website directory to be laid out like so: - - . - |-- _config.yml - |-- _includes - |-- _layouts - | |-- default.html - | |-- post.html - |-- _posts - | |-- 2011-10-25-open-source-is-good.markdown - | |-- 2011-04-26-hello-world.markdown - |-- _site - |-- index.html - |-- assets - |-- css - |-- style.css - |-- javascripts - - -- **\_config.yml** - Stores configuration data. - -- **\_includes** - This folder is for partial views. - -- **\_layouts** - This folder is for the main templates your content will be inserted into. - You can have different layouts for different pages or page sections. - -- **\_posts** - This folder contains your dynamic content/posts. - the naming format is required to be `@YEAR-MONTH-DATE-title.MARKUP@`. - -- **\_site** - This is where the generated site will be placed once Jekyll is done transforming it. - -- **assets** - This folder is not part of the standard jekyll structure. - The assets folder represents _any generic_ folder you happen to create in your root directory. - Directories and files not properly formatted for jekyll will be left untouched for you to serve normally. - -(read more: <https://github.com/mojombo/jekyll/wiki/Usage>) - - -### Jekyll Configuration - -Jekyll supports various configuration options that are fully outlined here: -(<https://github.com/mojombo/jekyll/wiki/Configuration>) - - - - -## Content in Jekyll - -Content in Jekyll is either a post or a page. -These content "objects" get inserted into one or more templates to build the final output for its respective static-page. - -### Posts and Pages - -Both posts and pages should be written in markdown, textile, or HTML and may also contain Liquid templating syntax. -Both posts and pages can have meta-data assigned on a per-page basis such as title, url path, as well as arbitrary custom meta-data. - -### Working With Posts - -**Creating a Post** -Posts are created by properly formatting a file and placing it the `_posts` folder. - -**Formatting** -A post must have a valid filename in the form `YEAR-MONTH-DATE-title.MARKUP` and be placed in the `_posts` directory. -If the data format is invalid Jekyll will not recognize the file as a post. The date and title are automatically parsed from the filename of the post file. -Additionally, each file must have [YAML Front-Matter](https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter) prepended to its content. -YAML Front-Matter is a valid YAML syntax specifying meta-data for the given file. - -**Order** -Ordering is an important part of Jekyll but it is hard to specify a custom ordering strategy. -Only reverse chronological and chronological ordering is supported in Jekyll. - -Since the date is hard-coded into the filename format, to change the order, you must change the dates in the filenames. - -**Tags** -Posts can have tags associated with them as part of their meta-data. -Tags may be placed on posts by providing them in the post's YAML front matter. -You have access to the post-specific tags in the templates. These tags also get added to the sitewide collection. - -**Categories** -Posts may be categorized by providing one or more categories in the YAML front matter. -Categories offer more significance over tags in that they can be reflected in the URL path to the given post. -Note categories in Jekyll work in a specific way. -If you define more than one category you are defining a category hierarchy "set". -Example: - - --- - title : Hello World - categories : [lessons, beginner] - --- - -This defines the category hierarchy "lessons/beginner". Note this is _one category_ node in Jekyll. -You won't find "lessons" and "beginner" as two separate categories unless you define them elsewhere as singular categories. - -### Working With Pages - -**Creating a Page** -Pages are created by properly formatting a file and placing it anywhere in the root directory or subdirectories that do _not_ start with an underscore. - -**Formatting** -In order to register as a Jekyll page the file must contain [YAML Front-Matter](https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter). -Registering a page means 1) that Jekyll will process the page and 2) that the page object will be available in the `site.pages` array for inclusion into your templates. - -**Categories and Tags** -Pages do not compute categories nor tags so defining them will have no effect. - -**Sub-Directories** -If pages are defined in sub-directories, the path to the page will be reflected in the url. -Example: - - . - |-- people - |-- bob - |-- essay.html - -This page will be available at `http://yourdomain.com/people/bob/essay.html` - - -**Recommended Pages** - -- **index.html** - You will always want to define the root index.html page as this will display on your root URL. -- **404.html** - Create a root 404.html page and GitHub Pages will serve it as your 404 response. -- **sitemap.html** - Generating a sitemap is good practice for SEO. -- **about.html** - A nice about page is easy to do and gives the human perspective to your website. - - -## Templates in Jekyll - -Templates are used to contain a page's or post's content. -All templates have access to a global site object variable: `site` as well as a page object variable: `page`. -The site variable holds all accessible content and metadata relative to the site. -The page variable holds accessible data for the given page or post being rendered at that point. - -**Create a Template** -Templates are created by properly formatting a file and placing it in the `_layouts` directory. - -**Formatting** -Templates should be coded in HTML and contain YAML Front Matter. -All templates can contain Liquid code to work with your site's data. - -**Rending Page/Post Content in a Template** -There is a special variable in all templates named : `content`. -The `content` variable holds the page/post content including any sub-template content previously defined. -Render the content variable wherever you want your main content to be injected into your template: - -{% capture text %}... -<body> - <div id="sidebar"> ... </div> - <div id="main"> - |.{content}.| - </div> -</body> -...{% endcapture %} -{% include JB/liquid_raw %} - -### Sub-Templates - -Sub-templates are exactly templates with the only difference being they -define another "root" layout/template within their YAML Front Matter. -This essentially means a template will render inside of another template. - -### Includes -In Jekyll you can define include files by placing them in the `_includes` folder. -Includes are NOT templates, rather they are just code snippets that get included into templates. -In this way, you can treat the code inside includes as if it was native to the parent template. - -Any valid template code may be used in includes. - - -## Using Liquid for Templating - -Templating is perhaps the most confusing and frustrating part of Jekyll. -This is mainly due to the fact that Jekyll templates must use the Liquid Templating Language. - -### What is Liquid? - -[Liquid](https://github.com/Shopify/liquid) is a secure templating language developed by [Shopify](http://shopify.com). -Liquid is designed for end-users to be able to execute logic within template files -without imposing any security risk on the hosting server. - -Jekyll uses Liquid to generate the post content within the final page layout structure and as the primary interface for working with -your site and post/page data. - -### Why Do We Have to Use Liquid? - -GitHub uses Jekyll to power [GitHub Pages](http://pages.github.com/). -GitHub cannot afford to run arbitrary code on their servers so they lock developers down via Liquid. - -### Liquid is Not Programmer-Friendly. - -The short story is liquid is not real code and its not intended to execute real code. -The point being you can't do jackshit in liquid that hasn't been allowed explicitly by the implementation. -What's more you can only access data-structures that have been explicitly passed to the template. - -In Jekyll's case it is not possible to alter what is passed to Liquid without hacking the gem or running custom plugins. -Both of which cannot be supported by GitHub Pages. - -As a programmer - this is very frustrating. - -But rather than look a gift horse in the mouth we are going to -suck it up and view it as an opportunity to work around limitations and adopt client-side solutions when possible. - -**Aside** -My personal stance is to not invest time trying to hack liquid. It's really unnecessary -_from a programmer's_ perspective. That is to say if you have the ability to run custom plugins (i.e. run arbitrary ruby code) -you are better off sticking with ruby. Toward that end I've built [Mustache-with-Jekyll](http://github.com/plusjade/mustache-with-jekyll) - - -## Static Assets - -Static assets are any file in the root or non-underscored subfolders that are not pages. -That is they have no valid YAML Front Matter and are thus not treated as Jekyll Pages. - -Static assets should be used for images, css, and javascript files. - - - - -## How Jekyll Parses Files - -Remember Jekyll is a processing engine. There are two main types of parsing in Jekyll. - -- **Content parsing.** - This is done with textile or markdown. -- **Template parsing.** - This is done with the liquid templating language. - -And thus there are two main types of file formats needed for this parsing. - -- **Post and Page files.** - All content in Jekyll is either a post or a page so valid posts and pages are parsed with markdown or textile. -- **Template files.** - These files go in `_layouts` folder and contain your blogs **templates**. They should be made in HTML with the help of Liquid syntax. - Since include files are simply injected into templates they are essentially parsed as if they were native to the template. - -**Arbitrary files and folders.** -Files that _are not_ valid pages are treated as static content and pass through -Jekyll untouched and reside on your blog in the exact structure and format they originally existed in. - -### Formatting Files for Parsing. - -We've outlined the need for valid formatting using **YAML Front Matter**. -Templates, posts, and pages all need to provide valid YAML Front Matter even if the Matter is empty. -This is the only way Jekyll knows you want the file processed. - -YAML Front Matter must be prepended to the top of template/post/page files: - - --- - layout: post - category : pages - tags : [how-to, jekyll] - --- - - ... contents ... - -Three hyphens on a new line start the Front-Matter block and three hyphens on a new line end the block. -The data inside the block must be valid YAML. - -Configuration parameters for YAML Front-Matter is outlined here: -[A comprehensive explanation of YAML Front Matter](https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter) - -#### Defining Layouts for Posts and Templates Parsing. - -The `layout` parameter in the YAML Front Matter defines the template file for which the given post or template should be injected into. -If a template file specifies its own layout, it is effectively being used as a `sub-template.` -That is to say loading a post file into a template file that refers to another template file with work in the way you'd expect; as a nested sub-template. - - - - - -## How Jekyll Generates the Final Static Files. - -Ultimately, Jekyll's job is to generate a static representation of your website. -The following is an outline of how that's done: - -1. **Jekyll collects data.** - Jekyll scans the posts directory and collects all posts files as post objects. It then scans the layout assets and collects those and finally scans other directories in search of pages. - -2. **Jekyll computes data.** - Jekyll takes these objects, computes metadata (permalinks, tags, categories, titles, dates) from them and constructs one - big `site` object that holds all the posts, pages, layouts, and respective metadata. - At this stage your site is one big computed ruby object. - -3. **Jekyll liquifies posts and templates.** - Next jekyll loops through each post file and converts (through markdown or textile) and **liquifies** the post inside of its respective layout(s). - Once the post is parsed and liquified inside the the proper layout structure, the layout itself is "liquified". - **Liquification** is defined as follows: Jekyll initiates a Liquid template, and passes a simpler hash representation of the ruby site object as well as a simpler - hash representation of the ruby post object. These simplified data structures are what you have access to in the templates. - -3. **Jekyll generates output.** - Finally the liquid templates are "rendered", thereby processing any liquid syntax provided in the templates - and saving the final, static representation of the file. - -**Notes.** -Because Jekyll computes the entire site in one fell swoop, each template is given access to -a global `site` hash that contains useful data. It is this data that you'll iterate through and format -using the Liquid tags and filters in order to render it onto a given page. - -Remember, in Jekyll you are an end-user. Your API has only two components: - -1. The manner in which you setup your directory. -2. The liquid syntax and variables passed into the liquid templates. - -All the data objects available to you in the templates via Liquid are outlined in the **API Section** of Jekyll-Bootstrap. -You can also read the original documentation here: <https://github.com/mojombo/jekyll/wiki/Template-Data> - -## Conclusion - -I hope this paints a clearer picture of what Jekyll is doing and why it works the way it does. -As noted, our main programming constraint is the fact that our API is limited to what is accessible via Liquid and Liquid only. - -Jekyll-bootstrap is intended to provide helper methods and strategies aimed at making it more intuitive and easier to work with Jekyll =) - -**Thank you** for reading this far. - -## Next Steps - -Please take a look at [{{ site.categories.api.first.title }}]({{ BASE_PATH }}{{ site.categories.api.first.url }}) -or jump right into [Usage]({{ BASE_PATH }}{{ site.categories.usage.first.url }}) if you'd like. \ No newline at end of file http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_site/History.markdown ---------------------------------------------------------------------- diff --git a/website/oldsite/_site/History.markdown b/website/oldsite/_site/History.markdown deleted file mode 100644 index 5ef89c1..0000000 --- a/website/oldsite/_site/History.markdown +++ /dev/null @@ -1,16 +0,0 @@ -## HEAD - -### Major Enhancements - -### Minor Enahncements - * Add `drafts` folder support (#167) - * Add `excerpt` support (#168) - * Create History.markdown to help project management (#169) - -### Bug Fixes - -### Site Enhancements - -### Compatibility updates - * Update `preview` task - http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_site/LICENSE ---------------------------------------------------------------------- diff --git a/website/oldsite/_site/LICENSE b/website/oldsite/_site/LICENSE deleted file mode 100644 index 01a0839..0000000 --- a/website/oldsite/_site/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -The MIT License (MIT) - -Copyright (c) 2015 Jade Dominguez - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_site/assets/themes/mahout-retro/css/bootstrap-responsive.css ---------------------------------------------------------------------- diff --git a/website/oldsite/_site/assets/themes/mahout-retro/css/bootstrap-responsive.css b/website/oldsite/_site/assets/themes/mahout-retro/css/bootstrap-responsive.css index a3b0df3..eef0f59 100644 --- a/website/oldsite/_site/assets/themes/mahout-retro/css/bootstrap-responsive.css +++ b/website/oldsite/_site/assets/themes/mahout-retro/css/bootstrap-responsive.css @@ -976,9 +976,6 @@ padding-left: 10px; margin: 0 0 0 -5px; } - /************************/ - - /************************/ .navbar-collapse { clear: both; } http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_site/atom.xml ---------------------------------------------------------------------- diff --git a/website/oldsite/_site/atom.xml b/website/oldsite/_site/atom.xml deleted file mode 100644 index 56afdb9..0000000 --- a/website/oldsite/_site/atom.xml +++ /dev/null @@ -1,443 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<feed xmlns="http://www.w3.org/2005/Atom";> - - <title>Apache Mahout</title> - <link href="http://username.github.io/atom.xml"; rel="self"/> - <link href="http://username.github.io"/> - <updated>2017-04-28T22:05:25-05:00</updated> - <id>http://username.github.io</id> - <author> - <name>The Apache Software Foundation</name> - <email>[email protected]</email> - </author> - - - <entry> - <title>Jekyll Introduction</title> - <link href="http://username.github.io/lessons/2011/12/29/jekyll-introduction"/> - <updated>2011-12-29T00:00:00-06:00</updated> - <id>http://username.github.io/lessons/2011/12/29/jekyll-introduction</id> - <content type="html"> -<p>This Jekyll introduction will outline specifically what Jekyll is and why you would want to use it. -Directly following the intro weâll learn exactly <em>how</em> Jekyll does what it does.</p> - -<h2 id="overview">Overview</h2> - -<h3 id="what-is-jekyll">What is Jekyll?</h3> - -<p>Jekyll is a parsing engine bundled as a ruby gem used to build static websites from -dynamic components such as templates, partials, liquid code, markdown, etc. Jekyll is known as âa simple, blog aware, static site generatorâ.</p> - -<h3 id="examples">Examples</h3> - -<p>This website is created with Jekyll. <a href="https://github.com/mojombo/jekyll/wiki/Sites">Other Jekyll websites</a>.</p> - -<h3 id="what-does-jekyll-do">What does Jekyll Do?</h3> - -<p>Jekyll is a ruby gem you install on your local system. -Once there you can call <code class="highlighter-rouge">jekyll --server</code> on a directory and provided that directory -is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files, -compute categories, tags, permalinks, and construct your pages from layout templates and partials.</p> - -<p>Once parsed, Jekyll stores the result in a self-contained static <code class="highlighter-rouge">_site</code> folder. -The intention here is that you can serve all contents in this folder statically from a plain static web-server.</p> - -<p>You can think of Jekyll as a normalish dynamic blog but rather than parsing content, templates, and tags -on each request, Jekyll does this once <em>beforehand</em> and caches the <em>entire website</em> in a folder for serving statically.</p> - -<h3 id="jekyll-is-not-blogging-software">Jekyll is Not Blogging Software</h3> - -<p><strong>Jekyll is a parsing engine.</strong></p> - -<p>Jekyll does not come with any content nor does it have any templates or design elements. -This is a common source of confusion when getting started. -Jekyll does not come with anything you actually use or see on your website - you have to make it.</p> - -<h3 id="why-should-i-care">Why Should I Care?</h3> - -<p>Jekyll is very minimalistic and very efficient. -The most important thing to realize about Jekyll is that it creates a static representation of your website requiring only a static web-server. -Traditional dynamic blogs like Wordpress require a database and server-side code. -Heavily trafficked dynamic blogs must employ a caching layer that ultimately performs the same job Jekyll sets out to do; serve static content.</p> - -<p>Therefore if you like to keep things simple and you prefer the command-line over an admin panel UI then give Jekyll a try.</p> - -<p><strong>Developers like Jekyll because we can write content like we write code:</strong></p> - -<ul> - <li>Ability to write content in markdown or textile in your favorite text-editor.</li> - <li>Ability to write and preview your content via localhost.</li> - <li>No internet connection required.</li> - <li>Ability to publish via git.</li> - <li>Ability to host your blog on a static web-server.</li> - <li>Ability to host freely on GitHub Pages.</li> - <li>No database required.</li> -</ul> - -<h1 id="how-jekyll-works">How Jekyll Works</h1> - -<p>The following is a complete but concise outline of exactly how Jekyll works.</p> - -<p>Be aware that core concepts are introduced in rapid succession without code examples. -This information is not intended to specifically teach you how to do anything, rather it -is intended to give you the <em>full picture</em> relative to what is going on in Jekyll-world.</p> - -<p>Learning these core concepts should help you avoid common frustrations and ultimately -help you better understand the code examples contained throughout Jekyll-Bootstrap.</p> - -<h2 id="initial-setup">Initial Setup</h2> - -<p>After <a href="/index.html#start-now">installing jekyll</a> youâll need to format your website directory in a way jekyll expects. -Jekyll-bootstrap conveniently provides the base directory format.</p> - -<h3 id="the-jekyll-application-base-format">The Jekyll Application Base Format</h3> - -<p>Jekyll expects your website directory to be laid out like so:</p> - -<div class="highlighter-rouge"><pre class="highlight"><code>. -|-- _config.yml -|-- _includes -|-- _layouts -| |-- default.html -| |-- post.html -|-- _posts -| |-- 2011-10-25-open-source-is-good.markdown -| |-- 2011-04-26-hello-world.markdown -|-- _site -|-- index.html -|-- assets - |-- css - |-- style.css - |-- javascripts -</code></pre> -</div> - -<ul> - <li> - <p><strong>_config.yml</strong> - Stores configuration data.</p> - </li> - <li> - <p><strong>_includes</strong> - This folder is for partial views.</p> - </li> - <li> - <p><strong>_layouts</strong> - This folder is for the main templates your content will be inserted into. - You can have different layouts for different pages or page sections.</p> - </li> - <li> - <p><strong>_posts</strong> - This folder contains your dynamic content/posts. - the naming format is required to be <code class="highlighter-rouge">@YEAR-MONTH-DATE-title.MARKUP@</code>.</p> - </li> - <li> - <p><strong>_site</strong> - This is where the generated site will be placed once Jekyll is done transforming it.</p> - </li> - <li> - <p><strong>assets</strong> - This folder is not part of the standard jekyll structure. - The assets folder represents <em>any generic</em> folder you happen to create in your root directory. - Directories and files not properly formatted for jekyll will be left untouched for you to serve normally.</p> - </li> -</ul> - -<p>(read more: <a href="https://github.com/mojombo/jekyll/wiki/Usage">https://github.com/mojombo/jekyll/wiki/Usage</a>)</p> - -<h3 id="jekyll-configuration">Jekyll Configuration</h3> - -<p>Jekyll supports various configuration options that are fully outlined here: -(<a href="https://github.com/mojombo/jekyll/wiki/Configuration">https://github.com/mojombo/jekyll/wiki/Configuration</a>)</p> - -<h2 id="content-in-jekyll">Content in Jekyll</h2> - -<p>Content in Jekyll is either a post or a page. -These content âobjectsâ get inserted into one or more templates to build the final output for its respective static-page.</p> - -<h3 id="posts-and-pages">Posts and Pages</h3> - -<p>Both posts and pages should be written in markdown, textile, or HTML and may also contain Liquid templating syntax. -Both posts and pages can have meta-data assigned on a per-page basis such as title, url path, as well as arbitrary custom meta-data.</p> - -<h3 id="working-with-posts">Working With Posts</h3> - -<p><strong>Creating a Post</strong> -Posts are created by properly formatting a file and placing it the <code class="highlighter-rouge">_posts</code> folder.</p> - -<p><strong>Formatting</strong> -A post must have a valid filename in the form <code class="highlighter-rouge">YEAR-MONTH-DATE-title.MARKUP</code> and be placed in the <code class="highlighter-rouge">_posts</code> directory. -If the data format is invalid Jekyll will not recognize the file as a post. The date and title are automatically parsed from the filename of the post file. -Additionally, each file must have <a href="https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter">YAML Front-Matter</a> prepended to its content. -YAML Front-Matter is a valid YAML syntax specifying meta-data for the given file.</p> - -<p><strong>Order</strong> -Ordering is an important part of Jekyll but it is hard to specify a custom ordering strategy. -Only reverse chronological and chronological ordering is supported in Jekyll.</p> - -<p>Since the date is hard-coded into the filename format, to change the order, you must change the dates in the filenames.</p> - -<p><strong>Tags</strong> -Posts can have tags associated with them as part of their meta-data. -Tags may be placed on posts by providing them in the postâs YAML front matter. -You have access to the post-specific tags in the templates. These tags also get added to the sitewide collection.</p> - -<p><strong>Categories</strong> -Posts may be categorized by providing one or more categories in the YAML front matter. -Categories offer more significance over tags in that they can be reflected in the URL path to the given post. -Note categories in Jekyll work in a specific way. -If you define more than one category you are defining a category hierarchy âsetâ. -Example:</p> - -<div class="highlighter-rouge"><pre class="highlight"><code>--- -title : Hello World -categories : [lessons, beginner] ---- -</code></pre> -</div> - -<p>This defines the category hierarchy âlessons/beginnerâ. Note this is <em>one category</em> node in Jekyll. -You wonât find âlessonsâ and âbeginnerâ as two separate categories unless you define them elsewhere as singular categories.</p> - -<h3 id="working-with-pages">Working With Pages</h3> - -<p><strong>Creating a Page</strong> -Pages are created by properly formatting a file and placing it anywhere in the root directory or subdirectories that do <em>not</em> start with an underscore.</p> - -<p><strong>Formatting</strong> -In order to register as a Jekyll page the file must contain <a href="https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter">YAML Front-Matter</a>. -Registering a page means 1) that Jekyll will process the page and 2) that the page object will be available in the <code class="highlighter-rouge">site.pages</code> array for inclusion into your templates.</p> - -<p><strong>Categories and Tags</strong> -Pages do not compute categories nor tags so defining them will have no effect.</p> - -<p><strong>Sub-Directories</strong> -If pages are defined in sub-directories, the path to the page will be reflected in the url. -Example:</p> - -<div class="highlighter-rouge"><pre class="highlight"><code>. -|-- people - |-- bob - |-- essay.html -</code></pre> -</div> - -<p>This page will be available at <code class="highlighter-rouge">http://yourdomain.com/people/bob/essay.html</code></p> - -<p><strong>Recommended Pages</strong></p> - -<ul> - <li><strong>index.html</strong> -You will always want to define the root index.html page as this will display on your root URL.</li> - <li><strong>404.html</strong> -Create a root 404.html page and GitHub Pages will serve it as your 404 response.</li> - <li><strong>sitemap.html</strong> -Generating a sitemap is good practice for SEO.</li> - <li><strong>about.html</strong> -A nice about page is easy to do and gives the human perspective to your website.</li> -</ul> - -<h2 id="templates-in-jekyll">Templates in Jekyll</h2> - -<p>Templates are used to contain a pageâs or postâs content. -All templates have access to a global site object variable: <code class="highlighter-rouge">site</code> as well as a page object variable: <code class="highlighter-rouge">page</code>. -The site variable holds all accessible content and metadata relative to the site. -The page variable holds accessible data for the given page or post being rendered at that point.</p> - -<p><strong>Create a Template</strong> -Templates are created by properly formatting a file and placing it in the <code class="highlighter-rouge">_layouts</code> directory.</p> - -<p><strong>Formatting</strong> -Templates should be coded in HTML and contain YAML Front Matter. -All templates can contain Liquid code to work with your siteâs data.</p> - -<p><strong>Rending Page/Post Content in a Template</strong> -There is a special variable in all templates named : <code class="highlighter-rouge">content</code>. -The <code class="highlighter-rouge">content</code> variable holds the page/post content including any sub-template content previously defined. -Render the content variable wherever you want your main content to be injected into your template:</p> - -<pre><code>... -&lt;body&gt; - &lt;div id="sidebar"&gt; ... &lt;/div&gt; - &lt;div id="main"&gt; - &#123;{content}&#125; - &lt;/div&gt; -&lt;/body&gt; -...</code></pre> - -<h3 id="sub-templates">Sub-Templates</h3> - -<p>Sub-templates are exactly templates with the only difference being they -define another ârootâ layout/template within their YAML Front Matter. -This essentially means a template will render inside of another template.</p> - -<h3 id="includes">Includes</h3> -<p>In Jekyll you can define include files by placing them in the <code class="highlighter-rouge">_includes</code> folder. -Includes are NOT templates, rather they are just code snippets that get included into templates. -In this way, you can treat the code inside includes as if it was native to the parent template.</p> - -<p>Any valid template code may be used in includes.</p> - -<h2 id="using-liquid-for-templating">Using Liquid for Templating</h2> - -<p>Templating is perhaps the most confusing and frustrating part of Jekyll. -This is mainly due to the fact that Jekyll templates must use the Liquid Templating Language.</p> - -<h3 id="what-is-liquid">What is Liquid?</h3> - -<p><a href="https://github.com/Shopify/liquid">Liquid</a> is a secure templating language developed by <a href="http://shopify.com">Shopify</a>. -Liquid is designed for end-users to be able to execute logic within template files -without imposing any security risk on the hosting server.</p> - -<p>Jekyll uses Liquid to generate the post content within the final page layout structure and as the primary interface for working with -your site and post/page data.</p> - -<h3 id="why-do-we-have-to-use-liquid">Why Do We Have to Use Liquid?</h3> - -<p>GitHub uses Jekyll to power <a href="http://pages.github.com/">GitHub Pages</a>. -GitHub cannot afford to run arbitrary code on their servers so they lock developers down via Liquid.</p> - -<h3 id="liquid-is-not-programmer-friendly">Liquid is Not Programmer-Friendly.</h3> - -<p>The short story is liquid is not real code and its not intended to execute real code. -The point being you canât do jackshit in liquid that hasnât been allowed explicitly by the implementation. -Whatâs more you can only access data-structures that have been explicitly passed to the template.</p> - -<p>In Jekyllâs case it is not possible to alter what is passed to Liquid without hacking the gem or running custom plugins. -Both of which cannot be supported by GitHub Pages.</p> - -<p>As a programmer - this is very frustrating.</p> - -<p>But rather than look a gift horse in the mouth we are going to -suck it up and view it as an opportunity to work around limitations and adopt client-side solutions when possible.</p> - -<p><strong>Aside</strong> -My personal stance is to not invest time trying to hack liquid. Itâs really unnecessary -<em>from a programmerâs</em> perspective. That is to say if you have the ability to run custom plugins (i.e. run arbitrary ruby code) -you are better off sticking with ruby. Toward that end Iâve built <a href="http://github.com/plusjade/mustache-with-jekyll">Mustache-with-Jekyll</a></p> - -<h2 id="static-assets">Static Assets</h2> - -<p>Static assets are any file in the root or non-underscored subfolders that are not pages. -That is they have no valid YAML Front Matter and are thus not treated as Jekyll Pages.</p> - -<p>Static assets should be used for images, css, and javascript files.</p> - -<h2 id="how-jekyll-parses-files">How Jekyll Parses Files</h2> - -<p>Remember Jekyll is a processing engine. There are two main types of parsing in Jekyll.</p> - -<ul> - <li><strong>Content parsing.</strong> - This is done with textile or markdown.</li> - <li><strong>Template parsing.</strong> -This is done with the liquid templating language.</li> -</ul> - -<p>And thus there are two main types of file formats needed for this parsing.</p> - -<ul> - <li><strong>Post and Page files.</strong> -All content in Jekyll is either a post or a page so valid posts and pages are parsed with markdown or textile.</li> - <li><strong>Template files.</strong> - These files go in <code class="highlighter-rouge">_layouts</code> folder and contain your blogs <strong>templates</strong>. They should be made in HTML with the help of Liquid syntax. - Since include files are simply injected into templates they are essentially parsed as if they were native to the template.</li> -</ul> - -<p><strong>Arbitrary files and folders.</strong> -Files that <em>are not</em> valid pages are treated as static content and pass through -Jekyll untouched and reside on your blog in the exact structure and format they originally existed in.</p> - -<h3 id="formatting-files-for-parsing">Formatting Files for Parsing.</h3> - -<p>Weâve outlined the need for valid formatting using <strong>YAML Front Matter</strong>. -Templates, posts, and pages all need to provide valid YAML Front Matter even if the Matter is empty. -This is the only way Jekyll knows you want the file processed.</p> - -<p>YAML Front Matter must be prepended to the top of template/post/page files:</p> - -<div class="highlighter-rouge"><pre class="highlight"><code>--- -layout: post -category : pages -tags : [how-to, jekyll] ---- - -... contents ... -</code></pre> -</div> - -<p>Three hyphens on a new line start the Front-Matter block and three hyphens on a new line end the block. -The data inside the block must be valid YAML.</p> - -<p>Configuration parameters for YAML Front-Matter is outlined here: -<a href="https://github.com/mojombo/jekyll/wiki/YAML-Front-Matter">A comprehensive explanation of YAML Front Matter</a></p> - -<h4 id="defining-layouts-for-posts-and-templates-parsing">Defining Layouts for Posts and Templates Parsing.</h4> - -<p>The <code class="highlighter-rouge">layout</code> parameter in the YAML Front Matter defines the template file for which the given post or template should be injected into. -If a template file specifies its own layout, it is effectively being used as a <code class="highlighter-rouge">sub-template.</code> -That is to say loading a post file into a template file that refers to another template file with work in the way youâd expect; as a nested sub-template.</p> - -<h2 id="how-jekyll-generates-the-final-static-files">How Jekyll Generates the Final Static Files.</h2> - -<p>Ultimately, Jekyllâs job is to generate a static representation of your website. -The following is an outline of how thatâs done:</p> - -<ol> - <li> - <p><strong>Jekyll collects data.</strong> - Jekyll scans the posts directory and collects all posts files as post objects. It then scans the layout assets and collects those and finally scans other directories in search of pages.</p> - </li> - <li> - <p><strong>Jekyll computes data.</strong> - Jekyll takes these objects, computes metadata (permalinks, tags, categories, titles, dates) from them and constructs one - big <code class="highlighter-rouge">site</code> object that holds all the posts, pages, layouts, and respective metadata. - At this stage your site is one big computed ruby object.</p> - </li> - <li> - <p><strong>Jekyll liquifies posts and templates.</strong> - Next jekyll loops through each post file and converts (through markdown or textile) and <strong>liquifies</strong> the post inside of its respective layout(s). - Once the post is parsed and liquified inside the the proper layout structure, the layout itself is âliquifiedâ. - <strong>Liquification</strong> is defined as follows: Jekyll initiates a Liquid template, and passes a simpler hash representation of the ruby site object as well as a simpler - hash representation of the ruby post object. These simplified data structures are what you have access to in the templates.</p> - </li> - <li> - <p><strong>Jekyll generates output.</strong> - Finally the liquid templates are ârenderedâ, thereby processing any liquid syntax provided in the templates - and saving the final, static representation of the file.</p> - </li> -</ol> - -<p><strong>Notes.</strong> -Because Jekyll computes the entire site in one fell swoop, each template is given access to -a global <code class="highlighter-rouge">site</code> hash that contains useful data. It is this data that youâll iterate through and format -using the Liquid tags and filters in order to render it onto a given page.</p> - -<p>Remember, in Jekyll you are an end-user. Your API has only two components:</p> - -<ol> - <li>The manner in which you setup your directory.</li> - <li>The liquid syntax and variables passed into the liquid templates.</li> -</ol> - -<p>All the data objects available to you in the templates via Liquid are outlined in the <strong>API Section</strong> of Jekyll-Bootstrap. -You can also read the original documentation here: <a href="https://github.com/mojombo/jekyll/wiki/Template-Data">https://github.com/mojombo/jekyll/wiki/Template-Data</a></p> - -<h2 id="conclusion">Conclusion</h2> - -<p>I hope this paints a clearer picture of what Jekyll is doing and why it works the way it does. -As noted, our main programming constraint is the fact that our API is limited to what is accessible via Liquid and Liquid only.</p> - -<p>Jekyll-bootstrap is intended to provide helper methods and strategies aimed at making it more intuitive and easier to work with Jekyll =)</p> - -<p><strong>Thank you</strong> for reading this far.</p> - -<h2 id="next-steps">Next Steps</h2> - -<p>Please take a look at <a href=""></a> -or jump right into <a href="">Usage</a> if youâd like.</p> -</content> - </entry> - - -</feed> http://git-wip-us.apache.org/repos/asf/mahout/blob/3c53a6dc/website/oldsite/_site/developers/buildingmahout.html ---------------------------------------------------------------------- diff --git a/website/oldsite/_site/developers/buildingmahout.html b/website/oldsite/_site/developers/buildingmahout.html index 16cd050..d58f42b 100644 --- a/website/oldsite/_site/developers/buildingmahout.html +++ b/website/oldsite/_site/developers/buildingmahout.html @@ -1,54 +1,46 @@ <!DOCTYPE html> -<!-- - - Licensed to the Apache Software Foundation (ASF) under one or more - contributor license agreements. See the NOTICE file distributed with - this work for additional information regarding copyright ownership. - The ASF licenses this file to You under the Apache License, Version 2.0 - (the "License"); you may not use this file except in compliance with - the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> - -<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> - <title>Apache Mahout: Scalable machine learning and data mining</title> - <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> - <meta name="Distribution" content="Global"> - <meta name="Robots" content="index,follow"> - <meta name="keywords" content="apache, apache hadoop, apache lucene, - business data mining, cluster analysis, - collaborative filtering, data extraction, data filtering, data framework, data integration, - data matching, data mining, data mining algorithms, data mining analysis, data mining data, - data mining introduction, data mining software, - data mining techniques, data representation, data set, datamining, - feature extraction, fuzzy k means, genetic algorithm, hadoop, - hierarchical clustering, high dimensional, introduction to data mining, kmeans, - knowledge discovery, learning approach, learning approaches, learning methods, - learning techniques, lucene, machine learning, machine translation, mahout apache, - mahout taste, map reduce hadoop, mining data, mining methods, naive bayes, - natural language processing, - supervised, text mining, time series data, unsupervised, web data mining"> - <link rel="shortcut icon" type="image/x-icon" href="https://mahout.apache.org/images/favicon.ico";> - <!--<script type="text/javascript" src="/js/prototype.js"></script>--> - <script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/prototype/1.7.2.0/prototype.js";></script> - <script type="text/javascript" src="/assets/themes/mahout-retro/js/effects.js"></script> - <script type="text/javascript" src="/assets/themes/mahout-retro/js/search.js"></script> - <script type="text/javascript" src="/assets/themes/mahout-retro/js/slides.js"></script> - - <link href="/assets/themes/mahout-retro/css/bootstrap.min.css" rel="stylesheet" media="screen"> - <link href="/assets/themes/mahout-retro/css/bootstrap-responsive.css" rel="stylesheet"> - <link rel="stylesheet" href="/assets/themes/mahout-retro/css/global.css" type="text/css"> - - <!-- mathJax stuff -- use `\(...\)` for inline style math in markdown --> +<html lang="en"> +<head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + + <title>BuildingMahout</title> + + <meta name="author" content="The Apache Software Foundation"> + + <!-- Enable responsive viewport --> + <meta name="viewport" content="width=device-width, initial-scale=1.0"> + + <!-- Bootstrap styles --> + <link href="/assets/themes/mahout3/css/bootstrap.min.css" rel="stylesheet"> + <!-- Optional theme --> + <link href="/assets/themes/mahout3/css/bootstrap-theme.min.css" rel="stylesheet"> + <!-- Sticky Footer --> + <link href="/assets/themes/mahout3/css/bs-sticky-footer.css" rel="stylesheet"> + + <!-- Custom styles --> + <link href="/assets/themes/mahout3/css/style.css" rel="stylesheet" type="text/css" media="all"> + + <!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries --> + <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js";></script> + <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js";></script> + <![endif]--> + + <!-- Fav and touch icons --> + <!-- Update these with your own images + <link rel="shortcut icon" href="images/favicon.ico"> + <link rel="apple-touch-icon" href="images/apple-touch-icon.png"> + <link rel="apple-touch-icon" sizes="72x72" href="images/apple-touch-icon-72x72.png"> + <link rel="apple-touch-icon" sizes="114x114" href="images/apple-touch-icon-114x114.png"> + --> + + <!-- atom & rss feed --> + <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Sitewide ATOM Feed"> + <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="Sitewide RSS Feed"> <script type="text/x-mathjax-config"> MathJax.Hub.Config({ tex2jax: { @@ -63,41 +55,35 @@ }); </script> <script type="text/javascript"> - var mathjax = document.createElement('script'); - mathjax.type = 'text/javascript'; + var mathjax = document.createElement('script'); + mathjax.type = 'text/javascript'; mathjax.async = true; mathjax.src = ('https:' == document.location.protocol) ? - 'https://c328740.ssl.cf1.rackcdn.com/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML' : + 'https://c328740.ssl.cf1.rackcdn.com/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML' : 'http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'; - - var s = document.getElementsByTagName('script')[0]; + + var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(mathjax, s); </script> </head> -<body id="home" data-twttr-rendered="true"> - <div id="wrap"> - <div id="header"> - <div id="logo"><a href="/"><img src="/assets/img/mahout-logo-brudman.png" alt="Logos for Mahout and Apache Software Foundation" /></a></div> - <div id="search"> - <form id="search-form" action="http://www.google.com/search"; method="get" class="navbar-search pull-right"> - <input value="http://mahout.apache.org"; name="sitesearch" type="hidden"> - <input class="search-query" name="q" id="query" type="text"> - <input id="submission" type="image" src="/assets/img/mahout-lupe.png" alt="Search" /> - </form> - </div> - - <div class="navbar navbar-inverse" style="position:absolute;top:133px;padding-right:0px;padding-left:0px;"> - <div class="navbar-inner" style="border: none; background: #999; border: none; border-radius: 0px;"> - <div class="container"> - <button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse"> - <span class="icon-bar"></span> - <span class="icon-bar"></span> - <span class="icon-bar"></span> - </button> - <!-- <a class="brand" href="#">Apache Community Development Project</a> --> - <!--<div class="nav-collapse collapse">--> +<nav class="navbar navbar-default navbar-fixed-top"> + <div class="container-fluid"> + <!-- Brand and toggle get grouped for better mobile display --> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1" aria-expanded="false"> + <span class="sr-only">Toggle navigation</span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <a class="navbar-brand" href="/"> + <img src="/assets/img/Mahout-logo-82x100.png" height="30" alt="I'm mahout"> + </a> + </div> + + <!--<div class="nav-collapse collapse">--> <div class="collapse navbar-collapse" id="main-navbar"> <ul class="nav navbar-nav"> <!-- <li><a href="/">Home</a></li> --> @@ -235,43 +221,15 @@ </li> </ul> </div><!--/.nav-collapse --> - </div> - </div> - </div> + </div><!-- /.container-fluid --> +</nav> -</div> - - <div id="sidebar"> - <div id="sidebar-wrap"> - <h2>Twitter</h2> - <ul class="sidemenu"> - <li> -<a class="twitter-timeline" href="https://twitter.com/ApacheMahout"; data-widget-id="422861673444028416">Tweets by @ApacheMahout</a> -<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script> -</li> - </ul> - <h2>Apache Software Foundation</h2> - <ul class="sidemenu"> - <li><a href="http://www.apache.org/foundation/how-it-works.html";>How the ASF works</a></li> - <li><a href="http://www.apache.org/foundation/getinvolved.html";>Get Involved</a></li> - <li><a href="http://www.apache.org/dev/";>Developer Resources</a></li> - <li><a href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li> - <li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li> - </ul> - <h2>Related Projects</h2> - <ul class="sidemenu"> - <li><a href="http://lucene.apache.org/";>Apache Lucene</a></li> - <li><a href="http://hadoop.apache.org/";>Apache Hadoop</a></li> - <li><a href="http://bigtop.apache.org/";>Apache Bigtop</a></li> - <li><a href="http://spark.apache.org/";>Apache Spark</a></li> - <li><a href="http://flink.apache.org/";>Apache Flink</a></li> - </ul> - </div> -</div> +<body> - <div id="content-wrap" class="clearfix"> - <div id="main"> +<div id="wrap"> + <body class=""> + <div class="container"> <h1 id="building-mahout-from-source">Building Mahout from source</h1> <h2 id="prerequisites">Prerequisites</h2> @@ -334,34 +292,30 @@ mvn -Phadoop1 -Dhadoop.version=1.2.1 clean install </div> - </div> - </div> -</div> - <footer class="footer" align="center"> - <div class="container"> - <p> - Copyright © 2014-2016 The Apache Software Foundation, Licensed under - the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version 2.0</a>. - <br /> - Apache Mahout, Mahout, Apache, the Apache feather logo, and the elephant rider logo are either registered trademarks or trademarks of <a href="http://www.apache.org/foundation/marks/";>The Apache Software Foundation</a> in the United States and other countries. - </p> - </div> - </footer> - - <script src="/assets/themes/mahout-retro/js/jquery-1.9.1.min.js"></script> - <script src="/assets/themes/mahout-retro/js/bootstrap.min.js"></script> - <script> - (function() { - var cx = '012254517474945470291:vhsfv7eokdc'; - var gcse = document.createElement('script'); - gcse.type = 'text/javascript'; - gcse.async = true; - gcse.src = (document.location.protocol == 'https:' ? 'https:' : 'http:') + - '//www.google.com/cse/cse.js?cx=' + cx; - var s = document.getElementsByTagName('script')[0]; - s.parentNode.insertBefore(gcse, s); - })(); - </script> + </div> + + +</div> + +<div id="footer"> + <div class="container"> + <p>© 2017 The Apache Software Foundation + with help from <a href="http://jekyllbootstrap.com"; target="_blank" title="The Definitive Jekyll Blogging Framework">Jekyll Bootstrap</a> + and <a href="http://getbootstrap.com"; target="_blank">Bootstrap</a> + </p> + </div> +</div> + + + + + + + +<!-- Latest compiled and minified JavaScript, requires jQuery 1.x (2.x not supported in IE8) --> +<!-- Placed at the end of the document so the pages load faster --> +<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js";></script> +<script src="/assets/themes/mahout3/js/bootstrap.min.js"></script> </body> </html>
