I’m scripting this in response to this post. Begin there and are available again; I am going to wait!
So… What do you assume? Issues definitely do not look too promising for WordPress, do they?
Or did you shut the tab as quickly as you noticed the primary lowercase p? The writer definitely did not make issues straightforward for himself: misspelled WordPress, informed us how Static Website Turbines are the longer term in a Medium submit, talked about his startup, a Static Website internet hosting firm, in the midst of his submit. However I am going to ask you to look previous that.
I discovered that submit very fascinating. In any case, I’m already accustomed to Static Website Turbines since this very site ran on Jekyll a couple of years again. I additionally spent a few months on Ghost, principally as a result of I needed to attempt the shiny new factor. Proper now, I’ve to say I am actually desirous about Mika’s project: generate a static website utilizing Hugo, after pulling knowledge from WordPress by way of the REST API.
The grass is all the time greener on the opposite aspect of the fence, as they are saying.
But I all the time come again to WordPress. The truth that I work for the company behind WordPress.com definitely has a bit of one thing to do with it. There are all the time new issues to dogfood! However that is not what pushes me again to WordPress each single time.
I keep on with WordPress for the little issues.
- oEmbeds. Pasting iFrame codes sucks.
- Feedback. I like them on my weblog, and do not need to give them away to a 3rd celebration.
- Knowledge portability. I personal my knowledge, and it is all obtainable in a simple to parse format.
- Since WordPress is so in style, I do know there are exporters for almost the whole lot.
- Talking of knowledge: I also needs to point out metadata. It is also moveable, extendable, there’s a widespread commonplace, and it may be
The post Static Website Turbines: are we doomed? appeared first on DICKLEUNG DESIGN 2014.
沒有留言:
張貼留言