This site is open source and contributions are extremely welcome. You can find the source code on GitHub, along with many open issues. If you want to get involved, but don't know how, reach out to email@example.com and I will help you get started.
In particular, we are looking for help with:
1. Site design and layout
We have a number of open issues on ease of use feature for the site, tagged with web-dev.
This could be reading new prompt engineering papers and writing pages about them, or writing articles on more anecdotal topics. Most all content is welcome. See open issues for content we have yet to add.
Prompt Engineering Techniques
We write articles on PE techniques, not entire papers. This means that multiple techniques used in a paper could be spread across multiple articles. The reasoning for this is, in part, that papers often reuse techniques, and we want to avoid repeating ourselves. Additionally, articles on bite sized, single techniques are easier to read and understand. Here is a good example this.
When taking content from a paper, article, or even tweet, make sure to update the bibliography files
docs/bibliography.md. Most papers have autogenerated BibTex citations that you can find online (e.g. on arxiv). You can then use the citation in a md files by typing
(@citation_name). See the CoT page for a good example of this. Citation lists will then autogenerate at the bottom of pages. Also see this PR about how to add vocabulary tooltips.
When considering a paper, make sure it uses PE. Some papers in open issues would not make for good articles, but are good to link to as additional resources. If you have found a good paper, synthesize it's different techniques into short articles, and put them in the appropriate sections. The PAL article is a good example of this.
Anecdotal and Other Content (e.g. Applied, Products, More)
We are always looking for more content. If you have a story to tell, or a product to recommend, please make a PR! We are also looking for more content on the applied side of prompt engineering, such as how to use prompts in your own research. Here.
We are looking for help translating the site into other languages. If you are interested, please join the Discord and mention you are interested in the respective language channel. If the channel does not exist, please message @Trigaten. You don't need to ask us to start translating files! Please use our Crowdin to do translations. Around 7 languages are currently being translated, so you will likely find people to work with!
When you run the website locally, make sure to follow Docusaurus instructions on running it in your language (e.g.
npm run start -- --locale fr).
Everything from fixing typos to recommendations for the site (suggest papers, layout changes, tell us what you want to learn about, etc.)
We need help maintaining the list of prompt engineering tools and products that use prompting.
Email firstname.lastname@example.org with any questions.