Tema dizini eklendi, public silindi

master
Özcan Oğuz 3 years ago
parent d3a22a7b62
commit 7a9e74cfb4
Signed by: ooguz
GPG Key ID: 2D33E2BD3D975818
  1. 2
      .gitignore
  2. 25
      public/_index.md.backup
  3. 371
      public/categories/atölye/index.html
  4. 31
      public/categories/atölye/index.xml
  5. 1
      public/categories/atölye/page/1/index.html
  6. 366
      public/categories/açılış/index.html
  7. 28
      public/categories/açılış/index.xml
  8. 1
      public/categories/açılış/page/1/index.html
  9. 372
      public/categories/cryptoparty/index.html
  10. 31
      public/categories/cryptoparty/index.xml
  11. 1
      public/categories/cryptoparty/page/1/index.html
  12. 291
      public/categories/development/index.html
  13. 24
      public/categories/development/index.xml
  14. 1
      public/categories/development/page/1/index.html
  15. 427
      public/categories/etkinlik/index.html
  16. 61
      public/categories/etkinlik/index.xml
  17. 1
      public/categories/etkinlik/page/1/index.html
  18. 343
      public/categories/index.html
  19. 51
      public/categories/index.xml
  20. 291
      public/categories/vim/index.html
  21. 24
      public/categories/vim/index.xml
  22. 1
      public/categories/vim/page/1/index.html
  23. BIN
      public/hsist.png
  24. 13
      public/iletisim.md.backup
  25. 339
      public/iletisim/index.html
  26. 359
      public/index.html
  27. 84
      public/index.xml
  28. 417
      public/isler/cryptoparty-0/index.html
  29. 56
      public/isler/gnulinux-ile-tanisma-atolyesi.md.backup
  30. 397
      public/isler/gnulinux-tanisma-atolyesi/index.html
  31. 75
      public/isler/hackerspace-istanbul-acilis-partisi (kopya 1).md.backup
  32. 348
      public/isler/hackerspace-istanbul-acilis-partisi/index.html
  33. 427
      public/isler/index.html
  34. 61
      public/isler/index.xml
  35. 1
      public/isler/page/1/index.html
  36. 274
      public/isler/spf13-vim-3-0-release-and-new-website/index.html
  37. BIN
      public/logo.png
  38. 161
      public/manifesto.md.backup
  39. 502
      public/manifesto/index.html
  40. 1
      public/page/1/index.html
  41. 101
      public/sitemap.xml
  42. 291
      public/tags/.vimrc/index.html
  43. 24
      public/tags/.vimrc/index.xml
  44. 1
      public/tags/.vimrc/page/1/index.html
  45. 427
      public/tags/2018/index.html
  46. 61
      public/tags/2018/index.xml
  47. 1
      public/tags/2018/page/1/index.html
  48. 402
      public/tags/atölye/index.html
  49. 48
      public/tags/atölye/index.xml
  50. 1
      public/tags/atölye/page/1/index.html
  51. 366
      public/tags/açılış/index.html
  52. 28
      public/tags/açılış/index.xml
  53. 1
      public/tags/açılış/page/1/index.html
  54. 372
      public/tags/cryptoparty/index.html
  55. 31
      public/tags/cryptoparty/index.xml
  56. 1
      public/tags/cryptoparty/page/1/index.html
  57. 396
      public/tags/hs.ist/index.html
  58. 44
      public/tags/hs.ist/index.xml
  59. 1
      public/tags/hs.ist/page/1/index.html
  60. 345
      public/tags/index.html
  61. 60
      public/tags/index.xml
  62. 291
      public/tags/plugins/index.html
  63. 24
      public/tags/plugins/index.xml
  64. 1
      public/tags/plugins/page/1/index.html
  65. 291
      public/tags/spf13-vim/index.html
  66. 24
      public/tags/spf13-vim/index.xml
  67. 1
      public/tags/spf13-vim/page/1/index.html
  68. 291
      public/tags/vim/index.html
  69. 24
      public/tags/vim/index.xml
  70. 1
      public/tags/vim/page/1/index.html
  71. 1
      themes/after-dark
  72. 2
      themes/after-dark/.gitignore
  73. 1
      themes/after-dark/.gitt/HEAD
  74. 11
      themes/after-dark/.gitt/config
  75. 1
      themes/after-dark/.gitt/description
  76. 15
      themes/after-dark/.gitt/hooks/applypatch-msg.sample
  77. 24
      themes/after-dark/.gitt/hooks/commit-msg.sample
  78. 8
      themes/after-dark/.gitt/hooks/post-update.sample
  79. 14
      themes/after-dark/.gitt/hooks/pre-applypatch.sample
  80. 49
      themes/after-dark/.gitt/hooks/pre-commit.sample
  81. 53
      themes/after-dark/.gitt/hooks/pre-push.sample
  82. 169
      themes/after-dark/.gitt/hooks/pre-rebase.sample
  83. 36
      themes/after-dark/.gitt/hooks/prepare-commit-msg.sample
  84. 128
      themes/after-dark/.gitt/hooks/update.sample
  85. BIN
      themes/after-dark/.gitt/index
  86. 6
      themes/after-dark/.gitt/info/exclude
  87. 1
      themes/after-dark/.gitt/logs/HEAD
  88. 1
      themes/after-dark/.gitt/logs/refs/heads/master
  89. 1
      themes/after-dark/.gitt/logs/refs/remotes/origin/HEAD
  90. BIN
      themes/after-dark/.gitt/objects/pack/pack-ff5558d864caefcd730fc872d89cbfd0b08effd7.idx
  91. BIN
      themes/after-dark/.gitt/objects/pack/pack-ff5558d864caefcd730fc872d89cbfd0b08effd7.pack
  92. 88
      themes/after-dark/.gitt/packed-refs
  93. 1
      themes/after-dark/.gitt/refs/heads/master
  94. 1
      themes/after-dark/.gitt/refs/remotes/origin/HEAD
  95. 517
      themes/after-dark/CHANGELOG.md
  96. 13
      themes/after-dark/COPYING
  97. 706
      themes/after-dark/README.md
  98. 6
      themes/after-dark/archetypes/default.md
  99. 27
      themes/after-dark/archetypes/post.md
  100. BIN
      themes/after-dark/images/docs/feat-instant-view.png
  101. Some files were not shown because too many files have changed in this diff Show More

2
.gitignore vendored

@ -0,0 +1,2 @@
public/
resources/

@ -1,25 +0,0 @@
+++
title = "ana sayfa"
+++
## Hackerspace nedir?
Hackerspace, hacker kıraathanesidir.
## Hacking nedir?
Hacking ifadesi gibi değişken bir ifade için basit bir tanım yapmak zordur; ama birçok hacker'ın ortak özelliği oyuncu, zeki ve keşifçi olmalarıdır. Bu nedenle hacking, oyuncu bir zeka ruhunda mümkün olanın sınırlarını keşfetmek anlamına gelmektedir. Oyuncu zeka gösteren etkinlikler hack değerine sahiptir.
-- <i>Richard Stallman, “Hacking Hakkında”</i>
## Hackerspace Istanbul nedir?
Hackerspace İstanbul; **2017 Aralık'ta kurulmuş olan**, el birliği ile toplanan imkanların bir arada bulunduğu, bilgisayar, elektronik, internet, DIY, sanat ve benzeri konulara ilgi duyan insanların beraber çalışabilecekleri, proje üretebilecekleri, sosyalleşebilecekleri ve etkinlikler düzenleyebilecekleri bir atölyedir.
## Mekan açık mı?
Bütçe sıkıntıları sebebiyle 2018 yılının Ekim ayında fiziksel mekanı kapatmak zorunda kaldık. Ancak Özgür Yazılım Derneği çevresinde yeniden açma çalışmalarımız devam etmektedir.
## Nasıl bağışta bulunabilirim?
**HSIST** yazıp **8071**'e göndererek aylık **20 TL** bağışta bulunarak destekçi üyemiz olabilirsiniz.

File diff suppressed because one or more lines are too long

@ -1,31 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Atölye on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/at%C3%B6lye/</link>
<description>Recent content in Atölye on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/at%C3%B6lye/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/at%C3%B6lye/</title><link rel="canonical" href="http://hackerspace.ist/categories/at%C3%B6lye/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/at%C3%B6lye/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,28 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Açılış on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/</link>
<description>Recent content in Açılış on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Fri, 13 Apr 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/</title><link rel="canonical" href="http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,31 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Cryptoparty on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/cryptoparty/</link>
<description>Recent content in Cryptoparty on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<atom:link href="http://hackerspace.ist/categories/cryptoparty/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/cryptoparty/</title><link rel="canonical" href="http://hackerspace.ist/categories/cryptoparty/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/cryptoparty/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Development on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/development/</link>
<description>Recent content in Development on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/development/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/development/</title><link rel="canonical" href="http://hackerspace.ist/categories/development/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/development/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,61 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Etkinlik on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/etkinlik/</link>
<description>Recent content in Etkinlik on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/etkinlik/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/etkinlik/</title><link rel="canonical" href="http://hackerspace.ist/categories/etkinlik/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/etkinlik/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,51 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Categories on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/</link>
<description>Recent content in Categories on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Atölye</title>
<link>http://hackerspace.ist/categories/at%C3%B6lye/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/categories/at%C3%B6lye/</guid>
<description></description>
</item>
<item>
<title>Açılış</title>
<link>http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/</guid>
<description></description>
</item>
<item>
<title>Cryptoparty</title>
<link>http://hackerspace.ist/categories/cryptoparty/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/categories/cryptoparty/</guid>
<description></description>
</item>
<item>
<title>Etkinlik</title>
<link>http://hackerspace.ist/categories/etkinlik/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/categories/etkinlik/</guid>
<description></description>
</item>
</channel>
</rss>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Vim on hackerspace istanbul</title>
<link>http://hackerspace.ist/categories/vim/</link>
<description>Recent content in Vim on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/categories/vim/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/categories/vim/</title><link rel="canonical" href="http://hackerspace.ist/categories/vim/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/categories/vim/" /></head></html>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.3 KiB

@ -1,13 +0,0 @@
---
title: "iletişim"
draft: false
---
- **Posta**: Özgür Yazılım Derneği PK 5, 34710 Kadıköy/İstanbul
- **E-posta**: iletisim {güzela} hackerspace.ist
<!-- - **GnuPG anahtarı**: 0xFFFFFFFF -->
- **E-posta listesi**: [hsist-genel listesine üye olmak için tıklayın.](mailto:hsist-genel-join@liste.oyd.org.tr?subject=subscribe)
<!-- **XMPP**: genel {güzela} hackerspace.ist -->
<!-- - **Amatör telsiz**: 439,775 MHz - YM2HS -->
<!-- - **Matrix**: hsist@matrix.hackerspace.ist -->
- **IRC**: freenode üzerinde #hsist

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

@ -1,84 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>ana sayfa on hackerspace istanbul</title>
<link>http://hackerspace.ist/</link>
<description>Recent content in ana sayfa on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
<item>
<title>iletişim</title>
<link>http://hackerspace.ist/iletisim/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/iletisim/</guid>
<description> Posta: Özgür Yazılım Derneği PK 5, 34710 Kadıköy/İstanbul E-posta: iletisim {güzela} hackerspace.ist E-posta listesi: hsist-genel listesine üye olmak için tıklayın. IRC: freenode üzerinde #hsist </description>
</item>
<item>
<title>manifesto</title>
<link>http://hackerspace.ist/manifesto/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/manifesto/</guid>
<description>“Hacking” &amp;ldquo;Hacking, oyuncu bir zeka ruhunda mümkün olanın sınırlarını keşfetmek anlamına gelmektedir. Oyuncu zeka gösteren etkinlikler hack değerine sahiptir.&amp;rdquo;
&amp;ndash; Richard M. Stallman (rms)
hs.ist Bu bölüm içerisindekiler hs.ist&amp;rsquo;in kendi için kendine hatırlattıklarıdır.
Yine hs.ist, merak edenler için yazıya dökülmesini rica etmiştir.
Bu noktadan sonra &amp;ldquo;Hackerspace İstanbul&amp;rdquo; için kısaca &amp;ldquo;hs.ist&amp;rdquo; denir.
Hackerspace İstanbul canlı olduğu, doğal ve otonom olarak hareket ettiğinden, bölüm boyunca; gideceği veya bulunacağı yolu tanımlar. Yani bu kısım; hs.</description>
</item>
</channel>
</rss>

File diff suppressed because one or more lines are too long

@ -1,56 +0,0 @@
+++
title = "GNU/Linux ile Tanışma Atölyesi"
description = "Atölye"
date = "2018-05-22"
author = "hs.ist"
categories = ["Etkinlik", "Atölye"]
slug = "gnulinux-tanisma-atolyesi"
tags = ["2018", "atölye", "hs.ist"]
+++
### GNU/Linux ile Tanışma Atölyesi
**Eğitmen:** Özcan Oğuz <ozcan@hackerspace.ist>
**Tarih:** 26 Mayıs 2018
**Saat:** 16.00-20.00
**Yer:** [Hackerspace İstanbul](https://hackerspace.ist/iletisim.html)
**Kontenjan:** 10
**Minimum Bağış Miktarı:** 25 TL (*Toplanan bütün bağış, HS'nin devamlılığını sağlamak adına kullanılacaktır.*)
**Kayıt:** Kayıt olmak için, **kayıt {güzela} hackerspace.ist** adresine, konusu "KVKK ve Verinin Geleceği" konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.
* Özgür yazılım felsefesi
* İşletim sistemi, dağıtım, çekirdek, donanım, yazılım kavramları
* Masaüstü ortamı, pencere yöneticisi, komut satırı kavramları
* GNU/Linux işletim sisteminin yapısı
* Giriş seviyesi masaüstü kullanımı
* Yardım almak
* Komut satırı ortamında dosya ve dizin işlemleri
* Giriş seviyesi kullanıcı yönetimi
* Paket yönetim sistemi
* Dosya yedekleme
Bütün akış, Debian GNU/Linux ve türevleri üzerinden ilerleyecektir.
#### Ön Gereksinimler
* Sanal makina üzerinde masaüstü ortamıyla birlikte Debian GNU/Linux kurulu bir kişisel bilgisayar ile gelmeniz beklenmektedir.
[VirtualBox Kurulum Belgesi](https://kurs.ab.org.tr/2018/wp-content/uploads/2018/01/virtual-box.pdf)
| [Debian GNU/Linux Kurulum Belgesi](https://kurs.ab.org.tr/2018/wp-content/uploads/2018/01/debian-kurulum.pdf)
Sanal makinanın bozulması ihtimaline karşı, makinanın bir yedeğini almanızı tavsiye ederiz.
#### Kayıt Soruları
* Kullandığınız ilk özgür yazılım nedir?
* GNU/Linux işletim sistemi hakkında birkaç cümle kurabilir misiniz?
Etiketler: atölye, gnu/linux, başlangıç, mayıs

File diff suppressed because one or more lines are too long

@ -1,75 +0,0 @@
+++
title = "CryptoParty #0"
description = "Etkinlik"
date = "2018-06-5"
author = "hs.ist"
categories = ["Etkinlik", "CryptoParty"]
slug = "cryptoparty-0"
tags = ["2018", "atölye", "cryptoparty"]
+++
## CryptoParty #0
**Eğitmen:** Özcan Oğuz
**Tarih:** 9 Haziran 2018 Cumartesi
**Saat:** 16:00
**Yer:** [Hackerspace İstanbul](https://hackerspace.ist/iletisim.html)
**Kontenjan:** 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
**Minimum Bağış Miktarı:** 25 TL (*Toplanan bütün bağış, HS'nin devamlılığını sağlamak adına kullanılacaktır.*)
**Kayıt:** [Kayıt sayfası](https://hackerspace.ist/etkinlikler)'nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty'de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.
Etkinlik sonunda, katılımcıların kişisel mahremiyetlerini ve gizliliklerini nasıl sağlayacakları konusunda tecrübe kazanmış olmaları hedeflenmektedir.
#### Akış
* Kriptoloji, şifre, parola kavramları
* Kriptolojinin kısa tarihçesi
* Kriptolojinin temel amaçları
* Asimetrik-simetrik şifreleme kavramları
* Basit şifreleme uygulamaları (Sezar, Poli-alfabetik vs.)
* Vernam şifreleme algoritması
* Açık-kapalı anahtar kavramları
* Diffie-Hellmann Anahtar Değişimi
* GnuPG/PGP'ye giriş
* GPG: Anahtar çifti oluşturma
* GPG: Anahtar sunucusu kullanımı
* GPG: Keychain yönetimi
* GPG: Anahtar imzalama
* GPG: Enigmail kurulumu ve şifreli e-posta gönderimi
* Tor nedir?
* Tor ağının çalışma prensipleri
* Tor: Tor tarayıcısına genel bakış
* Tor: Tor proxy kullanımı
* OTR ve OMEMO nedir?
* OTR: Pidgin üzerine OTR kurulumu
* OTR: Doğrulama yöntemleri
* OMEMO: Pidgin üzerine OMEMO kurulumu
* OMEMO ve OTR arasındaki farklar
* Gizliliğinizi ve güvenliğinizi sağlamanıza yardımcı olabilecek tarayıcı eklentileri
#### Ön Gereksinimler
* [GNU](https://gnu.org) işletim sistemi kurulu bir kişisel bilgisayar (**Not:** Akış bütünüyle GNU/Linux işletim sistemi üzerinden anlatılacaktır. Anlatılacak araçların birçoğu, özel mülk sistemler üzerinde de çalışmakla birlikte, şifreleme araçlarının özel mülk sistemlerde çalıştırılması mahremiyet ve güvenlik açısından uygun değildir. Eğer yine de özel mülkiyet bir sistem ile katılmak istiyorsanız, araçların işletim sisteminize uygun sürümlerini araştırıp kurabilirsiniz. Ancak, kurulumda veya uygulamada karşılaşabileceğiniz sorunlar veya hatalar için sizlere yardımcı olmayız.)
* [GPG](https://gnupg.org), [Pidgin](https://pidgin.im), pidgin-otr, [Thunderbird](https://thunderbird.net) ve [Tor Browser](https://ozgurlesin.org/tor.html) paketlerini atölyeye gelmeden önce kurmanız gerekmektedir.
* [F-Droid](https://f-droid.org) kurulu bir Android (tercihen Replicant veya LineageOS dağıtımı ile) cep telefonu (*Opsiyonel*)
#### Kayıt için sorular
* CryptoParty'den beklentiniz nedir?
* Şifre ve parola arasındaki farkı kısaca açıklar mısınız?
* "Deep Web" kavramını daha önce duydunuz mu? Sizin için ne ifade ettiğini kısaca belirtir misiniz?
Etiketler: cryptoparty, atölye, etkinlik, haziran

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

@ -1,61 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>işler on hackerspace istanbul</title>
<link>http://hackerspace.ist/isler/</link>
<description>Recent content in işler on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/isler/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/isler/</title><link rel="canonical" href="http://hackerspace.ist/isler/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/isler/" /></head></html>

File diff suppressed because one or more lines are too long

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.6 KiB

@ -1,161 +0,0 @@
+++
title = "manifesto"
+++
## “Hacking”
"Hacking, oyuncu bir zeka ruhunda mümkün olanın sınırlarını keşfetmek anlamına gelmektedir. Oyuncu zeka gösteren etkinlikler **hack değeri**ne sahiptir."
-- **Richard M. Stallman** (rms)
---
## hs.ist
Bu bölüm içerisindekiler hs.ist'in kendi için kendine hatırlattıklarıdır.
Yine hs.ist, merak edenler için yazıya dökülmesini rica etmiştir.
_Bu noktadan sonra "Hackerspace İstanbul" için kısaca **"hs.ist"** denir._
Hackerspace İstanbul canlı olduğu, doğal ve otonom olarak hareket ettiğinden, bölüm boyunca; gideceği veya bulunacağı yolu tanımlar. Yani bu kısım; hs.ist adına yapılanları ve hs.ist adına konuşulanları düzenler.
hs.ist, "Neden?" sorusundan hoşlanmaz. Cevabı hep "Çünkü yapabiliyorum" olur. Doğru soru "Nasıl?" olmalıdır.
hs.ist, yeniden üretimi ve değiştirmeyi de üretime dahil görür.
hs.ist, GNU Felsefesi[1] ile ilerler. HS olarak üreteceği her şey bu felsefeye uygun olarak "özgür" tanımına dahil olacaktır. Yani eğer yazılım üretiyorsa bu özgür yazılım, donanım üretiyorsa bu özgür donanım (tasarımı), bir belge yazıyorsa bu özgür bir belge olacak ve üretimlerini yine özgür bir lisans ile lisanslayacaktır. [2]
hs.ist, düzenlediği bütün etkinlikleri ve yaptığı bütün çalışmaları bu felsefeye dayanarak yürütecektir.
GNU felsefesi hs.ist'nin temel dayanağıdır.
hs.ist, özgür olanı "özgür" diye ifade eder. Özgür olmayanı ise "özel mülkiyet" veya "sahipli" olarak adlandırır. [3] Bu tanımları kaynağın açık ve kapalı olması ile sınırlamaz.
hs.ist için bir yazılımın "açık kaynak" olması hiçbir anlam ihtiva etmez. Önemli olan özgür olup olmadığıdır.
hs.ist, sahipli yazılım üreticilerinden ve savunucularından imtina eder.
hs.ist, hack kültürünün üretimlerini ve üreticilerini şapkalandırmaz.
hs.ist, hack kültürünü ve hacker'ları güvenlik ya da yazılım ile sınırlamaz.
hs.ist, tüketim "kültürüne" karşıdır, "yenisini almak" yerine tamir etmeyi tercih eder. HS için malzeme farklı bir alanda kullanılmak üzere saklanacak değerdedir.
hs.ist, her tür ve seviyeden sansür ve toplu gözetim karşıtıdır. Bu gözetime yardım eden, destek olan, öven; yapı, organizasyon veya çıktılara hiçbir açıdan dahil olmaz ve bunları meşrulaştırmaz.
hs.ist, mümkün olanın sınırlarını keşfetme hakkını saklı tutar.
hs.ist'e iştirak eden herkes işbu protokolü kabul etmiş sayılır.
---
<!--
## Kullanım
Etkinlikler ve açık toplantılar haricinde mekanın kullanım hakkı yalnızca üyelere aittir.
Eğer aksi belirtilmemişse etkinlikler herkese açıktır.
--- -->
## Üyelik
**Üyelik tipleri:**
hs.ist'in iki tip üyesi vardır:
* Üyeler
* Destekçi üyeler
**Üye olmak için:**
En üstte bulunan "Hacking" bölümündeki tanıma dahil olmak.
Mevcut hs.ist üyelerinden en az birinin size referans olması [4]
Açık toplantılara katılım sağlamak gerekmektedir. (Mekan fiziksel olarak kapalı olduğu için e-posta listesine katılım sağlamak.)
**Üye olarak kalmak için ise;**
hs.ist'in hayatta kalabilmesi ve devamlılığının sağlanması için gereken inisiyatifleri almak,
hs.ist'in bir parçası olduğunun bilincine varmak,
hs.ist'i mekan dışında olması gerektiği şekilde temsil etmek,
Diğer tüm üyelerle gerektiği kadar iletişim içerisinde olmak gerekmektedir.
**Destekçi üye olmak için**
hs.ist'e mali veya ayni olarak destek veren veya hs.ist'in devamlılığı ve sürdürülebilirliği için çalışan kişiler destekçi üye olabilir.
**Yetkililer;**
hs.ist, ilkeleri doğrultusunda otonom bir şekilde ilerlemektedir.
hs.ist'in bir yetkilisi yoktur, dolayısıyla sorumluluğu veya yetkiyi dağıtacak ve paylaştıracak hiç kimse bulunmamaktadır.
hs.ist canlıdır. Eğer yapılması gereken bir şey varsa, onunla ilgilenebilir veya onunla ilgilenen kişilerle hareket edebilirsiniz.
Her üye, hs.ist'in bir parçasıdır ve üzerine düşen yükümlülüğü yerine getirmeyi üye olarak taahhüt eder.
hs.ist'in özel güçleri vardır.
---
## Protokolün geçerliliği
Bu protokol, hs.ist'in varoluş ilkelerini içermektedir.
hs.ist, konumdan ve kişilerden bağımsız olup, var olduğu her yerde işbu protokol geçerlidir.
Protokolün maddeleri düzenli olarak ihlal edilmeye başlandığında, hs.ist anlamını yitirerek fiilen ortadan kalkacağından, işbu protokol de kendi kendini imha edecektir.
---
## Sıkça Verilen Cevaplar
Hayır, ~~mekana gelmek~~ hs.ist'e katılmak için Özgür Yazılım savunucusu olmak zorunda değilsiniz, ancak dahil olmak için özgür yazılım aktivisti olmak zorundasınız.
Hayır, mekana bir WC [5] veya özel mülkiyet bir sistem ile gelebilirsiniz, ancak dahil olmak için GNU işletim sistemi kullanmak zorundasınız.
Hayır, Facebook veya Instagram kullanıyor olmanız mekana gelmenize engel değil, ancak dahil olmak için neden bu servisleri kullanmamanız gerektiğinin bilincine varmış olmalısınız.
Hayır, mekana gelmek için düşünce yapınız mekan ile örtüşmek zorunda değildir, ancak dahil olmak için HS'nin ilkelerini benimsemek zorundasınız.
Hayır, bir ziyaretçi olarak sizin dışarıda ne yaptığınız bizi ilgilendirmiyor, ancak dahil olmak için yaşam tarzınızı felsefemize uydurmak zorundasınız.
Hayır, özel mülk yazılım savunucuları giremez.
Aynen öyle, bu mekanda demokrasi yok, çünkü çoğunluğun diktatörlüğünü reddediyoruz.
Bu koşulları beğenmiyorsanız, her mahallede bir co-working space var, fiyatları uygun olan bir tanesini deneyebilirsiniz.
Hayır, mekanda "Unity atölyesi" düzenleyemezsiniz.
Hayır, HS size uyum sağlamayacaktır, siz HS'ye uyum sağlamak zorundasınız.
Hayır, üye olmak için teknik biri olmak zorunda değilsiniz.
Hayır, hacker ve maker aynı şey değildir, dolayısıyla hackerspace ve makerspace de aynı şey değildir.
Hayır, üyelerin mekanda yaptığı bütün çalışmalar mekan tanımına uygun olmak zorunda değildir. Ancak mekan dahilinde; kullanıcıların özgürlüklerini kısıtlayan, insanları istekleri haricinde toplu gözetim ağlarına dahil eden, DRM ve benzeri yapılar içeren veya sansür aracı olarak kullanılan uygulamalar kati surette geliştirilemez. Ayrıca mekan içerisinde, harici bir internet bağlantısı veya cihaz kullanılıyor olsa dahi; ortam dinlemesi yapan, insanları toplu gözetime dahil eden uygulamalar kullanılamaz.
Hayır, X hesabının şifresini kırmıyoruz. Ayrıca o "şifre" değil "parola".
Hayır, parola da kırmıyoruz.
Hayır, "open source'çu" veya "Linüx'çu" değiliz, **özgür yazılımcıyız**.
---
- [1] [https://www.gnu.org/philosophy/free-sw.tr.html](https://www.gnu.org/philosophy/free-sw.tr.html)
- [2] [https://www.gnu.org/licenses/license-list.html](https://www.gnu.org/licenses/license-list.html)
- [3] [https://www.gnu.org/gnu/why-gnu-linux.tr.html](https://www.gnu.org/gnu/why-gnu-linux.tr.html)
- [4] Eğer mekandan size referans olabilecek kimseyi tanımıyorsanız, mekana açık toplantıların olduğu günlerde gelerek arkadaş edinmeyi deneyebilirsiniz.
- [5] [https://www.gnu.org/philosophy/words-to-avoid.html#PC](https://www.gnu.org/philosophy/words-to-avoid.html#PC)
----
Bu metin, Creative Commons Attribution-NoDerivs 4.0 International lisansı ile lisanslanmıştır. [Neden bu lisans?](https://www.gnu.org/licenses/license-list.html#OpinionLicenses)

File diff suppressed because one or more lines are too long

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://example.org/</title><link rel="canonical" href="http://example.org/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://example.org/" /></head></html>

@ -1,101 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
</url>
<url>
<loc>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</loc>
<lastmod>2018-04-13T00:00:00+00:00</lastmod>
</url>
<url>
<loc>http://hackerspace.ist/tags/2018/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/tags/at%C3%B6lye/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/categories/at%C3%B6lye/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/</loc>
<lastmod>2018-04-13T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/categories/a%C3%A7%C4%B1l%C4%B1%C5%9F/</loc>
<lastmod>2018-04-13T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/categories/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/isler/cryptoparty-0/</loc>
</url>
<url>
<loc>http://hackerspace.ist/tags/cryptoparty/</loc>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/categories/cryptoparty/</loc>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/categories/etkinlik/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/tags/hs.ist/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/tags/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
<priority>0</priority>
</url>
<url>
<loc>http://hackerspace.ist/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
</url>
<url>
<loc>http://hackerspace.ist/iletisim/</loc>
</url>
<url>
<loc>http://hackerspace.ist/isler/</loc>
<lastmod>2018-05-22T00:00:00+00:00</lastmod>
</url>
<url>
<loc>http://hackerspace.ist/manifesto/</loc>
</url>
</urlset>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>.Vimrc on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/.vimrc/</link>
<description>Recent content in .Vimrc on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/.vimrc/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/.vimrc/</title><link rel="canonical" href="http://hackerspace.ist/tags/.vimrc/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/.vimrc/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,61 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>2018 on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/2018/</link>
<description>Recent content in 2018 on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/2018/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/2018/</title><link rel="canonical" href="http://hackerspace.ist/tags/2018/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/2018/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,48 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Atölye on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/at%C3%B6lye/</link>
<description>Recent content in Atölye on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/at%C3%B6lye/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/at%C3%B6lye/</title><link rel="canonical" href="http://hackerspace.ist/tags/at%C3%B6lye/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/at%C3%B6lye/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,28 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Açılış on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/</link>
<description>Recent content in Açılış on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Fri, 13 Apr 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/</title><link rel="canonical" href="http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,31 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Cryptoparty on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/cryptoparty/</link>
<description>Recent content in Cryptoparty on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<atom:link href="http://hackerspace.ist/tags/cryptoparty/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>CryptoParty #0</title>
<link>http://hackerspace.ist/isler/cryptoparty-0/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/cryptoparty-0/</guid>
<description>CryptoParty #0 Eğitmen: Özcan Oğuz
Tarih: 9 Haziran 2018 Cumartesi
Saat: 16:00
Yer: Hackerspace İstanbul
Kontenjan: 15 + 5 (+5 kişi, merdiven oturma düzeni için geçerlidir.)
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt sayfası&amp;lsquo;nda bulunan kayıt butonundan aşağıda yer alan soruların cevaplarını içeren bir e-posta göndererek kayıt olabilirsiniz.
CryptoParty, tüm dünyada gayrimerkezi olarak yürütülen bir harekettir.
CryptoParty&amp;rsquo;de, öncelikle kriptolojinin kısa bir tarihçesine ve kavramlarına değinilecek; ardından ise pratikte uygulamaları anlatılacaktır.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/cryptoparty/</title><link rel="canonical" href="http://hackerspace.ist/tags/cryptoparty/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/cryptoparty/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,44 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Hs.ist on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/hs.ist/</link>
<description>Recent content in Hs.ist on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/hs.ist/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>GNU/Linux ile Tanışma Atölyesi</title>
<link>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/gnulinux-tanisma-atolyesi/</guid>
<description>GNU/Linux ile Tanışma Atölyesi Eğitmen: Özcan Oğuz ozcan@hackerspace.ist
Tarih: 26 Mayıs 2018
Saat: 16.00-20.00
Yer: Hackerspace İstanbul
Kontenjan: 10
Minimum Bağış Miktarı: 25 TL (Toplanan bütün bağış, HS&amp;rsquo;nin devamlılığını sağlamak adına kullanılacaktır.)
Kayıt: Kayıt olmak için, kayıt {güzela} hackerspace.ist adresine, konusu &amp;ldquo;KVKK ve Verinin Geleceği&amp;rdquo; konulu bir e-postayı, iletişim bilgileriniz ve aşağıda belirtilen soruların cevaplarıyla birlikte göndermeniz gerekmektedir.
Bu atölyede, GNU/Linux ile ilk defa tanışacak olan katılımcıların, aşağıdaki konular hakkında giriş seviyesinde bilgi sahibi olmaları hedeflenmektedir.</description>
</item>
<item>
<title>Hackerspace Istanbul açılış partisi</title>
<link>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/hackerspace-istanbul-acilis-partisi/</guid>
<description>Hackerspace İstanbul, 20 Nisan günü açılıyor! Yer: Eğitim Mh. Eylül Sk. Öğün İş Merkezi No:5-7 D:19 Kadıköy/İstanbul (KTM&amp;rsquo;in önündeki otoparkta toplanıyoruz)
Saat: 20:00
Kayıt: Kayıt gerekmiyor
Ayrıntılar:
Mekanda sandalye sayısı çok az, bu yüzden açılışı ayakta düzen yapmak zorundayız. Sandalye gibi birçok eksiğimiz var, eğer çorbada bir tuzum olsun diyorsanız, ihtiyaç listemizden eksiklerimize göz atabilirsiniz.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/hs.ist/</title><link rel="canonical" href="http://hackerspace.ist/tags/hs.ist/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/hs.ist/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,60 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Tags on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/</link>
<description>Recent content in Tags on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Tue, 22 May 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>2018</title>
<link>http://hackerspace.ist/tags/2018/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/tags/2018/</guid>
<description></description>
</item>
<item>
<title>Atölye</title>
<link>http://hackerspace.ist/tags/at%C3%B6lye/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/tags/at%C3%B6lye/</guid>
<description></description>
</item>
<item>
<title>Açılış</title>
<link>http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/</link>
<pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/tags/a%C3%A7%C4%B1l%C4%B1%C5%9F/</guid>
<description></description>
</item>
<item>
<title>Cryptoparty</title>
<link>http://hackerspace.ist/tags/cryptoparty/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/tags/cryptoparty/</guid>
<description></description>
</item>
<item>
<title>Hs.ist</title>
<link>http://hackerspace.ist/tags/hs.ist/</link>
<pubDate>Tue, 22 May 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/tags/hs.ist/</guid>
<description></description>
</item>
</channel>
</rss>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Plugins on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/plugins/</link>
<description>Recent content in Plugins on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/plugins/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/plugins/</title><link rel="canonical" href="http://hackerspace.ist/tags/plugins/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/plugins/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Spf13 Vim on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/spf13-vim/</link>
<description>Recent content in Spf13 Vim on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/spf13-vim/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/spf13-vim/</title><link rel="canonical" href="http://hackerspace.ist/tags/spf13-vim/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/spf13-vim/" /></head></html>

File diff suppressed because one or more lines are too long

@ -1,24 +0,0 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Vim on hackerspace istanbul</title>
<link>http://hackerspace.ist/tags/vim/</link>
<description>Recent content in Vim on hackerspace istanbul</description>
<generator>Hugo -- gohugo.io</generator>
<language>tr-tr</language>
<lastBuildDate>Sat, 23 Jun 2018 00:00:00 +0000</lastBuildDate>
<atom:link href="http://hackerspace.ist/tags/vim/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Deneme işi</title>
<link>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</link>
<pubDate>Sat, 23 Jun 2018 00:00:00 +0000</pubDate>
<guid>http://hackerspace.ist/isler/spf13-vim-3-0-release-and-new-website/</guid>
<description>Lorem ipsum Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</description>
</item>
</channel>
</rss>

@ -1 +0,0 @@
<!DOCTYPE html><html><head><title>http://hackerspace.ist/tags/vim/</title><link rel="canonical" href="http://hackerspace.ist/tags/vim/"/><meta name="robots" content="noindex"><meta http-equiv="content-type" content="text/html; charset=utf-8" /><meta http-equiv="refresh" content="0; url=http://hackerspace.ist/tags/vim/" /></head></html>

@ -1 +0,0 @@
Subproject commit 7748120681752fd4b669eae0cab0f2b7e14b0d74

@ -0,0 +1,2 @@
.DS_Store
node_modules

@ -0,0 +1 @@
ref: refs/heads/master

@ -0,0 +1,11 @@
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = https://github.com/comfusion/after-dark.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master

@ -0,0 +1 @@
Unnamed repository; edit this file 'description' to name the repository.

@ -0,0 +1,15 @@
#!/bin/sh
#
# An example hook script to check the commit log message taken by
# applypatch from an e-mail message.
#
# The hook should exit with non-zero status after issuing an
# appropriate message if it wants to stop the commit. The hook is
# allowed to edit the commit message file.
#
# To enable this hook, rename this file to "applypatch-msg".
. git-sh-setup
commitmsg="$(git rev-parse --git-path hooks/commit-msg)"
test -x "$commitmsg" && exec "$commitmsg" ${1+"$@"}
:

@ -0,0 +1,24 @@
#!/bin/sh
#
# An example hook script to check the commit log message.
# Called by "git commit" with one argument, the name of the file
# that has the commit message. The hook should exit with non-zero
# status after issuing an appropriate message if it wants to stop the
# commit. The hook is allowed to edit the commit message file.
#
# To enable this hook, rename this file to "commit-msg".
# Uncomment the below to add a Signed-off-by line to the message.
# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
# hook is more suited to it.
#
# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
# This example catches duplicate Signed-off-by lines.
test "" = "$(grep '^Signed-off-by: ' "$1" |
sort | uniq -c | sed -e '/^[ ]*1[ ]/d')" || {
echo >&2 Duplicate Signed-off-by lines.
exit 1
}

@ -0,0 +1,8 @@
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, rename this file to "post-update".
exec git update-server-info

@ -0,0 +1,14 @@
#!/bin/sh
#
# An example hook script to verify what is about to be committed
# by applypatch from an e-mail message.
#
# The hook should exit with non-zero status after issuing an
# appropriate message if it wants to stop the commit.
#
# To enable this hook, rename this file to "pre-applypatch".
. git-sh-setup
precommit="$(git rev-parse --git-path hooks/pre-commit)"
test -x "$precommit" && exec "$precommit" ${1+"$@"}
:

@ -0,0 +1,49 @@
#!/bin/sh
#
# An example hook script to verify what is about to be committed.
# Called by "git commit" with no arguments. The hook should
# exit with non-zero status after issuing an appropriate message if
# it wants to stop the commit.
#
# To enable this hook, rename this file to "pre-commit".
if git rev-parse --verify HEAD >/dev/null 2>&1
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
fi
# If you want to allow non-ASCII filenames set this variable to true.
allownonascii=$(git config --bool hooks.allownonascii)
# Redirect output to stderr.
exec 1>&2
# Cross platform projects tend to avoid non-ASCII filenames; prevent
# them from being added to the repository. We exploit the fact that the
# printable range starts at the space character and ends with tilde.
if [ "$allownonascii" != "true" ] &&
# Note that the use of brackets around a tr range is ok here, (it's
# even required, for portability to Solaris 10's /usr/bin/tr), since
# the square bracket bytes happen to fall in the designated range.
test $(git diff --cached --name-only --diff-filter=A -z $against |
LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
then
cat <<\EOF
Error: Attempt to add a non-ASCII file name.
This can cause problems if you want to work with people on other platforms.
To be portable it is advisable to rename the file.
If you know what you are doing you can disable this check using:
git config hooks.allownonascii true
EOF
exit 1
fi
# If there are whitespace errors, print the offending file names and fail.
exec git diff-index --check --cached $against --

@ -0,0 +1,53 @@
#!/bin/sh
# An example hook script to verify what is about to be pushed. Called by "git
# push" after it has checked the remote status, but before anything has been
# pushed. If this script exits with a non-zero status nothing will be pushed.
#
# This hook is called with the following parameters:
#
# $1 -- Name of the remote to which the push is being done
# $2 -- URL to which the push is being done
#
# If pushing without using a named remote those arguments will be equal.
#
# Information about the commits which are being pushed is supplied as lines to
# the standard input in the form:
#
# <local ref> <local sha1> <remote ref> <remote sha1>
#
# This sample shows how to prevent push of commits where the log message starts
# with "WIP" (work in progress).
remote="$1"
url="$2"
z40=0000000000000000000000000000000000000000
while read local_ref local_sha remote_ref remote_sha
do
if [ "$local_sha" = $z40 ]
then
# Handle delete
:
else
if [ "$remote_sha" = $z40 ]
then
# New branch, examine all commits
range="$local_sha"
else
# Update to existing branch, examine new commits
range="$remote_sha..$local_sha"
fi
# Check for WIP commit
commit=`git rev-list -n 1 --grep '^WIP' "$range"`
if [ -n "$commit" ]
then
echo >&2 "Found WIP commit in $local_ref, not pushing"
exit 1
fi
fi
done
exit 0

@ -0,0 +1,169 @@
#!/bin/sh
#
# Copyright (c) 2006, 2008 Junio C Hamano
#
# The "pre-rebase" hook is run just before "git rebase" starts doing
# its job, and can prevent the command from running by exiting with
# non-zero status.
#
# The hook is called with the following parameters:
#
# $1 -- the upstream the series was forked from.
# $2 -- the branch being rebased (or empty when rebasing the current branch).
#
# This sample shows how to prevent topic branches that are already
# merged to 'next' branch from getting rebased, because allowing it
# would result in rebasing already published history.
publish=next
basebranch="$1"
if test "$#" = 2
then
topic="refs/heads/$2"
else
topic=`git symbolic-ref HEAD` ||
exit 0 ;# we do not interrupt rebasing detached HEAD
fi
case "$topic" in
refs/heads/??/*)
;;
*)
exit 0 ;# we do not interrupt others.
;;
esac
# Now we are dealing with a topic branch being rebased
# on top of master. Is it OK to rebase it?
# Does the topic really exist?
git show-ref -q "$topic" || {
echo >&2 "No such branch $topic"
exit 1
}
# Is topic fully merged to master?
not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
if test -z "$not_in_master"
then
echo >&2 "$topic is fully merged to master; better remove it."
exit 1 ;# we could allow it, but there is no point.
fi
# Is topic ever merged to next? If so you should not be rebasing it.
only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
only_next_2=`git rev-list ^master ${publish} | sort`
if test "$only_next_1" = "$only_next_2"
then
not_in_topic=`git rev-list "^$topic" master`
if test -z "$not_in_topic"
then
echo >&2 "$topic is already up-to-date with master"
exit 1 ;# we could allow it, but there is no point.
else
exit 0
fi
else
not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
/usr/bin/perl -e '
my $topic = $ARGV[0];
my $msg = "* $topic has commits already merged to public branch:\n";
my (%not_in_next) = map {
/^([0-9a-f]+) /;
($1 => 1);
} split(/\n/, $ARGV[1]);
for my $elem (map {
/^([0-9a-f]+) (.*)$/;
[$1 => $2];
} split(/\n/, $ARGV[2])) {
if (!exists $not_in_next{$elem->[0]}) {
if ($msg) {
print STDERR $msg;
undef $msg;
}
print STDERR " $elem->[1]\n";
}
}
' "$topic" "$not_in_next" "$not_in_master"
exit 1
fi
<<\DOC_END
This sample hook safeguards topic branches that have been
published from being rewound.
The workflow assumed here is:
* Once a topic branch forks from "master", "master" is never
merged into it again (either directly or indirectly).
* Once a topic branch is fully cooked and merged into "master",
it is deleted. If you need to build on top of it to correct
earlier mistakes, a new topic branch is created by forking at
the tip of the "master". This is not strictly necessary, but
it makes it easier to keep your history simple.
* Whenever you need to test or publish your changes to topic
branches, merge them into "next" branch.
The script, being an example, hardcodes the publish branch name
to be "next", but it is trivial to make it configurable via
$GIT_DIR/config mechanism.
With this workflow, you would want to know:
(1) ... if a topic branch has ever been merged to "next". Young
topic branches can have stupid mistakes you would rather
clean up before publishing, and things that have not been
merged into other branches can be easily rebased without
affecting other people. But once it is published, you would
not want to rewind it.
(2) ... if a topic branch has been fully merged to "master".
Then you can delete it. More importantly, you should not
build on top of it -- other people may already want to
change things related to the topic as patches against your
"master", so if you need further changes, it is better to
fork the topic (perhaps with the same name) afresh from the
tip of "master".
Let's look at this example:
o---o---o---o---o---o---o---o---o---o "next"
/ / / /
/ a---a---b A / /
/ / / /
/ / c---c---c---c B /
/ / / \ /
/ / / b---b C \ /
/ / / / \ /
---o---o---o---o---o---o---o---o---o---o---o "master"
A, B and C are topic branches.
* A has one fix since it was merged up to "next".
* B has finished. It has been fully merged up to "master" and "next",
and is ready to be deleted.
* C has not merged to "next" at all.
We would want to allow C to be rebased, refuse A, and encourage
B to be deleted.
To compute (1):
git rev-list ^master ^topic next
git rev-list ^master next
if these match, topic has not merged in next at all.
To compute (2):
git rev-list master..topic
if this is empty, it is fully merged to "master".
DOC_END

@ -0,0 +1,36 @@
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by "git commit" with the name of the file that has the
# commit message, followed by the description of the commit
# message's source. The hook's purpose is to edit the commit
# message file. If the hook fails with a non-zero status,
# the commit is aborted.
#
# To enable this hook, rename this file to "prepare-commit-msg".
# This hook includes three examples. The first comments out the
# "Conflicts:" part of a merge commit.
#
# The second includes the output of "git diff --name-status -r"
# into the message, just before the "git status" output. It is
# commented because it doesn't cope with --amend or with squashed
# commits.
#
# The third example adds a Signed-off-by line to the message, that can
# still be edited. This is rarely a good idea.
case "$2,$3" in
merge,)
/usr/bin/perl -i.bak -ne 's/^/# /, s/^# #/#/ if /^Conflicts/ .. /#/; print' "$1" ;;
# ,|template,)
# /usr/bin/perl -i.bak -pe '
# print "\n" . `git diff --cached --name-status -r`
# if /^#/ && $first++ == 0' "$1" ;;
*) ;;
esac
# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"

@ -0,0 +1,128 @@
#!/bin/sh
#
# An example hook script to block unannotated tags from entering.
# Called by "git receive-pack" with arguments: refname sha1-old sha1-new
#
# To enable this hook, rename this file to "update".
#
# Config
# ------
# hooks.allowunannotated
# This boolean sets whether unannotated tags will be allowed into the
# repository. By default they won't be.
# hooks.allowdeletetag
# This boolean sets whether deleting tags will be allowed in the
# repository. By default they won't be.
# hooks.allowmodifytag
# This boolean sets whether a tag may be modified after creation. By default
# it won't be.
# hooks.allowdeletebranch
# This boolean sets whether deleting branches will be allowed in the
# repository. By default they won't be.
# hooks.denycreatebranch
# This boolean sets whether remotely creating branches will be denied
# in the repository. By default this is allowed.
#
# --- Command line
refname="$1"
oldrev="$2"
newrev="$3"
# --- Safety check
if [ -z "$GIT_DIR" ]; then
echo "Don't run this script from the command line." >&2
echo " (if you want, you could supply GIT_DIR then run" >&2
echo " $0 <ref> <oldrev> <newrev>)" >&2
exit 1
fi
if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
echo "usage: $0 <ref> <oldrev> <newrev>" >&2
exit 1
fi
# --- Config
allowunannotated=$(git config --bool hooks.allowunannotated)
allowdeletebranch=$(git config --bool hooks.allowdeletebranch)
denycreatebranch=$(git config --bool hooks.denycreatebranch)
allowdeletetag=$(git config --bool hooks.allowdeletetag)
allowmodifytag=$(git config --bool hooks.allowmodifytag)
# check for no description
projectdesc=$(sed -e '1q' "$GIT_DIR/description")
case "$projectdesc" in
"Unnamed repository"* | "")
echo "*** Project description file hasn't been set" >&2
exit 1
;;
esac
# --- Check types
# if $newrev is 0000...0000, it's a commit to delete a ref.
zero="0000000000000000000000000000000000000000"
if [ "$newrev" = "$zero" ]; then
newrev_type=delete
else
newrev_type=$(git cat-file -t $newrev)
fi
case "$refname","$newrev_type" in
refs/tags/*,commit)
# un-annotated tag
short_refname=${refname##refs/tags/}
if [ "$allowunannotated" != "true" ]; then
echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2
echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2
exit 1
fi
;;
refs/tags/*,delete)
# delete tag
if [ "$allowdeletetag" != "true" ]; then
echo "*** Deleting a tag is not allowed in this repository" >&2
exit 1
fi
;;
refs/tags/*,tag)
# annotated tag
if [ "$allowmodifytag" != "true" ] && git rev-parse $refname > /dev/null 2>&1
then
echo "*** Tag '$refname' already exists." >&2
echo "*** Modifying a tag is not allowed in this repository." >&2
exit 1
fi
;;
refs/heads/*,commit)
# branch
if [ "$oldrev" = "$zero" -a "$denycreatebranch" = "true" ]; then
echo "*** Creating a branch is not allowed in this repository" >&2
exit 1
fi
;;
refs/heads/*,delete)
# delete branch
if [ "$allowdeletebranch" != "true" ]; then
echo "*** Deleting a branch is not allowed in this repository" >&2
exit 1
fi
;;
refs/remotes/*,commit)
# tracking branch
;;
refs/remotes/*,delete)
# delete tracking branch
if [ "$allowdeletebranch" != "true" ]; then
echo "*** Deleting a tracking branch is not allowed in this repository" >&2
exit 1
fi
;;
*)
# Anything else (is there anything else?)
echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2
exit 1
;;
esac
# --- Finished
exit 0

Binary file not shown.

@ -0,0 +1,6 @@
# git ls-files --others --exclude-from=.git/info/exclude
# Lines that start with '#' are comments.
# For a project mostly in C, the following would be a good set of
# exclude patterns (uncomment them if you want to use them):
# *.[oa]
# *~

@ -0,0 +1 @@
0000000000000000000000000000000000000000 7748120681752fd4b669eae0cab0f2b7e14b0d74 Özcan Oğuz <ozcan@napiyoruz.org> 1529795165 +0300 clone: from https://github.com/comfusion/after-dark.git

@ -0,0 +1 @@
0000000000000000000000000000000000000000 7748120681752fd4b669eae0cab0f2b7e14b0d74 Özcan Oğuz <ozcan@napiyoruz.org> 1529795165 +0300 clone: from https://github.com/comfusion/after-dark.git

@ -0,0 +1 @@
0000000000000000000000000000000000000000 7748120681752fd4b669eae0cab0f2b7e14b0d74 Özcan Oğuz <ozcan@napiyoruz.org> 1529795165 +0300 clone: from https://github.com/comfusion/after-dark.git

@ -0,0 +1,88 @@
# pack-refs with: peeled fully-peeled
ec272a67a502a1fd8624db1e11fd36d69c75f9df refs/remotes/origin/gh-pages
7748120681752fd4b669eae0cab0f2b7e14b0d74 refs/remotes/origin/master
9c8a41ddbc6c43fcc173dd0d11e86c9b164b5ba6 refs/tags/v1.0.0
^9c1a4153aaf9b4ad1e4c814a41ea6bcf26c87800
6747007b1358bfb02900d2296f1ad102fbbe57c0 refs/tags/v1.1.0
^1eec663085eff5a17819bbab28b47010d9f0647e
21d797d9cdab74585ca21094629b1c142f0060cb refs/tags/v1.2.0
^6d4d32c241cd376b5515c646190d6b5bce048152
379c0e97e0f529d383fb08434119315fd858d8ab refs/tags/v1.3.0
^b5603bb3cadd187043f8effd6759ae784a98d3bd
729e49326e1f9a92cd088c59646e77214c80acca refs/tags/v1.3.1
^2b5a4c81236dbf8d27f8ab2ccc3aa896c73ba694
cae4b291118ce288271c290b13b27aeebbb0b03c refs/tags/v1.3.2
^e6dac3f2155d37ce5222d10fdae0fe4ead58fb3c
b4837f991e0ec642f10698fda38252a318cd6c90 refs/tags/v1.4.0
^3d3d5fa8ad17d82a949ec58fef7620e5c12df587
5f8656edf73ed7d780f658070e50aa951593ccb6 refs/tags/v1.5.0
^e9346c33eb9e5ad290eda46a867fb04b6ef318c8
51e3bdc93bc1e546aebf1e6e6e802997ab98e213 refs/tags/v1.5.1
^002ff76d431a6b7dfdaa7b7f03e123c26842f80d
13dbdbc6230372d2f33791bd50ee5cec481a7e02 refs/tags/v1.5.2
^43e28c69e36d0a855a2622874b12d929cbfad25d
204c397d5c0b2f770e09534682d9b8a98ecb8b6d refs/tags/v1.6.0
^2cfc646377923e0998d877cb8780ba292940524d
3d008fd9d7d969a493cc8440310fba78c7512627 refs/tags/v1.6.1
^a1ecb78b01bd6fa1107621759c7dd513d58dad3b
88e026788bb7c7ff702e45fd6d6edaa566c5ed60 refs/tags/v1.7.0
^608db18d10d1e32fc984cbc3c23c85519c658870
0a3f0af72b2cc13a90eed7aa2123345560b5081c refs/tags/v1.7.1
^ce91fa707d52e2a0685cf6e8018cfe2a4ef76e90
01ff55ebe33283f16078f8d7c41fd7b403b68398 refs/tags/v1.7.2
^84ceed8d785454b5ff83f4fa8239a75f480fbff8
e530257bceac7c3a7eb753d8c9bcb925f48e3e14 refs/tags/v1.7.6
^cd4889abd9858898787dc394d579173388b71858
1ca0488d01f9c1bda0b395853541d2b6c7ab7378 refs/tags/v1.8.0
^97351ccb1dc7266e9f858f3d164ca14fddabf4e0
a8adba5b1b952d0470e088766c0ae54820d04d7f refs/tags/v1.8.1
^00ece20a71460eb2242354cbb1a1c000bc5e69b0
ad244e71260bd92b988243a130a88b734f323557 refs/tags/v1.8.2
^5dced2eaa28b2aa08956ad462a9660646f128fe8
c25a49d0442d53f671e3f9f18114c0d16f69b2a8 refs/tags/v1.8.3
^3489f98258d7dd4caf58f54fe5d1062bd8f644e8
2fbd542b1de147b58129e029b84052e6366d0014 refs/tags/v1.8.4
^44d175c8788407966fd68146d5f003b8913c8bdd
b30dae2c07535ae804ba211215d7b347cb93c959 refs/tags/v2.0.0
fd245ac925bf1dea39fd22b83ad304981918b6fb refs/tags/v2.1.0
^59e88784ed977ab9e54d6d8963df5ce3038a072b
a630d387921dda659f77c0043c354a228180ea1d refs/tags/v2.1.1
^874dbd3df7b852af31f18f9ff1cf1cf29b8deada
7529f784f6bbf597abbf20ea92192c316c3adad6 refs/tags/v3.0.0
^d98bff5b1d25c3132627667e728dddab7f9b135d
23c99b867baac93956a0ba3cc4e2e9528a1ec128 refs/tags/v3.1.0
^fa0c96855fddd51b4ae974a22792e68ad1348191
7f7b7d79849acd11ff1dc18534cd6c513724b0c8 refs/tags/v3.1.1
^87ca482aad5b88e924e1b07b16319c1b0b3404cd
dda1f05eb0079ca79d15bc248f3e83b40d548dbd refs/tags/v3.10.0
^5b87e2aea64bfacbead22e2ee3135d8a1c3fff6a
0b79bc25e4116808874a4eacbd2bf848aa5b7c1c refs/tags/v3.2.0
^fa31d99e2bd06d73678dec810afdd6431b924944
7a4dccff61f1172c36f5538c08b81da0cb3991d4 refs/tags/v3.3.0
^e3faf61ea6f3944116d5e48504345485a3df46b2
51ec5b7514615d8eb1945ca84a4710cd8eeb2048 refs/tags/v3.4.0
^31f9f32c9b21ede969db3e298e1cabbe8c7a35d0
6ebbfc85a2923f624f5b32176cf279e41642e70a refs/tags/v3.5.0
^8565075c2fbc4965d6c2fbf48452de15041f98c2
61e674130eda16ff300606177d19eec1ce0a7341 refs/tags/v3.5.1
^a50bffa4ebdf0e858be10538031a7729f1285096
20530be5661ab77835b59763243dbf72fbc12d0a refs/tags/v3.6.0
^6ce006347df4616279b6bb270a679b954d88dab7
165d39f372dd57c34e6621801796c40368ef5ba2 refs/tags/v3.7.0
^ebe66aa2e8cac6facd38e95d98bfda61f288bec9
91859b7f0c5d5a807e379785b275f27337389458 refs/tags/v3.8.0
^45b52342603bd2e3a3e4a593a3b245e29eabd163
853f5bb52180d87b0252181bb74b918f546954ab refs/tags/v3.8.1
^e4f934be38f23ff1e6276fcf1d8a4c20b23ecabc
e5d75a80cbb4b80daf83775e8a7213ee7cf8f5a8 refs/tags/v3.8.2
^a16eaf25fa4f2f71b9ebf50a4b0f9d94308bf2e4
47f5641c15adfd40d25414b0e7cda2b1076d4ac0 refs/tags/v3.8.3
^ae16f9b6c04253d85ed0ea20652e60e8a4d8f35e
5731cdfc8addf81d29847299711fbecc0a85c5ab refs/tags/v3.8.4
^7b4ddbf697db366c53fb3279aefa8bf36daad991
70702177d8844ae127b92b61bda3b760f7830d5f refs/tags/v3.9.0
^cf95248dffb19ff5f331fdbd298012da9af6b959
8ed9d7a89286e806a985150fdca343369eb49c3e refs/tags/v3.9.1
^4dd99f4ed03f3db22266201c1df2d471137d1b95
8a22859919ebfde549e2491669e83bb67e16400a refs/tags/v3.9.2
^de290dc8b7c926148a0d5525b5a020d37a014d78

@ -0,0 +1 @@
7748120681752fd4b669eae0cab0f2b7e14b0d74

@ -0,0 +1 @@
ref: refs/remotes/origin/master

@ -0,0 +1,517 @@
# Change Log
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
<a name="3.10.0"></a>
# [3.10.0](https://github.com/comfusion/after-dark/compare/v3.9.1...v3.10.0) (2018-06-18)
### Bug Fixes
* **$layouts:** resolve search layout header display ([9eee69c](https://github.com/comfusion/after-dark/commit/9eee69c)), closes [#104](https://github.com/comfusion/after-dark/issues/104)
### Features
* **$layout:** add telegram iv support ([4d520f9](https://github.com/comfusion/after-dark/commit/4d520f9)), closes [#113](https://github.com/comfusion/after-dark/issues/113)
<a name="3.9.2"></a>
## [3.9.2](https://github.com/comfusion/after-dark/compare/v3.9.1...v3.9.2) (2018-06-09)
### Bug Fixes
* **$layouts:** resolve search layout header display ([9eee69c](https://github.com/comfusion/after-dark/commit/9eee69c)), closes [#104](https://github.com/comfusion/after-dark/issues/104)
<a name="3.9.1"></a>
## [3.9.1](https://github.com/comfusion/after-dark/compare/v3.9.0...v3.9.1) (2018-05-13)
### Bug Fixes
* **$layouts:** hide search app when noscript ([c3bcff0](https://github.com/comfusion/after-dark/commit/c3bcff0))
<a name="3.9.0"></a>
# [3.9.0](https://github.com/comfusion/after-dark/compare/v3.8.4...v3.9.0) (2018-05-03)
### Features
* **$layouts:** allow customization of referrer policy and add privacy-focused default ([5759a30](https://github.com/comfusion/after-dark/commit/5759a30)), closes [#96](https://github.com/comfusion/after-dark/issues/96)
<a name="3.8.4"></a>
## [3.8.4](https://github.com/comfusion/after-dark/compare/v3.8.3...v3.8.4) (2018-05-01)
### Bug Fixes
* **$layouts:** prevent js error on search form submit ([0dce741](https://github.com/comfusion/after-dark/commit/0dce741)), closes [#94](https://github.com/comfusion/after-dark/issues/94)
<a name="3.8.3"></a>
## [3.8.3](https://github.com/comfusion/after-dark/compare/v3.8.2...v3.8.3) (2018-04-16)
### Bug Fixes
* **$layouts:** improve search input focus and usability ([e94f6df](https://github.com/comfusion/after-dark/commit/e94f6df)), closes [#91](https://github.com/comfusion/after-dark/issues/91)
<a name="3.8.2"></a>
## [3.8.2](https://github.com/comfusion/after-dark/compare/v3.8.1...v3.8.2) (2018-04-16)
### Bug Fixes
* **$layouts:** disable ua input styling safari mobile ([f7c81f4](https://github.com/comfusion/after-dark/commit/f7c81f4))
* **$layouts:** prevent auto-zoom on safari mobile ([81c3f39](https://github.com/comfusion/after-dark/commit/81c3f39))
<a name="3.8.1"></a>
## [3.8.1](https://github.com/comfusion/after-dark/compare/v3.8.0...v3.8.1) (2018-04-15)
### Bug Fixes
* **$layouts:** remove duplicate descriptor from post image srcset ([0295370](https://github.com/comfusion/after-dark/commit/0295370))
<a name="3.8.0"></a>
# [3.8.0](https://github.com/comfusion/after-dark/compare/v3.7.0...v3.8.0) (2018-04-15)
### Features
* **$layouts:** add fuzzy search ([93d2a29](https://github.com/comfusion/after-dark/commit/93d2a29)), closes [#83](https://github.com/comfusion/after-dark/issues/83)
<a name="3.7.0"></a>
# [3.7.0](https://github.com/comfusion/after-dark/compare/v3.6.0...v3.7.0) (2018-03-25)
### Features
* **$layouts:** add post images ([06457bc](https://github.com/comfusion/after-dark/commit/06457bc))
<a name="3.6.0"></a>
# [3.6.0](https://github.com/comfusion/after-dark/compare/v3.5.1...v3.6.0) (2018-03-22)
### Bug Fixes
* **$style:** add more whitespace on list pages and darken muted text ([646e98b](https://github.com/comfusion/after-dark/commit/646e98b))
### Features
* **$layouts:** add twitter cards ([6562e80](https://github.com/comfusion/after-dark/commit/6562e80)), closes [#76](https://github.com/comfusion/after-dark/issues/76)
<a name="3.5.1"></a>
## [3.5.1](https://github.com/comfusion/after-dark/compare/v3.5.0...v3.5.1) (2018-01-17)
### Bug Fixes
* **$style:** fix a whitespace issue near the readmore link ([dee3530](https://github.com/comfusion/after-dark/commit/dee3530)), closes [#70](https://github.com/comfusion/after-dark/issues/70)
<a name="3.5.0"></a>
# [3.5.0](https://github.com/comfusion/after-dark/compare/v3.4.0...v3.5.0) (2017-11-08)
### Features
* **$shortcodes:** add youtube without cookies ([613e545](https://github.com/comfusion/after-dark/commit/613e545)), closes [#62](https://github.com/comfusion/after-dark/issues/62)
<a name="3.4.0"></a>
# [3.4.0](https://github.com/comfusion/after-dark/compare/v3.3.0...v3.4.0) (2017-10-27)
### Features
* **$shortcode:** add coub shortcode for gifs with sound ([0267d5b](https://github.com/comfusion/after-dark/commit/0267d5b)), closes [#63](https://github.com/comfusion/after-dark/issues/63)
<a name="3.3.0"></a>
# [3.3.0](https://github.com/comfusion/after-dark/compare/v3.2.0...v3.3.0) (2017-10-13)
### Features
* **$layouts:** hide related content reading time on small screen ([480d57a](https://github.com/comfusion/after-dark/commit/480d57a))
* **$partials:** add pubdate structured data to post byline ([a3bcb0c](https://github.com/comfusion/after-dark/commit/a3bcb0c))
<a name="3.2.0"></a>
# [3.2.0](https://github.com/comfusion/after-dark/compare/v3.1.1...v3.2.0) (2017-10-06)
### Bug Fixes
* **$shortcodes:** fix issue with external link appearance ([afcc8e6](https://github.com/comfusion/after-dark/commit/afcc8e6))
### Features
* **$layout:** add base element to base layout ([bf25c67](https://github.com/comfusion/after-dark/commit/bf25c67)), closes [#60](https://github.com/comfusion/after-dark/issues/60)
* **$shortcode:** style cite element inside block quotation ([65a4278](https://github.com/comfusion/after-dark/commit/65a4278))
* **$shortcodes:** add frame targeting to custom figure shortcode ([a66b076](https://github.com/comfusion/after-dark/commit/a66b076))
* **$shortcodes:** enable target and method control for button/buttongroup ([f705d19](https://github.com/comfusion/after-dark/commit/f705d19)), closes [#56](https://github.com/comfusion/after-dark/issues/56)
* **$shortcodes:** make button shortcode clickable ([1bc643f](https://github.com/comfusion/after-dark/commit/1bc643f)), closes [#40](https://github.com/comfusion/after-dark/issues/40)
### Reverts
* **$layout:** add base element to base layout ([769e2d9](https://github.com/comfusion/after-dark/commit/769e2d9))
<a name="3.1.1"></a>
## [3.1.1](https://github.com/comfusion/after-dark/compare/v3.1.0...v3.1.1) (2017-09-13)
### Bug Fixes
* **$layouts:** fix error calling partial in related content ([8a6253d](https://github.com/comfusion/after-dark/commit/8a6253d)), closes [#55](https://github.com/comfusion/after-dark/issues/55)
<a name="3.1.0"></a>
# [3.1.0](https://github.com/comfusion/after-dark/compare/v3.0.0...v3.1.0) (2017-09-13)
### Features
* **$layouts:** use related content feature introduced in hugo@0.27 ([f0474f4](https://github.com/comfusion/after-dark/commit/f0474f4)), closes [#54](https://github.com/comfusion/after-dark/issues/54)
<a name="3.0.0"></a>
# [3.0.0](https://github.com/comfusion/after-dark/compare/v2.1.1...v3.0.0) (2017-09-13)
### Features
* **$archetypes:** turn archetypes into go templates ([5ed2d9f](https://github.com/comfusion/after-dark/commit/5ed2d9f))
### BREAKING CHANGES
* **$archetypes:** Minimum Hugo version set 0.24, 0.16 - 0.23 must modify archetypes
to upgrade add `date` and `title` to custom archetypes. if using a version of hugo prior to 0.24 the custom templates should remove `title` and `date` and not use go templating logic in the archetype files
<a name="2.1.1"></a>
## [2.1.1](https://github.com/comfusion/after-dark/compare/v2.1.0...v2.1.1) (2017-09-11)
### Bug Fixes
* **$layouts:** move stylesheets back to partials, reorganize files ([b93b4a7](https://github.com/comfusion/after-dark/commit/b93b4a7)), closes [#50](https://github.com/comfusion/after-dark/issues/50)
<a name="2.1.0"></a>
# [2.1.0](https://github.com/comfusion/after-dark/compare/v2.0.0...v2.1.0) (2017-09-09)
### Bug Fixes
* **$images:** improve bpg image support ([7681dde](https://github.com/comfusion/after-dark/commit/7681dde)), closes [#48](https://github.com/comfusion/after-dark/issues/48)
### Features
* **$layout:** Add support for external stylesheets ([9abe627](https://github.com/comfusion/after-dark/commit/9abe627)), closes [#49](https://github.com/comfusion/after-dark/issues/49)
<a name="2.0.0"></a>
# [2.0.0](https://github.com/comfusion/after-dark/compare/v1.8.4...v2.0.0) (2017-09-08)
### Features
* **$theme:** add support for bpg image format ([49204d0](https://github.com/comfusion/after-dark/commit/49204d0))
### BREAKING CHANGES
* **$build:** inline css using readFile template function ([3787d10](https://github.com/comfusion/after-dark/commit/3787d10))
to upgrade skip this release and move directly to 2.1.1 or a later release
<a name="1.8.4"></a>
## [1.8.4](https://github.com/comfusion/after-dark/compare/v1.8.3...v1.8.4) (2017-06-27)
### Bug Fixes
* **$layouts:** add support for protocol-relative base urls ([755f446](https://github.com/comfusion/after-dark/commit/755f446)), closes [#37](https://github.com/comfusion/after-dark/issues/37)
<a name="1.8.3"></a>
## [1.8.3](https://github.com/comfusion/after-dark/compare/v1.8.2...v1.8.3) (2017-06-22)
### Bug Fixes
* **$layouts:** remove iframe borders by default ([3b4f7c1](https://github.com/comfusion/after-dark/commit/3b4f7c1))
<a name="1.8.2"></a>
## [1.8.2](https://github.com/comfusion/after-dark/compare/v1.8.1...v1.8.2) (2017-06-09)
### Reverts
* **layouts:** update powered-by to link to new theme site ([2237ead](https://github.com/comfusion/after-dark/commit/2237ead))
<a name="1.8.1"></a>
## [1.8.1](https://github.com/comfusion/after-dark/compare/v1.8.0...v1.8.1) (2017-06-07)
### Bug Fixes
* **$layouts:** update powered-by to link to new theme site ([c031934](https://github.com/comfusion/after-dark/commit/c031934))
<a name="1.8.0"></a>
# [1.8.0](https://github.com/comfusion/after-dark/compare/v1.7.6...v1.8.0) (2017-06-06)
### Features
* **LICENSE:** you just do what the fuck you want to ([c2eb957](https://github.com/comfusion/after-dark/commit/c2eb957))
<a name="1.7.6"></a>
## [1.7.6](https://github.com/comfusion/after-dark/compare/v1.7.2...v1.7.6) (2017-06-06)
#### Licensing
Upgraded to The Unlicense, skipping for patch releases.
<a name="1.7.2"></a>
## [1.7.2](https://github.com/comfusion/after-dark/compare/v1.7.1...v1.7.2) (2017-05-14)
### Bug Fixes
* **install:** move it back to bin ([13441f5](https://github.com/comfusion/after-dark/commit/13441f5))
<a name="1.7.1"></a>
## [1.7.1](https://github.com/comfusion/after-dark/compare/v1.7.0...v1.7.1) (2017-05-13)
### Bug Fixes
* **install:** move to scripts folder ([204e516](https://github.com/comfusion/after-dark/commit/204e516))
<a name="1.7.0"></a>
# [1.7.0](https://github.com/comfusion/after-dark/compare/v1.6.1...v1.7.0) (2017-05-08)
### Bug Fixes
* **install:** improve install experience ([4a30955](https://github.com/comfusion/after-dark/commit/4a30955))
### Features
* **shortcodes:** add hack progress bar component ([dda60f2](https://github.com/comfusion/after-dark/commit/dda60f2))
* **shortcodes:** add hackcss alert shortcode ([6ed1c58](https://github.com/comfusion/after-dark/commit/6ed1c58))
* **shortcodes:** add hackcss alert shortcode ([eebe7a9](https://github.com/comfusion/after-dark/commit/eebe7a9))
* **shortcodes:** add hackcss button group component ([1f90e2d](https://github.com/comfusion/after-dark/commit/1f90e2d))
* **shortcodes:** add hackcss button shortcode ([829cb7d](https://github.com/comfusion/after-dark/commit/829cb7d))
* **shortcodes:** add hackcss card component ([4526c60](https://github.com/comfusion/after-dark/commit/4526c60))
* **shortcodes:** add hackcss loading component ([6f667e8](https://github.com/comfusion/after-dark/commit/6f667e8))
* **shortcodes:** add hackcss progress component ([4e99c75](https://github.com/comfusion/after-dark/commit/4e99c75))
<a name="1.6.1"></a>
## [1.6.1](https://github.com/comfusion/after-dark/compare/v1.6.0...v1.6.1) (2017-05-05)
### Bug Fixes
* **typography:** remove text justification and hyphenation ([8fdbe2f](https://github.com/comfusion/after-dark/commit/8fdbe2f))
<a name="1.6.0"></a>
# [1.6.0](https://github.com/comfusion/after-dark/compare/v1.5.2...v1.6.0) (2017-05-03)
### Bug Fixes
* **install:** add flags for theme setup script ([01ad1ee](https://github.com/comfusion/after-dark/commit/01ad1ee))
* **layouts:** use relative urls in post byline taxonomy links ([419752d](https://github.com/comfusion/after-dark/commit/419752d))
### Features
* **install:** simplify installation ([765dcb8](https://github.com/comfusion/after-dark/commit/765dcb8))
<a name="1.5.2"></a>
## [1.5.2](https://github.com/comfusion/after-dark/compare/v1.5.1...v1.5.2) (2017-04-30)
### Bug Fixes
* **typography:** only justify and hyphenate article bodies ([ed83bee](https://github.com/comfusion/after-dark/commit/ed83bee))
<a name="1.5.1"></a>
## [1.5.1](https://github.com/comfusion/after-dark/compare/v1.5.0...v1.5.1) (2017-04-20)
### Bug Fixes
* **typography:** stop justifying and hyphenating text on small viewports ([77c6033](https://github.com/comfusion/after-dark/commit/77c6033))
<a name="1.5.0"></a>
# [1.5.0](https://github.com/comfusion/after-dark/compare/v1.4.0...v1.5.0) (2017-04-16)
### Bug Fixes
* **links:** style external links in all browsers ([ccef559](https://github.com/comfusion/after-dark/commit/ccef559)), closes [#22](https://github.com/comfusion/after-dark/issues/22)
* **partials:** fix markup validation error ([c82fc66](https://github.com/comfusion/after-dark/commit/c82fc66))
### Features
* **layouts:** add support for hugo 0.20.2 ([eba70c9](https://github.com/comfusion/after-dark/commit/eba70c9)), closes [#28](https://github.com/comfusion/after-dark/issues/28)
* **typography:** justify text output and hyphenate ([4775618](https://github.com/comfusion/after-dark/commit/4775618))
### Performance Improvements
* **favicon:** add svg favicon ([b3b0008](https://github.com/comfusion/after-dark/commit/b3b0008))
* **install:** remove design resources ([6eb145d](https://github.com/comfusion/after-dark/commit/6eb145d))
### Reverts
* **docs(README:** remove erroneous markdown file): ([925ed3e](https://github.com/comfusion/after-dark/commit/925ed3e))
<a name="1.4.0"></a>
# [1.4.0](https://github.com/comfusion/after-dark/compare/v1.3.2...v1.4.0) (2017-04-10)
### Features
* **layouts:** add meta keywords to base template ([4b1f0f1](https://github.com/comfusion/after-dark/commit/4b1f0f1)), closes [#20](https://github.com/comfusion/after-dark/issues/20)
<a name="1.3.2"></a>
## [1.3.2](https://github.com/comfusion/after-dark/compare/v1.3.1...v1.3.2) (2017-04-09)
### Bug Fixes
* **layouts:** output meta description when not explicitly set ([9f11bd6](https://github.com/comfusion/after-dark/commit/9f11bd6)), closes [#21](https://github.com/comfusion/after-dark/issues/21)
<a name="1.3.1"></a>
## [1.3.1](https://github.com/comfusion/after-dark/compare/v1.3.0...v1.3.1) (2017-04-08)
### Bug Fixes
* **bundle:** add images to npm ignore file ([1694334](https://github.com/comfusion/after-dark/commit/1694334))
<a name="1.3.0"></a>
# [1.3.0](https://github.com/comfusion/after-dark/compare/v1.2.0...v1.3.0) (2017-04-08)
### Bug Fixes
* **bundle:** remove images folder from npm release ([b277a20](https://github.com/comfusion/after-dark/commit/b277a20))
### Features
* **powered-by:** add page generation date ([c0c421a](https://github.com/comfusion/after-dark/commit/c0c421a))
### Reverts
* **powered-by:** remove page generation date ([478ba0b](https://github.com/comfusion/after-dark/commit/478ba0b))
<a name="1.2.0"></a>
# [1.2.0](https://github.com/comfusion/after-dark/compare/v1.1.0...v1.2.0) (2017-03-30)
### Features
* **highlighting:** add syntax highlighting ([455062f](https://github.com/comfusion/after-dark/commit/455062f))
* **shortcodes:** add figure shortcode ([8a0317f](https://github.com/comfusion/after-dark/commit/8a0317f))
<a name="1.1.0"></a>
# [1.1.0](https://github.com/comfusion/after-dark/compare/v1.0.0...v1.1.0) (2017-03-30)
### Features
* **shortcodes:** add blockquote shortcode ([ea293e3](https://github.com/comfusion/after-dark/commit/ea293e3))
<a name="1.0.0"></a>
# 1.0.0 (2017-03-30)
### Bug Fixes
* 404 page theme color url ref ([79d2377](https://github.com/comfusion/after-dark/commit/79d2377))
* add add theme color to 404 page ([4f5ec87](https://github.com/comfusion/after-dark/commit/4f5ec87))

@ -0,0 +1,13 @@
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004
Copyright 2016-2018 Josh Habdas <jhabdas@protonmail.com> (https://habd.as)
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. You just DO WHAT THE FUCK YOU WANT TO.

@ -0,0 +1,706 @@
<h1 align="center">After Dark</h1>
<p align="center">
<strong>A retro dark theme for <a target="intro" href="https://gohugo.io/">Hugo</a>.</strong>
</p>
<p align="center">
<img src="images/minimal-mac.png" title="After Dark running on a MacBook and iPhone" alt="After Dark theme screenshots">
</p>
<p align="center">
<a href="https://www.npmjs.com/package/after-dark"><img src="https://img.shields.io/npm/dm/after-dark.svg?style=flat-square" alt="NPM downloads per month"></a>
<a href="https://www.npmjs.com/package/after-dark"><img src="https://img.shields.io/npm/v/after-dark.svg?style=flat-square" alt="Latest NPM version"></a>
<a href="https://github.com/comfusion/after-dark/blob/master/COPYING"><img src="https://img.shields.io/github/license/comfusion/after-dark.svg?style=flat-square" alt="Project license"></a>
</p>
## Features
<details>
<summary style="margin-bottom:1em">
View the full list of features
</summary>
<table>
<thead>
<tr>
<th>Feature</th>
<th>Summary</th>
</tr>
</thead>
<tbody>
<tr>
<td>Deceptive Simplicity</td>
<td>After Dark is a <a target="feature" href="http://themes.gohugo.io/">Hugo theme</a>, making it a suitable starting point for <b>novice and advanced developers</b> alike. It advances using the "Code for today, not for tomorrow" philosophy of <abbr title="eXtreme Programming">XP</abbr> and includes only what's necessary to create and run your site &ndash; nothing more.</td>
</tr>
<tr>
<td>Semantic Versioning</td>
<td>Predictable changes enable theme users stay up-to-date with what's happening. After Dark uses <a target="feature" href="http://semver.org/">Semantic Versioning</a> and maintains a <a target="feature" href="https://github.com/comfusion/after-dark/blob/master/CHANGELOG.md">CHANGELOG</a> for easy consumption.</td>
</tr>
<tr>
<td>Inclusive Design</td>
<td>Optimized for mobile, tablet, desktop and <kbd>terminal</kbd> browsers.</td>
</tr>
<tr>
<td>Performance Optimized</td>
<td>Page content, favicon and styles <b>load in a single request</b> on all pages. Resources loaded asynchronously whenver possible. Responsive images with LQIP out of the box. Users should see a <b>~1 second page loads over 2G</b> when hosted using a <abbr title="Content Delivery Network">CDN</abbr>.</td>
</tr>
<tr>
<td>Designed to Scale</td>
<td>After Dark is capable of generating <b>~1000 pages per second</b> thanks to <a target="feature" href="https://gohugo.io/">Hugo</a> and is likely to become faster over time.</td>
</tr>
<tr>
<td><a href="#lazy-loading">Lazy Loading</a></td>
<td>Lazily load your images, iFrames and script embeds. After Dark uses the <a title="feature" href="https://github.com/aFarkas/lazysizes">lazysizes</a> library, a zero-configuration JavaScript library with support for <abbr title="Low Quality Image Placeholders">LQIP</abbr> and responsive images.</td>
</tr>
<tr>
<td><a href="#bpg-image-support">BPG Image Support</a></td>
<td>After Dark supports the <a href="https://bellard.org/bpg/">BPG Image format</a>. Native browser support for BPG is dismal. As a result, a polyfill has been provided to render BPG images.</td>
</tr>
<tr>
<td><a href="#social-engagement">Social Engagement</a></td>
<td>After Dark provides automatic and configurable <a target="feature" href="http://ogp.me/">Open Graph</a> support, Twitter Cards and Telegram Instant View making social shares pop like 37 pieces of flair.</td>
</tr>
<tr>
<td><a href="#search-optimization">Search Optimization</a></td>
<td>Using <a target="feature" href="https://moz.com/learn/seo/schema-structured-data">Schema Structured Data</a> and meta tags, After Dark gives crawlers rich data about the site structure and content. No configuration required.</td>
</tr>
<tr>
<td><a href="#post-images">Post Images</a></td>
<td>Increase the visual appeal of your posts by providing a captivating image above your content. After Dark enables configuration-driven post images which are lazy-loaded, responsive and automatically cropped for a consistent look-and-feel across your site.</td>
</tr>
<tr>
<td><a href="#fuzzy-search">Fuzzy Search</a></td>
<td>After Dark ships with an in-browser search app built with <a target="features" href="https://vuejs.org/">Vue</a>, <a target="features" href="http://fusejs.io/">Fuse</a> and <a target="features" href="https://markjs.io">Mark</a>. Use it to quickly find content anywhere your site.</td>
</tr>
<tr>
<td><a href="#personalization">Personalization</a></td>
<td>Adjust CSS using purpose-built <a href="#custom-styles">customization file</a>. Choose one of several <a href="#theme-variants">theme variants</a>. Swap in <a href="#favicon">your own favicon</a>. Leverage <a target="features" href="https://gohugo.io/templates/blocks">block templates</a> to quickly extend new custom layouts. And use <a target="features" href="https://hackcss.egoist.moe/dark.html">hack.css</a> flexbox grids and CSS components to add style your site.</td>
</tr>
<tr>
<td><a href="#section-menu">Section Menu</a></td>
<td>Add and customize your site's global navigation. After Dark uses Hugo's <a target="feature" href="https://gohugo.io/extras/menus#section-menu-for-the-lazy-blogger">Section Menu for "the Lazy Blogger"</a>, making navigation easy to create and predictable to use. Don't want navigation? Simply disable it from your site configuration.</td>
</tr>
<tr>
<td><a href="#content-reuse">Content Reuse</a></td>
<td>Sometimes plan markdown isn't enough to build engaging page content. For this reason After Dark provides a number of reusable code snippets and shortcodes for adding things blockquotes, figure elements, coubs, videos, <a target="feature" href="https://hackcss.egoist.moe/">hackcss components</a> and more to your pages and posts. Use them to create completely custom layouts or simply spice up an old page.</td>
</tr>
<tr>
<td><a href="#related-content">Related Content</a></td>
<td>Promote more of your content to your site visitors. By offering your readers more content that's relevant to them you can <b>increase your site's page views</b>, the time spent on your site and reader loyalty.</td>
</tr>
<tr>
<td><a href="#table-of-contents">Table Of Contents</a></td>
<td>Help users locate and share information on your site. By providing a <abbr title="Table Of Contents">TOC</abbr>, users will spend less time scrolling to locate information in larger documents and are more likely to <i>deep link</i> to specific information on a page.</td>
</tr>
<tr>
<td>Analytics</td>
<td>Understand and action on user behavior by enabling Google Analytics. After Dark uses the <a target="feature" href="https://developers.google.com/analytics/devguides/collection/analyticsjs/">async tracking snippet</a> to boost performance and allow script preloading.</td>
</tr>
<tr>
<td>User Generated Content</td>
<td>Improve search rankings and provide interactivity to users with <abbr title="User Generated Content">UGC</abbr>. Enable <a target="feature" href="https://disqus.com/">Disqus</a> commenting to get started.</td>
</tr>
<tr>
<td>Reading Time</td>
<td>Set user expectations up-front. After Dark provides <b>estimated reading time</b> for each post near the top of the page. This feature is automatic and assumes a reading speed of 200-250 words per minute.</td>
</tr>
<tr>
<td><a href="#modification-dating">Modification Dating</a></td>
<td>Surface recently updated content to users and crawlers, allowing them to understand when a post or page was was last modified. Recently updated posts will be flagged as modified and visually lifted upwards in chronological listings.</td>
</tr>
<tr>
<td><a href="#syntax-highlighting">Custom Syntax Highlighting</a></td>
<td>Share code snippets with style. After Dark provides <b>custom syntax highlighting</b> with support for both Pygments and Chroma.</td>
</tr>
<tr>
<td>Taxonomy Pages</td>
<td>Help users discover taxonomic content. After Dark automatically generates <b>taxonomy and taxonomy terms pages</b> and links to them in post bylines.</td>
</tr>
<tr>
<td>Post Bylines</td>
<td>Rich post bylines include optional author name, word count, links to taxonomy pages and metadata for search engines.</td>
</tr>
<tr>
<td>Pagination</td>
<td>Pagination can be hard. After Dark makes it easy with simple list pagination with page indication.</td>
</tr>
<tr>
<td>Animated Error Page</td>
<td>Decrease bounce rate when URL errors occur. After Dark provides an <a target="feature" href="https://hackcabin.com/post/after-dark-error-page-redesign/">engaging 404 page</a> with animated background.</td>
</tr>
<tr>
<td>Accessibility</td>
<td>After Dark uses semantic HTML5 markup to provide a better experience for aural readers and facilitates <b>navigation via keyboard</b> only.</td>
</tr>
</tbody>
</table>
</details>
## Demo & Tutorial
Head to [Hack Cabin](https://hackcabin.com) for a **production example** of which the [site architecture](https://hackcabin.com/post/initial-commit/) can be recreated using a [step-by-step guide](https://go.habd.as/zero-to-http-2). And while you're looking at example sites, check out [a few others](https://github.com/comfusion/after-dark/wiki) for even more inspiration.
## Getting Started
First [Install Hugo](https://gohugo.io/#action) and, optionally, [elinks](http://elinks.or.cz/) on your machine. Instructions for installing both using [Homebrew](https://brew.sh/) on macOS:
```shell
brew install hugo elinks
```
Then run the install script located in `bin/install.sh`, or just paste this into a terminal and press <kbd>Enter</kbd>:
```shell
curl -s https://raw.githubusercontent.com/comfusion/after-dark/master/bin/install.sh | sh
```
Installation should complete in a matter of seconds.
## Customizing
### Section Menu
After Dark uses Hugo's [Section Menu for Lazy Bloggers](https://gohugo.io/extras/menus/#section-menu-for-the-lazy-blogger) to produce global site navigation if enabled.
To customize the menu, update the settings in `config.toml` like:
```toml
[[menu.main]]
name = "Home"
weight = 1
identifier = "home"
url = "/"
[[menu.main]]
name = "Posts"
weight = 2
identifier = "post"
url = "/post/"
```
Or update the menu using front matter from your pages:
```toml
menu = "main"
weight = 3
```
### Lazy Loading
Lazy loading prioritizes when and how images and more are downloaded, improving perceived performance and reducing page load times. Lazy loading will start working automatically. No configuration is necessary.
To activate lazy loading with [lazysizes], add `lazyload` to the `class` attribute of your images/iframes in conjunction with a `data-src` and/or `data-srcset` attribute:
```html
<!-- non-responsive -->
<img data-src="image.jpg" class="lazyload">
```
```html
<!-- responsive with automatic sizes calculation -->
<img
data-sizes="auto"
data-src="image2.jpg"
data-srcset="image1.jpg 300w, image2.jpg 600w, image3.jpg 900w"
class="lazyload">
```
```html
<!-- iframe example -->
<iframe frameborder="0"
class="lazyload"
allowfullscreen
data-src="//www.youtube.com/embed/ZfV-aYdU4uE">
</iframe>
```
After Dark includes a _Shortcode_ taking advantage of this feature, enabling you to easily create [lazy-loaded `figure` elements](#content-reuse) within your markdown content.
Additional information and examples, including how to set-up and use LQIP (Low-Quality Image Placeholders), are available on the [lazysizes] repository on GitHub.
### BPG Image Support
The BPG image format provides [high-fidelity images](http://xooyoozoo.github.io/yolo-octo-bugfixes/#vintage-car&jpg=s&bpg=s) which look more like PNGs but loads as fast as a JPG. From a compression standpoint, BPG really shines when handling animations. With support for alpha transparency and given its compression, BPG [literally steamrolls](https://bellard.org/bpg/animation.html) the GIF format of yesteryear.
**Why haven't I heard of BPG?** You have now, and you'll learn about all kinds of cool stuff like this by keeping your eye on [Perf.Rocks](http://perf.rocks/). Please help push BPG forward by encouraging browser makers to improve [current support levels](http://caniuse.com/#search=bpg).
Use BPG just like any other image with the `img` element with a `.bpg` image file extension on any [encoded image](https://webencoder.libbpg.org/). After Dark will asynchronously download a BPG polyfill and render the image in a `canvas` element.
BPG image support is enabled by default in After Dark. To disable support for BPG images add the following to your site configuration:
```toml
[params.seo]
disable_bpg = true # Disable BPG image support
```
### Related Content
Promote more of your content to your site visitors. By offering your readers more content that's relevant to them you can increase your site's page views, the time spent on your site and reader loyalty.
Related content surfaces content across sections by matching taxonomy tags. If After Dark finds related content, it will automatically output a list of links to that content in reverse chronological order below the byline of your post content.
By default After Dark will display up to 7 items by title along with their reading times. You can limit the number of items displayed by setting the following optional parameter in the `[params]` section of your `config.toml` file:
```toml
related_content_limit = 5
```
Learn more about [Related Content in Hugo](https://gohugo.io/content-management/related/), including configuration options you may wish to add to your site.
### Table Of Contents
Help users locate and share information on your site. By providing a <abbr title="Table Of Contents">TOC</abbr>, users will spend less time scrolling to locate information in larger documents and are more likely to deep to specific information on a page.
To automatically generate a TOC for a post based on the [page outline](https://gsnedders.html5.org/outliner/), add the following to your post front matter:
```toml
toc = true
```
To hide the TOC set `toc = false`, or simply remove the setting from the post front matter.
After Dark uses the HTML5 [`details`](http://devdocs.io/html/element/details) and [`summary`](http://devdocs.io/html/element/summary) elements to provide a TOC which does not require use of CSS or JavaScript to function.
When a page is first loaded, the TOC will be collapsed so it does not clutter up the page. Once expanded, selecting an item in the TOC will smooth scroll to that section within the document, highlight the section header and updating the browser's location bar for deep linking and back-button support.
### Social Engagement
Increase user engagement when sharing links on social media.
#### Open Graph
After Dark leverages Open Graph tags using the *undocumented* [internal template](https://github.com/spf13/hugo/blob/142558719324aa1628541d556ef1fa2d123f1e68/tpl/tplimpl/template_embedded.go#L159-L201) to achieve rich sharing cards for Facebook and other social networks, as shown here:
![Open Graph sharing card screenshot](images/docs/feat-social-awareness.png "Example Open Graph sharing card produced by After Dark")
To create a social sharing card like the one shown above, specify `author` in `config.toml` and, optionally, override it from your front matter as shown here:
```toml
title = "Become a Digital Nomad in Bali: The Lost Guide"
description = "Everything you need to know to become a Digital Nomad in Bali."
author = "Bali Bebas!"
date = "2017-02-02T11:57:24+08:00"
publishdate = "2017-01-28T02:31:22+08:00"
images = [
"https://source.unsplash.com/-09QE4q0ezw/2000x1322"
]
```
**Why use array notation for one image?** [The Open Graph protocol](http://ogp.me) supports [arrays](http://ogp.me/#array) and users may wish to extend Hugo internal templates to do so.
To configure site-wide Open Graph images to use as fallbacks for posts not specifying their own open graph images, add an array of URLs to the `[params]` section in `config.toml`:
```toml
images = [
"https://source.unsplash.com/-09QE4q0ezw/2000x1322" # Default Open Graph image for site
]
```
Or, if using [Page Bundle](https://gohugo.io/content-management/page-bundles/), specify the relative path to an image resource for the page:
```toml
images = [
"/post/post-title/images/lana-abie-581813-unsplash.jpg"
]
```
See [Unsplash Source](https://source.unsplash.com/) for image configuration options.
**Note:** While it would be possible, After Dark does not currently support relative links to images. If you would like to see this feature, please [open a new issue](https://github.com/comfusion/after-dark/issues/new).
#### Twitter Cards
Optimize tweets with Twitter Cards. After Dark leverages the Hugo [internal template](https://gohugo.io/templates/internal/#the-internal-templates) for Twitter to provide large preview images in addition to associating shares with the site creator.
See the Hugo [Internal Templates documentation](https://gohugo.io/templates/internal/#the-internal-templates) for more information.
#### Telegram Instant View
Improve the experience for Telegram users by providing an [Instant View](https://instantview.telegram.org/) (IV). After Dark makes easy.
![Open Graph sharing card screenshot](images/docs/feat-instant-view.png "Example Telegram Instant View for After Dark")
To create an IV for your site simply [create your own](https://instantview.telegram.org/my/) Instant View template modeling from the example template below.
```
# enable for items in the post section
?path: /post/.+
# define required elements
title: //*[@itemprop="headline"]
body: //*[@itemprop="articleBody"]
# if cover exists, define images
?exists: //head/meta[@property="og:image"]/@content
cover: //head/meta[@property="og:image"]/@content
image_url: $cover/self::img/@src
# author and post date extracted automatically
```
Additionally, if your site has a telegram channel, you can specify it by setting the following in your site config:
```toml
[params.seo]
telegram_channel = "channelname" # omit the `@`
```
Specifying a channel name allows Telegram users to join your channel with a single click from within an Instant View.
See the [Telegram IV docs](https://instantview.telegram.org/docs) for additional information.
### Search Optimization
After Dark is built with SEO in mind. Schema Structured Data and other meta are applied to give robots what they want, automatically, without any configuration necessary.
The default set-up helps ensure your After Dark site will rank well in <abbr title="Search Engine Results Pages">SERP</abbr>s and prevent search crawlers from indexing undesirable content. Fine-tune your search settings using the following available options.
#### Webmaster Verification
Verify your site with several webmaster tools including Google, Bing, Alexa and Yandex. To allow verification of your site with any or all of these providers simply add the following to your `config.toml` and fill in their respective values:
```toml
[params.seo.webmaster_verifications]
google = "" # Optional, Google verification code
bing = "" # Optional, Bing verification code
alexa = "" # Optional, Alexa verification code
yandex = "" # Optional, Yandex verification code
```
**Note:** Claiming your site with Alexa was [retired in May 2016](https://support.alexa.com/hc/en-us/articles/219135887-Claiming-has-been-retired-May-2016). However, Alexa verification has been added as a convenience for existing sites migrating to After Dark.
#### Meta Descriptions
Well-crafted page titles help catch the human eye on search results pages and meta descriptions provide a summary of the content and why its relevant for the reader, driving click-throughs.
To add a custom meta description to your pages and posts add `description` to the front matter:
```toml
description = "Everything you need to know to become a Digital Nomad in Bali."
```
In addition to appearing in search engines, meta descriptions also appear on individual pages and in content summaries in After Dark, adding transparency to how your page will appear in search.
If no custom description is provided, After Dark will fallback to the description provided in `config.toml`. Learn more on [how to craft your meta descriptions](https://moz.com/learn/seo/meta-description).
#### Modification Dating
Help user agents know when posts were last modified. To do so add `publishdate` to your page front matter and update `date` anytime you make an update to a post.
Updates will be made visible to readers by surfacing content higher in your page and post listings and by using visible callouts on content summaries. For robots, making this change will automatically update Schema Structured Data and Web feeds, as well as the `lastmod` setting in your `sitemap.xml` file.
You can be specific and use a datetime (with timezone offset) like:
```
date = "2017-02-02T01:20:56-06:00"
publishdate = "2016-11-21T10:32:33+08:00"
```
Or less specific and use just the dates:
```
date = "2017-02-02"
publishdate = "2016-11-21"
```
In addition to `date` and `publishdate`, it's also possible to set an expiry date. Expired posts will automatically disappear when the site is built, but the content will be retained. To future- or back-date content for expiration, set the `expirydate` field in the front matter.
#### Index Blocking
Just because a page appears in your `sitemap.xml` does not mean you want it to appear in a SERP. Examples of pages which will appear in your `sitemap.xml` that you typically do not want indexed by crawlers include error pages, search pages, legal pages, and pages that simply list summaries of other pages.
Though it's possible to block search indexing from a `robots.txt` file, After Dark makes it possible to block page indexing using Hugo configuration as well. By default the following page types will be blocked:
- Section Pages (e.g. Post listings)
- Taxonomy Pages (e.g. Category and Tag listings)
- Taxonomy Terms Pages (e.g. Pages listing taxonomies)
To customize default blocking configure the `noindex_kinds` setting in the `[params]` section of your `config.toml`.
For example, if you want to enable crawling for sections appearing in [Section Menu](#adding-a-section-menu), add the following to your configuration file:
```
[params]
noindex_kinds = [
"taxonomy",
"taxonomyTerm"
]
```
To block individual pages from being indexed add `noindex` to your page's front matter and set the value to `true`, like:
```toml
noindex = true
```
And, finally, if you're using Hugo `v0.18` or newer, you can also add an `_index.md` file with the `noindex` front matter to control indexing for specific section list layouts:
```shell
├── content
│ ├── modules
│ │ ├── starry-night.md
│ │ └── flying-toilets.md
│ └── news
│ ├── _index.md
│ └── return-flying-toasters.md
```
To learn more about how crawlers use this feature read [block search indexing with meta tags](https://support.google.com/webmasters/answer/93710).
#### Referrer Policy
Resource requests such as images and scripts typically send an HTTP header containing the location where the request originated. Most of the time this is okay. But sometimes it's not. Sometimes the referrer header is used to censor information or even perform [spear phishing](https://en.wikipedia.org/wiki/Phishing#Spear_phishing) attacks. Perhaps more importantly, transmission of the referrer header can present a privacy concern when transmitted to external sites. But not in After Dark.
After Dark leverages [Referrer Policy](https://w3c.github.io/webappsec-referrer-policy/) to increase security and privacy beyond browser defaults by preventing spec-compliant browsers from passing referrer data when making cross-origin requests.
If you wish to relax the security policy for whatever reason you may do so by:
- Setting the [`referrerpolicy`](https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-delivery-referrer-attribute) by HTML attribute;
- Override the policy using a [nested browsing context](https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-delivery-nested); or,
- Override the page-level default specified by After Dark.
To override the page-level default of [`same-origin`](https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-same-origin) add/adjust the following config when building your site:
```
[params.seo]
referrer = "same-origin"
```
For a list of possible values and their meanings please see W3C's [Referrer Policy](https://w3c.github.io/webappsec-referrer-policy/).
#### Link Types
For related content split across multiple pages in a sequence After Dark supports use of `prev` and `next` settings in your front matter. Use them to provide semantic relationships between pages in a segmented article or series or [LiveBlogPosting](https://schema.org/LiveBlogPosting).
```toml
prev = "/series/learn-to-code/part-one/"
next = "/series/learn-to-code/part-three/"
```
Link Types are commonly shown at the top of the page in terminal browsers as auxiliary means of navigation and may help crawlers better understand relationships within your content.
Learn more about [link types](http://devdocs.io/html/link_types) and how to [customize Hugo taxonomies](https://gohugo.io/taxonomies/overview/).
#### Meta Keywords
Meta keywords offer semantic detail to crawlers regarding the subject matter of your content. Keywords meta are generated automatically for pages given the tags used for that page, and for other pages using the site categories taxonomy. Keywords and key phrases may be customized by setting a `keywords` array in your front matter:
```toml
keywords = [
"web development",
"digital marketing",
"social media",
"link building"
]
```
While not considered relevant to some crawlers, keywords can be a useful way to document target search terms for use in <abbr title="Pay-Per-Click">PPC</abbr> online advertising and provide semantic value to your pages.
### Post Images
Bring your words to life with post images. Post images appear above post content and leverage Hugo's inbuilt [Image Processing](https://gohugo.io/content-management/image-processing/) to enable automatic cropping and image positioning.
Because post images are often one of the first things users see when visiting your site After Dark takes some extra steps to load them in a performant manner. Techniques used to speed up image loading include [Low-Quality Image Placeholders](https://www.afasterweb.com/2016/08/31/low-quality-blur-in/), [Lazy Loading](#lazy-loading) and responsive images using the `srcset` and `sizes` attributes.
Using post images requires some opinion with regard to the structure of your content. To create a post with a post image you must:
1. Create a [Page Bundle](https://gohugo.io/content-management/page-bundles/) grouping your desired image together with your post content.
2. Specify the [Resources Metadata](https://gohugo.io/content-management/page-resources/#resources-metadata-toml-example) in the post front matter and set the `name` property to `"header"`.
An example page bundle might look like:
```
└── post
   └── secure-your-digital-life
      ├── images
        └── florian-klauer-119557-unsplash.jpg
      └── index.md
```
With the following front matter specified in `index.md`:
```
[[resources]]
src = "images/florian-klauer-119557-unsplash.jpg"
name = "header"
```
That's it! After Dark does the rest.
### Fuzzy Search
Find content site-wide in the blink of an eye. JavaScript fuzzy search is at your fingertips. To use it simply create a section called `search` using the After Dark search layout like so:
```
└── content
   └── search
      └── _index.md
```
With `_index.md` like:
```
+++
title = "Search"
layout = "search"
noindex = true
+++
```
Then tell Hugo to output an `index.json` file along with your site when building by adding the following to the config:
```
[outputs]
home = ["HTML", "RSS", "JSON"]
section = ["HTML", "RSS", "JSON"]
```
**Note:** If you don't see `index.json` in your `public` folder after building try running a `hugo --gc` to cajole the generator into creating the JSON file.
After that navigate to the `/search/` path on your site and let the fun begin.
**Tip:** Consider enabling the After Dark [section menu](#section-menu) to expose the search section to users.
While deep link searches are supported, please note Fuzzy Search will only return results for [Regular Pages](https://gohugo.io/variables/site/#site-variables-list) and intentionally omits any page tagged for [index blocking](#index-blocking). In other words it's easy to find stuff. But only if you want it to be found.
### Markdown Output
Gain more control over markdown conversion to HTML. By modifying the markdown processor settings you can take advantage of [Blackfriday](https://github.com/russross/blackfriday) features not enabled by default.
To customize conversion output add a `[blackfriday]` section to your site's `config.toml` file like so:
```toml
[blackfriday]
hrefTargetBlank = true
fractions = false
```
Overrides to theme markdown processing defaults are available from page front matter as well, giving you control on a page-by-page basis.
See the Hugo docs for additional [configuration options](http://gohugo.io/overview/configuration/#configure-blackfriday-rendering).
### Content Reuse
Keep your content <abbr title="Don't Repeat Yourself">DRY</abbr> and improve thematic consistency across your site. After Dark provides a number [Shortcodes](https://gohugo.io/extras/shortcodes) and composable components to help you keep your content and layouts easy to maintain.
Take for example After Dark's `blockquote` shortcode:
```html
<blockquote {{ with .Get "class" }}class="{{ . }}"{{ end }} {{ with .Get "citelink" }}cite="{{ . }}"{{ end }}>
{{ .Inner }}
{{ with .Get "citelink" }}
<cite><a target="_blank" href="{{ . }}">{{ $.Get "cite" }}</a></cite>
{{ else }}
<cite>{{ .Get "cite" }}</cite>
{{ end }}
</blockquote>
```
Use it in your page or post markdown files like:
```html
{{< blockquote cite="Bitly" citelink="https://bitly.is/2mkxskj" >}}
<p>When you create your own Branded Short Domain, you can expect to see up to a 34% increase in CTR when compared to standard bit.ly links.</p>
{{< /blockquote >}}
```
Additional theme-provided shortcodes at your disposal:
- `privacytube` – It's YouTube. But without cookies and UI cruft.
- `coub` - GIFs with sound. Think of it like YouTube for video loops.
- `figure` - Similar to the Hugo built-in, but with [Lazy Loading](#lazy-loading), an adjusted caption title and smaller caption text.
Also included are a number of shortcodes for [hackcss components](https://hackcss.egoist.moe/). These shortcodes function across After Dark [theme variants](#theme-variants) and were created as partials, enabling reuse in both your content as well as your [personalized layouts](#personalization):
- `hackcss-alert` - Provides themed alert boxes. See `hackcss-alert.html` for usage notes.
- `hackcss-button` - Provides themed buttons. See `hackcss-button.html` for usage notes.
- `hackcss-buttongroup` - Allows buttons to be grouped together. See `hackcss-buttongroup.html` for usage notes.
- `hackcss-card` - Provides themed card element. See `hackcss-card.html` for usage notes.
- `hackcss-progress` - Provides themed progress meter. See `hackcss-progress.html` for usage notes.
- `hackcss-throbber` - Provides themed loading indicator. See `hackcss-throbber.html` for usage notes.
To create your own custom shortcodes add a `layouts/shortcodes` directory to your site, place your shortcodes within and start using them in your markdown content. To create or override provided components add a `layouts/partials/components` directory to your site and reference the theme-provided files as you hack away.
Reference the Hugo docs for [shortcode usage instructions](https://gohugo.io/content-management/shortcodes/#using-a-shortcode) and see the inline documentation within each shortcode for example usage instructions.
### Syntax Highlighting
Provide a richer experience when sharing code snippets on your site. After Dark provides support for code highlighting using the lovely [One Dark](https://github.com/atom/one-dark-syntax) and [One Light](https://github.com/atom/one-light-syntax) syntax themes for Pygments and Chroma.
![Syntax Highlighting screenshot](images/docs/feat-syntax-highlighting.png "Syntax Highlighting using Atom One Pygments and Chroma")
To set-up syntax highlighting for your After Dark site:
- Follow Hugo's [Syntax Highlighting](https://gohugo.io/content-management/syntax-highlighting/) instructions.
- Open the `themes/after-dark` folder and run `npm i` (assumes NPM installed).
- Then open `./node_modules/atom-one-pygments` and `npm i`.
- Once dependencies are installed, issue `npm run build` within the module to generate the stylesheets to the module's `./dist` directory.
Then choose either `./dist/light.css` or `dark.css` depending on your [Theme Variant](#theme-variants) and copy the contents of the file into your [Custom Styles](#custom-styles) file.
Once configured, syntax highlighting can be achieved using the Hugo built-in [`highlight` shortcode](https://gohugo.io/extras/shortcodes#highlight). Reference Hugo's [Syntax Highlighting docs](https://gohugo.io/content-management/syntax-highlighting/) for usage instructions.
**Not completely satisfied?** [Atom One Pygments](https://github.com/comfusion/atom-one-pygments) is built as a theme roller, making it possible to modify the look-and-feel of the resulting syntax highlighting. Make it your own. See the [README](https://github.com/comfusion/atom-one-pygments/blob/master/README.md) for more details.
### Personalization
After Dark uses [hack.css](https://hackcss.egoist.moe/dark.html) to automatically style your markup, giving you instant access to flexbox grids, light and dark theme variants, and other pre-built components. Use them while creating new [sections](#section-menu) leveraging [block templates](https://gohugo.io/templates/blocks). Additional personalization options listed below.
#### Custom Styles
Customize theme styles without forking using Hugo's inbuilt [Partial Templates](https://gohugo.io/templates/partials/). To get started:
1. Create a `critical-custom.css` in your site's `layouts/partials/head` directory. If the directory does not exist yet, simply create it.
2. Add your custom styles inside the file.
Example customization file:
```css
/* override theme defaults */
.muted {
color: rgba(255, 255, 255, 0.5);
}
/* custom styles */
figure {
margin-left: auto;
margin-right: auto;
text-align: center;
}
figure img {
max-width: 80%;
}
figure a {
border-bottom: none !important;
}
figure a:hover {
background-color: inherit !important;
}
```
Styles are inlined into the `head` of each page. If you would prefer to use external stylesheets override the `partials/global-styles.html` template, modeling from the theme's version of the file, and make any adjustments you see fit.
#### Theme Variants
[`hack.css`](https://hackcss.egoist.moe/) provides a few variants you may wish to use instead of the After Dark defaults. To download them do an `npm install` from `/themes/after-dark/` (assumes NodeJS installed).
Once downloaded, open `./node_modules/hack/dist`, copy the styles you wish to use into a `critical-vendor.css` [template override](https://gohugo.io/themes/customizing/#override-template-files) and apply the variant by setting `theme_variant` in your site config to one of:
"standard"
"hack dark-grey"
"hack solarized-dark"
Once variant applied, open your browser's dev tools and test the changes by previewing your site on mobile, tablet and desktop at different display resolutions and orientations—overriding and making any desired changes to your [overridden](https://gohugo.io/themes/customizing/#override-template-files) `critical-theme.css`, 404 page, `theme-color.html` and [Custom Styles](#custom-styles).
#### Favicon
After Dark ships with a lightweight SVG favicon embedded into every page. To customize or replace it create a file named `favicon.html` under `layouts/partials/head` within your site and place an [`icon` link](http://devdocs.io/html/link_types#icon) within it.
**Why SVG?** Though they don't have perfect [browser support](http://caniuse.com/#feat=link-icon-svg) yet, SVG favicons are smaller in size and more flexible. SVG favicons can be styled with CSS or even animated with JavaScript.
## License
Copyright 2016-2018 Josh Habdas <jhabas@protonmail.com> (https://habd.as)
<br>This work is free. You can redistribute it and/or modify it under the
<br>terms of the Do What The Fuck You Want To Public License, Version 2,
<br>as published by Sam Hocevar. See the COPYING file for more details.
[lazysizes]: https://github.com/aFarkas/lazysizes

@ -0,0 +1,6 @@
+++
title = "{{ replace .TranslationBaseName "-" " " | title }}"
date = {{ .Date }}
description = ""
draft = true
+++

@ -0,0 +1,27 @@
+++
title = "{{ replace .TranslationBaseName "-" " " | title }}"
date = {{ .Date }}
description = "Thank you for choosing After Dark."
draft = true
toc = false
categories = ["technology"]
tags = ["hello", "world"]
images = [
"https://source.unsplash.com/category/technology/1600x900"
] # overrides the site-wide open graph image
+++
Before you continue, please take a moment to configure your archetypes.
Archetypes are located in the `archetypes` directory in the source of your site. To learn more about archetypes, visit [Archetypes](https://gohugo.io/content-management/archetypes/) on the Hugo website. And when you're ready, check out the [Customizing](https://comfusion.github.io/after-dark/#customizing) section of the After Dark documentation for additional options.
<!--more-->
This information appears below the [Summary Split](https://gohugo.io/content-management/summaries/).
After Dark supports the `bpg` image format without any additional configuration necessary. Here's an example BPG image animation:
<img src="/bpg/cinemagraph-6.bpg" alt="BPG file format example">
BPG compresses the above animation to `48KB`, about **97% smaller** than what would be possible with GIF. In addition to animation BPG handles still images as well. Head to the [side-by-side comparisons](http://xooyoozoo.github.io/yolo-octo-bugfixes/#vallee-de-colca&jpg=s&bpg=s) to see BPG stacked up against JPEG. Create your own BPG images using the [BPG web encoder](https://webencoder.libbpg.org/) for use on your After Dark site.
See the <a href="https://github.com/comfusion/after-dark/blob/master/README.md" target="_blank" rel="noopener nofollow">After Dark `README`</a> for more info.

Binary file not shown.

After

Width:  |  Height:  |  Size: 144 KiB

Some files were not shown because too many files have changed in this diff Show More

Loading…
Cancel
Save