-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PyLadies Website: Framework Decision #61
Comments
Con with something like wagtail / django is that we need to host it somewhere on the cloud. Unless we already have something in place? With static website like pelican, it can just be hosted for free as GitHub pages. |
We use Pelican on GitHub Pages for our local chapter's website. For the global site, would the 1GB site limit per GH Pages docs be enough? I'm not at a computer or I'd clone the current site's repo for a guesstimate. |
Currently the size of https://github.com/pyladies/pyladies is 110.5 MB |
Fun fact: the issue that started this discussion was 161 and this issue is 61. Neat! Also, user @Mindiell posted an update in the previous thread about having updated Mynt to modern Python. I'm still hoping for us to move to Pelican, pending consensus, but this sounds like a possible way to extend the relevance life of the Mynt-ness. |
I also prefer Pelican myself. The existing website doesn't have backend code, so switching to another static-site generator is easier effort. We'll also have to look at each chapter's individual websites that we host in the same repo and see what tech they're using, and coordinate with them. cc @pyladies/tech-and-infra-admins |
I'm 👍 pelican, I personally use that for my website |
Per pyladies/pyladies#161, and as mentioned in #6 , we have been considering a new framework for the PyLadies website.
The two main candidates are
Pelican (static)
Wagtail (dynamic)
The action item for this issue is to decide between these frameworks.
A follow-up item would be to create a project proposal issue outlining steps to implement.
Summary of pros/cons for each ported over from the issue linked above:
Pelican review
Pros
Far less babysitting in terms of security vulnerabilities and potential ddos'ing
Actively maintained
PyLadies.com was originally on Pelican
Low barrier to entry
Some local chapters already use
Cons
Not a full-featured CMS
Wagtail review
Pros
Extensible
User-friendly CMS
Based on Python3
Based on Django LTS
Cons
Based on Django which adds complexity over a static site
The text was updated successfully, but these errors were encountered: