Ready to setup your location’s website? Great!
Please DO NOT purchase your own separate domain!
We will easily setup a subdomain on the
pyladies.com site for you (e.g.
nyc.pyladies.com). It’s also possible if you’d prefer to use the
pyladies.org namespace (e.g.
nyc.pyladies.org). We can also do
pyladies.org/nyc too. Your choice!
If you are in a location that frequently uses other TLDs, e.g.
.co.uk, please contact our domain administrators listed above.
You have two options: a Static Website website, or a Dynamic Website website. Whichever you prefer! And you can switch over any time. It may be easier/quicker for you to start with a static website - then create a dynamic website when you have more time.
www.pyladies.com site is set up). It’s great if you don’t want a database or server-side logic; it’s really easy to maintain.
There are plenty of PyLadies locations that have simple static websites. Here are a couple:
If you’re interested in the various static website tools out there, check out Tools.
To setup your static website:
Fork the pyladies/pyladies repository to your own (or your local PyLadies) GitHub account.
Locally clone your fork of the repository.
Create a directory within the main
pyladiesfolder of the repository (on the same directory level as
wwwand the other subdomains.)
Develop the website within your new directory.
Be sure to add a
README.mdfile that explains how to create the HTML files if you are using a static site generator (like here).
Commit the code locally, and push it up to your fork.
Make a pull request against the
When making a pull request, please squash all your commits into one commit! We like a clean history! Here’s a good how-to on git rebase to squash commits.
In your pull request - please include the desired subdomain namespace - e.g.
You can hand-write all your HTML files, but that’s a bit of a pain. Here are a list of tools that can help create your static website for you:
You write the content of your site in Markdown format, design the layout and organization of the site (e.g. how the content will be presented) using Jinja2 templates (another Python library), and edit/create your own themes with CSS. Running
mynt gen over your Markdown & CSS files and Jinja2 templates will create static HTML files that you can then view via the
mynt serve command.
Pelican does offer a bigger user base than mynt, and therefore has many plugins and themes already setup to use.
Other Python Static Site Generators¶
Some others if you’re curious:
Other Non-Python Static Site Generators¶
It’s totally okay to use a non-Python package(s) to help make your website. Here’s a list of common & widely-used ones:
There are a few PyLadies locations that have built their own dynamic websites. Here are a couple:
If you’re interested in the various dynamic website frameworks out there, check out Frameworks.
To setup your dynamic website:
Create your own git repository (ideally under your local PyLadies GitHub account, registered under your
Create your website.
When you’re ready to deploy, ping the domain admins (above). They will set up your PyLadies email address to an admin-managed Heroku app (which will give your PyLadies complete access for deployment) as well as setup all the DNS records needed.
Log into your Heroku account and follow the instructions for deploying (available under newly-created application that the admins made).