Blog posts, announcements, videos (and other sections with tags and categories) should unify naming and grouping.

Right now (especially blog posts) are "randomly" added to categories. I believe this should be updated and unified, e.g., for easier usage like on /pmemstream: https://pmem.io/pmemstream#blog-entries

We may easily point to all posts/announcements/videos/... on selected microsties.

When the unification is done, we should also update the archetypes with proposed categories... or maybe we should list somewhere what's proposed (e.g. in README or in CONTRIBUTING files).

Add links to GitHub for authors of the content. Right now we only state the author by their name. We could also add a link to GH profiles, based on a login delivered as a separate metadata, e.g., in blog content.

# Blog post creation date
date: 2022-01-26

# Blog post author and GH link
author: "Łukasz Stolarczuk"
gh-link: lukaszstolarczuk

I believe this would be a nice addition and could make a way for readers to contact us easier.

It applies to all archetypes, which inform about the content's user.

Our FAQ page is rather empty. Perhaps we should make more out of it, so if the user asks a repeated question, we could just link them here for a well-written, ready answer.

https://pmem.io/faq/

Events section in the Community page (https://pmem.io/community/) is full of "lorem ipsum" 😉 even though the Events page is properly filled with data (https://pmem.io/events/).

Error:

hugo v0.92.1+extended linux/amd64 BuildDate=unknown
ERROR 2022/02/17 07:51:47 Page.Dir is deprecated and will be removed in Hugo 0.93.0. Use .File.Dir

Page.Dir occurs here:

./layouts/shortcodes/manpages.html:3:{{ $.Scratch.Add "dir" $.Page.Dir }}

Try to use the search button at the top of the webpage.
In result, I got the following message:

Search results
Unable to execute your query. Ensure that a valid subscription key has been set up for your instance.

On the pmemkv's manpage, there are no links to other manpages available for selected release. It should be done using layouts/shortcodes/manpages.html script available in the repository. This script perhaps requires some modifications to work properly with pmemkv.

Usage example:
{{< manpages >}}
see e.g. here:
https://github.com/pmem/pmem.github.io/blob/main/content/pmdk/manpages/linux/master/libpmem/libpmem.7.md

Other thing to check is missing metadata in pmemkv's manpages - header: "..."
or additional (perhaps redundant) layout: "library".

I believe we may update the link on the Developer Hub (tools section, down below) to point to our version of valgrind instead of the upstream one. We may update the content of the valgrind section to inform users it's our fork (with pmemcheck support).
Pmemcheck is listed as a separate tool, so maybe their description could be updated (for a clear statement what is what 😉 ).

The content of valgrind's microsite (https://pmem.io/valgrind) could also mention it's a fork + a link to the upstream repo.

Each new repository that would like to have a separate microsite (sub-page) is required to write single.html and lists.html views. We should probably define a new content view "library", re-name/remove existing views, and most likely, unify 'single' view for all our microsites (required for articles/manpages/...).

We have to copy-paste now, quite a lot of content for a new library's microsite.

Perhaps it'd be also possible to create a new archetype to simplify creation of a new microsite.

Our web sites, built from forks do not work 100% properly - links ref to "pmem.io" instead of "myfork.github.io", which is not ideal for testing and providing a preview (for review, on PR). It's because of hardcoded baseURL in our config.toml and CNAME (?).

Ref. to the discussion in PR: #181 (comment) and mentioned there a link with a proposed solution:
rstudio/blogdown#412

Describe the bug
Update blog post with TieredMemDB name:
https://pmem.io/blog/2020/09/memkeydb-redis-with-persistent-memory/

How often is the bug experienced?
Always

Bug Severity
Based on the frequency and how it impacts you and others, do you consider the issue to be high, medium, or low severity?

• High
• Medium
• Low

Website URL
https://pmem.io/blog/2020/09/memkeydb-redis-with-persistent-memory/

We may, most likely, want to update the Developer Hub, to avoid looking for, e.g., 'RPMA' within PMDK section. I believe we should have a separate section for all repositories independent from PMDK repository.

Some of the descriptions within the PMDK page should probably be also updated with more/up-to-date content.

Perhaps repositories that will move out (to a separate sub-page with a link in Dveloper Hub) should be removed or just clearly stated that they are not part of the PMDK repo (links for backward compatibility would be nice - there is a possibility to specify
a link to a section within PMDK web page).

Describe the bug
Some links on pmem.io doesn't follow to any page.

To Reproduce

1. install broken-link-checker
2. run it against pmem.io

blc --exclude glossary -ro https://pmem.io

Log
broken_links.log

Additional context

• broken-link-checker returns some false positives, especially for external links with redirection.
• On my machine, check for glossary page takes long, that's why I excluded it.
• It may be useful to create weekly CI job to check links.

The description has a typo with the word functionality:

... With this functionality ...

NDCTL microsite is not displayed with proper styling (missing css/layout):
https://pmem.io/ndctl/

A vast of manpages on our website does not provide an easy transfer to other manpages - A.K.A. clickable links.

For PMDK (and other repos), perhaps this could be resolved at the moment of generating web content (it's done, e.g., in "auto doc update script": https://github.com/pmem/pmdk/blob/master/utils/docker/run-doc-update.sh).

It includes at least manpages for PMDK, RPMA, pmemkv.

You may see html tags in code snippets in blog posts e.g.:

• https://pmem.io/blog/2021/09/concurrency-considerations-in-libpmemobj-cpp/
• https://pmem.io/blog/2020/10/api-overview-of-pmemkv-java-binding/
• https://pmem.io/blog/2019/02/c-persistent-containers-vector/
• https://pmem.io/blog/2019/06/multi-level-vmemcache/
• https://pmem.io/blog/2019/10/c-standard-limitations-and-persistent-memory/
• https://pmem.io/blog/2020/05/introduction-to-llpl/

iPage should be Page

Describe the bug
Developer Hub -> MemKind link should be renamed to "Memkind" (without capital K)

How often is the bug experienced?
Always

Bug Severity
Based on the frequency and how it impacts you and others, do you consider the issue to be high, medium, or low severity?

• High
• Medium
• Low

Website URL
https://pmem.io/blog/

To Reproduce
Steps to reproduce the behavior:

1. Go to Developer Hub
2. See "MemKind" instead of "Memkind"

Sub-page: https://pmem.io/solutions/ contains 2 links to VTune in utilities section.

Some blog posts contain code snippets and they (sometimes) do not look well. Some of them become quite unreadable.
Example of bad snippets: https://pmem.io/blog/2017/07/using-standard-library-containers-with-persistent-memory/

I believe it includes, at least:

• wrong parsing of a '*' char,
• wrong language coloring,
• improper var names and broken comments.

1. https://pmem.io/vmem/libvmem/ looks really bad.
2. libvmem is mentioned in data/releases_*.yml till 1.12 where it is not released for quite some time.

It would be best to display all/recent blog posts (or announcements, videos, tutorials, ...) related to a selected project.
For example, instead of just adding a link to the category "pmemstream" on its microsite (https://pmem.io/pmemstream#blog-entries), it'd be better to display the most recent blog posts (as thumbnails) with the link to other related posts.

It should be done similarly to, e.g., "News and announcements" section on the home page.

It applies to (at least): PMDK, pmemkv, memkind, libpmemobj-cpp, pmemstream

Describe the bug
In "Developers Hub" there is a link to "MemKeyDB" project. It should be replaced with a link to TieredMemDB (https://tieredmemdb.github.io/TieredMemDB/)

How often is the bug experienced?
Always

Bug Severity
Based on the frequency and how it impacts you and others, do you consider the issue to be high, medium, or low severity?

• High
• Medium
• Low

Website URL
https://pmem.io/

To Reproduce
Steps to reproduce the behavior:

1. Click on 'Developers Hub'
2. See link to "MemKeyDB" instead of TieredMemDB (https://tieredmemdb.github.io/TieredMemDB/)

We could add line numbering for code snippets/highlighting as default param in hugo.

Right now, because of using syntax, e.g. like:

```c++

we lose line numbering. We can make it appear by using syntax like:

{{< highlight C "linenos=table" >}}
{{< /highlight >}}

But then the code highlighting does not work well in IDE (at least in mine 😉 ).

ref. #270

On the Solutions page, the 'Share' button in the "Show your work" section should point to the Issues page on this GitHub repo with a template. Currently, it points at the main https://pmem.io URL.