Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Make Timeless a little more contributor friendly

  • Loading branch information...
commit 665fea117674b1639a476647df7c94aa12821d36 1 parent e55c467
Magnus Holm judofyr authored

Showing 2 changed files with 46 additions and 31 deletions. Show diff stats Hide diff stats

  1. +7 0 content/contribute
  2. +39 31 content/timeless
7 content/contribute
... ... @@ -0,0 +1,7 @@
  1 +Title: Contribute
  2 +Subtitle: Help us make Timeless even better
  3 +
  4 +Timeless is not only [open source](http://github.com/judofyr/timeless), but
  5 +also very open for contributors: we'd love to have your voice among us.
  6 +
  7 +(snip)
70 content/timeless
... ... @@ -1,17 +1,15 @@
1 1 Title: Timeless
2 2 Subtitle: A mixture of a blog, wiki and CMS
  3 +Author: judofyr
3 4
4   -Welcome to Timeless, the new incarnation of my blog. If you're reading this
5   -from the feed, I would recommend you to take a moment and visit the [newly
6   -redesigned site](http://timeless.judofyr.net/) which has been improved in
7   -many ways.
  5 +Welcome to Timeless, a community blog with focus on *content*.
8 6
9 7 I started my first technical blog in Feburary 2008 and have been blogging
10   -infrequently since then. As time has passed by, I've discovered that a blog is
11   -a surprisingly *bad* way to present technical content, both for the author and
12   -the reader. Timeless is an attempt at creating a new kind of blog with a focus
13   -on frequently updated, quality content which lasts longer than the beta of your
14   -favourite framework.
  8 +infrequently since then. As time has passed by, I've discovered that a blog
  9 +is a surprisingly *bad* way to present technical content, both for the author
  10 +and the reader. Timeless is an attempt at creating a new kind of blog with a
  11 +focus on frequently updated, quality content which lasts longer than the beta
  12 +of your favourite framework.
15 13
16 14 (snip)
17 15
@@ -22,8 +20,8 @@ order. Simple and effective. For almost a decade blogs have been the primary
22 20 medium for inviduals to express their opinion on the internet. A blog is
23 21 perfect for writing about *changes*: a person's life, the society in general,
24 22 the progress of a project, or other events. The readers are encouraged to
25   -frequently visit the blog in order to keep up to date, and in some blogs (these
26   -days: *most* blogs) they can also post comments and take a part of the
  23 +frequently visit the blog in order to keep up to date, and in some blogs
  24 +(these days: *most* blogs) they can also post comments and take a part of the
27 25 discussion.
28 26
29 27 So simple and so effective that it has slowly taken over the internet, which
@@ -33,19 +31,21 @@ because all blog posts should be immutable. People forget to write down the
33 31 context (in the technical world: version numbers, operation systems etc), so
34 32 it's impossible to know if the post still applies a few years later.
35 33
36   -The blog has become the norm, even in the places where it doesn't fit *at all*.
  34 +The blog has become the norm, even in the places where it doesn't fit *at
  35 +all*.
37 36
38 37 ## A blog that isn't a blog
39 38
40 39 You might have arrived at this site under the impression that this is a blog.
41 40 If so, I'm sorry to disappoint you: you won't find any timestamps here. Why?
42   -Because I don't want to write about changes. I don't have what it takes to
43   -maintain a blog and post regularly. All I want to do is to *write*. Not often,
44   -not always, but still: there are times when I simply want to write.
  41 +Because we don't want to write about changes. We don't have what it takes to
  42 +maintain a blog and post regularly. All we want to do is to *write*. Not
  43 +often, not always, but still: there are times when we simply want to write.
45 44
46   -If I'm not going to take advantage of the blog medium, then why should I be
47   -impeded by the disadvantages? Why do I feel I'm *obliged* to add a timestamp to
48   -each post? Why do I feel I'm *not allowed* to change or update the posts?
  45 +If we're not going to take advantage of the blog medium, then why should we
  46 +be impeded by the disadvantages? Why do I feel I'm *obliged* to add a
  47 +timestamp to each post? Why do I feel I'm *not allowed* to change or update
  48 +the posts?
49 49
50 50 I feel brainwashed, and Timeless is my attempt at breaking out of the prison.
51 51
@@ -53,30 +53,38 @@ I feel brainwashed, and Timeless is my attempt at breaking out of the prison.
53 53
54 54 The goal of Timeless is that every articles should be *timeless*. Well, not
55 55 timeless in the usual meaning of the word, but timeless as in every article
56   -should include enough context to be easily understandable if you discover it a
57   -month, a year or maybe even ten years later. The article should be regularly
58   -updated as I learn and discover new aspects of the topic.
  56 +should include enough context to be easily understandable if you discover it
  57 +a month, a year or maybe even ten years later. The article should be
  58 +regularly updated as we learn and discover new aspects of the topic.
59 59
60   -Just because Timeless focuses on content, doesn't mean there's no focus on the
61   -changes. I don't expect people to manually look for changes, so I have both an
62   -[RSS feed](http://feeds.feedburner.com/MagnusHolm) and [a separate
  60 +Just because Timeless focuses on content, doesn't mean there's no focus on
  61 +the changes. I don't expect people to manually look for changes, so there's
  62 +both an [RSS feed](http://feeds.feedburner.com/TimelessRepo) and [a separate
63 63 page](/changelog) about the recent changes at Timeless.
64 64
65   -This gives me the perfect flexibilty: New readers can browser and explore the
66   -content like it's a wiki, while returning readers can easily see if there's any
67   -updated content. If you want to be notifed about further updates, you can
  65 +This gives us the perfect flexibilty: New readers can browser and explore the
  66 +content like it's a wiki, while returning readers can easily see if there's
  67 +any updated content. If you want to be notifed about further updates, you can
68 68 simply subscribe to the feed, just like a normal blog.
69 69
  70 +## You can help too!
  71 +
  72 +Nothing about Timeless is limited to *one* author (in fact, we are two
  73 +authors writing regulary now) and as long as you have something interesting
  74 +to say, you are more than welcome to [help us make Timeless even
  75 +better](/contribute).
  76 +
70 77 ## This is just the beginning...
71 78
72 79 What you are seeing here is only the first version of Timeless. It's far from
73 80 complete, but definitely *good enough* for now. In the future I hope to add
74   -more features (like tags, sub-articles and maybe even comments), but there's no
75   -point of implementing something before I actually need it.
  81 +more features (like tags, sub-articles and maybe even comments), but there's
  82 +no point of implementing something before we actually need it.
76 83
77 84 If you're still interested in Timeless, you can [subscribe to the
78   -feed](http://feeds.feedburner.com/MagnusHolm) or follow the project at
  85 +feed](http://feeds.feedburner.com/TimelessRepo) or follow the project at
79 86 [GitHub](http://github.com/judofyr/timeless).
80 87
81   -Please let me know if you [have any comments, thoughts or questions](/comments).
  88 +Please let me know if you [have any comments, thoughts or
  89 +questions](/comments).
82 90

0 comments on commit 665fea1

Please sign in to comment.
Something went wrong with that request. Please try again.