This way, anytime someone updates and saves content through the GUI, a script will trigger and re-build your static site based on the new JSON file, and publish to s3. To completely decouple the editing experience (and those who create and maintain content) from the actual design and code, is the real ticket.
One day when I get some more time...
For example, the existing internal API has a backup method that exports all MySQL tables to JSON files. The heavy lifting is already done for you. (It also wraps all your themes and uploads into a TAR along with the JSON files so you have a real, full backup — not just your post content.)
I'd love to explore this more down the road :)
PSA: if you put open source in the title of your product but don't put a link to the source on your front page, you are doing it wrong.
Anyways, the link to GitHub will be on the homepage soon. As I mentioned earlier, the org repo didn't even exist until late last night!
Well it's a good this blogging platform doesn't suck.
* unmaintainable / poorly organized code == suck
* untested code == suck
* easily spammable == suck
how many answers you need? because i can do this all day...
For example, I have my own software that runs my website, and I've spent a lot of time making it work exactly how I want. But, I'm not the best at building editing interfaces, so I have avoided building an inline posting interface. I would much rather use a tool that someone has spent a lot of time making work well, if it can save articles to my own website.
After going to the "Features" page and reading through it, pretty much every feature highlighted is something that almost every other blogging platform has as well.
I commend the author for the design, though. It certainly looks nice.
Why oh why handlebars?
Also, why submit the .net if it just redirects to .org?
Handlebars because PHP isn't great for webpage templates. There are many alternatives, but handlebars has implementations on many, many platforms. It makes the project easier to port to other platforms in the future.
...nope, sorry. Web server agnostic or I won't even consider you these days.
> Unable to connect to the database: The database is not responding. Is the host correct?
If you want to distinguish yourself then say what you are good at, what makes your experience better/different and to what kind of users this solution is tailored to.
That said, it does look very nice.
- PHP 5.5+
- MySQL 5.5.3+
Maybe you are suggesting that PHP+MySQL apps aren't universally terrible. In this case, please state that and defend it.
Or you are unaware that PHP+MySQL apps have a history of being terrible. In this case, I am not sure what to say.
Sure, I could have built Postleaf in Node, for example. It's all the rage these days. I even considered it, but then I considered my end users who (sadly) still have trouble setting up a basic PHP app on a shared LAMP box.
I think part of the allure with Postleaf is the ease of use from the initial install all the way to publishing a post. If I had chosen Node, most of my target users wouldn't have been able to install it. Sure, I could have taken advantage of that to offer paid services that do it for them, but that's not why I developed Postleaf.
The choice to use PHP wasn't me sitting on a platform high horse, it's just what's available pretty much everywhere TODAY. It's also convenient that they're already familiar with the stack. That may change in the future, and Postleaf will pivot accordingly, hence why themes use Handlebars, not Twig or another platform-specific template system.
That PHP+MySQL apps are universally terrible is very subjective. You can build shitty apps with any language :)
Why? Is it because this dev is clearly trying hard and looking for support?
I'm GIVING support. Much, much more than I got when I was searching altavista for information about how CGI works.
I don't recommend using PHP for your next project.
I copy/pasted that section from your readme to save others time. I am certain that I am not the only one not interested in a PHP blogging platform.