I also added missing/broken logic to some templates, as well as [basic] SEO support to all pages — for articles, it automatically uses the first 80 characters of the content/summary. That could be improved in the future to use a hand-crafted description. Last, but certainly not least, huge thanks to @Pixelcode for joining in! Co-authored-by: vednoc <email@example.com> Co-authored-by: Pixelcode <firstname.lastname@example.org> Reviewed-on: Codeberg/blog#18 Co-authored-by: vednoc <email@example.com> Co-committed-by: vednoc <firstname.lastname@example.org>
|8 months ago|
|content||8 months ago|
|themes/codeberg||8 months ago|
|.gitignore||3 years ago|
|Makefile||8 months ago|
|README.md||1 year ago|
|pelicanconf.py||8 months ago|
|publishconf.py||2 years ago|
|tasks.py||8 months ago|
This repository is responsible for the publication of the Codeberg blog at https://blog.codeberg.org.
It is using Pelican - you can read more about it at https://blog.getpelican.com/
Like everything Codeberg, the blog is absolutely meant to be open for contributions! Feel free to write an interesting article or make changes to the design of the blog.
To contribute, just fork the repository using the Fork button of Codeberg. You can then clone the repository to your local machine, make, commit and push changes and finally create a Pull Request to this repository (If you are unfamiliar with the general git workflow, check out the Codeberg docs for help: https://codeberg.org/Codeberg/Documentation). As soon as your PR is merged, the blog will get updated with your content.
Content of the blog resides in content/ as Markdown (.md) files. You can add your own files and follow the workflow described above.
Make changes to the theme
The theme of the blog and content related to it can be found in themes/codeberg/ . You will find a dedicated README.md about technical aspects of the pelican theme.
You require pelican to build the blog. On many Linux distributions, there is already a package called 'pelican'. Try to install it with your local package manager, e. g. on Debian based distros
sudo apt install pelican. This is the recommended way as it will be easier to handle dependencies and updates.
If that was no success but you already have Python and pip installed, you can also issue
pip install pelican[Markdown]
in your terminal to install pelican to your machine. To install it globally, you require root access, you might need to add
sudo to the command above. You can learn more about Pelican installation at https://docs.getpelican.com/en/stable/install.html.
If you still need Python and Pip, refer to the Python and Pip docs on how to install it to your machine.
Local testing and development
To preview the changes you made (not necessary when writing articles but recommended when you make changes to the pelican setup), you can use the commands in the Makefile.
To build the pelican site to the path specified in the Makefile at
OUTPUTDIR (default: /var/www/blog.codeberg.org) run
pelican publish. If you don't want to set up a web server serving this directory, you can also run
pelican serve to serve the site locally at http://localhost:8000
In case that directory does not exist on your machine, you can create it or change the OUTPUTDIR to another path.
Blog articles inside the folder
content/ are licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0) if not stated otherwise inside the document or next to image files.