brislink.github.io
- A pleasant writing environment - A system that can be configured and deployed in minutes - Customization that is limited only by your imagination. - Power of node and elastic search in your blog.
Be sure to give it a try!
Interesting: "I wrote something new in a way or with tools that I had not used before. Here's what worked, here's what didn't, and here's what I learned."
Unfortunately, this is the former. I'd be interested in reading the latter if you wrote something up about your experience with this.
I wrote in detail about specter and what I learnt building it on my blog, if you care to read you can go on the link below.
Is it okay if I keep writing post in HTML, rather than REST? Or am I missing out on some awesome set of features? I'd love to know if anyone actually converted to one of these platforms and found themselves writing more. I definitely have some trouble finishing the posts that I start, but I get the distinct impression that using one of these would be akin to getting a gym membership: if I'm not finishing blog posts now I won't magically start finishing blog posts just because of this new tool.
I think it's nice to see a variety of self-made blogging platforms come around. Not only do we bloggers get our pick of the litter but it shows how some languages/frameworks work in creating something conventional like a blog. I agree that is seems to have become some sort of rite of passage.
In terms of awesome features - well yes. There are tons and tons and tons that are available from pages dynamically generated by a server-side program that would be a real pain to produce on manually updating HTML pages.
> Is it okay if I keep writing post in HTML, rather than REST?
What?
Of course, I probably consider this workflow easier because as a developer I'm already perfectly comfortable with git, and with working with source files. I can just open a terminal and type `vim /path/to/blog/new-post.markdown` and start writing. I find Wordpress slow, fiddly and limiting by contrast.
I'm not uncomfortable making the extended inference that most who prefer markdown for posting are at least very computer-literate and quite possibly software developers. I tried to sell my wife (a writer) on markdown and she didn't get it at all.
>Specter takes the elegant/lazy approach of not using sessions at all - access to edit and create pages is entirely via url, and permission to actually perform those changes is granted by including a 'secret' (a password) in the form. It's not the most secure form of defense (I'm not using ssl, so a wireless sniffer could easily determine my password, for example), but its sufficient for a nonprofessional.
Is there something that I can do to make it more secure but still follow the lazy approach. I am asking cause I use heroku which is not secure as well.
On the other side, it is typically better not to store the password on the server either. You could accomplish that by giving a utility to store a hash in a file, but that's a bit heavy I guess.
I meant for a nonprofessional /blogger/, incidentally, not a nonprofessional coder :-)
https://github.com/gschier/simple-blog
I wrote about it here
I for one think JavaScript is an utterly hideous language full of all kinds of gotchas and abortions and that the only reason it has any relevance is it got their first.
I will take PHP over JS (and Python over both).
I've been using static blogging for about a year now, it's great. Fast, simple, miss nothing from Blogger or Posterous, don't know about Wordpress never used it, and all your content is stored in your own Github repository.
Dynamic engines: * Do many things (i.e. having multiple authors, multiple formats, visual editors, plugins, etc.) * Many more (as in x^5) lines of code, which means: * * Harder to maintain * * Easier to use for _non programmers_ * * Easy to customize SOME things (apply a theme), HARD to customize the whole thing properly (you need to read huge chunks of code that might break if you change them) --
The above reasons make Wordpress pretty much insecure compared to a Static website (i.e. Jekyll engine like octopress). Of course you could have a bloated wordpress websites where all it's plugins are revised and secure while you could have a static website where it's running buggy JavaScript which reveals your IP to the NSA (random example pick) but the % of having a bug in a bigger (in terms of lines of code) app is way higher.
Obviously it'd be "nice" to have some better contributor management, and instead of forcing me to manipulate the URL to do stuff it'd be "nice" to just click buttons, but frankly I don't care much about any of that.
Real feature request: Language specific syntax highlighting for the code bits. I'd like my snippets to come with highlighting as I explain stuff. JavaScript, Python, C, HTML to start, if you have to pick some languages. :)
Also I notice at the bottom of your blog an rrs and atom feed set of links. any plans on implementing that globally?
/feed/rss and /feed/atom
So all you got to do is add an anchor tag that points to these urls.
Settings can be set in the preferences file.
Regarding syntax highlighting...
Can you not use javascript libraries to do this? I have got no idea how to go about implementing this..
As for syntax highlighting yeah, I'm sure it's just a matter of a library, but you know, it's your project! Sometimes people are looking for stuff to add, just wanted to point out a place I'd find useful. :)
Anyway I updated the pages to have the feeds into them by default so it does not cause any confusion.
I'm sorry. My initial reaction to that was harsh and childish. I wish you the best of luck with your project, and if I can do anything to help please let me know.
Ugh. I wonder how many more of these we'll see before the year's end.
> and a .io domain
And that's just Github's domain... Furthermore, Google is currently treating .io as a generic TLD. Considering the exhaustion of .com and .net addresses, is it any surprise that people have adopted another one en masse?