Add new site

.github/workflows/pelican.yml

@@ -0,0 +1,19 @@
+name: Pelican site CI
+
+on:
+  # Trigger the workflow on push or pull request,
+  # but only for the main branch
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - uses: bimbimprasetyoafif/pelican-simple@v1
+      env:
+        GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.gitignore

@@ -0,0 +1,160 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

content/2023-10-22--novo-site.md

@@ -0,0 +1,69 @@
+title: Novo site do PyLadies São Carlos
+description: Documentação do novo site do PyLadies São Carlos
+modified: 2023-10-22
+category: site
+tags: site
+author: Juliana Karoline de Sousa 
+
+## Motivação
+O site original do PyLadies São Carlos foi criado em 2015, e desde então não havia sido atualizado.
+A ideia desse projeto é atualizar o site, tornando-o mais moderno e com uma aparência mais profissional.
+
+## Tecnologias utilizadas
+### [Pelican](https://getpelican.com/)
+Pelican é um gerador de sites estáticos escrito em Python. Ele utiliza o Markdown para escrever os posts e o Jinja2 para os templates.
+
+## Como rodar o projeto
+1. Clone o repositório
+```bash
+$ git clone https://github.com/pyladiessanca/pyladiessanca.github.io.git
+```
+2. Entre na pasta clonada
+```bash
+$ cd pyladiessanca.github.io
+```
+3. Crie um ambiente virtual
+```bash
+$ python -m venv .venv
+```
+4. Ative o ambiente virtual
+```bash
+$ source .venv/bin/activate
+```
+5. Instale as dependências
+```bash
+$ python -m pip install .
+```
+6. Rode o servidor
+```bash
+$ pelican --listen
+```
+7. Acesse o site em http://localhost:8000
+
+Caso crie um arquivo, rode o comando `pelican content` para gerar o HTML e atualizar o site.
+
+## Como contribuir
+1. Faça um fork do repositório
+2. Crie uma branch para o seu post
+```bash
+$ git checkout -b meu-post
+```
+3. Escreva o seu post utilizando Markdown e coloque-o na pasta `content`
+Atente-se para utilizar a convenção de nomenclatura `AAAA-MM-DD--nome-do-post.md`
+4. Coloque no começo do seu arquivo as seguintes informações:
+```
+title: Título do seu post
+description: Descrição do seu post
+modified: AAAA-MM-DD
+category: categoria
+tags: tags
+```
+3. Faça o commit das suas alterações
+```bash
+$ git commit -m 'meu post'
+```
+4. Faça o push para a sua branch
+```bash
+$ git push origin --set-upstream meu-post
+```
+5. Abra um Pull Request no repositório original