Nikola – static site generator

On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v8.1.1. This release is mainly due to an incorrect PGP key being used for the PyPI artifacts; three regressions were also fixed in this release. What is ... [More] Nikola? Nikola is a static site and blog generator, written in Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown — and can even turn Jupyter Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads Install using pip install Nikola. Changes Bugfixes Default to no line numbers in code blocks, honor CodeHilite requesting no line numbers. Listing pages still use line numbers (Issue #3426) Remove duplicate MathJax config in bootstrap themes (Issue #3427) Fix doit requirement to doit>=0.32.0 (Issue #3422) [Less]

On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v8.1.0. This release makes a few feature changes, improvements, and fixes a few bugs. What is Nikola? Nikola is a static site and blog generator, written in ... [More] Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown — and can even turn Jupyter Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads Install using pip install Nikola. Changes Features Support posts without titles (Issue #3408) Support WebP image scaling (Issue #3399) Use Luxon instead of Moment for fancy dates to make it more lightweight, going from 328k to 68k (Issue #3232) New nikola console -s script.py option to run scripts that access your site (Issue #3385) Allow preview images to be relative to posts for bootblog4 featured posts Change the listings formatting to support word wrap with line numbers and improve appearance Put the current language’s feed links first so that feed readers prefer it (Issue #3248) Added support for default preview image for posts (Issue #3326) Added support for thumbnails in gallery lists (Issue #1771) Bugfixes Support directory names in REDIRECTIONS (Issue #3421) Return a non-zero error code when nikola github_deploy fails Refactored scale_image causing performance increasing in image resizing. Don’t force absolute links for brand/languages (Issue #3229) Fix RTL mirroring in base theme (:dir() pseudo-class is Firefox only) (Issue #3353) Work around Bootstrap 4 alignment bug for RTL languages (Issue #3353) Handle multiple level of inherit/import nesting in Mako templates correctly (Issue #3349) Output a more informative error when files are missing due to broken symlinks or incorrect TRANSLATIONS_PATTERN values Avoid installing tests package to site-packages, remove it from your environment if it was inadvertently added (Issue #3348) Sometimes hyphenation added hyphens at the beginning of words (Issue #3362) Mark gallery images as "dirty" if EXIF configuration changes (Issue #3357) Fix regression in gallery titles being "index" if there was a index.txt and no title (Issue #3360) Make gallery indexes depend on destination images to avoid multithreading race condition (Issue #3361) Mark gallery thumbnails as lazy loading (Issue #2918) Don't consider JPEG images with EXIF thumbnails as animated (Issue #3332) Use correct language for hyphenation in posts that are not translated to all languages (Issue #3377) Internal Added Post.source() method to get a Post's object unprocessed contents. Added Post.save() method to modify Post contents. Made is_two_file a property that uses save() [Less]

On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v8.1.0. This release makes a few feature changes, improvements, and fixes a few bugs. What is Nikola? Nikola is a static site and blog generator, written in ... [More] Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown — and can even turn Jupyter Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads Install using pip install Nikola. Changes Features Support posts without titles (Issue #3408) Support WebP image scaling (Issue #3399) Use Luxon instead of Moment for fancy dates to make it more lightweight, going from 328k to 68k (Issue #3232) New nikola console -s script.py option to run scripts that access your site (Issue #3385) Allow preview images to be relative to posts for bootblog4 featured posts Change the listings formatting to support word wrap with line numbers and improve appearance Put the current language’s feed links first so that feed readers prefer it (Issue #3248) Added support for default preview image for posts (Issue #3326) Added support for thumbnails in gallery lists (Issue #1771) Bugfixes Support directory names in REDIRECTIONS (Issue #3421) Return a non-zero error code when nikola github_deploy fails Refactored scale_image causing performance increasing in image resizing. Don’t force absolute links for brand/languages (Issue #3229) Fix RTL mirroring in base theme (:dir() pseudo-class is Firefox only) (Issue #3353) Work around Bootstrap 4 alignment bug for RTL languages (Issue #3353) Handle multiple level of inherit/import nesting in Mako templates correctly (Issue #3349) Output a more informative error when files are missing due to broken symlinks or incorrect TRANSLATIONS_PATTERN values Avoid installing tests package to site-packages, remove it from your environment if it was inadvertently added (Issue #3348) Sometimes hyphenation added hyphens at the beginning of words (Issue #3362) Mark gallery images as "dirty" if EXIF configuration changes (Issue #3357) Fix regression in gallery titles being "index" if there was a index.txt and no title (Issue #3360) Make gallery indexes depend on destination images to avoid multithreading race condition (Issue #3361) Mark gallery thumbnails as lazy loading (Issue #2918) Don't consider JPEG images with EXIF thumbnails as animated (Issue #3332) Use correct language for hyphenation in posts that are not translated to all languages (Issue #3377) Internal Added Post.source() method to get a Post's object unprocessed contents. Added Post.save() method to modify Post contents. Made is_two_file a property that uses save() [Less]

On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v8.1.0. This release makes a few feature changes, improvements, and fixes a few bugs. What is Nikola? Nikola is a static site and blog generator, written in ... [More] Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown — and can even turn Jupyter Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads Install using pip install Nikola. Changes Features Support posts without titles (Issue #3408) Support WebP image scaling (Issue #3399) Use Luxon instead of Moment for fancy dates to make it more lightweight, going from 328k to 68k (Issue #3232) New nikola console -s script.py option to run scripts that access your site (Issue #3385) Allow preview images to be relative to posts for bootblog4 featured posts Change the listings formatting to support word wrap with line numbers and improve appearance Put the current language’s feed links first so that feed readers prefer it (Issue #3248) Added support for default preview image for posts (Issue #3326) Added support for thumbnails in gallery lists (Issue #1771) Bugfixes Support directory names in REDIRECTIONS (Issue #3421) Return a non-zero error code when nikola github_deploy fails Refactored scale_image causing performance increasing in image resizing. Don’t force absolute links for brand/languages (Issue #3229) Fix RTL mirroring in base theme (:dir() pseudo-class is Firefox only) (Issue #3353) Work around Bootstrap 4 alignment bug for RTL languages (Issue #3353) Handle multiple level of inherit/import nesting in Mako templates correctly (Issue #3349) Output a more informative error when files are missing due to broken symlinks or incorrect TRANSLATIONS_PATTERN values Avoid installing tests package to site-packages, remove it from your environment if it was inadvertently added (Issue #3348) Sometimes hyphenation added hyphens at the beginning of words (Issue #3362) Mark gallery images as "dirty" if EXIF configuration changes (Issue #3357) Fix regression in gallery titles being "index" if there was a index.txt and no title (Issue #3360) Make gallery indexes depend on destination images to avoid multithreading race condition (Issue #3361) Mark gallery thumbnails as lazy loading (Issue #2918) Don't consider JPEG images with EXIF thumbnails as animated (Issue #3332) Use correct language for hyphenation in posts that are not translated to all languages (Issue #3377) Internal Added Post.source() method to get a Post's object unprocessed contents. Added Post.save() method to modify Post contents. Made is_two_file a property that uses save() [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]

In this guide, we’ll set up GitHub Actions to rebuild a Nikola website and host it on GitHub Pages. Why? By using GitHub Actions to build your site, you can easily blog from anywhere you can edit text files. Which means you can blog with only a web ... [More] browser and GitHub.com. You also won’t need to install Nikola and Python to write. You won’t need a real computer either — a mobile phone could probably access GitHub.com and write something. Caveats The build might take a couple minutes to finish (1:30 for the demo site; YMMV) When you commit and push to GitHub, the site will be published unconditionally. If you don’t have a copy of Nikola for local use, there is no way to preview your site. What you need A computer for the initial setup that can run Nikola. You can do it with any OS (Linux, macOS, *BSD, but also Windows). A GitHub account (free) Setting up Nikola Start by creating a new Nikola site and customizing it to your liking. Follow the Getting Started guide. You might also want to add support for other input formats, namely Markdown, but this is not a requirement. After you’re done, you must configure deploying to GitHub in Nikola. There are a few important things you need to take care of: Make your first deployment from your local computer and make sure your site works right. Don’t forget to set up .gitignore. The GITHUB_COMMIT_SOURCE and GITHUB_REMOTE_NAME settings are overridden, so you can use values appropriate for your local builds. Ensure that the correct branch for GitHub Pages is set on GitHub.com. If everything works, you can make some change to your site (so you see that rebuilding works), but don’t commit it just yet. Setting up GitHub Actions Next, we need to set up GitHub Actions. This is really straightforward. On your source branch, create a file named .github/workflows/main.yml with the following contents: github-workflow.yml (Source) on: [push] jobs:   nikola_build:     runs-on: ubuntu-latest     name: 'Deploy Nikola to GitHub Pages'     steps:     - name: Check out       uses: actions/checkout@v2     - name: Build and Deploy Nikola       uses: getnikola/nikola-action@v2 There might be a newer version of the action available, you can check the latest version in the getnikola/nikola-action repo on GitHub. By default, the action will install the latest stable release of Nikola[extras]. If you want to use the bleeding-edge version from master, or want to install some extra dependencies, you can provide a requirements.txt file in the repository. Commit everything to GitHub: git add . git commit -am "Automate builds with GitHub Actions" Hopefully, GitHub will build your site and deploy. Check the Actions tab in your repository or your e-mail for build details. If there are any errors, make sure you followed this guide to the letter. [Less]