Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update contributing.md #225

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

0xlukem
Copy link
Contributor

@0xlukem 0xlukem commented Jan 9, 2025

Description

This PR is a follow-up to PR #218. It includes information about the new standard for indexes and addresses the feedback provided in the previous PR.

Checklist

  • I have added a label to this PR 🏷️
  • I have run my changes through Grammarly
  • If this page requires a disclaimer, I have added one
  • If pages have been moved around, I have created an additional PR in tanssi-mkdocs to update redirects

@0xlukem 0xlukem requested a review from a team as a code owner January 9, 2025 21:36
Copy link
Contributor

@eshaben eshaben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few remaining things to update! I think some of my comments got lost between this new PR and the old one.

Can #218 be closed then?


<!-- Add content in markdown here -->

## Explore What This Section Covers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We changed this to ## Explore This Section

Comment on lines +73 to 74
```
Some important things to note:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Watch spacing here. There should be a space between the code sample and the following sentence

Some important things to note:

- The `title` represents the `<title>` tag and is used for SEO purposes
- The `description` represents the meta-description and is also used for SEO purposes
- The `icon` is used on index pages (`index.md`). So it should be an icon representative of the content on the page. You should stick to using Octicons 24px icons. You can search through the available icons on the [Primer Design System website](https://primer.style/foundations/icons)
- The `template` defines the template to be used. It should always be `main.html` for new content pages and `index-page.html` when adding a new section
- The `icon` is used on index pages (`index.md`). It should be an icon representative of the content on the page. You should stick to using Octicons 24px icons, ensuring they are outlined and not filled to maintain style consistency. You can search through the available icons on the [Primer Design System website](https://primer.style/foundations/icons)
- The `<div>` is populated with links to any pages or subdirectories and is populated automatically by a script at runtime that builds the landing pages
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is no longer relevant

- The `<div>` is populated with links to any pages or subdirectories and is populated automatically by a script at runtime that builds the landing pages
- The `template` defines the template to be used. It should always `index-page.html` to correctly render the table of contents (TOC)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean the table of contents? Because the TOC is usually the navigation element that shows up on the right side of the page, so when I read this that's what I think about and that's incorrect. I think maybe the issue here is just the wrong use of words

- The `<div>` is populated with links to any pages or subdirectories and is populated automatically by a script at runtime that builds the landing pages
- The `template` defines the template to be used. It should always `index-page.html` to correctly render the table of contents (TOC)
- The `## Explore What This Section Covers` serves as the title that acts as a divider between the content and the TOC
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what content and what TOC?

- The `<div>` is populated with links to any pages or subdirectories and is populated automatically by a script at runtime that builds the landing pages
- The `template` defines the template to be used. It should always `index-page.html` to correctly render the table of contents (TOC)
- The `## Explore What This Section Covers` serves as the title that acts as a divider between the content and the TOC
- The `:::INSERT_GENERATED_CARDS:::` is required for the `template` to function correctly and automatically generate the TOCs for each index
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so yeah this pretty much confirms it. I don't think I would refer to this as the TOC because that is a specific element that appears on other pages. Instead, it should be referred to as the section cards, or something like that

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. I mistook the the tocs with the section cards

- The colors should be:
- Light mode: #262626
- Dark mode: #e9e9e9
Images should follow these specs:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are no specs listed after this sentence

@eshaben eshaben added A2 - Maintenance Minor Pull request contains minor updates to an existing page (i.e., modifying parameters, steps, etc.) B0 - Needs Review Pull request is ready for review C0 - Low Low priority task labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A2 - Maintenance Minor Pull request contains minor updates to an existing page (i.e., modifying parameters, steps, etc.) B0 - Needs Review Pull request is ready for review C0 - Low Low priority task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants