Skip to content

Comments

mention Scala on landing page and colophon page#579

Open
SethTisue wants to merge 2 commits intotypelevel:mainfrom
SethTisue:mention-scala
Open

mention Scala on landing page and colophon page#579
SethTisue wants to merge 2 commits intotypelevel:mainfrom
SethTisue:mention-scala

Conversation

@SethTisue
Copy link
Member

@SethTisue SethTisue commented Feb 18, 2026

on discord, @jducoeur indicated that some form of the landing page change would be welcome

it's of course bikesheddable exactly where to insert "Scala" and whether it should be a link. here's one possibility

@SethTisue SethTisue changed the title mention Scala on landing page mention Scala on landing page and colophon page Feb 18, 2026
Copy link
Member

@jducoeur jducoeur left a comment

Choose a reason for hiding this comment

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

Makes sense to me, although I'll defer to Arman and Andrew, who have been driving the vision so far.

@SethTisue
Copy link
Member Author

SethTisue commented Feb 18, 2026

Andrew already altered the colophon page to mention Scala further down, but I (mildly) think my change (to also mention it right up front) is desirable. the first mention will serve to emphasize that the whole thing is Scala-based; the later mention then adds that y'all are using Scala for your scripting, too

@valencik
Copy link
Member

Yeah the colophon changes can be "both"

It's the landing page I wanna think more about.
I feel like this is becoming too much:

image

@jducoeur
Copy link
Member

Interesting point. I like it in principle, but I agree that the link comes out way too bold visually.

Can/should we treat this as a style thing, and switch it to old-fashioned underscore?

@SethTisue
Copy link
Member Author

or just un-link it and figure those who know, know, and those who don't, can google?

@armanbilge
Copy link
Member

quoting Seth from Discord:

the word "Scala" appears nowhere on the landing page. oversight, or deliberate omission?

I have been reflecting on this, and I am realizing that this was actually deliberate choice on my part, albeit subconscious enough that I was not sure at first. Working to stand up the Foundation as a 501(c)(3) public charity and the surrounding discussions we have had about what Typelevel is have influenced some of my thinking.

My hypothesis is that not putting Scala front-and-center on our landing page may help us appeal to a broader audience. Essentially, I am getting at the nuance between:

  • We develop functional programming libraries for the Scala community/ecosystem.
  • We develop functional programming libraries for everyone, using the Scala language.

My (possibly unfounded) fear is that by mentioning Scala too upfront, potential users may move along because they are not using the Scala programming language.

Instead, my vision for the website is to entice curious developers with functional programming and compelling examples of how to use our stack, and that they will learn about Scala along the way :)

@reardonj
Copy link

My (possibly unfounded) fear is that by mentioning Scala too upfront, potential users may move along because they are not using the Scala programming language.

Instead, my vision for the website is to entice curious developers with functional programming and compelling examples of how to use our stack, and that they will learn about Scala along the way :)

I could see this working if there was a next page showing the user more specifically what the benefits of using Cats/CE/fs2/etc. Presumably this would include some explanation of why Scala is a specifically good choice for all this. The current site though is pretty cryptic and users really only have the project page to figure out what is going on right now, which has cryptic tags like js, jvm, native.

IMO, it might be helpful for the time being to mention Scala so uninformed visitors (and search engines) have some notion of what is going on.

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.

5 participants