@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

Hum, weird, inline HTML check should have been disabled. I will look into this.

@wusatosi , what should I do here?

I didn't change these lines. And I want to keep them! (collapsable menus in docs).

Hum, weird, inline HTML check should have been disabled. I will look into this.

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

No. lint break is caused by changed lines.

Avoid fighting with markdownlint with ignore statements, ignore should be the last resort.

Put faith into the linting infrastructure, let's not have our code littered with lint-ignores.

I agree with any solution which can work right now. So what should I do if the CI complains the line is too long? And I actually want to insert a text with hyperlink? (The text is short, the hyperlink is long).

Currently, the infrastructure seems to not consider this case. If this is true, it should be solved in other issue/PR.

OK. Then I will proceed with the PR, as this behaviour is not from changed lines.

No. lint break is caused by changed lines.
Avoid fighting with markdownlint with ignore statements, ignore should be the last resort.
Put faith into the linting infrastructure, let's not have our code littered with lint-ignores.

I agree with any solution which can work right now. So what should I do if the CI complains the line is too long? And I actually want to insert a text with hyperlink? (The text is short, the hyperlink is long).

Currently, the infrastructure seems to not consider this case. If this is true, it should be solved in other issue/PR.

It looks like markdown lint ignores length overflow due to url via []().

It looks like markdown lint ignores length overflow due to url via []().

@wusatosi , would you agree with current PR state? Check rendered version.

@wusatosi , can you take a look?

It looks like markdown lint ignores length overflow due to url via []().

@wusatosi , would you agree with current PR state? Check rendered version.

Hey sorry I missed this PR.
Is it possible to just use a generic table to format this?

Also, since the image is not in the table, why not just use the markdown facility for image embedding over <img>?

Edit: agh, I see, it takes the entire page.

Also, I think you should reference the direct asset link.

Instead of the github link . The link you provided does not get displayed correct everywhere.

Or you should add raw=true to the end of the github link. See: this stackoverflow post.

e.g. in visual studio/ our codespace environment

I do want to point out that "under development and not yet ready for production use." does not have good visibility on a 100% zoom view.

And is invisible on your own screenshot.

Edit: there is readability issue on mobile as well.

Why not, instead of putting this cute logo on the front, we just put a badge here. e.g.

# beman.exemplar: A Beman Library Exemplar

![Beman lifetime status: Under development](https://img.shields.io/badge/Beman%20lifetime-under%20dvelopment-blue)
![Continuous Integration Tests](https://github.com/bemanproject/exemplar/actions/workflows/ci_tests.yml/badge.svg)
![Lint Check (pre-commit)](https://github.com/bemanproject/exemplar/actions/workflows/pre-commit.yml/badge.svg)

`beman.exemplar` is a minimal C++ library conforming to [The Beman Standard](https://github.com/bemanproject/beman/blob/main/docs/BEMAN_STANDARD.md).
This can be used as a template for those intending to write Beman libraries.
It may also find use as a minimal and modern  C++ project structure.

This is a lot cleaner, there's no readability issue and weird formatting, its dense and easy to glance over.
Its all native markdown, should work across all markdown renders/ linters.

See: my alternative with badge

We could still put the cute logo in a later section to allow branding and a more detailed write out.

If we still want the logo, would this be a better altnerative? See this as an example

Note: We could still add Status below the implementation back. As this would violate [README.LIBRARY_STATUS]

Concern regarding the readability.

We can proceed without the icon for now and move the discussion to discourse.

https://discourse.bemanproject.org/t/readability-concern-with-the-new-beman-lifetime-notation/301

@wusatosi , check latest status of this PR.

I proposed to put this 4 SVGs in the beman docs: https://github.com/bemanproject/beman/pull/84/files.

Concern regarding the readability.
We can proceed without the icon for now and move the discussion to discourse.
https://discourse.bemanproject.org/t/readability-concern-with-the-new-beman-lifetime-notation/301

@wusatosi , check latest status of this PR.

I proposed to put this 4 SVGs in the beman docs: https://github.com/bemanproject/beman/pull/84/files.

This is fantastic, thank you for all these work.