Should we move away from mynt? about pyladies

[willingc]

Bumping this issue. We should consider either porting mynt to Python 3 (either contributing upstream or forking and creating mynt3) or select another static site generator.

[mUtterberg]

One of the business owners that attends our local user group creates a lot of his client sites in Wagtail. This month’s meetup was last night, but I can ask for feedback next month. From what I remember, he had generally positive things to say about the usability. The only complaints I can remember were related to difficulty implementing e-commerce type CRM components. I doubt that’s super relevant to our needs.

If we’re sticking with a static site, I’m still on team Pelican. But if we do commit to dynamic, Wagtail sounds like a strong option.

[mUtterberg]

@willingc Gladly!

[Mindiell]

Hi there, french dev trying to help on python-docs-fr. I saw a lnk to pyladies and discovered you were using mynt which is py2 only.
So, I started to play with it and made an upgrade to py3 (maybe not totally full for now, but functional). Then I installed the pyladies website and generated it without any problem (just modified some "iteritems" into "items" on archive and tag templates you are using.

And then, I dicovered this discussion :D

So, if you still want to use mynt, I would be glad to help. If not, no problem, it was very interesting to convert it. I'll continue on it and publish something soon wether you want to keep it or not.

[ellisonleao]

Hey @econchick i did a pelican version of the brazilian chapter website. If you want to check out the source code: https://github.com/pyladies-curitiba/br-pyladies-pelican

It has a lot of room for improvement but its working great so far.

[econchick]

cool thank you @ellisonleao - will check it out!

[ellisonleao]

Sorry about only having a portuguese README version btw.

[mUtterberg]

If we're considering other static site generators, I vote Pelican. We chose that package because CLEpy uses it for their site, so we could get help in-person if we got stuck. Plus the documentation is pretty thorough. Our repo for it is deployed to gh-pages at present. I'm not sure what unique issues the global site will run into, but the community support is stellar. Compared to maintenance on our local Django Girls site, I really appreciate the simplicity of Pelican. It still feels like development, but it's also a low barrier to entry for participants that want to contribute.

[willingc]

Nikola and Pelican are both reasonable options. I would give a slight edge to Nikola as it can support rST, markdown, and Jupyter notebooks.

[mUtterberg]

@willingc I like the sound of that! Pelican does rST and markdown, but the user groups in town have just been posting notebook content to dedicated GitHub repos. Is Nikola as easy to learn & simple to contribute content as Pelican?

[mUtterberg]

I'm a little hesitant to jump on the Nikola train. I tried to install it tonight and ran into a bunch of issues. Their pip version doesn't work on mac, so I'll need to try again if I decide to install homebrew. I just want one package manager and/or distribution to rule them all! haha but actually I've just been avoiding homebrew for no good reason or than I like my conda/pip setup.

But I do think others will run into this issue and Pelican is a more stable static site gen to recommend local sites (and newbies) check out. So I'm still somewhat in favor of Pelican, but working on trying out Nikola.

[willingc]

@mUtterberg Good point re: new contributors. Let's look at moving to Pelican.

@econchick @estherbester @jackiekazil @audreyr Thoughts on moving to Pelican?

[estherbester]

PyLadies.com was originally on Pelican! :D I'm ok with Pelican, if it supports all the modern Python goodness.

…

On Fri, Oct 26, 2018 at 7:34 AM Carol Willing ***@***.***> wrote: @mUtterberg <https://github.com/mUtterberg> Good point re: new contributors. Let's look at moving to Pelican. @econchick <https://github.com/econchick> @estherbester <https://github.com/estherbester> @jackiekazil <https://github.com/jackiekazil> @audreyr <https://github.com/audreyr> Thoughts on moving to Pelican? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#161 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFy80fCMsGwh3bOKbksF43N-c9LemQmks5uox1cgaJpZM4D_brk> .

[thursdayb]

What do folks think of using a more fully-featured CMS for the blog?

[jackiekazil]

Example?

On Tue, Oct 30, 2018 at 7:57 PM thursdayb ***@***.***> wrote: What do folks think of using a more fully-featured CMS for the blog? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#161 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKLTqqXvKFnkGkElqDAEp9aSyIVwOIAks5uqOdfgaJpZM4D_brk> .

-- Jacqueline Kazil | @jackiekazil

[econchick]

We had a CMS before mynt; I switched it since static site generators need far less babysitting in terms of security vulnerabilities and potential ddos'ing.

I'm okay with moving to pelican or something else. Just something that's actively maintained (as mynt no longer is). I just moved my own blog to hugo and love it, but it's golang, and therefore the templating language is a bit different.

[willingc]

I love hugo and use it for my projects. As a Python group, probably good to stick with something Python? 😄

Which CMS? Wagtail?

[thursdayb]

Wagtail would be amazing

Just having some basic editorial tools would be so helpful

[willingc]

Let's discuss and make a decision at PyCon.

[willingc]

I don't think that this ever was discussed at PyCon.

Wagtail has been very active since I started this issue. Here's info about their latest release: https://wagtail.io/blog/wagtail-2-5/

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

[willingc]

The migration-base branch in this repo restructures the repo and provides a baseline for you to try different ideas/apps locally. The README contains info about the branch's structure.

[willingc]

Thanks @mUtterberg for resurfacing this. Would you mind leaving an issue on the global organizing repo for a decision Pelican or Wagtail? Thanks ☀️

[mUtterberg]

Hi @Mindiell . That sounds like a great project! This discussion has moved over to pyladies/global-organizing. I am adding a link to your comment in that thread!

I would definitely love to read about your process when you publish. Thank you.

[Mindiell]

Hello @mUtterberg, I published my code on https://github.com/Mindiell/mynt3 in order to give you something. Now, I have to contact Anomareh in order to tell him/her what I did and if it could be pushed into original mynt.

PS: I continue on this discussion in order to not override your decisions on the other side ;o)

[willingc]

@mUtterberg I went ahead and archived the sponsors repo. cc/ @Mariatta

@Mindiell Thanks for letting us know about this project. Congrats.

I'm in favor of moving to Python 3 in the interim @mUtterberg using this port if all tests well. Long term, I think that a redo of the frontend and contributor access make sense.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days