Open kentcdodds opened 10 months ago
Just a point of clarity,
Can the docs be hosted in this repo as well or did you envision them in a completely separate repo all together? I think I understand the requirement that you don't want to have to redeploy to make changes, I think we can accomplish that via github actions and still host all the markdown in this repo.
Thanks @swalker326! Sorry, when I wrote this initially, I was writing it in a comment on the other discussion then I moved it over here and didn't update that part 😅
I think all the docs should be in this repo, code and the docs files themselves 😅
Hey @kentcdodds I got a bunch of cool stuff pushed today and working. I was wondering if we can do a call (maybe this week) and I can run you through it and maybe get some input on if this is a good direction or not. Got search working and build time mdx working which were two I was kind of unsure of.
This is awesome! Thank you! I'd love to do a call sometime. Shoot me an email and we can schedule something: me@kentcdodds.com
Thanks again! I'm loving this!
Email sent, I've had it reported a couple times that my email went to spam. If you don't see it check there 😬
Yep. That went to spam 😅 Will reply there. Thanks!
Just a few thoughts:
I'm really thinking the architecture can be similar to my site which is similar to the Epic Stack in many ways. This file is probably most helpful for compiling mdx on the fly. A simpler and similar implementation that you may reference is the speed-metal-stack which is based on my personal site.
Personally, I'd probably start with the Epic Stack and remove stuff we don't want. I think keeping the user accounts could actually be useful for the admin interface with the cache etc.