Attendees
@alexandersandberg
@daveverwer
@James_Dempsey
@kaishin
@tomerd
@0xTim
Notes
Content Improvements PR
- Addressed feedback from Core Team and how to move ahead with the PR. Some key decisions:
- We're moving ahead with a single PR as multiple PRs will provide less context individually.
@0xTim Sort download sections for the different tutorials.- @kaishin
- Add a couple of todos in the description.
- Create a PR for
main. - Add a link to the live site.
- @alexandersandberg Post the PR link on the forums.
- The review will mostly focus on the preview, and less on the codebase.
- We need to merge pending PRs before opening the PR against
main. - @tomerd to update his PR and merge it.
- Discussion around the Why Swift section.
- @daveverwer To open a PR that introduces a new title and tagline.
- Code snippet PR pending further feedback on the code snippets.
- @alexandersandberg to merge the PR.
- A fixed code snippet height can be used to avoid the content jumping around.
- @kaishin mentioned that the code snippet rotation could be less friendly to linking.
- @James_Dempsey mentioned that we a blog post about the updated site could be a good idea.
- @0xTim brought attention to the blog post PR backlog.
- @James_Dempsey The reference value type blog post is a blocker for the content improvement PR.