15 |
16 | {% include footer.html %}
17 |
18 |
19 |
20 |
21 |
--------------------------------------------------------------------------------
/_data/lang/ja.yml:
--------------------------------------------------------------------------------
1 | description: "WordPress のウェブサイトのセキュリティを強化するために行うべきチェックリスト"
2 | commit: "Would you like to improve the checklist? [Access the project on GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Access the project on GitHub'){:target='_blank'}."
3 | apps: "Get our app!"
4 | blog: "Blog"
5 | subscribe: "Subscribe"
6 | byrss: "via RSS"
7 | redirecting: "にリダイレクト"
8 | lang:
9 | en: "English"
10 | br: "Português"
11 | es: "Español"
12 | ja: "日本語"
13 |
--------------------------------------------------------------------------------
/_data/lang/es.yml:
--------------------------------------------------------------------------------
1 | description: "Una lista de acciones para aumentar la seguridad de una instalación WordPress"
2 | commit: "Quieres ayudar a mejorar la lista? [Accede al proyecto en GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Accede al proyecto en GitHub'){:target='_blank'}."
3 | apps: "Instala nuestra app!"
4 | blog: "Blog"
5 | subscribe: "Suscríbete"
6 | byrss: "vía RSS"
7 | redirecting: "volver a"
8 | lang:
9 | en: "English"
10 | br: "Português"
11 | es: "Español"
12 | ja: "日本語"
13 |
--------------------------------------------------------------------------------
/_data/lang/br.yml:
--------------------------------------------------------------------------------
1 | description: "Uma lista de ações para aumentar a segurança da sua instalação WordPress."
2 | commit: "Quer ajudar a melhorar essa lista? [Acesse o projeto no GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Acesse o projeto no GitHub'){:target='_blank'}."
3 | apps: "Instale nosso aplicativo!"
4 | blog: "Blog"
5 | subscribe: "Inscreva-se"
6 | byrss: "via RSS"
7 | redirecting: "Redirecionando para"
8 | lang:
9 | en: "English"
10 | br: "Português"
11 | es: "Español"
12 | ja: "日本語"
13 |
--------------------------------------------------------------------------------
/_data/lang/en.yml:
--------------------------------------------------------------------------------
1 | description: "A checklist of actions that you should take to increase the security of your WordPress website."
2 | commit: "Would you like to improve the checklist? [Access the project on GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Access the project on GitHub'){:target='_blank'}."
3 | apps: "Get our app!"
4 | blog: "Blog"
5 | subscribe: "Subscribe"
6 | byrss: "via RSS"
7 | redirecting: "Redirecting to"
8 | lang:
9 | en: "English"
10 | br: "Português"
11 | es: "Español"
12 | ja: "日本語"
13 |
--------------------------------------------------------------------------------
/js/manifest.json:
--------------------------------------------------------------------------------
1 | {
2 | "name":"Rafael Funchal",
3 | "short_name":"Rafael Funchal",
4 | "description":"Web Developer apaixonado por WordPress",
5 | "icons":[{"src":"https:\/\/www.rafaelfunchal.com.br\/wp-content\/uploads\/2016\/07\/logo-rafaelfunchal.png",
6 | "sizes":"192x192",
7 | "type":"image\/png"},
8 | {"src":"https:\/\/www.rafaelfunchal.com.br\/wp-content\/uploads\/2016\/07\/logo-rafaelfunchal.png",
9 | "sizes":"512x512",
10 | "type":"image\/png"}],
11 | "background_color":"#D5E0EB",
12 | "theme_color":"#D5E0EB",
13 | "display":"standalone",
14 | "orientation":"portrait",
15 | "start_url":".",
16 | "scope":"\/"
17 | }
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Numerous always-ignore extensions
2 | *.diff
3 | *.err
4 | *.orig
5 | *.log
6 | *.rej
7 | *.swo
8 | *.swp
9 | *.vi
10 | *~
11 | *.sass-cache
12 | Gemfile.lock
13 |
14 | # OS or Editor folders
15 | .DS_Store
16 | .cache
17 | .project
18 | .settings
19 | nbproject
20 | Thumbs.db
21 |
22 | # Dreamweaver added files
23 | _notes
24 | dwsync.xml
25 |
26 | # Komodo
27 | *.komodoproject
28 | .komodotools
29 |
30 | # Folders to ignore
31 | .hg
32 | .svn
33 | intermediate
34 | publish
35 | .idea
36 |
37 | # build script local files
38 | build/buildinfo.properties
39 | build/config/buildinfo.properties
40 |
41 | # Jekyll
42 | _site
43 | .sass-cache
44 | _gh_pages
45 |
--------------------------------------------------------------------------------
/_posts/2015-07-13-english-version.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Now we have an English version of the checklist"
4 | date: 2015-07-13 15:30:00
5 | categories: update
6 | language: en
7 | permalink: /:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | Finally I found a few time to translate the checklist to English \o/
11 |
12 | Probably you noticed that there are a few strings in Brazilian Portuguese on header and footer. Right now, only the checklist is translated, but I intend to make the entire website multi language friendly soon.
13 |
14 | If you have some suggestion, please, poke me on [Twitter](http://twitter.com/RafaelFunchal){:target="_blank"} or [open an issue on GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist/issues){:target="_blank"}.
15 |
--------------------------------------------------------------------------------
/_posts/br/2015-07-13-english-version.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Agora nós temos uma versão em Inglês do checklist"
4 | date: 2015-07-13 15:30:00
5 | categories: update
6 | language: br
7 | permalink: /:language/:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | Finalmente encontrei algum tempo livre para traduzir o checklist para inglês \o/
11 |
12 | Provavelmente você percebeu que ainda há alguns elementos em português no cabeçalho e no rodapé. Isso acontece por que, no momento, apenas a lista está traduzida, mas eu pretendo deixar o site totalmente bilingue em breve.
13 |
14 | Caso você tenha alguma sugestão, por favor, fale comigo no [Twitter](http://twitter.com/RafaelFunchal){:target="_blank"} ou [abra um issue no GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist/issues){:target="_blank"}.
15 |
--------------------------------------------------------------------------------
/_posts/2015-07-07-news.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Now it's easier to manage the items"
4 | date: 2015-07-07 01:17:07
5 | categories: update
6 | language: en
7 | permalink: /:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | I created this project earlier this year inspired by a post on the group WordPress Brasil on Facebook ([read more here](http://www.rafaelfunchal.com.br/blog/wordpress-security-checklist/)) and made it quickly without considering its scalability and maintenance.
11 |
12 | As I intend to create an English version and in order to make the content management easier, it would necessary to remove the content from the HTML code.
13 |
14 | In short words:
15 |
16 | > I don't want to rewrite unnecessary code.
17 |
18 | So migrating to Jekyll was the best solution because I'll keep the project on Github :-)
19 |
--------------------------------------------------------------------------------
/_posts/br/2015-07-07-news.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Agora ficou mais fácil gerenciar os itens"
4 | date: 2015-07-07 01:17:07
5 | categories: update
6 | language: br
7 | permalink: /:language/:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | Criei esse repositório no começo do ano após um post no grupo WordPress Brasil no Facebook ([leia mais aqui](http://www.rafaelfunchal.com.br/blog/wordpress-security-checklist/)) e o fiz rapidamente sem levar a manutenção e escalabilidade em questão.
11 |
12 | Agora pretendo criar a **versão em Inglês** e, para isso, tornou-se necessário separar o conteúdo do resto da página para permitir um gerenciamento mais fácil do conteúdo.
13 |
14 | Resumidamente:
15 |
16 | > Não quero reescrever código desnecessariamente.
17 |
18 | Nada mais justo do que usar Jekyll já que tudo continuará sendo hospedado aqui no Github :-)
19 |
20 |
--------------------------------------------------------------------------------
/_posts/2015-08-24-printable-version.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Printable version"
4 | date: 2015-08-24 23:17:00
5 | image: "/img/printable-version.png"
6 | categories: update
7 | language: en
8 | permalink: /:categories/:year/:month/:day/:title/
9 | ---
10 |
11 |
12 | That was the [second issue](https://github.com/rafaelfunchal/wordpress-security-checklist/issues/2){:target="_blank"} I created on this project and, thanks to [Fellyph Cintra](https://github.com/fellyph){:target="_blank"}, now it's closed.
13 |
14 | Thanks to Fellyph the checklist will look better when you print it.
15 |
16 | 
17 |
18 | A lot of people still use paper to manage their developed projects and now it's possible to *print the checklist without losing the links mentioned in each item*.
19 |
20 | Thanks, Fellyph! :-)
21 |
--------------------------------------------------------------------------------
/_sass/_print.scss:
--------------------------------------------------------------------------------
1 | @media print {
2 | .site-nav {
3 | display: none;
4 | }
5 |
6 | .site-header {
7 | background-color: #fff;
8 | border-bottom: 1px solid $text-color;
9 | padding: 1em 0;
10 | color: $text-color;
11 |
12 | .site-title {
13 | color: $text-color;
14 | }
15 |
16 | .site-description:after {
17 | content: "wpsecuritychecklist.org";
18 | display: block;
19 | margin-top: 0.5em;
20 | font-size: 0.75em;
21 | }
22 | }
23 |
24 | .site-footer {
25 | display: none;
26 | }
27 |
28 | a,
29 | a:visited,
30 | a:active {
31 | color: $text-color;
32 | }
33 |
34 | .page-content a:after {
35 | content: " url:" attr(href) " ";
36 | font-size: 0.8em;
37 | font-weight: normal;
38 | }
39 | }
40 |
--------------------------------------------------------------------------------
/_posts/br/2015-08-24-printable-version.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Versão imprimível"
4 | date: 2015-08-24 23:17:00
5 | image: "/img/versao-imprimivel.png"
6 | categories: update
7 | language: br
8 | permalink: /:language/:categories/:year/:month/:day/:title/
9 | ---
10 |
11 |
12 | Essa foi a [segunda issue](https://github.com/rafaelfunchal/wordpress-security-checklist/issues/2){:target="_blank"} que criei no projeto e graças ao [Fellyph Cintra](https://github.com/fellyph){:target="_blank"} agora está fechada.
13 |
14 | Graças ao Fellyph o checklist ficará muito mais bonito caso você precise imprimi-lo.
15 |
16 | 
17 |
18 | Muita gente ainda utiliza papel para gerenciar os projetos desenvolvidos e agora é possível *imprimir o checklist e, mesmo assim, visualizar os links mencionados em cada item*.
19 |
20 | Valeu, Fellyph! :-)
21 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | # Site settings
2 | title: WordPress Security Checklist
3 | email: rafaelfunchal@gmail.com
4 | baseurl: "" # the subpath of your site, e.g. /blog/
5 | url: "https://wpsecuritychecklist.org" # the base hostname & protocol for your site
6 | twitter_username: rafaelfunchal
7 | github_username: rafaelfunchal
8 | image: "/img/screenshot.png"
9 | markdown: kramdown
10 | kramdown:
11 | input: GFM
12 | exclude: [ "README.md" ]
13 | paginate: 10
14 | paginate_file: index.html
15 | encoding: UTF-8
16 | future: false
17 |
18 | # Permalinks
19 | permalink: pretty
20 |
21 | # Gems
22 | gems:
23 | - github-pages
24 | - jekyll-paginate
25 | - jekyll-language-plugin
26 |
27 | # Languages
28 | language_data: data.lang.%%
29 | language_includes_dir: _i18n
30 | languages: [ 'en', 'br', 'es', 'ja' ]
31 |
--------------------------------------------------------------------------------
/_posts/2015-07-23-android-app.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Release of our Android app"
4 | date: 2015-07-23 08:53:00
5 | categories: update
6 | language: en
7 | permalink: /:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | Since I created this project I've received a lot of positive feedbacks on social networks. **Thank you, guys!**
11 |
12 | In order to keep the good vibes, I decided to create a mobile version of the checklist. The website is well rendered on mobile devices, but I believe that an app would make the user experience even better.
13 |
14 | Besides that, I used it as an excuse to learn about [Ionic](http://ionicframework.com/){:target="_blank"}.
15 |
16 | You can see the app screenshots and install it on your Android device on [Google Play](https://play.google.com/store/apps/details?id=com.ionicframework.wordpresssecuritychecklistapp804039){:target="_blank"}.
17 |
18 | Don't forget to give it some stars :-)
19 |
--------------------------------------------------------------------------------
/_posts/br/2015-07-23-android-app.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Lançamento do aplicativo para Android"
4 | date: 2015-07-23 08:53:00
5 | categories: update
6 | language: br
7 | permalink: /:language/:categories/:year/:month/:day/:title/
8 | ---
9 |
10 | Desde que criei esse projeto tenho recebido muitos feedbacks positivos nas redes sociais. **Muito obrigado, galera!**
11 |
12 | Para continuar com essa onda positiva, decidi criar uma versão mobile do checklist. O site já é bem renderizado em dispositivos mobile, porém, acredito que um aplicativo tornará a experiência do usuário ainda melhor.
13 |
14 | Além disso serviu como desculpa para que eu estudasse [Ionic](http://ionicframework.com/){:target="_blank"}.
15 |
16 | Você pode ver os screenshots do aplicativo e instalá-lo em seu Android diretamente do [Google Play](https://play.google.com/store/apps/details?id=com.ionicframework.wordpresssecuritychecklistapp804039){:target="_blank"}.
17 |
18 | Não se esqueça de dar algumas estrelinhas :-)
19 |
--------------------------------------------------------------------------------
/_posts/2015-09-02-trello.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "The checklist is available on Trello"
4 | date: 2015-09-02 10:35:00
5 | image: "/img/trello.png"
6 | categories: update
7 | language: en
8 | permalink: /:categories/:year/:month/:day/:title/
9 | ---
10 |
11 | [Rick Benetti](https://twitter.com/RickBenettiBR){:target="_blank"} created a clone of the checklist for those who prefer to use [Trello](https://trello.com/wordpresssecuritychecklist){:target="_blank"}.
12 |
13 | [](https://trello.com/wordpresssecuritychecklist){:target="_blank"}
14 |
15 | We created an [organization on Trello](https://trello.com/wordpresssecuritychecklist){:target="_blank"} to keep the boards divided by language.
16 |
17 | In order to copy the desired board to your own user, you just need to follow these steps: **Menu > More > Copy Board**
18 |
19 | It's awesome to see this project getting stronger and receiving a lot of collaborations.
20 |
21 | Thanks, Rick!
22 |
--------------------------------------------------------------------------------
/_posts/br/2015-09-02-trello.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "A lista está disponível no Trello"
4 | date: 2015-09-02 10:35:00
5 | image: "/img/trello.png"
6 | categories: update
7 | language: br
8 | permalink: /:language/:categories/:year/:month/:day/:title/
9 | ---
10 |
11 | O [Rick Benetti](https://twitter.com/RickBenettiBR){:target="_blank"} criou um clone do checklist para quem prefere usar o [Trello](https://trello.com/wordpresssecuritychecklist){:target="_blank"}.
12 |
13 | [](https://trello.com/wordpresssecuritychecklist){:target="_blank"}
14 |
15 | Criamos uma [organização no Trello](https://trello.com/wordpresssecuritychecklist){:target="_blank"} para juntar os boards separados por idiomas.
16 |
17 | Para copiar o board desejado para o seu usuário basta seguir esses passos: **Menu > More > Copy Board**
18 |
19 | É muito bacana ver o projeto crescer dessa forma e receber mais e mais contribuições.
20 |
21 | Obrigado, Rick!
22 |
23 |
--------------------------------------------------------------------------------
/root-index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | language: en
4 | subset: root
5 | permalink: /
6 | ---
7 |
8 |
30 |
--------------------------------------------------------------------------------
/css/main.scss:
--------------------------------------------------------------------------------
1 | ---
2 | # Only the main Sass file needs front matter (the dashes are enough)
3 | ---
4 | @charset "utf-8";
5 |
6 |
7 |
8 | // Our variables
9 | $base-font-family: Helvetica, Arial, sans-serif;
10 | $base-font-size: 1em;
11 | $small-font-size: $base-font-size * 0.875;
12 | $base-line-height: 1.5;
13 |
14 | $spacing-unit: 30px;
15 |
16 | $text-color: #333;
17 | $background-color: #fdfdfd;
18 | $brand-color: #008CBA;
19 |
20 | $grey-color: #828282;
21 | $grey-color-light: lighten($grey-color, 40%);
22 | $grey-color-dark: darken($grey-color, 25%);
23 |
24 | // Width of the content area
25 | $content-width: 800px;
26 |
27 | $on-palm: 600px;
28 | $on-laptop: 800px;
29 |
30 |
31 |
32 | // Using media queries with like this:
33 | // @include media-query($on-palm) {
34 | // .wrapper {
35 | // padding-right: $spacing-unit / 2;
36 | // padding-left: $spacing-unit / 2;
37 | // }
38 | // }
39 | @mixin media-query($device) {
40 | @media screen and (max-width: $device) {
41 | @content;
42 | }
43 | }
44 |
45 |
46 | // Import partials from `sass_dir` (defaults to `_sass`)
47 | @import
48 | "base",
49 | "layout",
50 | "syntax-highlighting",
51 | "print"
52 | ;
--------------------------------------------------------------------------------
/_posts/2015-11-14-apple-store.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Available on Apple Store"
4 | date: 2015-11-14 01:10:00
5 | image: "/img/apple-store.png"
6 | categories: update
7 | language: en
8 | permalink: /:categories/:year/:month/:day/:title/
9 | ---
10 |
11 | [Ionic Framework](http://ionicframework.com/){:target="_blank"} is the best framework, IMHO, to create hybrid apps, but nothing is perfect.
12 |
13 | In order to create the app version for iOS it's necessary to use an Apple OS and, nowadays in Brazil, a Macbook costs around US $ 6,500.
14 |
15 | [](https://itunes.apple.com/us/app/security-checklist-for-wordpress/id1035454332?ls=1&mt=8){:target="_blank"}
16 |
17 | I said that nothing is perfect, but the WordPress community *is pretty close to perfection*.
18 |
19 | [Sergio Costa](https://www.facebook.com/sergio.costa.5815){:target="_blank"} of [República Interativa](http://republicainterativa.com.br/){:target="_blank"}, **one of the best agencies in Salvador**, liked the project and decided to create the iOS version of our app and, more than that, he published it on [Apple Store](https://itunes.apple.com/us/app/security-checklist-for-wordpress/id1035454332?ls=1&mt=8){:target="_blank"}.
20 |
21 | **I love the WordPress community!**
22 |
23 | Thanks a lot for that, Sergio!
24 |
--------------------------------------------------------------------------------
/feed.xml:
--------------------------------------------------------------------------------
1 | ---
2 | layout: null
3 | ---
4 |
5 |
6 |
7 | {{ site.title | xml_escape }}
8 | {{ site.description | xml_escape }}
9 | {{ site.url }}{{ site.baseurl }}/
10 |
11 | {{ site.time | date_to_rfc822 }}
12 | {{ site.time | date_to_rfc822 }}
13 | Jekyll v{{ jekyll.version }}
14 | {% for post in site.posts limit:10 %}
15 |
16 | {{ post.title | xml_escape }}
17 | {{ post.content | xml_escape }}
18 | {{ post.date | date_to_rfc822 }}
19 | {{ post.url | prepend: site.baseurl | prepend: site.url }}
20 | {{ post.url | prepend: site.baseurl | prepend: site.url }}
21 | {% for tag in post.tags %}
22 | {{ tag | xml_escape }}
23 | {% endfor %}
24 | {% for cat in post.categories %}
25 | {{ cat | xml_escape }}
26 | {% endfor %}
27 |
28 | {% endfor %}
29 |
30 |
31 |
--------------------------------------------------------------------------------
/_posts/br/2017-07-31-novo-dominio.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Novo redirecionamento de domínio"
4 | date: 2017-07-31 15:00:00
5 | image: "/img/listadesegurancawp.org.png"
6 | categories: update
7 | language: br
8 | permalink: /:language/:categories/:year/:month/:day/:title/
9 | ---
10 |
11 | Em Maio estive em Porto Alegre para [palestrar](https://2017.portoalegre.wordcamp.org/session/configurando-ssl-com-lets-encrypt-easyengine-e-wp-cli/){:target="_blank"} no [WordCamp](https://2017.portoalegre.wordcamp.org/){:target="_blank"} que ocorreu no dia 6.
12 |
13 | Durante uma das minhas conversas com o [Marco Andrei Kichalowsky](http://arsnova.digital/){:target="_blank"}, organizador da edição 2017 do WordCamp Porto Alegre, ele me perguntou:
14 |
15 | > Por que o WP Security Checklist não tem um domínio em português para facilitar o acesso?
16 |
17 | Embora eu tenha demorado para aplicar essa ideia, gostei muito dela.
18 |
19 | [](http://listadesegurancawp.org){:target="_blank"}
20 |
21 | **Hoje, finalmente, essa ideia saiu da cabeça!**
22 |
23 | *listadesegurancawp.org -> http://wpsecuritychecklist.org/br/items/*
24 |
25 | Agora o domínio *listadesegurancawp.org* redirecionará diretamente para o checklist em português e ficou ainda mais simples para compartilhar a lista com aquela pessoa que pensa que segurança não é coisa séria \o/
26 |
27 | Muito obrigado pela sugestão, Marco :-)
28 |
--------------------------------------------------------------------------------
/_posts/br/2015-11-14-apple-store.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Estamos na Apple Store"
4 | date: 2015-11-14 01:10:00
5 | image: "/img/apple-store.png"
6 | categories: update
7 | language: br
8 | permalink: /:language/:categories/:year/:month/:day/:title/
9 | ---
10 |
11 | O [Ionic Framework](http://ionicframework.com/){:target="_blank"} é o melhor framework, na minha opinião, para criação de aplicativos híbridos, porém, nada no mundo é perfeito.
12 |
13 | Para criar a versão do aplicativo para iOS é necessário que você utilize o sistema operacional da Apple e um Macbook está custando cerca de R$ 23.000 atualmente aqui no Brasil.
14 |
15 | [](https://itunes.apple.com/us/app/security-checklist-for-wordpress/id1035454332?ls=1&mt=8){:target="_blank"}
16 |
17 | Eu disse que nada no mundo é perfeito, mas a comunidade WordPress *chega bem perto da perfeição*.
18 |
19 | O [Sergio Costa](https://www.facebook.com/sergio.costa.5815){:target="_blank"} da [República Interativa](http://republicainterativa.com.br/){:target="_blank"}, **uma das melhores agências de Salvador**, curtiu o projeto e decidiu criar a versão para iOS do app e, não feliz só com isso, ele também publicou na [Apple Store](https://itunes.apple.com/us/app/security-checklist-for-wordpress/id1035454332?ls=1&mt=8){:target="_blank"}.
20 |
21 | **Ah como eu adoro a comunidade WordPress!**
22 |
23 | Muito obrigado por essa, Sergio!
24 |
25 |
--------------------------------------------------------------------------------
/_data/lang.yml:
--------------------------------------------------------------------------------
1 | en:
2 | description: "A checklist of actions that you should take to increase the security of your WordPress website."
3 | commit: "Would you like to improve the checklist? [Access the project on GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Access the project on GitHub'){:target='_blank'}."
4 | switch: "English"
5 | apps: "Get our app!"
6 | blog: "Blog"
7 | subscribe: "Subscribe"
8 | byrss: "via RSS"
9 | redirecting: "Redirecting to"
10 | br:
11 | description: "Uma lista de ações para aumentar a segurança da sua instalação WordPress."
12 | commit: "Quer ajudar a melhorar essa lista? [Acesse o projeto no GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Acesse o projeto no GitHub'){:target='_blank'}."
13 | switch: "Português"
14 | apps: "Instale nosso aplicativo!"
15 | blog: "Blog"
16 | subscribe: "Inscreva-se"
17 | byrss: "via RSS"
18 | redirecting: "Redirecionando para"
19 | ja:
20 | description: "WordPress のウェブサイトのセキュリティを強化するために行うべきチェックリスト"
21 | commit: "Would you like to improve the checklist? [Access the project on GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Access the project on GitHub'){:target='_blank'}."
22 | switch: "日本語"
23 | apps: "Get our app!"
24 | blog: "Blog"
25 | subscribe: "Subscribe"
26 | byrss: "via RSS"
27 | redirecting: "にリダイレクト"
28 | es:
29 | description: "Una lista de acciones para aumentar la seguridad de una instalación WordPress"
30 | commit: "Quieres ayudar a mejorar la lista? [Accede al proyecto en GitHub](https://github.com/rafaelfunchal/wordpress-security-checklist#contribute-to-the-project 'Accede al proyecto en GitHub'){:target='_blank'}."
31 | switch: "Español"
32 | apps: "Instala nuestro app!"
33 | blog: "Blog"
34 | subscribe: "Suscribete"
35 | byrss: "vía RSS"
36 | redirecting: "volver a dirigir a"
37 |
--------------------------------------------------------------------------------
/_includes/header.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
6 | {% t 'description' %}
7 |
8 |
36 |
37 |
--------------------------------------------------------------------------------
/_includes/head.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | {% if page.title %}{{ site.title }} - {{ page.title }}{% else %}{{ site.title }}{% endif %}
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
--------------------------------------------------------------------------------
/_sass/_syntax-highlighting.scss:
--------------------------------------------------------------------------------
1 | /**
2 | * Syntax highlighting styles
3 | */
4 | .highlight {
5 | background: #fff;
6 | @extend %vertical-rhythm;
7 |
8 | .c { color: #998; font-style: italic } // Comment
9 | .err { color: #a61717; background-color: #e3d2d2 } // Error
10 | .k { font-weight: bold } // Keyword
11 | .o { font-weight: bold } // Operator
12 | .cm { color: #998; font-style: italic } // Comment.Multiline
13 | .cp { color: #999; font-weight: bold } // Comment.Preproc
14 | .c1 { color: #998; font-style: italic } // Comment.Single
15 | .cs { color: #999; font-weight: bold; font-style: italic } // Comment.Special
16 | .gd { color: #000; background-color: #fdd } // Generic.Deleted
17 | .gd .x { color: #000; background-color: #faa } // Generic.Deleted.Specific
18 | .ge { font-style: italic } // Generic.Emph
19 | .gr { color: #a00 } // Generic.Error
20 | .gh { color: #999 } // Generic.Heading
21 | .gi { color: #000; background-color: #dfd } // Generic.Inserted
22 | .gi .x { color: #000; background-color: #afa } // Generic.Inserted.Specific
23 | .go { color: #888 } // Generic.Output
24 | .gp { color: #555 } // Generic.Prompt
25 | .gs { font-weight: bold } // Generic.Strong
26 | .gu { color: #aaa } // Generic.Subheading
27 | .gt { color: #a00 } // Generic.Traceback
28 | .kc { font-weight: bold } // Keyword.Constant
29 | .kd { font-weight: bold } // Keyword.Declaration
30 | .kp { font-weight: bold } // Keyword.Pseudo
31 | .kr { font-weight: bold } // Keyword.Reserved
32 | .kt { color: #458; font-weight: bold } // Keyword.Type
33 | .m { color: #099 } // Literal.Number
34 | .s { color: #d14 } // Literal.String
35 | .na { color: #008080 } // Name.Attribute
36 | .nb { color: #0086B3 } // Name.Builtin
37 | .nc { color: #458; font-weight: bold } // Name.Class
38 | .no { color: #008080 } // Name.Constant
39 | .ni { color: #800080 } // Name.Entity
40 | .ne { color: #900; font-weight: bold } // Name.Exception
41 | .nf { color: #900; font-weight: bold } // Name.Function
42 | .nn { color: #555 } // Name.Namespace
43 | .nt { color: #000080 } // Name.Tag
44 | .nv { color: #008080 } // Name.Variable
45 | .ow { font-weight: bold } // Operator.Word
46 | .w { color: #bbb } // Text.Whitespace
47 | .mf { color: #099 } // Literal.Number.Float
48 | .mh { color: #099 } // Literal.Number.Hex
49 | .mi { color: #099 } // Literal.Number.Integer
50 | .mo { color: #099 } // Literal.Number.Oct
51 | .sb { color: #d14 } // Literal.String.Backtick
52 | .sc { color: #d14 } // Literal.String.Char
53 | .sd { color: #d14 } // Literal.String.Doc
54 | .s2 { color: #d14 } // Literal.String.Double
55 | .se { color: #d14 } // Literal.String.Escape
56 | .sh { color: #d14 } // Literal.String.Heredoc
57 | .si { color: #d14 } // Literal.String.Interpol
58 | .sx { color: #d14 } // Literal.String.Other
59 | .sr { color: #009926 } // Literal.String.Regex
60 | .s1 { color: #d14 } // Literal.String.Single
61 | .ss { color: #990073 } // Literal.String.Symbol
62 | .bp { color: #999 } // Name.Builtin.Pseudo
63 | .vc { color: #008080 } // Name.Variable.Class
64 | .vg { color: #008080 } // Name.Variable.Global
65 | .vi { color: #008080 } // Name.Variable.Instance
66 | .il { color: #099 } // Literal.Number.Integer.Long
67 | }
68 |
--------------------------------------------------------------------------------
/_sass/_base.scss:
--------------------------------------------------------------------------------
1 | /**
2 | * Reset some basic elements
3 | */
4 | body, h1, h2, h3, h4, h5, h6,
5 | p, blockquote, pre, hr,
6 | dl, dd, ol, ul, figure {
7 | margin: 0;
8 | padding: 0;
9 | }
10 |
11 |
12 |
13 | /**
14 | * Basic styling
15 | */
16 | body {
17 | font-family: $base-font-family;
18 | font-size: $base-font-size;
19 | line-height: $base-line-height;
20 | font-weight: 300;
21 | color: $text-color;
22 | background-color: $background-color;
23 | -webkit-text-size-adjust: 100%;
24 | }
25 |
26 | ::selection {
27 | background: #fe57a1;
28 | color: #ffffff;
29 | }
30 |
31 |
32 |
33 | /**
34 | * Set `margin-bottom` to maintain vertical rhythm
35 | */
36 | h1, h2, h3, h4, h5, h6,
37 | p, blockquote, pre,
38 | ul, ol, dl, figure,
39 | %vertical-rhythm {
40 | margin-bottom: $spacing-unit / 2;
41 | }
42 |
43 |
44 |
45 | /**
46 | * Images
47 | */
48 | img {
49 | max-width: 100%;
50 | vertical-align: middle;
51 | }
52 |
53 |
54 |
55 | /**
56 | * Figures
57 | */
58 | figure > img {
59 | display: block;
60 | }
61 |
62 | figcaption {
63 | font-size: $small-font-size;
64 | }
65 |
66 |
67 |
68 | /**
69 | * Lists
70 | */
71 | ul, ol {
72 | }
73 |
74 | li {
75 | > ul,
76 | > ol {
77 | margin-bottom: 0;
78 | }
79 | }
80 |
81 |
82 |
83 | /**
84 | * Headings
85 | */
86 | h1, h2, h3, h4, h5, h6 {
87 | font-weight: 300;
88 | }
89 |
90 |
91 |
92 | /**
93 | * Links
94 | */
95 | a {
96 | color: $brand-color;
97 | text-decoration: none;
98 |
99 | &:visited {
100 | color: darken($brand-color, 15%);
101 | }
102 |
103 | &:hover {
104 | color: $text-color;
105 | text-decoration: underline;
106 | }
107 | }
108 |
109 |
110 |
111 | /**
112 | * Blockquotes
113 | */
114 | blockquote {
115 | color: $grey-color;
116 | border-left: 4px solid $grey-color-light;
117 | padding-left: $spacing-unit / 2;
118 | font-size: 18px;
119 | letter-spacing: -1px;
120 | font-style: italic;
121 |
122 | > :last-child {
123 | margin-bottom: 0;
124 | }
125 | }
126 |
127 |
128 |
129 | /**
130 | * Code formatting
131 | */
132 | pre,
133 | code {
134 | font-size: 15px;
135 | border: 1px solid $grey-color-light;
136 | border-radius: 3px;
137 | background-color: #eef;
138 | }
139 |
140 | code {
141 | padding: 1px 5px;
142 | }
143 |
144 | pre {
145 | padding: 8px 12px;
146 | overflow-x: scroll;
147 |
148 | > code {
149 | border: 0;
150 | padding-right: 0;
151 | padding-left: 0;
152 | }
153 | }
154 |
155 |
156 |
157 | /**
158 | * Wrapper
159 | */
160 | .wrapper {
161 | max-width: -webkit-calc(#{$content-width} - (#{$spacing-unit} * 2));
162 | max-width: calc(#{$content-width} - (#{$spacing-unit} * 2));
163 | margin-right: auto;
164 | margin-left: auto;
165 | padding-right: $spacing-unit;
166 | padding-left: $spacing-unit;
167 | @extend %clearfix;
168 |
169 | @include media-query($on-laptop) {
170 | max-width: -webkit-calc(#{$content-width} - (#{$spacing-unit}));
171 | max-width: calc(#{$content-width} - (#{$spacing-unit}));
172 | padding-right: $spacing-unit / 2;
173 | padding-left: $spacing-unit / 2;
174 | }
175 | }
176 |
177 |
178 |
179 | /**
180 | * Clearfix
181 | */
182 | %clearfix {
183 |
184 | &:after {
185 | content: "";
186 | display: table;
187 | clear: both;
188 | }
189 | }
190 |
191 |
192 |
193 | /**
194 | * Icons
195 | */
196 | .icon {
197 |
198 | > svg {
199 | display: inline-block;
200 | width: 16px;
201 | height: 16px;
202 | vertical-align: middle;
203 |
204 | path {
205 | fill: $grey-color-light;
206 | }
207 | }
208 | }
209 |
--------------------------------------------------------------------------------
/_includes/footer.html:
--------------------------------------------------------------------------------
1 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
72 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | [collaborating]: https://help.github.com/categories/63/articles
2 | [youtube-video]: http://www.youtube.com/watch?v=H3olaBo83As
3 | [jekyll]: https://jekyllrb.com/
4 | [bundler]: http://bundler.io/
5 | [gem-download]: https://rubygems.org/pages/download
6 |
7 | # Sobre #
8 |
9 | Uma lista simples para melhorar a segurança da sua instalação WordPress.
10 |
11 | ## Contribua com o projeto ##
12 |
13 | Se você quiser contribuir com esse projeto e adicionar mais itens na lista, por favor, clique no botão **Fork**, crie um **Branch**, melhore o código e envie sua contribuição como um **Pull Request**.
14 |
15 | Você pode ver mais informações sobre como contribuir e enviar Pull Requests em [GitHub Collaborating][collaborating].
16 |
17 | [Como colaborar com projetos opensource no GitHub][youtube-video].
18 |
19 | ### Como instalar ###
20 |
21 | #### Instalando os itens necessários ####
22 |
23 | Caso você não tenha `gem` instalado em seu computador, você pode instalá-lo usando esse [link][gem-download];
24 |
25 | Esse projeto utiliza [Jekyll][jekyll] como gerenciador de conteúdo e [Bundler][bundler] como gerenciador de dependências, então é necessário instalá-los em seu computador executando esse comando no terminal:
26 |
27 | `$ gem install jekyll bundler`
28 |
29 | #### Copiando o projeto para seu computador ####
30 |
31 | Clique no botão `Fork` para copiar o projeto para sua conta do GitHub.
32 |
33 | Após criar uma versão do projeto em seu próprio GitHub, é necessário salvá-la em seu computador. Abra o terminal e utilize esse código (note que você precisa substituir SEU-NOME-DE-USUÁRIO por seu nome de usuário real):
34 |
35 | `$ git clone git@github.com:SEU-NOME-DE-USUÁRIO/wordpress-security-checklist.git`
36 |
37 | #### Rodando o Jekyll ####
38 |
39 | Acesse o projeto onde você o salvou usando o comando:
40 |
41 | `$ cd /caminho/para/o/diretorio`
42 |
43 | Agora vamos instalar as dependências (isso pode demorar alguns minutos):
44 |
45 | `$ bundle install`
46 |
47 | Agora você já pode executar o Jekyll para ver o projeto rodando em seu navegador:
48 |
49 | `$ jekyll serve`
50 |
51 | Ao rodar esse comando, será exibido um link que você precisa copiar e colar em seu navegador.
52 |
53 | Pronto! Agora você só precisa fazer as alterações que quiser, commitar e mandar o Pull Request.
54 |
55 | ------
56 |
57 | # About #
58 |
59 | A simple checklist to improve the security of your WordPress installation.
60 |
61 | ## Contribute to the Project ##
62 |
63 | If you want to contribute with this project and add more items to the list, please, click on the **Fork** button, create a *Branch*, improve the code and send it with a **Pull Request**.
64 |
65 | More details about how to contribute and send Pull Requests in [GitHub Collaborating][collaborating].
66 |
67 | [How to colaborate to opensource projects on GitHub][youtube-video].
68 |
69 | ### How to install ###
70 |
71 | #### Installing all necessary items ####
72 |
73 | If you don't have `gem` installed on your computer, it is possible to install from this [link][gem-download];
74 |
75 | This project uses [Jekyll][jekyll] as a content management system and [Bundler][bundler] as a dependency manager, so it is necessary to install them on your computer by executing this command on terminal:
76 |
77 | `$ gem install jekyll bundler`
78 |
79 | #### Copying the project to your computer ####
80 |
81 | Click on the `Fork` button to copy the project to your own GitHub account.
82 |
83 | After that, it is necessary to save the project on your computer by running this command on terminal (replace YOUR-USERNAME by your real username):
84 |
85 | `$ git clone git@github.com:YOUR-USERNAME/wordpress-security-checklist.git`
86 |
87 | #### Running Jekyll ####
88 |
89 | Access the directory where the project has been saved by using this command on terminal:
90 |
91 | `$ cd /path/to/directory`
92 |
93 | Let's install all dependencies (it can take a while):
94 |
95 | `$ bundle install`
96 |
97 | Now your are all set to execute Jekyll and navigate to your own copy on your browser:
98 |
99 | `$ jekyll serve`
100 |
101 | By running that command, Jekyll will give you a link. Copy and paste it on your browser.
102 |
103 | All done! Now you just need to make the changes you want to, commit them, and send me a Pull Request.
104 |
--------------------------------------------------------------------------------
/items.ja.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: ja-JP
4 | permalink: /ja/items/
5 | language: ja
6 | subset: root
7 | ---
8 |
9 | > WordPress で稼働しているウェブサイトがハッキングされる原因は WordPress にあるわけではなく、そのほとんどが開発中に回避できるいくつかの設定ミスによるものです。
10 | > あなたのウェブサイトのセキュリティを高めるために取るべき行動のチェックリストであること、それがこのプロジェクトの考えです。
11 |
12 | ## ログイン画面
13 |
14 | *
15 | *
16 | *
17 | *
18 | *
19 | *
20 | *
21 | *
22 |
23 | ## 管理画面
24 |
25 | *
26 | *
27 | *
28 | *
29 | *
30 | *
31 | *
32 |
33 | ## テーマ
34 |
35 | *
36 | *
37 | *
38 | *
39 |
40 | ## プラグイン
41 |
42 | *
43 | *
44 | *
45 | *
46 | *
47 |
48 | ## データベース
49 |
50 | *
51 | *
52 | *
53 |
54 | ## ホスティングサービス
55 |
56 | *
57 | *
58 | *
59 | *
60 | *
61 | *
62 | *
63 |
--------------------------------------------------------------------------------
/items.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: en-US
4 | permalink: /items/
5 | language: en
6 | subset: root
7 | ---
8 |
9 | > Most of the time a website running WordPress is hacked the culprit is not WordPress, but of any silly misconfiguration that could be avoided during its development.
10 | > That's the idea of this project: Being a checklist of actions that you should take to increase the security of your website.
11 |
12 | ## wp-config
13 |
14 | *
15 |
16 | ## Login Page
17 |
18 | *
19 | *
20 | *
21 | *
22 | *
23 | *
24 | *
25 | *
26 | *
27 |
28 | ## Administrative Panel
29 |
30 | *
31 | *
32 | *
33 | *
34 | *
35 | *
36 | *
37 |
38 | ## Themes
39 |
40 | *
41 | *
42 | *
43 | *
44 |
45 | ## Plugins
46 |
47 | *
48 | *
49 | *
50 | *
51 | *
52 |
53 | ## Database
54 |
55 | *
56 | *
57 | *
58 |
59 | ## Hosting provider
60 |
61 | *
62 | *
63 | *
64 | *
65 | *
66 | *
67 | *
68 |
--------------------------------------------------------------------------------
/items.es.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: es-ES
4 | permalink: /es/items/
5 | language: es
6 | subset: root
7 | ---
8 |
9 | > En la mayoría de las veces que un sitio con WordPress és invadido la culpa no es de WordPress, pero si de algunos fallos tontos que se podrían haber evitado durante su construcción.
10 | > Esa es la idea de este proyecto: Ser una lista de acciones que se debe tomar para aumentar la seguridad de su sitio.
11 |
12 | ## wp-config
13 | *
14 |
15 | ## Página de ingreso
16 |
17 | *
18 | *
19 | *
20 | *
21 | *
22 | *
23 | *
24 | *
25 |
26 | ## Panel Administrativo
27 |
28 | *
29 | *
30 | *
31 | *
32 | *
33 | *
34 | *
35 |
36 | ## Plantilla
37 |
38 | *
39 | *
40 | *
41 | *
42 |
43 | ## Plugins
44 |
45 | *
46 | *
47 | *
48 | *
49 | *
50 |
51 | ## Base de datos
52 |
53 | *
54 | *
55 | *
56 |
57 | ## Alojamiento (hosting)
58 |
59 | *
60 | *
61 | *
62 | *
63 | *
64 | *
65 | *
66 |
--------------------------------------------------------------------------------
/items.br.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: pt-BR
4 | permalink: /br/items/
5 | language: br
6 | subset: root
7 | ---
8 |
9 | > A maioria das vezes que um site feito com WordPress é invadido a culpa não é do WordPress, mas sim de alguma falha boba que poderia ter sido evitada durante a sua construção.
10 | > Essa é a ideia desse projeto: Ser um checklist de ações que você deve tomar para aumentar a segurança do seu site.
11 |
12 | ## wp-config
13 | *
14 |
15 | ## Página de login
16 |
17 | *
18 | *
19 | *
20 | *
21 | *
22 | *
23 | *
24 | *
25 | *
26 |
27 | ## Painel Administrativo
28 |
29 | *
30 | *
31 | *
32 | *
33 | *
34 | *
35 | *
36 |
37 | ## Tema
38 |
39 | *
40 | *
41 | *
42 | *
43 |
44 | ## Plugins
45 |
46 | *
47 | *
48 | *
49 | *
50 | *
51 |
52 | ## Banco de dados
53 |
54 | *
55 | *
56 | *
57 |
58 | ## Hospedagem
59 |
60 | *
61 | *
62 | *
63 | *
64 | *
65 | *
66 | *
67 |
--------------------------------------------------------------------------------
/_sass/_layout.scss:
--------------------------------------------------------------------------------
1 | /**
2 | * Site header
3 | */
4 | .site-header {
5 | background-color: $brand-color;
6 | color: $grey-color-light;
7 | padding-top: 1em;
8 | text-align: center;
9 |
10 | // Positioning context for the mobile navigation icon
11 | position: relative;
12 | }
13 |
14 | .site-title {
15 | font-size: 3em;
16 | line-height: 100%;
17 | margin: 0;
18 | letter-spacing: -1px;
19 |
20 | a,
21 | a:visited {
22 | color: $grey-color-light;
23 | }
24 |
25 | @include media-query($on-palm) {
26 | font-size: 1.5em;
27 | }
28 |
29 | }
30 |
31 | .site-description {
32 | display: block;
33 | font-size: 1em;
34 | font-weight: 700;
35 | line-height: 100%;
36 | margin: 0 auto;
37 | max-width: 95%;
38 | }
39 |
40 | .site-nav {
41 | background-color: $grey-color-dark;
42 | border: 2px solid lighten($grey-color-dark, 10%);
43 | border-left: none;
44 | border-right: none;
45 | line-height: $base-line-height;
46 | margin-top: 1em;
47 | padding: 0.5em 0;
48 | width: 100%;
49 |
50 | .menu-icon {
51 | display: none;
52 | }
53 |
54 | .page-link {
55 | color: $grey-color-light;
56 | line-height: $base-line-height;
57 |
58 | // Gaps between nav items, but not on the first one
59 | &:not(:first-child) {
60 | margin-left: 20px;
61 | }
62 | }
63 |
64 | .language-switch {
65 | margin-left: 20px;
66 | }
67 | }
68 |
69 |
70 |
71 | /**
72 | * Site footer
73 | */
74 | .site-footer {
75 | background-color: $brand-color;
76 | border-top: 2px solid darken($brand-color, 10%);
77 | color: $grey-color-light;
78 | margin-top: 2em;
79 | padding: $spacing-unit 0;
80 |
81 | a {
82 | color: $grey-color-light;
83 | &:visited {
84 | color: $grey-color-light;
85 | }
86 | }
87 | }
88 |
89 | .footer-heading {
90 | color: $grey-color-light;
91 | font-size: 18px;
92 | margin-bottom: $spacing-unit / 2;
93 | }
94 |
95 | .badges {
96 | li {
97 | list-style-type: none;
98 | margin-bottom: 10px;
99 |
100 | img {
101 | width: 135px;
102 | }
103 | }
104 | }
105 |
106 | .contact-list,
107 | .social-media-list {
108 | list-style: none;
109 | margin-left: 0;
110 | }
111 |
112 | .footer-col-wrapper {
113 | font-size: 15px;
114 | color: $grey-color-light;
115 | margin-left: -$spacing-unit / 2;
116 | @extend %clearfix;
117 | }
118 |
119 | .footer-col {
120 | float: left;
121 | margin-bottom: $spacing-unit / 2;
122 | padding-left: $spacing-unit / 2;
123 | }
124 |
125 | .footer-col-1 {
126 | width: -webkit-calc(30% - (#{$spacing-unit} / 2));
127 | width: calc(30% - (#{$spacing-unit} / 2));
128 | }
129 |
130 | .footer-col-2 {
131 | width: -webkit-calc(40% - (#{$spacing-unit} / 2));
132 | width: calc(40% - (#{$spacing-unit} / 2));
133 | }
134 |
135 | .footer-col-3 {
136 | width: -webkit-calc(30% - (#{$spacing-unit} / 2));
137 | width: calc(30% - (#{$spacing-unit} / 2));
138 | }
139 |
140 | @include media-query($on-laptop) {
141 | .footer-col-1,
142 | .footer-col-2 {
143 | width: -webkit-calc(50% - (#{$spacing-unit} / 2));
144 | width: calc(50% - (#{$spacing-unit} / 2));
145 | }
146 |
147 | .footer-col-3 {
148 | width: -webkit-calc(100% - (#{$spacing-unit} / 2));
149 | width: calc(100% - (#{$spacing-unit} / 2));
150 | }
151 | }
152 |
153 | @include media-query($on-palm) {
154 | .footer-col {
155 | float: none;
156 | width: -webkit-calc(100% - (#{$spacing-unit} / 2));
157 | width: calc(100% - (#{$spacing-unit} / 2));
158 | }
159 | }
160 |
161 |
162 |
163 | /**
164 | * Page content
165 | */
166 | .page-content {
167 | padding: $spacing-unit 0;
168 |
169 | ul {
170 | list-style: none;
171 |
172 | li {
173 | list-style-image: none;
174 | list-style-type: none;
175 |
176 | label {
177 | cursor: pointer;
178 | }
179 |
180 | .checked {
181 | text-decoration: line-through;
182 | color: lighten($text-color, 50%);
183 |
184 | a,
185 | a:visited {
186 | color: lighten($text-color, 50%);
187 | }
188 |
189 | pre,
190 | code {
191 | background-color: lighten($text-color, 75%);
192 | text-decoration: line-through;
193 | }
194 |
195 | input[type=checkbox] {
196 | filter: progid:DXImageTransform.Microsoft.Alpha(Opacity=80);
197 | opacity: 0.8;
198 | }
199 | }
200 |
201 | input[type=checkbox] {
202 | margin-right: 5px;
203 | }
204 | }
205 | }
206 | }
207 |
208 | .page-heading {
209 | font-size: 20px;
210 | }
211 |
212 | .post-list {
213 | margin-left: 0;
214 | list-style: none;
215 |
216 | > li {
217 | margin-bottom: $spacing-unit;
218 | }
219 | }
220 |
221 | .post-meta {
222 | font-size: $small-font-size;
223 | color: $grey-color;
224 | }
225 |
226 | .post-link {
227 | display: block;
228 | font-size: 24px;
229 | }
230 |
231 |
232 |
233 | /**
234 | * Posts
235 | */
236 | .post-header {
237 | margin-bottom: $spacing-unit;
238 | }
239 |
240 | .post-title {
241 | font-size: 42px;
242 | letter-spacing: -1px;
243 | line-height: 1;
244 |
245 | @include media-query($on-laptop) {
246 | font-size: 36px;
247 | }
248 | }
249 |
250 | .post-content {
251 | margin-bottom: $spacing-unit;
252 |
253 | h2 {
254 | font-size: 32px;
255 | margin-bottom: 0;
256 | margin-top: $spacing-unit / 2;
257 |
258 | .items-counter {
259 | margin-left: 10px;
260 |
261 | &.all-checked {
262 | color: #008CBA;
263 | }
264 | }
265 |
266 | @include media-query($on-laptop) {
267 | font-size: 28px;
268 | }
269 | }
270 |
271 | h3 {
272 | font-size: 26px;
273 |
274 | @include media-query($on-laptop) {
275 | font-size: 22px;
276 | }
277 | }
278 |
279 | h4 {
280 | font-size: 20px;
281 |
282 | @include media-query($on-laptop) {
283 | font-size: 18px;
284 | }
285 | }
286 | }
287 |
--------------------------------------------------------------------------------
/Gemfile.lock:
--------------------------------------------------------------------------------
1 | GEM
2 | remote: https://rubygems.org/
3 | specs:
4 | activesupport (6.0.4.6)
5 | concurrent-ruby (~> 1.0, >= 1.0.2)
6 | i18n (>= 0.7, < 2)
7 | minitest (~> 5.1)
8 | tzinfo (~> 1.1)
9 | zeitwerk (~> 2.2, >= 2.2.2)
10 | addressable (2.8.0)
11 | public_suffix (>= 2.0.2, < 5.0)
12 | coffee-script (2.4.1)
13 | coffee-script-source
14 | execjs
15 | coffee-script-source (1.11.1)
16 | colorator (1.1.0)
17 | commonmarker (0.17.13)
18 | ruby-enum (~> 0.5)
19 | concurrent-ruby (1.1.9)
20 | dnsruby (1.61.9)
21 | simpleidn (~> 0.1)
22 | em-websocket (0.5.3)
23 | eventmachine (>= 0.12.9)
24 | http_parser.rb (~> 0)
25 | ethon (0.15.0)
26 | ffi (>= 1.15.0)
27 | eventmachine (1.2.7)
28 | execjs (2.8.1)
29 | faraday (1.9.3)
30 | faraday-em_http (~> 1.0)
31 | faraday-em_synchrony (~> 1.0)
32 | faraday-excon (~> 1.1)
33 | faraday-httpclient (~> 1.0)
34 | faraday-multipart (~> 1.0)
35 | faraday-net_http (~> 1.0)
36 | faraday-net_http_persistent (~> 1.0)
37 | faraday-patron (~> 1.0)
38 | faraday-rack (~> 1.0)
39 | faraday-retry (~> 1.0)
40 | ruby2_keywords (>= 0.0.4)
41 | faraday-em_http (1.0.0)
42 | faraday-em_synchrony (1.0.0)
43 | faraday-excon (1.1.0)
44 | faraday-httpclient (1.0.1)
45 | faraday-multipart (1.0.3)
46 | multipart-post (>= 1.2, < 3)
47 | faraday-net_http (1.0.1)
48 | faraday-net_http_persistent (1.2.0)
49 | faraday-patron (1.0.0)
50 | faraday-rack (1.0.0)
51 | faraday-retry (1.0.3)
52 | ffi (1.15.5)
53 | forwardable-extended (2.6.0)
54 | gemoji (3.0.1)
55 | github-pages (223)
56 | github-pages-health-check (= 1.17.9)
57 | jekyll (= 3.9.0)
58 | jekyll-avatar (= 0.7.0)
59 | jekyll-coffeescript (= 1.1.1)
60 | jekyll-commonmark-ghpages (= 0.1.6)
61 | jekyll-default-layout (= 0.1.4)
62 | jekyll-feed (= 0.15.1)
63 | jekyll-gist (= 1.5.0)
64 | jekyll-github-metadata (= 2.13.0)
65 | jekyll-include-cache (= 0.2.1)
66 | jekyll-mentions (= 1.6.0)
67 | jekyll-optional-front-matter (= 0.3.2)
68 | jekyll-paginate (= 1.1.0)
69 | jekyll-readme-index (= 0.3.0)
70 | jekyll-redirect-from (= 0.16.0)
71 | jekyll-relative-links (= 0.6.1)
72 | jekyll-remote-theme (= 0.4.3)
73 | jekyll-sass-converter (= 1.5.2)
74 | jekyll-seo-tag (= 2.7.1)
75 | jekyll-sitemap (= 1.4.0)
76 | jekyll-swiss (= 1.0.0)
77 | jekyll-theme-architect (= 0.2.0)
78 | jekyll-theme-cayman (= 0.2.0)
79 | jekyll-theme-dinky (= 0.2.0)
80 | jekyll-theme-hacker (= 0.2.0)
81 | jekyll-theme-leap-day (= 0.2.0)
82 | jekyll-theme-merlot (= 0.2.0)
83 | jekyll-theme-midnight (= 0.2.0)
84 | jekyll-theme-minimal (= 0.2.0)
85 | jekyll-theme-modernist (= 0.2.0)
86 | jekyll-theme-primer (= 0.6.0)
87 | jekyll-theme-slate (= 0.2.0)
88 | jekyll-theme-tactile (= 0.2.0)
89 | jekyll-theme-time-machine (= 0.2.0)
90 | jekyll-titles-from-headings (= 0.5.3)
91 | jemoji (= 0.12.0)
92 | kramdown (= 2.3.1)
93 | kramdown-parser-gfm (= 1.1.0)
94 | liquid (= 4.0.3)
95 | mercenary (~> 0.3)
96 | minima (= 2.5.1)
97 | nokogiri (>= 1.12.5, < 2.0)
98 | rouge (= 3.26.0)
99 | terminal-table (~> 1.4)
100 | github-pages-health-check (1.17.9)
101 | addressable (~> 2.3)
102 | dnsruby (~> 1.60)
103 | octokit (~> 4.0)
104 | public_suffix (>= 3.0, < 5.0)
105 | typhoeus (~> 1.3)
106 | html-pipeline (2.14.0)
107 | activesupport (>= 2)
108 | nokogiri (>= 1.4)
109 | http_parser.rb (0.8.0)
110 | i18n (0.9.5)
111 | concurrent-ruby (~> 1.0)
112 | jekyll (3.9.0)
113 | addressable (~> 2.4)
114 | colorator (~> 1.0)
115 | em-websocket (~> 0.5)
116 | i18n (~> 0.7)
117 | jekyll-sass-converter (~> 1.0)
118 | jekyll-watch (~> 2.0)
119 | kramdown (>= 1.17, < 3)
120 | liquid (~> 4.0)
121 | mercenary (~> 0.3.3)
122 | pathutil (~> 0.9)
123 | rouge (>= 1.7, < 4)
124 | safe_yaml (~> 1.0)
125 | jekyll-avatar (0.7.0)
126 | jekyll (>= 3.0, < 5.0)
127 | jekyll-coffeescript (1.1.1)
128 | coffee-script (~> 2.2)
129 | coffee-script-source (~> 1.11.1)
130 | jekyll-commonmark (1.3.1)
131 | commonmarker (~> 0.14)
132 | jekyll (>= 3.7, < 5.0)
133 | jekyll-commonmark-ghpages (0.1.6)
134 | commonmarker (~> 0.17.6)
135 | jekyll-commonmark (~> 1.2)
136 | rouge (>= 2.0, < 4.0)
137 | jekyll-default-layout (0.1.4)
138 | jekyll (~> 3.0)
139 | jekyll-feed (0.15.1)
140 | jekyll (>= 3.7, < 5.0)
141 | jekyll-gist (1.5.0)
142 | octokit (~> 4.2)
143 | jekyll-github-metadata (2.13.0)
144 | jekyll (>= 3.4, < 5.0)
145 | octokit (~> 4.0, != 4.4.0)
146 | jekyll-include-cache (0.2.1)
147 | jekyll (>= 3.7, < 5.0)
148 | jekyll-language-plugin (1.3.5)
149 | jekyll-mentions (1.6.0)
150 | html-pipeline (~> 2.3)
151 | jekyll (>= 3.7, < 5.0)
152 | jekyll-optional-front-matter (0.3.2)
153 | jekyll (>= 3.0, < 5.0)
154 | jekyll-paginate (1.1.0)
155 | jekyll-readme-index (0.3.0)
156 | jekyll (>= 3.0, < 5.0)
157 | jekyll-redirect-from (0.16.0)
158 | jekyll (>= 3.3, < 5.0)
159 | jekyll-relative-links (0.6.1)
160 | jekyll (>= 3.3, < 5.0)
161 | jekyll-remote-theme (0.4.3)
162 | addressable (~> 2.0)
163 | jekyll (>= 3.5, < 5.0)
164 | jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
165 | rubyzip (>= 1.3.0, < 3.0)
166 | jekyll-sass-converter (1.5.2)
167 | sass (~> 3.4)
168 | jekyll-seo-tag (2.7.1)
169 | jekyll (>= 3.8, < 5.0)
170 | jekyll-sitemap (1.4.0)
171 | jekyll (>= 3.7, < 5.0)
172 | jekyll-swiss (1.0.0)
173 | jekyll-theme-architect (0.2.0)
174 | jekyll (> 3.5, < 5.0)
175 | jekyll-seo-tag (~> 2.0)
176 | jekyll-theme-cayman (0.2.0)
177 | jekyll (> 3.5, < 5.0)
178 | jekyll-seo-tag (~> 2.0)
179 | jekyll-theme-dinky (0.2.0)
180 | jekyll (> 3.5, < 5.0)
181 | jekyll-seo-tag (~> 2.0)
182 | jekyll-theme-hacker (0.2.0)
183 | jekyll (> 3.5, < 5.0)
184 | jekyll-seo-tag (~> 2.0)
185 | jekyll-theme-leap-day (0.2.0)
186 | jekyll (> 3.5, < 5.0)
187 | jekyll-seo-tag (~> 2.0)
188 | jekyll-theme-merlot (0.2.0)
189 | jekyll (> 3.5, < 5.0)
190 | jekyll-seo-tag (~> 2.0)
191 | jekyll-theme-midnight (0.2.0)
192 | jekyll (> 3.5, < 5.0)
193 | jekyll-seo-tag (~> 2.0)
194 | jekyll-theme-minimal (0.2.0)
195 | jekyll (> 3.5, < 5.0)
196 | jekyll-seo-tag (~> 2.0)
197 | jekyll-theme-modernist (0.2.0)
198 | jekyll (> 3.5, < 5.0)
199 | jekyll-seo-tag (~> 2.0)
200 | jekyll-theme-primer (0.6.0)
201 | jekyll (> 3.5, < 5.0)
202 | jekyll-github-metadata (~> 2.9)
203 | jekyll-seo-tag (~> 2.0)
204 | jekyll-theme-slate (0.2.0)
205 | jekyll (> 3.5, < 5.0)
206 | jekyll-seo-tag (~> 2.0)
207 | jekyll-theme-tactile (0.2.0)
208 | jekyll (> 3.5, < 5.0)
209 | jekyll-seo-tag (~> 2.0)
210 | jekyll-theme-time-machine (0.2.0)
211 | jekyll (> 3.5, < 5.0)
212 | jekyll-seo-tag (~> 2.0)
213 | jekyll-titles-from-headings (0.5.3)
214 | jekyll (>= 3.3, < 5.0)
215 | jekyll-watch (2.2.1)
216 | listen (~> 3.0)
217 | jemoji (0.12.0)
218 | gemoji (~> 3.0)
219 | html-pipeline (~> 2.2)
220 | jekyll (>= 3.0, < 5.0)
221 | kramdown (2.3.1)
222 | rexml
223 | kramdown-parser-gfm (1.1.0)
224 | kramdown (~> 2.0)
225 | liquid (4.0.3)
226 | listen (3.7.1)
227 | rb-fsevent (~> 0.10, >= 0.10.3)
228 | rb-inotify (~> 0.9, >= 0.9.10)
229 | mercenary (0.3.6)
230 | mini_portile2 (2.7.1)
231 | minima (2.5.1)
232 | jekyll (>= 3.5, < 5.0)
233 | jekyll-feed (~> 0.9)
234 | jekyll-seo-tag (~> 2.1)
235 | minitest (5.15.0)
236 | multipart-post (2.1.1)
237 | nokogiri (1.13.1)
238 | mini_portile2 (~> 2.7.0)
239 | racc (~> 1.4)
240 | octokit (4.22.0)
241 | faraday (>= 0.9)
242 | sawyer (~> 0.8.0, >= 0.5.3)
243 | pathutil (0.16.2)
244 | forwardable-extended (~> 2.6)
245 | public_suffix (4.0.6)
246 | racc (1.6.0)
247 | rb-fsevent (0.11.1)
248 | rb-inotify (0.10.1)
249 | ffi (~> 1.0)
250 | rexml (3.2.5)
251 | rouge (3.26.0)
252 | ruby-enum (0.9.0)
253 | i18n
254 | ruby2_keywords (0.0.5)
255 | rubyzip (2.3.2)
256 | safe_yaml (1.0.5)
257 | sass (3.7.4)
258 | sass-listen (~> 4.0.0)
259 | sass-listen (4.0.0)
260 | rb-fsevent (~> 0.9, >= 0.9.4)
261 | rb-inotify (~> 0.9, >= 0.9.7)
262 | sawyer (0.8.2)
263 | addressable (>= 2.3.5)
264 | faraday (> 0.8, < 2.0)
265 | simpleidn (0.2.1)
266 | unf (~> 0.1.4)
267 | terminal-table (1.8.0)
268 | unicode-display_width (~> 1.1, >= 1.1.1)
269 | thread_safe (0.3.6)
270 | typhoeus (1.4.0)
271 | ethon (>= 0.9.0)
272 | tzinfo (1.2.9)
273 | thread_safe (~> 0.1)
274 | unf (0.1.4)
275 | unf_ext
276 | unf_ext (0.0.8)
277 | unicode-display_width (1.8.0)
278 | webrick (1.7.0)
279 | zeitwerk (2.5.4)
280 |
281 | PLATFORMS
282 | ruby
283 |
284 | DEPENDENCIES
285 | github-pages
286 | jekyll-language-plugin
287 | jekyll-paginate
288 | webrick (~> 1.7)
289 |
290 | BUNDLED WITH
291 | 2.1.2
292 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 2, June 1991
3 |
4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
6 | Everyone is permitted to copy and distribute verbatim copies
7 | of this license document, but changing it is not allowed.
8 |
9 | Preamble
10 |
11 | The licenses for most software are designed to take away your
12 | freedom to share and change it. By contrast, the GNU General Public
13 | License is intended to guarantee your freedom to share and change free
14 | software--to make sure the software is free for all its users. This
15 | General Public License applies to most of the Free Software
16 | Foundation's software and to any other program whose authors commit to
17 | using it. (Some other Free Software Foundation software is covered by
18 | the GNU Lesser General Public License instead.) You can apply it to
19 | your programs, too.
20 |
21 | When we speak of free software, we are referring to freedom, not
22 | price. Our General Public Licenses are designed to make sure that you
23 | have the freedom to distribute copies of free software (and charge for
24 | this service if you wish), that you receive source code or can get it
25 | if you want it, that you can change the software or use pieces of it
26 | in new free programs; and that you know you can do these things.
27 |
28 | To protect your rights, we need to make restrictions that forbid
29 | anyone to deny you these rights or to ask you to surrender the rights.
30 | These restrictions translate to certain responsibilities for you if you
31 | distribute copies of the software, or if you modify it.
32 |
33 | For example, if you distribute copies of such a program, whether
34 | gratis or for a fee, you must give the recipients all the rights that
35 | you have. You must make sure that they, too, receive or can get the
36 | source code. And you must show them these terms so they know their
37 | rights.
38 |
39 | We protect your rights with two steps: (1) copyright the software, and
40 | (2) offer you this license which gives you legal permission to copy,
41 | distribute and/or modify the software.
42 |
43 | Also, for each author's protection and ours, we want to make certain
44 | that everyone understands that there is no warranty for this free
45 | software. If the software is modified by someone else and passed on, we
46 | want its recipients to know that what they have is not the original, so
47 | that any problems introduced by others will not reflect on the original
48 | authors' reputations.
49 |
50 | Finally, any free program is threatened constantly by software
51 | patents. We wish to avoid the danger that redistributors of a free
52 | program will individually obtain patent licenses, in effect making the
53 | program proprietary. To prevent this, we have made it clear that any
54 | patent must be licensed for everyone's free use or not licensed at all.
55 |
56 | The precise terms and conditions for copying, distribution and
57 | modification follow.
58 |
59 | GNU GENERAL PUBLIC LICENSE
60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
61 |
62 | 0. This License applies to any program or other work which contains
63 | a notice placed by the copyright holder saying it may be distributed
64 | under the terms of this General Public License. The "Program", below,
65 | refers to any such program or work, and a "work based on the Program"
66 | means either the Program or any derivative work under copyright law:
67 | that is to say, a work containing the Program or a portion of it,
68 | either verbatim or with modifications and/or translated into another
69 | language. (Hereinafter, translation is included without limitation in
70 | the term "modification".) Each licensee is addressed as "you".
71 |
72 | Activities other than copying, distribution and modification are not
73 | covered by this License; they are outside its scope. The act of
74 | running the Program is not restricted, and the output from the Program
75 | is covered only if its contents constitute a work based on the
76 | Program (independent of having been made by running the Program).
77 | Whether that is true depends on what the Program does.
78 |
79 | 1. You may copy and distribute verbatim copies of the Program's
80 | source code as you receive it, in any medium, provided that you
81 | conspicuously and appropriately publish on each copy an appropriate
82 | copyright notice and disclaimer of warranty; keep intact all the
83 | notices that refer to this License and to the absence of any warranty;
84 | and give any other recipients of the Program a copy of this License
85 | along with the Program.
86 |
87 | You may charge a fee for the physical act of transferring a copy, and
88 | you may at your option offer warranty protection in exchange for a fee.
89 |
90 | 2. You may modify your copy or copies of the Program or any portion
91 | of it, thus forming a work based on the Program, and copy and
92 | distribute such modifications or work under the terms of Section 1
93 | above, provided that you also meet all of these conditions:
94 |
95 | a) You must cause the modified files to carry prominent notices
96 | stating that you changed the files and the date of any change.
97 |
98 | b) You must cause any work that you distribute or publish, that in
99 | whole or in part contains or is derived from the Program or any
100 | part thereof, to be licensed as a whole at no charge to all third
101 | parties under the terms of this License.
102 |
103 | c) If the modified program normally reads commands interactively
104 | when run, you must cause it, when started running for such
105 | interactive use in the most ordinary way, to print or display an
106 | announcement including an appropriate copyright notice and a
107 | notice that there is no warranty (or else, saying that you provide
108 | a warranty) and that users may redistribute the program under
109 | these conditions, and telling the user how to view a copy of this
110 | License. (Exception: if the Program itself is interactive but
111 | does not normally print such an announcement, your work based on
112 | the Program is not required to print an announcement.)
113 |
114 | These requirements apply to the modified work as a whole. If
115 | identifiable sections of that work are not derived from the Program,
116 | and can be reasonably considered independent and separate works in
117 | themselves, then this License, and its terms, do not apply to those
118 | sections when you distribute them as separate works. But when you
119 | distribute the same sections as part of a whole which is a work based
120 | on the Program, the distribution of the whole must be on the terms of
121 | this License, whose permissions for other licensees extend to the
122 | entire whole, and thus to each and every part regardless of who wrote it.
123 |
124 | Thus, it is not the intent of this section to claim rights or contest
125 | your rights to work written entirely by you; rather, the intent is to
126 | exercise the right to control the distribution of derivative or
127 | collective works based on the Program.
128 |
129 | In addition, mere aggregation of another work not based on the Program
130 | with the Program (or with a work based on the Program) on a volume of
131 | a storage or distribution medium does not bring the other work under
132 | the scope of this License.
133 |
134 | 3. You may copy and distribute the Program (or a work based on it,
135 | under Section 2) in object code or executable form under the terms of
136 | Sections 1 and 2 above provided that you also do one of the following:
137 |
138 | a) Accompany it with the complete corresponding machine-readable
139 | source code, which must be distributed under the terms of Sections
140 | 1 and 2 above on a medium customarily used for software interchange; or,
141 |
142 | b) Accompany it with a written offer, valid for at least three
143 | years, to give any third party, for a charge no more than your
144 | cost of physically performing source distribution, a complete
145 | machine-readable copy of the corresponding source code, to be
146 | distributed under the terms of Sections 1 and 2 above on a medium
147 | customarily used for software interchange; or,
148 |
149 | c) Accompany it with the information you received as to the offer
150 | to distribute corresponding source code. (This alternative is
151 | allowed only for noncommercial distribution and only if you
152 | received the program in object code or executable form with such
153 | an offer, in accord with Subsection b above.)
154 |
155 | The source code for a work means the preferred form of the work for
156 | making modifications to it. For an executable work, complete source
157 | code means all the source code for all modules it contains, plus any
158 | associated interface definition files, plus the scripts used to
159 | control compilation and installation of the executable. However, as a
160 | special exception, the source code distributed need not include
161 | anything that is normally distributed (in either source or binary
162 | form) with the major components (compiler, kernel, and so on) of the
163 | operating system on which the executable runs, unless that component
164 | itself accompanies the executable.
165 |
166 | If distribution of executable or object code is made by offering
167 | access to copy from a designated place, then offering equivalent
168 | access to copy the source code from the same place counts as
169 | distribution of the source code, even though third parties are not
170 | compelled to copy the source along with the object code.
171 |
172 | 4. You may not copy, modify, sublicense, or distribute the Program
173 | except as expressly provided under this License. Any attempt
174 | otherwise to copy, modify, sublicense or distribute the Program is
175 | void, and will automatically terminate your rights under this License.
176 | However, parties who have received copies, or rights, from you under
177 | this License will not have their licenses terminated so long as such
178 | parties remain in full compliance.
179 |
180 | 5. You are not required to accept this License, since you have not
181 | signed it. However, nothing else grants you permission to modify or
182 | distribute the Program or its derivative works. These actions are
183 | prohibited by law if you do not accept this License. Therefore, by
184 | modifying or distributing the Program (or any work based on the
185 | Program), you indicate your acceptance of this License to do so, and
186 | all its terms and conditions for copying, distributing or modifying
187 | the Program or works based on it.
188 |
189 | 6. Each time you redistribute the Program (or any work based on the
190 | Program), the recipient automatically receives a license from the
191 | original licensor to copy, distribute or modify the Program subject to
192 | these terms and conditions. You may not impose any further
193 | restrictions on the recipients' exercise of the rights granted herein.
194 | You are not responsible for enforcing compliance by third parties to
195 | this License.
196 |
197 | 7. If, as a consequence of a court judgment or allegation of patent
198 | infringement or for any other reason (not limited to patent issues),
199 | conditions are imposed on you (whether by court order, agreement or
200 | otherwise) that contradict the conditions of this License, they do not
201 | excuse you from the conditions of this License. If you cannot
202 | distribute so as to satisfy simultaneously your obligations under this
203 | License and any other pertinent obligations, then as a consequence you
204 | may not distribute the Program at all. For example, if a patent
205 | license would not permit royalty-free redistribution of the Program by
206 | all those who receive copies directly or indirectly through you, then
207 | the only way you could satisfy both it and this License would be to
208 | refrain entirely from distribution of the Program.
209 |
210 | If any portion of this section is held invalid or unenforceable under
211 | any particular circumstance, the balance of the section is intended to
212 | apply and the section as a whole is intended to apply in other
213 | circumstances.
214 |
215 | It is not the purpose of this section to induce you to infringe any
216 | patents or other property right claims or to contest validity of any
217 | such claims; this section has the sole purpose of protecting the
218 | integrity of the free software distribution system, which is
219 | implemented by public license practices. Many people have made
220 | generous contributions to the wide range of software distributed
221 | through that system in reliance on consistent application of that
222 | system; it is up to the author/donor to decide if he or she is willing
223 | to distribute software through any other system and a licensee cannot
224 | impose that choice.
225 |
226 | This section is intended to make thoroughly clear what is believed to
227 | be a consequence of the rest of this License.
228 |
229 | 8. If the distribution and/or use of the Program is restricted in
230 | certain countries either by patents or by copyrighted interfaces, the
231 | original copyright holder who places the Program under this License
232 | may add an explicit geographical distribution limitation excluding
233 | those countries, so that distribution is permitted only in or among
234 | countries not thus excluded. In such case, this License incorporates
235 | the limitation as if written in the body of this License.
236 |
237 | 9. The Free Software Foundation may publish revised and/or new versions
238 | of the General Public License from time to time. Such new versions will
239 | be similar in spirit to the present version, but may differ in detail to
240 | address new problems or concerns.
241 |
242 | Each version is given a distinguishing version number. If the Program
243 | specifies a version number of this License which applies to it and "any
244 | later version", you have the option of following the terms and conditions
245 | either of that version or of any later version published by the Free
246 | Software Foundation. If the Program does not specify a version number of
247 | this License, you may choose any version ever published by the Free Software
248 | Foundation.
249 |
250 | 10. If you wish to incorporate parts of the Program into other free
251 | programs whose distribution conditions are different, write to the author
252 | to ask for permission. For software which is copyrighted by the Free
253 | Software Foundation, write to the Free Software Foundation; we sometimes
254 | make exceptions for this. Our decision will be guided by the two goals
255 | of preserving the free status of all derivatives of our free software and
256 | of promoting the sharing and reuse of software generally.
257 |
258 | NO WARRANTY
259 |
260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
268 | REPAIR OR CORRECTION.
269 |
270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
278 | POSSIBILITY OF SUCH DAMAGES.
279 |
280 | END OF TERMS AND CONDITIONS
281 |
282 | How to Apply These Terms to Your New Programs
283 |
284 | If you develop a new program, and you want it to be of the greatest
285 | possible use to the public, the best way to achieve this is to make it
286 | free software which everyone can redistribute and change under these terms.
287 |
288 | To do so, attach the following notices to the program. It is safest
289 | to attach them to the start of each source file to most effectively
290 | convey the exclusion of warranty; and each file should have at least
291 | the "copyright" line and a pointer to where the full notice is found.
292 |
293 | {description}
294 | Copyright (C) {year} {fullname}
295 |
296 | This program is free software; you can redistribute it and/or modify
297 | it under the terms of the GNU General Public License as published by
298 | the Free Software Foundation; either version 2 of the License, or
299 | (at your option) any later version.
300 |
301 | This program is distributed in the hope that it will be useful,
302 | but WITHOUT ANY WARRANTY; without even the implied warranty of
303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
304 | GNU General Public License for more details.
305 |
306 | You should have received a copy of the GNU General Public License along
307 | with this program; if not, write to the Free Software Foundation, Inc.,
308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
309 |
310 | Also add information on how to contact you by electronic and paper mail.
311 |
312 | If the program is interactive, make it output a short notice like this
313 | when it starts in an interactive mode:
314 |
315 | Gnomovision version 69, Copyright (C) year name of author
316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
317 | This is free software, and you are welcome to redistribute it
318 | under certain conditions; type `show c' for details.
319 |
320 | The hypothetical commands `show w' and `show c' should show the appropriate
321 | parts of the General Public License. Of course, the commands you use may
322 | be called something other than `show w' and `show c'; they could even be
323 | mouse-clicks or menu items--whatever suits your program.
324 |
325 | You should also get your employer (if you work as a programmer) or your
326 | school, if any, to sign a "copyright disclaimer" for the program, if
327 | necessary. Here is a sample; alter the names:
328 |
329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program
330 | `Gnomovision' (which makes passes at compilers) written by James Hacker.
331 |
332 | {signature of Ty Coon}, 1 April 1989
333 | Ty Coon, President of Vice
334 |
335 | This General Public License does not permit incorporating your program into
336 | proprietary programs. If your program is a subroutine library, you may
337 | consider it more useful to permit linking proprietary applications with the
338 | library. If this is what you want to do, use the GNU Lesser General
339 | Public License instead of this License.
340 |
341 |
--------------------------------------------------------------------------------