git clone [email protected]:tijptjik/thegodsproject.git && cd thegodsproject
git submodule update --init --recursive
conda env create -n thegodsproject -f environment.yml
source activate thegodsproject
NOTE : You should always run source activate thegodsproject when running the pelican project locally as it activated the conda environment with all the python dependencies in it.
thegodsproject
|-- content # Markdown posts for the blog
| `-- extra # Misc files - explicitly mapped to output in pelicanconf.py
|-- develop_server.sh
|-- environment.yml # Conda Environement with Python Dependencies
|-- nest # theme
| `-- static # CSS and fonts
| `-- templates # HTML jinja templates
|-- Makefile # Make Tasks
|-- pelicanconf.py # Main config
|-- plugins # Submodules - don't edit
|-- publishconf.py # Config file with additional settings for production
`-- readme.md # You are hereSo based on the project structure, the config is managed by :
pelicanconf.pypublishconf.py
Site development isdone following the conventions for Pelican themes which uses Jinja for its templates`.
The Jinja templates are located at nesttemplates. Inspect the following three Jinja templates to get an idea of the site structure:
nest/templates/base.html # All pages should extend the base template
nest/templates/index.html # The landing page
nest/templates/article.html # Basis for all articlesFrom the project root
make htmlmake regenerate./develop_server.sh start # generate & run server
./develop_server.sh stop # stop backgrounded server
# or
make devservermake github