Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

Latest commit

 

History

History
120 lines (71 loc) · 7.45 KB

CONTRIBUTING.md

File metadata and controls

120 lines (71 loc) · 7.45 KB
Raw

Contributing

Thank you so much for your interest in contributing to WWDC Notes! ❤️

Add a new note

The recommended (and quickest) way to add a new note is to check out the add a new note page and choose the session you'd like to add from there.

If you'd rather add a note manually, see chapter Add a new note manually at the end of this page.

Note content

Every note comes in the following format:

---
contributors: yourGithubHandle, anotherGithubUsername
---

...your notes here (no session title needed) ...

Besides adding your GitHub username among the contributors, the rest of the file is for you to use: try to be as concise and straightforward as possible.

Do not worry about the session title, tags, description, video link, etc.: all of that will be added automatically later.

Where to Save the Note Images

Two steps:

  1. Add the image(s) in the folder /images/notes/wwdcYY/SSS where YY is the session WWDC year (e.g., wwdc23 for WWDC 2023) and SSS the session number (e.g., 101) (it's the same path as your note).

  2. Link them in your note using the URL ../../../images/notes/wwdcYY/SSS/file-name.png, for example:

![I am a description for the image.][reference-name]

[reference-name]: ../../../images/notes/wwdc23/101/file-name.jpg

Use exactly this format including the ../../../ prefix to make it possible to preview the images both on the website and on GitHub. You can place the [reference-name]: <link> part at the end of the document or inline, there's no strict rulem, both will work.

Guidelines for Incorporating Images and Screenshots

  1. Privacy Considerations: Prioritize presenter privacy by cropping out any individuals from the screenshots.

  2. Image Quality: Maintain high-quality screenshots that remain clear and crisp even on larger displays like external monitors or MacBooks, avoiding any pixelation.

  3. Image Resizing for Server Optimization: To optimize server load, follow these steps to resize images:

    On a Mac: a. Open the image in Preview. b. Utilize the selection tool to crop unnecessary portions, like black bars at the top and bottom, by dragging with the mouse. c. Crop the selected area using Command + K. d. Save the edited image. e. For exporting, either choose File > Export, pick JPG format, assign a filename, and save it in the designated WWDC folder on your Mac.

    Or, you can right-click on the screenshot (typically a PNG file), then select: Quick Actions -> Convert Image.

    On an iPad: The Photo app on an iPad doesn't directly support image resizing. However, you can use the Shortcut app (Link) to create a custom shortcut. This will allow you to automate the resizing process for your images. When preparing images for the web and MacBook Pro displays, for web use, common sizes include 1920x1080 (Full HD), 2560x1440 (2K), and 3840x2160 (4K) for background images or banners. But widths around 800 to 1200 pixels are often suitable for accommodating various screen sizes without excessive resizing and a resolution of 72 pixels per inch (PPI) is generally sufficient.

  4. In Preview on macOS, you have the capability to select and copy text directly from images, even including code snippets. Consequently, opting for a code block is more advantageous than using an image that contains text or code.

  5. To render the Markdown we use Ink. If images or code blocks are not rendering correctly on the website, consider the following steps.

  • Reveal Invisible Characters in Xcode: access the invisibles feature in Xcode via the Editor menu. This will allow you to visualize hidden characters.
  • Eliminate Preceding Spaces: Before your image or code block, ensure there are no extraneous spaces or indentations. While a single return or new line is acceptable, multiple spaces can confuse the parser and hinder proper rendering.

How to check if someone else works on it in parallel

If you're providing notes durnig the week of WWDC, it's possible that others are currently watching sessions & providing notes as well. While it's totally encouraged that multiple people provide notes for the same session to combine them, if you don't want to contribute notes for a session that already is being worked on, make sure to check the latest messages in the #wwdc23 channel on our Slack space. Also, if you do decide to work on a session during WWDC week, make sure to inform the community about it in the same place. Thank you! 🙏

Update a note

It's encouraged to update an existing note with more content, corrections, and further enhancements, even if you're not the one who originally wrote it.

You can add yourself among the note contributors if your change is substantial (a.k.a. more than adding a link, adjusting a few sentences, or fixing typos).

Community member details

Details like full name, avatar, website, etc., come automatically from your GitHub profile. All details are updated every time you make a new contribution to this repository.

Don't copy the transcript

While we don't have any specific requirements on the exact form of the summary (people take notes differently!), it's important that they still are notes that you're sharing. Here are some signs that contributions are NOT notes, so we strongly discourage the following:

  • Blocks of text can be found word for word in Apple's session transcript within the Developer app.
  • The text is written from the "I" perspective of the presenter of the session.

Please avoid simply copying larger blocks from the transcript. A few shorter direct quotes are fine. For example, if they list things, it's natural to list the same things in a note. But if they say something like: "There are many scenarios where feature X can improve your workflow. First of all, they allow you to Y..." then this should not be directly quoted in a summary. Instead, write something like "Feature X helps with: Y, ...", which is also shorter than the original text.

Add a new note manually

You're free to add notes manually instead of using the recommended way: follow the note format with the header shown above and place it at the correct location.

Note location

All notes are located in /content/notes/wwdcYY/SSS.md, where YY is the WWDC year (e.g., wwdc21 for WWDC 2021), and SSS is the WWDC session number, for example 101.md.

Click here to find out how to get a WWDC session number.

To find the session number of a WWDC video, please refer to its url.

e.g.,:
The SwiftUI Essentials session url is https://developer.apple.com/videos/play/wwdc2019/216/: its session number is 216.

Therefore the file containing its notes will be named 216.md.

More Questions

If you need any further help or clarification, feel free ask in the #random channel on our Slack space or reach out to Jeehut via a direct message there.

Thank you, and we look forward to your PRs! 🎉