Closed ChristopherBiscardi closed 5 years ago
Nice. Thanks @ChristopherBiscardi. Are you interested in working more on this going forward? Should I be trying to round up folks who might be willing to chip in?
Could you write up some "how it all works" docs that help people get started?
I'll merge in the next few days or so when I have some make sure the infrastructure is all in place for having it "be live".
@ChristopherBiscardi do you have a netlify.toml that should be used for deploying the site on netlify?
Very cool!
BTW, looking through the netlify preview, it looks like there is an issue with underscores in function names being interpreted as markdown-italics:
It also looks like Sean has a typo in his function names :grin:
I'll also note that we might want to add a .gitattributes
file with the following contents:
docs-raw-md/* linguist-generated=true
Doing so will cause the raw md changes to be hidden in pull requests, for easier review.
@jemc that .gitattributes change sounds like an excellent idea
Closing as this has all been incorporated. Thanks Chris!
This is all of the infrastructure and the initial implementation of a gatsby-based main.actor. You can see the site currently deployed at https://gracious-keller-8bfb46.netlify.com
URLs are generated as such:
packages/<name>/<version>/<markdown-file-path>
so you might end up with the following forhttp
@0.2.1
when looking at thePayload
class:There are some areas of different markdown files that end up looking a bit awkward (here's an example that uses types in the heading), so we'll probably want to format the output differently