61–70 of 119 posts
Earlier quoted context omitted.
Markdown specifically allows and recommends inline HTML for anything more complex than writing prose [1] [1]: https://daringfireball.net/projects/markdown/syntax (see "Inline HTML")
Well, sort of. HN doesn't seem to accept any HTML.
Absolutely love Jekyll and GitHub Pages for hosting project documentation and personal websites. Just wish GH Pages would support SSL. :(
I don't know much about GitHub Pages, but if it's only for static pages, then why do you need SSL? I mean if you're not going to be sending sensitive dynamic data. Is it so people can't snoop the contents of your pages over request/response on a network?
Kramdown has strange behavior. http://stackoverflow.com/questions/23751917/how-do-you-disab...
Earlier quoted context omitted.
Nice. One way you could distinguish your service from all other options (S3, Github Pages), is to support the history API for single page webapps. I'm hosting a static site on EC2 instead of S3 because I need URLs to fallback to index.html. Literally for this one nginx rule: location / { try_files $uri /index.html =404; } Also, I'd like to try the beta of your service, just signed up. My email is in my profile. Thank…
Surge and Firebase hosting both allow for this
Staying away from Firebase after what happened to Parse.
Absolutely love Jekyll and GitHub Pages for hosting project documentation and personal websites. Just wish GH Pages would support SSL. :(
I don't know much about GitHub Pages, but if it's only for static pages, then why do you need SSL? I mean if you're not going to be sending sensitive dynamic data. Is it so people can't snoop the contents of your pages over request/response on a network?
OK, a standard dialect of Markdown. In the beginning was RUNOFF from MIT, which originally had about the power of Markdown. More features were added, and it became nroff, then troff, the ditrofff, and macro systems were added on top of it. It became too hard to use for casual work. Then there was TeX, which was a saner approach to what troff did. Macro systems were added on top of it. It became too hard to use for ca…
Markdown specifically allows and recommends inline HTML for anything more complex than writing prose [1] [1]: https://daringfireball.net/projects/markdown/syntax (see "Inline HTML")
Earlier quoted context omitted.
I'm working on a static hosting service. We are working on SSL and making that easy. Would you be interested in trying the beta? http://www.statichosting.co
Your site doesn't accept connections over SSL.
My partner and I are finishing up a CLI app and then SSL comes after that. We are hoping to integrate nicely with something like letsencrypt.org, but we don't have a working solution yet.
I know from experience that HTTPS setup isn't as easy, nice, or cheap as it should be and we plan to fix that if possible for static sites.
Earlier quoted context omitted.
In case SSL support is essential to you please know that we'll looking to bring it to _GitLab_ Pages in a few months https://gitlab.com/gitlab-org/gitlab-ee/issues/134
Is GitLab pages going to be available to non-enterprise gitlab.com users? If not, may I respectfully request that it is?
Earlier quoted context omitted.
Markdown specifically allows and recommends inline HTML for anything more complex than writing prose [1] [1]: https://daringfireball.net/projects/markdown/syntax (see "Inline HTML")
Well, sort of. HN doesn't seem to accept any HTML.
Jekyll 3 is pretty great. If you need any help getting your site hosted, I'm working on a hosting setup that is way easier than S3 or any other option out there. http://www.statichosting.co We are in private beta and are looking for people to try it out and give us feedback. We think it's great and are looking for early adopters who want an awesome static hosting experience.
Pretty cool! If you can set up some sort of integration with Travis (which itself integrates nicely with GitHub), and you set up SSL, HTTP/2, good caching policies etc., you're golden.
Our focus is on simplicity and there are only two of us, so adding features in a way that fit our limited resources and vision is a bit tough.
We are working on SSL and making sure we have good caching policies by default. Travis and GitHub integration are things we haven't looked at yet, but will.
If you are looking for something right away before we have all those features, you might check out netlify. They already support a lot of those features and might be a better fit in the short term.