blog.davep.org/2023/07/05/the-switch-has-been-made.html
Preview meta tags from the blog.davep.org website.
Linked Hostnames
15- 14 links toblog.davep.org
- 3 links togithub.com
- 2 links togetpelican.com
- 1 link tobit.ly
- 1 link todavep.at
- 1 link toelisp.dev
- 1 link tofosstodon.org
- 1 link topypi.org
Thumbnail

Search Engine Appearance
The switch has been made
Well, it didn't take as long as I expected it to. Just yesterday morning I was giving Pelican a look over as a possible engine for generating my blog, having wanted to move away from Jekyll for a while now. Having tried it and liked what I saw to start with, I wrote about how I liked it and wondered how long it would take me to make the switch. By the evening I was making a proper effort to get the switchover started, and just a wee while earlier, before writing this post, the switch was made! The process of making the switch was roughly this (and keep in mind I'm coming from using Jekyll): Made a branch in the repo to work in. Removed all of the Jekyll-oriented files. Decided to set up Pelican and related tools in a virtual environment, managed using pipenv. Ran pelican-quickstart to kick things off and give me a framework to start with. Renamed the old _posts directory to content. Kept tweaking the hell out of the Pelican config file until it started to look "just so" (this is a process that has been ongoing, and doubtless will keep happening for some time to come). Tried out a few themes and settled on Flex; while not exactly what I wanted, it was close enough to help keep me motivated (while rolling my own theme from scratch would seem fun, I just know it would mean the work would never get done, or at least finished). Did a mass tidy up of all the tags in all the posts; something I'd never really paid too much attention to as the Jekyll-based blog never actually allowed for following tags. Went though all the posts and removed double quotes from a lot of the titles in the frontmatter (something Jekyll seems to have stripped, but which Pelican doesn't). Tweaked the FILE_METADATA to ensure that the slugs for the URLs came from the filenames -- by default Pelican seems to slugify the title of a post and this meant that some of the URLs were changing. All in all I probably spent 6 or 7 hours on making the move; a lot of that involving reading up on how to configure Pelican and researching themes. The rest of it was a lot of repetitive work to fix or tidy things. The most important aspect of this was keeping the post URLs the same all the way back to the first post; as best as I can tell I've managed that. So far I'm pleased with the result. I'm going to live with the look/theme for a wee while and see how it sits for me. I'm sure I'll tweak it a bit as time goes on, but at the moment I'm comfortable with how it looks.
Bing
The switch has been made
Well, it didn't take as long as I expected it to. Just yesterday morning I was giving Pelican a look over as a possible engine for generating my blog, having wanted to move away from Jekyll for a while now. Having tried it and liked what I saw to start with, I wrote about how I liked it and wondered how long it would take me to make the switch. By the evening I was making a proper effort to get the switchover started, and just a wee while earlier, before writing this post, the switch was made! The process of making the switch was roughly this (and keep in mind I'm coming from using Jekyll): Made a branch in the repo to work in. Removed all of the Jekyll-oriented files. Decided to set up Pelican and related tools in a virtual environment, managed using pipenv. Ran pelican-quickstart to kick things off and give me a framework to start with. Renamed the old _posts directory to content. Kept tweaking the hell out of the Pelican config file until it started to look "just so" (this is a process that has been ongoing, and doubtless will keep happening for some time to come). Tried out a few themes and settled on Flex; while not exactly what I wanted, it was close enough to help keep me motivated (while rolling my own theme from scratch would seem fun, I just know it would mean the work would never get done, or at least finished). Did a mass tidy up of all the tags in all the posts; something I'd never really paid too much attention to as the Jekyll-based blog never actually allowed for following tags. Went though all the posts and removed double quotes from a lot of the titles in the frontmatter (something Jekyll seems to have stripped, but which Pelican doesn't). Tweaked the FILE_METADATA to ensure that the slugs for the URLs came from the filenames -- by default Pelican seems to slugify the title of a post and this meant that some of the URLs were changing. All in all I probably spent 6 or 7 hours on making the move; a lot of that involving reading up on how to configure Pelican and researching themes. The rest of it was a lot of repetitive work to fix or tidy things. The most important aspect of this was keeping the post URLs the same all the way back to the first post; as best as I can tell I've managed that. So far I'm pleased with the result. I'm going to live with the look/theme for a wee while and see how it sits for me. I'm sure I'll tweak it a bit as time goes on, but at the moment I'm comfortable with how it looks.
DuckDuckGo
The switch has been made
Well, it didn't take as long as I expected it to. Just yesterday morning I was giving Pelican a look over as a possible engine for generating my blog, having wanted to move away from Jekyll for a while now. Having tried it and liked what I saw to start with, I wrote about how I liked it and wondered how long it would take me to make the switch. By the evening I was making a proper effort to get the switchover started, and just a wee while earlier, before writing this post, the switch was made! The process of making the switch was roughly this (and keep in mind I'm coming from using Jekyll): Made a branch in the repo to work in. Removed all of the Jekyll-oriented files. Decided to set up Pelican and related tools in a virtual environment, managed using pipenv. Ran pelican-quickstart to kick things off and give me a framework to start with. Renamed the old _posts directory to content. Kept tweaking the hell out of the Pelican config file until it started to look "just so" (this is a process that has been ongoing, and doubtless will keep happening for some time to come). Tried out a few themes and settled on Flex; while not exactly what I wanted, it was close enough to help keep me motivated (while rolling my own theme from scratch would seem fun, I just know it would mean the work would never get done, or at least finished). Did a mass tidy up of all the tags in all the posts; something I'd never really paid too much attention to as the Jekyll-based blog never actually allowed for following tags. Went though all the posts and removed double quotes from a lot of the titles in the frontmatter (something Jekyll seems to have stripped, but which Pelican doesn't). Tweaked the FILE_METADATA to ensure that the slugs for the URLs came from the filenames -- by default Pelican seems to slugify the title of a post and this meant that some of the URLs were changing. All in all I probably spent 6 or 7 hours on making the move; a lot of that involving reading up on how to configure Pelican and researching themes. The rest of it was a lot of repetitive work to fix or tidy things. The most important aspect of this was keeping the post URLs the same all the way back to the first post; as best as I can tell I've managed that. So far I'm pleased with the result. I'm going to live with the look/theme for a wee while and see how it sits for me. I'm sure I'll tweak it a bit as time goes on, but at the moment I'm comfortable with how it looks.
General Meta Tags
15- titleblog.davep.org – The switch has been made
- charsetutf-8
- X-UA-CompatibleIE=edge
- HandheldFriendlyTrue
- viewportwidth=device-width, initial-scale=1.0
Open Graph Meta Tags
7- og:site_nameblog.davep.org
- og:titleThe switch has been made
- og:descriptionWell, it didn't take as long as I expected it to. Just yesterday morning I was giving Pelican a look over as a possible engine for generating my blog, having wanted to move away from Jekyll for a while now. Having tried it and liked what I saw to start with, I wrote about how I liked it and wondered how long it would take me to make the switch. By the evening I was making a proper effort to get the switchover started, and just a wee while earlier, before writing this post, the switch was made! The process of making the switch was roughly this (and keep in mind I'm coming from using Jekyll): Made a branch in the repo to work in. Removed all of the Jekyll-oriented files. Decided to set up Pelican and related tools in a virtual environment, managed using pipenv. Ran pelican-quickstart to kick things off and give me a framework to start with. Renamed the old _posts directory to content. Kept tweaking the hell out of the Pelican config file until it started to look "just so" (this is a process that has been ongoing, and doubtless will keep happening for some time to come). Tried out a few themes and settled on Flex; while not exactly what I wanted, it was close enough to help keep me motivated (while rolling my own theme from scratch would seem fun, I just know it would mean the work would never get done, or at least finished). Did a mass tidy up of all the tags in all the posts; something I'd never really paid too much attention to as the Jekyll-based blog never actually allowed for following tags. Went though all the posts and removed double quotes from a lot of the titles in the frontmatter (something Jekyll seems to have stripped, but which Pelican doesn't). Tweaked the FILE_METADATA to ensure that the slugs for the URLs came from the filenames -- by default Pelican seems to slugify the title of a post and this meant that some of the URLs were changing. All in all I probably spent 6 or 7 hours on making the move; a lot of that involving reading up on how to configure Pelican and researching themes. The rest of it was a lot of repetitive work to fix or tidy things. The most important aspect of this was keeping the post URLs the same all the way back to the first post; as best as I can tell I've managed that. So far I'm pleased with the result. I'm going to live with the look/theme for a wee while and see how it sits for me. I'm sure I'll tweak it a bit as time goes on, but at the moment I'm comfortable with how it looks.
og:locale
en_US- og:urlhttps://blog.davep.org/2023/07/05/the-switch-has-been-made.html
Link Tags
13- alternatehttps://blog.davep.org/feeds/all.atom.xml
- alternatehttps://blog.davep.org/feed.xml
- icon/static/favicon.ico
- shortcut icon/static/favicon.ico
- stylesheethttps://fonts.googleapis.com/css2?family=Source+Code+Pro:ital,wght@0,400;0,700;1,400&family=Source+Sans+Pro:ital,wght@0,300;0,400;0,700;1,400&display=swap
Links
31- http://bit.ly/flex-pelican
- http://davep.at
- http://getpelican.com
- https://blog.davep.org
- https://blog.davep.org/2023/07/04/considering-pelican.html