···11+Welcome to at://advent! An atproto adventure to learn [atproto](https://atproto.com/) in an interactive and
22+hopefully fun way in the style of advent of code.
33+44+The majority of these challenges can be done without writing any code, but using community tooling. But you may find
55+writing code will also be a good exercise to get your feet wet. Some tools that may be helpful are:
66+77+- [goat](https://github.com/bluesky-social/goat) - Swiss army knife of a CLI that allows you to do most if not all
88+ atproto actions with.
99+- [pdsls](https://pds.ls/) - A web browser base atproto explorer (and more). Will allow you to view records, create
1010+ records, PLC data, download/view repo exports, and listen to firehose or jetstream.
1111+- [boat](https://boat.kelinci.net/) - Various atporot odds & ends tools. PLC, download/view repos, and more.
1212+- [atproto.at](https://atproto.at/) - A web browser base atproto explorer (and more). Will allow you to view records,
1313+ create records, PLC data, download/view a users repo exports, and listen to the jetstream for that user. May need to
1414+ turn on developer mode for the more advance options.
1515+1616+We are going to start simple. Everyone knows they have a handle, but `did` you know you also have a unique id called a
1717+[did](https://atproto.com/specs/did). This is a unique identifier for your identity that never changes. This comes in
1818+two flavors for atproto [did:plc](https://web.plc.directory/)
1919+and [did:web](https://atproto.com/specs/did#did-web-in-at-protocol).
2020+Each one have a unique way to find something called a [DID document](https://atproto.com/specs/did#did-documents). Your
2121+did document holds various information about your identity. Things like where does your PDS live, the key that signs
2222+your repo, handle, and more.
2323+2424+# plc
2525+2626+talk about where to find the PLC
2727+2828+# did:web
2929+3030+talk about how to find your did:web (altho you probably already know this)
3131+132Hey! Welcome to at://advent! A 25 day challenge to learn atproto with a new set of challenges every day.
233334(Pretend this is going into more details explaining everything)
+2
shared/challenges_markdown/one/part_two.md
···11+This will be submitting their public verification code from the did doc since each did doc will have one.
22+13Great job beating Part 1! Now onto Part 2.
2435Keeping it simple proof of concept, blah, blah will have a real one here another time. Add a new field `partTwo` to the
+5
shared/challenges_markdown/three/part_one.md
···11+Great job beating Part 1! Now onto Part 2.
22+33+Keeping it simple proof of concept, blah, blah will have a real one here another time. Add a new field `partTwo` to the
44+record with the value `{{code}}`
55+
+14-4
shared/challenges_markdown/two/part_one.md
···11-Great job beating Part 1! Now onto Part 2.
11+Hey! Welcome to at://advent! A 25 day challenge to learn atproto with a new set of challenges every day.
22+33+(Pretend this is going into more details explaining everything)
2433-Keeping it simple proof of concept, blah, blah will have a real one here another time. Add a new field `partTwo` to the
44-record with the value `{{code}}`
55-55+Starting out simple, create a record at the collection `codes.advent.challenge.day`
66+with the record key `1` and put this as the record.
77+88+```json
99+{
1010+ "$type": "codes.advent.challenge.day",
1111+ "partOne": "{{code}}"
1212+}
1313+```
1414+1515+[//]: # (<input type="file" id="part_one_input" placeholder="Enter your code here" />)
+7
shared/challenges_markdown/two/part_two.md
···11+Great job beating Part 1! Now onto Part 2.
22+33+Keeping it simple proof of concept, blah, blah will have a real one here another time. Add a new field `partTwo` to the
44+record with the value `{{code}}`
55+66+77+[//]: # (<input type="file" id="part_one_input" placeholder="Enter your code here" />)