Skip to content

Update Start Contributing Guide and Community pages - #676

Open
reardonj wants to merge 2 commits into
typelevel:mainfrom
reardonj:update-start-contributing
Open

Update Start Contributing Guide and Community pages#676
reardonj wants to merge 2 commits into
typelevel:mainfrom
reardonj:update-start-contributing

Conversation

@reardonj

Copy link
Copy Markdown
Contributor

@abby-ql , I pulled out a few more updates I was making to the start contributing page to it's own PR while I finish off the rest of my work.

Later this week I'll have another PR with more detailed contributing guidelines covering details like copyright and other stuff the GSoC guidelines had, but they're quite separate from these updates.

reorganized the community page

  • make layout take up move space on wide screens. Same behavior on smaller screens. With the pages already having 'columns' letting it take up a bit more space saves users on large monitors having to scroll as much to see everything.
  • expand descriptions, so the new sections are similar sized to the others
  • move new sections ahead of coc. I like resources and code of conduct last, since they're not quite get involved pages like the others

Note

I feel there should be a way to template the community page instead of having to update all these css classes, but I didn't want to go down a bikeshedding rabbit-hole.

community page

tweaks to the start contributing guide

  • don't say it's simple, it's a phrase that tends to make newcomers assume the opposite.
  • I added links to all the suggestions and put them as a 'Become a user of the ecosystem you want to contribute to.' section
  • use bold instead of incorrect subheading levels.
  • add AI note
image

reardonj added 2 commits July 28, 2026 18:07
- make layout take up move space on wide screens
- expand descriptions
move new sections ahead of coc
- don't say it's simple
- links to suggestions and put them in a list
- use bold instead of incorrect subheading levels
- add AI note
@armanbilge

Copy link
Copy Markdown
Member

When I set up the site I also had a vision of adding a "Get Started" button and "Learn" menu item to the navbar, but lacking content at the time. So we could consider bringing those to life.

<!-- <div class="bulma-navbar-item"><a class="bulma-button bulma-is-rounded bulma-is-primary bulma-has-text-light">Get Started</a></div> -->
<!-- <div class="bulma-navbar-item"><a class="bulma-button bulma-is-text">Learn</a></div> -->

@reardonj

Copy link
Copy Markdown
Contributor Author

When I set up the site I also had a vision of adding a "Get Started" button and "Learn" menu item to the navbar, but lacking content at the time. So we could consider bringing those to life.

<!-- <div class="bulma-navbar-item"><a class="bulma-button bulma-is-rounded bulma-is-primary bulma-has-text-light">Get Started</a></div> -->
<!-- <div class="bulma-navbar-item"><a class="bulma-button bulma-is-text">Learn</a></div> -->

oooo. I think Learn would be better pointed at the future TL learning guide, but get started could point to @abby-ql 's page

@reardonj

Copy link
Copy Markdown
Contributor Author

But I think it best to turn that on once we have the full contributing guide too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants