Commit Graph

15 Commits

Author SHA1 Message Date
bc274c3d1b start adding my personal rules in a new patchset
* Cypher volatility
* Making recovery rolls in any order
* Wounds to be a narrative place for damage
2025-07-24 21:38:41 -05:00
28569236c3 have make copy the HTML output to a custom location 2025-07-23 11:21:44 -05:00
281a0acbe1 remove a lot of the OG extra content and similar references
these are things that are not included in the core commons version
because they're homebrew, because they are a lot of writing/creativity
that I don't feel comfortable stealing/distributing, or so on. most of
Old Gus's and the community's content is removed in order to have a
near-CSRD state

what remains is the rules clarifications, errata, splicing together some
information from secondary sources (like the Starter Set or from game
authors on Twitter), and organizational assists

things removed includes ideas that I like, but either plan to write my
own way in the future, or again I just don't feel comfortable copying
verbatim, especially if, for instance, I have my own process and don't
need to advocate for a different one

stuff that's likely to get folded into my core is arbitrarily numbered
300s instead of 000s
2025-07-23 11:17:49 -05:00
9fc2f76df3 write to HTML output with a custom template and style 2025-07-19 17:32:54 -05:00
5aeaedb169 base the project on OG-CSRD to try to stay maintained
if this branch makes it to core, it's because this was a far easier
thing to keep patches up to date with than having to hack the DOCX SRD
apart and back together again. naturally, I went through all of that
work and then CSRD updates happened and everything unraveled. this is
hopefully a better way to do things, by leaning on the existing
community's work

anyway, this creates the CCSRD based on the OG-CSRD and omits the
incorporeal-cms parts of this, since my project doesn't understand
Pandoc Markdown, but Pandoc does (naturally)
2025-07-19 15:53:10 -05:00
4a581e041f start running our patches against the new SRD and see where we get
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-06-19 00:05:44 -05:00
89a37f0421 don't echo the patch command now that I got info working
just for readability

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-05-07 08:07:16 -05:00
179d5c162a clean up how the website is built a bit
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 18:00:31 -05:00
71c50c340c slowly I am learning how to do Makefiles properly
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 17:20:18 -05:00
50fd495b2c replace non-breaking space characters with spaces
this is a formatting/publishing artifact that we don't need in the
Markdown, and the existence of those characters is throwing off some
other scripts

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 13:19:53 -05:00
7b15ed3c4c for the web, add a table of contents extension
this will need to be styled better (off on the side?), especially when
there are more levels to the TOC, but I can use this to test for now

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 11:02:37 -05:00
38984146cc add level 1 and level 2 headers
had to do this one by hand, at least parts of level 3 should be easier,
but I think some level 4 stuff will accidentally get 3ed. we'll see

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 10:28:16 -05:00
a681bd6d54 more Makefile scaffolding, automate building a website
this isn't the final form of how the web build has to work, by any
means, but I can test with it

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 08:47:14 -05:00
ec8bf0c2f3 modularize the Makefile a bit for testing
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-04 08:22:07 -05:00
3dd2bf61a3 scaffolding for patching the SRD
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2025-04-03 23:52:40 -05:00