You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Training Team meetings start at 07:00 UTC weekly on Tuesdays. Anyone is welcome to contribute to the meeting by commenting in Slack threads throughout the week. Meeting notes will be published at the end of the week to also incorporate these asynchronous conversations.
Help validate the issue and comment on the issue what specifically needs to change
Content Audit for Learning Pathways -- we need volunteers to help us identify the content we can utilize or enhance and incorporate it into our lessons. Learn more about how to get involved in this post.
There was some discussion around #1880, which we would like to bring to the team.
Generally, when implementing internal anchor link fragments (where an HTML anchor tag links to the id attribute of another element on the same page instead of an external URL) the fragment uses lowercase, not sentence case. While this does not seem to be a requirement according to the HTML spec, it's not something commonly used, as most developers will use lowercase when defining id attributes of HTML elements.
However, the Tip box in the lesson plan saved pattern defines the links as sentence-case, but there are also some instances where it might be all lowercase. So while we're not sure that the case ultimately matters, we do think it should be formalized, documented, and then used accordingly across the site.
So this leaves us with a question, and a follow-up problem:
Should we stick to sentence case, or switch to all lowercase.
Whatever we decide, once implemented, we'll need to review both the lesson plan saved pattern, and any existing lesson plans, to ensure the links work as expected.
Therefore we'd like to bring this to the training team to discuss, decide on, and implement a plan to get the relevant parts updated.
Thank you @Piyopiyo-Kitsune. Notes from the dev-squad triage session have been added, with a new discussion item. You are welcome to move the discussion item to the open discussions part of the meeting, or wherever you prefer.
Discussion item: I have created the PR for the Sensei Pro upgrade. I would like to ask any members of the faculty dev-squad, or any other contributors with developer experience, to help review and test the PR.
Training Team meetings start at 07:00 UTC weekly on Tuesdays. Anyone is welcome to contribute to the meeting by commenting in Slack threads throughout the week. Meeting notes will be published at the end of the week to also incorporate these asynchronous conversations.
This week’s meeting will be hosted by @Piyopiyo-Kitsune
1. Intro/Welcome
Welcome to all new teammates who joined the Training Team this week!
2. News
1. Meeting Note Takers
2. Looking for feedback
3. Looking for volunteers
4. Updates from last week's dev-squad triage session
This week the dev-squad triaged 2 new PRs and one new bug:
There was some discussion around #1880, which we would like to bring to the team.
Generally, when implementing internal anchor link fragments (where an HTML anchor tag links to the id attribute of another element on the same page instead of an external URL) the fragment uses lowercase, not sentence case. While this does not seem to be a requirement according to the HTML spec, it's not something commonly used, as most developers will use lowercase when defining id attributes of HTML elements.
However, the Tip box in the lesson plan saved pattern defines the links as sentence-case, but there are also some instances where it might be all lowercase. So while we're not sure that the case ultimately matters, we do think it should be formalized, documented, and then used accordingly across the site.
So this leaves us with a question, and a follow-up problem:
Therefore we'd like to bring this to the training team to discuss, decide on, and implement a plan to get the relevant parts updated.
5. Other news
3. Open requests for review
See our Guidelines for reviewing content to review the following content.
4. Project updates
5. Open Discussions
If you have topics you’d liked discussed in the meeting, please leave them as a comment on this issue.
You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.
The text was updated successfully, but these errors were encountered: