Intial Commit
This commit is contained in:
Sai Kiran Sripada
9
_posts/2014-06-08-mixyll-has-pagination.md
Normal file
9
_posts/2014-06-08-mixyll-has-pagination.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
layout: post
|
||||
title: Mixyll has Pagination
|
||||
date: 2014-06-08 11:21:29
|
||||
summary: This is an empty post to illustrate the pagination component with Mixyll.
|
||||
categories: jekyll mixyll
|
||||
---
|
||||
|
||||
This is an empty post to illustrate the pagination component with Mixyll.
|
||||
17
_posts/2014-06-09-so-what-is-jekyll.md
Normal file
17
_posts/2014-06-09-so-what-is-jekyll.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
layout: post
|
||||
title: So, What is Jekyll?
|
||||
date: 2014-06-09 12:32:18
|
||||
summary: Transform your plain text into static websites and blogs. Simple, static, and blog-aware.
|
||||
categories: jekyll mixyll
|
||||
---
|
||||
|
||||
Jekyll is a tool for transforming your plain text into static websites and
|
||||
blogs. It is simple, static, and blog-aware. Jekyll uses the
|
||||
[Liquid](http://docs.shopify.com/themes/liquid-basics) templating
|
||||
language and has builtin [Markdown](http://daringfireball.net/projects/markdown/)
|
||||
and [Textile](http://en.wikipedia.org/wiki/Textile_(markup_language)) support.
|
||||
|
||||
It also ties in nicely to [Github Pages](https://pages.github.com/).
|
||||
|
||||
Learn more about Jekyll on their [website](http://jekyllrb.com/).
|
||||
174
_posts/2014-06-10-see-mixyll-in-action.md
Normal file
174
_posts/2014-06-10-see-mixyll-in-action.md
Normal file
@@ -0,0 +1,174 @@
|
||||
---
|
||||
layout: post
|
||||
title: Mixyll in Action
|
||||
date: 2014-06-10 12:31:19
|
||||
summary: See what the different elements looks like. Your markdown has never looked better. I promise.
|
||||
categories: jekyll mixyll
|
||||
---
|
||||
|
||||
There is a significant amount of subtle, yet precisely calibrated, styling to ensure
|
||||
that your content is emphasized while still looking aesthetically pleasing.
|
||||
|
||||
All links are easy to [locate and discern](#), yet don't detract from the [harmony
|
||||
of a paragraph](#). The _same_ goes for italics and __bold__ elements. Even the the strikeout
|
||||
works if <del>for some reason you need to update your post</del>. For consistency's sake,
|
||||
<ins>The same goes for insertions</ins>, of course.
|
||||
|
||||
### Code, with syntax highlighting
|
||||
|
||||
Here's an example of some ruby code with line anchors.
|
||||
|
||||
{% highlight ruby lineanchors %}
|
||||
# The most awesome of classes
|
||||
class Awesome < ActiveRecord::Base
|
||||
include EvenMoreAwesome
|
||||
|
||||
validates_presence_of :something
|
||||
validates :email, email_format: true
|
||||
|
||||
def initialize(email, name = nil)
|
||||
self.email = email
|
||||
self.name = name
|
||||
self.favorite_number = 12
|
||||
puts 'created awesomeness'
|
||||
end
|
||||
|
||||
def email_format
|
||||
email =~ /\S+@\S+\.\S+/
|
||||
end
|
||||
end
|
||||
{% endhighlight %}
|
||||
|
||||
Here's some CSS:
|
||||
|
||||
{% highlight css %}
|
||||
.foobar {
|
||||
/* Named colors rule */
|
||||
color: tomato;
|
||||
}
|
||||
{% endhighlight %}
|
||||
|
||||
Here's some JavaScript:
|
||||
|
||||
{% highlight js %}
|
||||
var isPresent = require('is-present')
|
||||
|
||||
module.exports = function doStuff(things) {
|
||||
if (isPresent(things)) {
|
||||
doOtherStuff(things)
|
||||
}
|
||||
}
|
||||
{% endhighlight %}
|
||||
|
||||
Here's some HTML:
|
||||
|
||||
{% highlight html %}
|
||||
<div class="m0 p0 bg-blue white">
|
||||
<h3 class="h1">Hello, world!</h3>
|
||||
</div>
|
||||
{% endhighlight %}
|
||||
|
||||
# Headings!
|
||||
|
||||
They're responsive, and well-proportioned (in `padding`, `line-height`, `margin`, and `font-size`).
|
||||
They also heavily rely on the awesome utility, [BASSCSS](http://www.basscss.com/).
|
||||
|
||||
##### They draw the perfect amount of attention
|
||||
|
||||
This allows your content to have the proper informational and contextual hierarchy. Yay.
|
||||
|
||||
### There are lists, too
|
||||
|
||||
* Apples
|
||||
* Oranges
|
||||
* Potatoes
|
||||
* Milk
|
||||
|
||||
1. Mow the lawn
|
||||
2. Feed the dog
|
||||
3. Dance
|
||||
|
||||
### Images look great, too
|
||||
|
||||
|
||||
|
||||
__
|
||||
|
||||
|
||||
### There are also pretty colors
|
||||
|
||||
Also the result of [BASSCSS](http://www.basscss.com/), you can <span class="bg-dark-gray white">highlight</span> certain components
|
||||
of a <span class="red">post</span> <span class="mid-gray">with</span> <span class="green">CSS</span> <span class="orange">classes</span>.
|
||||
|
||||
I don't recommend using blue, though. It looks like a <span class="blue">link</span>.
|
||||
|
||||
### Footnotes!
|
||||
|
||||
Markdown footnotes are supported, and they look great! Simply put e.g. `[^1]` where you want the footnote to appear,[^1] and then add
|
||||
the reference at the end of your markdown.
|
||||
|
||||
### Stylish blockquotes included
|
||||
|
||||
You can use the markdown quote syntax, `>` for simple quotes.
|
||||
|
||||
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse quis porta mauris.
|
||||
|
||||
However, you need to inject html if you'd like a citation footer. I will be working on a way to
|
||||
hopefully sidestep this inconvenience.
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
|
||||
</p>
|
||||
<footer><cite title="Antoine de Saint-Exupéry">Antoine de Saint-Exupéry</cite></footer>
|
||||
</blockquote>
|
||||
|
||||
|
||||
### Tables
|
||||
|
||||
Tables represent tabular data and can be built using markdown syntax. They are rendered responsively in Mixyll for a variety of screen widths.
|
||||
|
||||
Here's a simple example of a table:
|
||||
|
||||
| Quantity | Description | Price |
|
||||
|----------+-------------+----------:|
|
||||
| 2 | Orange | $0.99 |
|
||||
| 1 | Pineapple | $2.99 |
|
||||
| 4 | Banana | $0.39 |
|
||||
|==========|=============|===========|
|
||||
| | **Total** | **$6.14** |
|
||||
|
||||
A table must have a body of one or more rows, but can optionally also have a header or footer.
|
||||
|
||||
The cells in a column, including the header row cell, can either be aligned:
|
||||
|
||||
- left,
|
||||
- right or
|
||||
- center.
|
||||
|
||||
Most inline text formatting is available in table cells, block-level formatting are not.
|
||||
|
||||
|----------------+----------------------+------------------------+----------------------------------|
|
||||
| Default header | Left header | Center header | Right header |
|
||||
|----------------|:---------------------|:----------------------:|---------------------------------:|
|
||||
| Default | Left | Center | Right |
|
||||
| *Italic* | **Bold** | ***Bold italic*** | `monospace` |
|
||||
| [link text](#) | ```code``` | ~~Strikeout~~ | <ins>Insertion<ins> |
|
||||
| line<br/>break | "Smart quotes" | <mark>highlight</mark> | <span class="green">green</span> |
|
||||
| Footnote[^2] | <sub>subscript</sub> | <sup>superscript</sup> | <span class="red">red</span> |
|
||||
|================+======================+========================+==================================+
|
||||
| Footer row |
|
||||
|----------------+----------------------+------------------------+----------------------------------|
|
||||
|
||||
### There's more being added all the time
|
||||
|
||||
Checkout the [Github repository](https://github.com/saikiransripada/mixyll) to request,
|
||||
or add, features.
|
||||
|
||||
Happy writing.
|
||||
|
||||
---
|
||||
|
||||
[^1]: Important information that may distract from the main text can go in footnotes.
|
||||
|
||||
[^2]: Footnotes will work in tables since they're just links.
|
||||
26
_posts/2014-06-11-welcome-to-mixyll.markdown
Normal file
26
_posts/2014-06-11-welcome-to-mixyll.markdown
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
layout: post
|
||||
title: Hello, Mixyll
|
||||
date: 2014-06-11 15:31:19
|
||||
summary: Mixyll is a simple, beautiful theme for Jekyll that emphasizes content rather than aesthetic fluff.
|
||||
categories: jekyll mixyll
|
||||
---
|
||||
|
||||
Hello.
|
||||
|
||||
Mixyll (Minimal version of Pixyll) is a simple, beautiful theme for Jekyll based on the popular Jekyll theme Pixyll by John Otander that emphasizes content rather than aesthetic fluff. It's mobile _first_, fluidly responsive, and delightfully lightweight.
|
||||
|
||||
It's pretty minimal, but leverages large type and drastic contrast to make a statement, on all devices.
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
|
||||
</p>
|
||||
<footer><cite title="Antoine de Saint-Exupéry">Antoine de Saint-Exupéry</cite></footer>
|
||||
</blockquote>
|
||||
|
||||
## Where is it?
|
||||
|
||||
Checkout the [Github repository](https://github.com/saikiransripada/mixyll) to download it, request a feature, or report a bug.
|
||||
|
||||
It's free, and open source ([MIT](http://opensource.org/licenses/MIT)).
|
||||
66
_posts/2019-01-26-guide-to-forking-pixyll.md
Normal file
66
_posts/2019-01-26-guide-to-forking-pixyll.md
Normal file
@@ -0,0 +1,66 @@
|
||||
---
|
||||
layout: post
|
||||
title: Guide to Forking Mixyll
|
||||
date: 2019-01-26 19:22
|
||||
summary: Mixyll is available to you under the MIT license.
|
||||
categories: jekyll mixyll
|
||||
---
|
||||
|
||||
The following is an overview to copying and sharing Mixyll.[^1]
|
||||
|
||||
Most people have an understanding of what the copyright and licensing obligations are for source code, but not everyone has practical experience. There is a lot of information about how to use free and open source source code generally, but not necessarily how it works specifically.
|
||||
|
||||
## Basics
|
||||
|
||||
Mixyll is free and open source software under the MIT license, a _permissive license_. You can use Mixyll without charge and it is provided to you, "as is", without warranty of any kind.
|
||||
|
||||
These are some of the rights for Mixyll since it is under the MIT license:[^2]
|
||||
|
||||
1. You can **copy** Mixyll by forking it on GitHub or by any other means of copying.
|
||||
2. You can **use** Mixyll to publish your site without restriction or limitation.
|
||||
3. You can **change** Mixyll as you wish, and you can publish your site with a modified version of Mixyll.
|
||||
4. You can also **distribute** copies of Mixyll to other people.
|
||||
5. You can also **distribute modified** copies of Mixyll.
|
||||
|
||||
Other rights you have of Mixyll under the MIT license:
|
||||
|
||||
- You can **sell** copies of Mixyll, including copies you have modified.
|
||||
- You can **combine** Mixyll with other works that are under the MIT license, or other permissive licenses, a copyleft license or a proprietary license. Mixyll already does this itself by using Jekyll, Ruby and other dependencies.
|
||||
- You can distribute copies of Mixyll to others under either the MIT license or you can **relicense** Mixyll under another license. This includes a different permissive license, a copyleft license or a proprietary license.
|
||||
|
||||
Your only responsibility is to preserve both the copyright notices of Mixyll and the MIT license in your copy or modified work.
|
||||
|
||||
## How to
|
||||
|
||||
If you've modified Mixyll significantly and want to share your version, especially public copies of the code, then there are a few items you should do.
|
||||
|
||||
1. You should probably **rename** your fork of Mixyll with a different name.
|
||||
2. A new name isn't required by the MIT license, but it is good etiquette.[^3]
|
||||
3. You should add your name to the **copyright** of your version, and you should preserve the existing copyrights of Mixyll.
|
||||
4. Maintaining the copyright notices isn't required of the MIT license, but it is suggested by the license and is a good practice for documenting the copyrights of your derived work.
|
||||
|
||||
The items above do not apply when you just copied and modified Mixyll in small ways to just publish your site and you have no plans to fork Mixyll under a different name.
|
||||
|
||||
If you want to publish a fork of Mixyll under a different name but keeping it under the MIT license, then you should add your name to the copyright notices:
|
||||
|
||||
Copyright (c) 2019 Your Name
|
||||
Copyright (c) 2014-2019 John Otander for Mixyll
|
||||
|
||||
However, if you want to publish a fork of Mixyll under a different name *and* a different license, then you should should still add your name to the copyright notices but have a section titled "Mixyll" at the bottom of your LICENSE file that preserves the copyright and license notices for Mixyll:
|
||||
|
||||
Mixyll
|
||||
|
||||
Copyright (c) 2014-2019 John Otander
|
||||
|
||||
MIT License
|
||||
|
||||
Permission is hereby granted, [...]
|
||||
|
||||
If you are just modifying Mixyll in small ways to customize your site, you are not obligated to maintain the copyright notices of Mixyll on your site. However, if you want to credit the Mixyll theme that would be appreciated, see section on "Mixyll Plug" in the README file that came with Mixyll.
|
||||
|
||||
Thanks for using Mixyll, and happy hacking!
|
||||
|
||||
---
|
||||
[^1]: **Disclaimer**: This material is for informational purposes only, and should not be construed as legal advice or opinion. For actual legal advice, you should consult with professional legal services.
|
||||
[^2]: This list of privileges are derived from the four freedoms of "The Free Software Definition" published by the GNU project <https://www.gnu.org/philosophy/free-sw.en.html>.
|
||||
[^3]: Using a different name from "Mixyll" for your derivate work helps avoid misdirected questions from people who are using your version. It's similar to using version numbers to discrimate the revisions of software when troubleshooting issues.
|
||||
Reference in New Issue
Block a user