README: Scrap and write a new one in Markdown
ClosedPublic
Actions

Authored by ziaee on Fri, Nov 6, 5:38 AM.

Project Tags

None

Referenced Files

	F177558932: D61254.1794718235.diff
	Sat, Nov 14, 4:50 AM

	F177558665: D61254.1794717658.diff
	Sat, Nov 14, 4:40 AM

	F177552290: D61254.1794698493.diff
	Fri, Nov 13, 11:21 PM

	F177543824: D61254.1794675220.diff
	Fri, Nov 13, 4:53 PM

	F177531349: D61254.1794644651.diff
	Fri, Nov 13, 8:24 AM

Subscribers

Details

Reviewers

Group Reviewers

docs
doceng

Commits

Summary

I do not want to duplicate information, but we need something.
I think this covers the bases without making people tl;dr.

Event: FreeBSD 2026 Vendor Summit

Repository

R9 FreeBSD doc repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

ziaee requested review of this revision.Fri, Nov 6, 5:38 AM

ziaee created this revision.

I wrote this to look good on a numbered 80x25 console as well as the rendering on phorges with a phone web browser, such as https://ron-dev.freebsd.org/FreeBSD/doc . I have an old one up at https://github.com/concussious/freebsd-doc , but since then I added the bit about sending us pings based on the talk today by @amy.vargas_netapp.com

README.md
19	Typo

For me it's ok, thank you

This revision is now accepted and ready to land.Fri, Nov 6, 6:38 AM

It doesn't address all Amy's concerns but it is good enough per se.

Nice stuff! Two comments, neither blocking at all.

README.md
10–11	At least it requires a semicolon, not a comma :)
33–34	It seems like `## Translations` could become its own subsection with brief pointers to the relevant materials (follow-up change).