prepare files for website#24
Conversation
|
This will put the documentation in some preliminary structure. Can be changed later. |
|
Thanks @floesche — merged. A couple of quick FYIs (no action needed unless you want to):
Let me know if you'd rather adjust either. |
|
Thanks @mbreiser. Re 1: I set the Re 2: I am currently ignoring README.md for the website and instead have them as "landing pages" when you go to the repository itself. I would usually create a separate landing page for the website. In my idea, the README.md would contain a condensed version of everything about the repository (or folder in your case) in one file, while a webpage landing page would guide the reader through the rest of the documentation pages. I recommend creating a separate |
Per Frank's review feedback on PR #24 (READMEs are repo-only landing pages; the unified docs site should have separate docs/<topic>.md guides), revert the front matter on patterns/README.md and add docs/patterns.md with equivalent content for the website. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
first steps for https://reiserlab.github.io/Modular-LED-Display/