Adding a Fediverse Share Button to my Emacs Nikola Blog
Just to get extra meta, I published this blog post, then shared it to my #Fediverse account by clicking the "Fediverse Share Button" and writing these words you're reading right now.
Next I will grab the article ID of this toot, and rebuild and redeploy, so that when (if?) anyone replies to this toot, their replies will appear in the "Comments" section of my blog!
100% static site, written in Emacs, built and deployed using Nikola.
Do you enjoy the articles you see from Linux Magazine? Support from readers has kept us going for 24 years. We are committed to bringing you trusted content from real-world experts. Learn how you can support our work and keep us publishing for another 20+ years! https://www.linux-magazine.com/Support-Our-Work #Linux#OpenSource#tutorials#FOSS
I really hate the trend that #documentation is no longer written but the details are in video #tutorials, especially in #gamedev. I want to READ documentation, with graphics and explanation. On long pages with varying degrees of details. Not some obscure 50min video where I can find the missing piece of information in a single frame at minute 34. #unreal#ue5
🚨 Deadline Extension - The deadline for Workshops, Tutorials, and BoF submissions for US-RSE’24 have been EXTENDED to Monday, April 1! Consider submitting your ideas! #usrse24#rse#submissions#tutorials#workshops#bofs
This is so much better than our first #videoTest, and more what I had in mind when it comes to our #vectorArt in the framework of Inkscape #tutorials.
Hopefully, #MastoArt & #FediArt followers are more interested in #Inkscape, this time. Of course that's among our main reasons to make videos in the first place, not just selfish promotion. Every time one of our videos will turn an #Adobe#Illustrator user into an @inkscape artist, we are promoting #FreeSoftware successfully.
#APIs#APIDocumentation#Tutorials#TechnicalWriting#SoftwareDocumentation#SoftwareDevelpment: "The best tutorials present information that helps consumers fulfill a use-case scenario that feels real and meaningful. Instead of coming up with a made-up use-case, you can research what are the things your API consumers would want to do. Then, create tutorials that teach how to achieve those results with your API. The goal of the tutorial is to educate readers on how they can use your API—or some of its operations—to get their job done.
So, what are the elements that a good API tutorial should have? Let's look at some of the most important ones:"
Today, I had a work meeting with a young but eager fellow. We had a chat, I explained a few things, and he agreed with the technical choices I suggested. However, the issue arose when I mentioned writing a few lines of a "tutorial" on how to do certain things. His response: "Can't you make a video?" Surprised (but not too much), I argued that in my opinion, a concise written tutorial is more practical than a pointless video. His reply: "We only watch videos now, even my colleagues look up solutions on YouTube." This is despite the wealth of excellent tutorials on StackExchange and various blogs. I wonder: why waste half an hour watching a video that could be summarized in a few lines of text (saving time for both the producer and the user)?
I linked myself with my #wordpress blog and even though I post on the blog, I never get notifications even though I tried to follow. When I look it says Follow requested, but from the wordpress site, I can't see anyway to let a mastodon person follow me.
I got one follow early on during testing, but now when I view my site it says that it has no followers.
Are there any #tutorials for managing mastodon from wordpress?
Migrating from a site to Wordpress. We have custom importers working very nicely, but, we are really struggling to fully understand the new Gutenberg blocks. It appears that NASA in their new website had a similar lack of docs.
My question to all Mastodonians… where is some really good current up-to-date docs/tutorials on understanding and using the power of the Gutenberg blocks?
The entries are grouped by category or application domain and include coverage at all skill levels, from basic to advanced. Within categories the entries are sorted alphabetically by title.
I so often get annoyed with #CSS#tutorials whose half of the code is variables, just to reduce redundancy. They would be much quicker to understand in pure CSS. If I need a value just barely twice, I'd rather write "0.3s" twice instead of "var(--blah-motion-duration)". What the fuck? You don't need to show off that you understand #CustomProperties.