You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see the feed of contributors, however the new content isn't there.
Just out of curiosity, why not using Jekyll + GitHub Pages for the same purposes? That could have saved a lot of operational problems. Did it have less capabilities then lambdapad?
The text was updated successfully, but these errors were encountered:
We need to either get some sort of CI builds going to push this to Amazon or use github pages as you suggest. I haven't setup a site using github pages, so I'm not sure what's involved there.
As for using Jekyll, I'd rather just fix LambdaPad - the point of that is to drive functionality in LamdaPad to make it more useful to people. Yes, reinventing the wheel, perhaps - but that doesn't bother me. If LambdaPad becomes a bottleneck, we can switch.
I'll keep this open to drive a CI process, or a switch to github pages so people don't have to rely on me to push. Or, I could just be more diligent in pushing whenever I merge (that seems like a better approach actually). I'll keep this open until we reach a consensus in any case.
I can see the feed of contributors, however the new content isn't there.
Just out of curiosity, why not using Jekyll + GitHub Pages for the same purposes? That could have saved a lot of operational problems. Did it have less capabilities then lambdapad?
The text was updated successfully, but these errors were encountered: