Live demo here: http://185.164.138.19:7311/
601 karma · joined December 9, 2014
* Adding code highlighting? 3 lines of code to add in index.php
* Adding analytics (unique visitor count)? 3 lines of code to add in index.php
* Adding Disqus comments ? Less than 10 lines to copy/paste.
Is it this you call a mess?
I've used at least 10 CMS before, and what I call a mess is more: having to create a SQL DB, having to login/logout all the time, having to understand how the marvellous "install-a-plugin-to-extend-the-CMS" system works...
If possible, I like to understand. For Wordpress, I can't (too big). For simple projects, I can and I enjoy it!
> Why would you install a development tool on the server? Do you install gcc on servers too?
At the moment of my last comment, I didn't know at all how Jekyll works, and knew nothing, zero, about Ruby. Never used in my life. Thus my comment. I had a quick look, in the meantime.
> it does not generate static pages, and actually generates them on request-time.
Exactly. Like a CMS, like a blog, like a Wordpress. I never said my tool generates static HTML that should be uploaded to server after each new article. I don't want this by the way. (True that some people thought it was a static generator. My bad, because few documentation yet (currently writing it...))
> gp's question was how this compared to Jekyll, and that's what I answered.
Sure, no problem. I just don't understand why the awfully in your comment. The point of this tool is not to be a static generator. I never said that. Why is it "awful" to just drop .txt files into the server, and let the server and PHP generate content on request-time?
(the polemic part of my answer was related with the other message "The answer is awfully: ..." )
You compare :
* Jekyll which is a great tool, with lots of features, but which has at least 50 files & probably 1000s of line of code. It's great but I wouldn't be able to understand 100% of how it works in 2 hours. Impossible. Moreover I cannot install gem (and probably not Jekyll) on my shared hosting. Huh...
* Void, my toy-website-creation-tool (yes, I have no problem with that: it's a toy tool): you can understand 100% of how it works by reading less than 100 lines. Nothing more. You can install it on a shared hosting, only requirement: Apache + PHP.
Yes, you need to open and hack the PHP file of Void to customize. What's the problem with that? It's done on purpose.
Is it mandatory nowadays to use many tools like Brew, Composer, Gem, Symfony, etc. to set up a simple website? (I mixed random names that are required in lots of CMS/static generators I found).
My answer is no: you can do something simple with a "hack it yourself" philosophy. And less of 100 lines of code.
I have a math research background: if you can prove something in 2 pages with no extra tool, it's far better than doing the same by invoking a big difficult Theorem.
Moreover, I am not a profesionnal developer. And for me, installing Apache+PHP is enough. I don't want to add more tools, more layers. The list could be endless: Let's use Symfony, Composer, Brew (random name here, I don't know what is Brew)... and at the end I'll have a big big thing...
I really want to keep it simple...
Each new layer is like "minus 10 points" for my project ;)
The point of Void is minimalism: apache+php, nothing else required. < 100 lines of code in a single php file (+ the markdown parser lib of course).
If you like stats in the same fashion as yours: http://www.thisisvoid.org/article/04 ;)