Hello Sara & Rui,
I hope you’re doing well in these dark times…
Do you think it is possible, for each tutorial, to make appear:
- the date of publication of the article
- the date of last revision
… without it being too much work at your level (but I suppose the WordPress theme you use can be easily modified to make this information appear)?
It is often overlooked, but it is information that can be important, given the versions of hardware and software used and their possible obsolescence.
It’s just an idea, but if it seems too time-consuming, forget it!
Luckily we’re doing well. Sorry for taking so long to get back to you, but these last few days have been crazy for everyone!
We’ll be re-organizing all posts in the RNT blog and making the website easier to navigate.
There’s one reason to don’t use dates in our posts, it usually hurts the search engine results (because google think it’s outdated information).
The most important thing is that we try our best to have all our posts always updated and ensure that they work with the latest library versions.
Thanks again! Your feedback is highly appreciated.
Stay safe. Regards,
Hi Rui and thank you for your answer.
Okay, I get it.
However, you need to know that the publication and last modification dates of your articles are still injected in the header of the HTML page. For example, if I look at:
<meta property="article:published_time" content="2018-11-06T13:36:28Z" /> <meta property="article:modified_time" content="2019-04-02T10:23:17Z" />
Consequently, Google has access to this information. So, I don’t see how displaying them on the page, for us, your readers, is an obstacle to SEO.
It allows us to know when your last updates were made. I think it’s an important piece of information. And it makes it more accessible than having to inspect the HTML code of the page to get it.
iframe should be blocked. But not all HTML elements are dangerous! Moreover, the inclusion of some HTML elements, like
iframes, can be constrained by the plugin, which injects the sensitive HTML code itself. This is for example the case of many plugins to inject a YouTube video player. There are some very interesting and secure plugins that allow users to write their comments in Markdown. The plugin then takes care of the conversion to HTML, without taking any risks, by prohibiting the inclusion of certain HTML tags considered dangerous.
There is also the possibility to turn to the Discourse platform, which is a reference to manage a forum. But it seems to me that I already told you about it in another suggestion post.
I assume that you will choose the optimal solution for you, as well as for us 🙂
On the other hand, I’m about to finish a big tutorial that I would like to share with your community through the forum. I’ve tried to gather some experiments that answer to different problems I encountered lately during my discussions on the RNT Lab. So it’s a rather condensed tutorial that deals with a lot of subtleties on how to code things. I hope you and Sara won’t be opposed to me sharing it here. I can send you a link so you can read it before I release it on the forum.
Either way, I’ll abide by your wishes.
Well, I’m glad to know that you’re doing well.
Take good care of yourselves.