I don't have to do that for the English blog posts but if I am going to follow a pattern it is better to apply in all blog posts. That is too much, it is easier for me to set the URL for each post: title: "Something" And what if I move out from Netlify? I would have to follow the other server configuration to redirect. There would be too much pain to create a redirect file. If you just create a filename content/posts/-something.en.md the URL will be and a filename content/posts/ will be I don't have any blog post with a language prefix, because the URL is already a translation. (4) And because of that I had other issue with the URLs: How-to-import-imdb-database-using-csvkit: "en"Īnd I wrote my own code to link them together.īut hugo detects the translation based on filename, for that example to work I had to rename the files like: content/posts/Ĭontent/posts/-how-to-import-imdb-database-using-csvkit.en.md como-importar-imdb-usando-csvkit: "pt-br" I am using shortcodes! Just create a partial in layouts/shortcodes/tldr.html ( tldr can be any name): If I switch theme and have to change the css or something I will be in trouble, besides I never put much effort in making that thing “beautful” because I would have to copy over and over. I have to copy and paste that whole thing (except the content, of course), over and over again. I have in a lot of blog posts with something like: * * * (3) Later on I found about shortcodes to make the md files DRYer. It is the best thing since sliced bread □. When I migrated from Jekyll to Middleman I had these changes: The current API is using OpenApi Specification, but I feel like we can add more content. I only migrated from Middleman to Hugo because I am planning to better document one API. Of course I always wanted to test the fastest static website generator □.īut things with middleman were good.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |