Closed avivace closed 2 years ago
(for reference: the CowBiteSpec was allowed for use here https://github.com/gbdev/gbadoc/issues/1#issuecomment-817118343)
I'd like to use CowBiteSpec as starting point, splitting in single files (per article/topic) and starting to improve and work on that baseline
Since neither me or avivace are expecting to get an answer from Martin about GBATEK, and no other reference was brought up, I think we can considered this settled?
Since neither me or avivace are expecting to get an answer from Martin about GBATEK, and no other reference was brought up, I think we can considered this settled?
Worst case we can add stuff fom gbatek later. I'd start importing CowBiteSpec here (but we first have to close https://github.com/gbdev/gbadoc/issues/2)
Yeah if we can agree on a tech stack then we can get writing.
I would suggest that we do not just wholesale import from cowbite. i think we can do a little better on the organization of things that way.
Yeah if we can agree on a tech stack then we can get writing.
I would suggest that we do not just wholesale import from cowbite. i think we can do a little better on the organization of things that way.
I'd start importing and reformatting the content splitting the document so we can have a separate file per chapter, after the initial import we can re-organize the structure, step by step
Initial import is now covered by #17!
Which document should we use as a baseline?
Keep in mind we'll also need a permission enabling us to reuse. Items marked with * are already released with a permissive license.