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

Add "Get farmOS, "Develop farmOS", and "Follow farmOS" headers and links to homepage #87

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mstenta
Copy link
Member

@mstenta mstenta commented Jan 15, 2024

This add a bunch of links to the homepage, based on feedback we've heard from the community. It also adds 3 <h2> headers to organize everything:

  • Get farmOS
  • Develop farmOS
  • Follow farmOS

Copy link

netlify bot commented Jan 15, 2024

Deploy Preview for gracious-brattain-bdd606 ready!

Name Link
🔨 Latest commit ab97d3d
🔍 Latest deploy log https://app.netlify.com/sites/gracious-brattain-bdd606/deploys/65a57ec163c05f0008cae4d0
😎 Deploy Preview https://deploy-preview-87--gracious-brattain-bdd606.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@wotnak
Copy link
Collaborator

wotnak commented Jan 15, 2024

Looks good, although I'm not sure if the repositories list is really needed on the homepage. It pushes the 'Follow farmOS' section down, and Github org with all repos is already linked right above it. Maybe a better place to list important git repos would be in the Github org README.

@mstenta
Copy link
Member Author

mstenta commented Jan 15, 2024

For what it's worth, part of the motivation for adding the repositories was related to: #22 (comment)

@mstenta
Copy link
Member Author

mstenta commented Jan 15, 2024

I agree that visitors can find the repositories if they need to, but another reason to include them on the homepage (IMO), is for emphasis to non-developers. I think there is a positive psychological effect to a farmer or other non-developer visiting farmOS.org for the first time to see the list of code repos, which gives a sense that this is a "real" project with multiple pieces that many people are working on. I don't have anything to base that on, just a sense... :-)

If there's consensus that it isn't necessary or is detrimental to include them, I'm happy to remove that commit and we can find another place to put direct links to repos in farmOS.org.

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

Successfully merging this pull request may close these issues.

None yet

2 participants