8000 New landing page design by shravanngoswamii · Pull Request #119 · TuringLang/turinglang.github.io · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

New landing page design #119

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

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

New landing page design #119

wants to merge 29 commits into from

Conversation

shravanngoswamii
Copy link
Member
@shravanngoswamii shravanngoswamii commented Apr 14, 2025

Continuing #105
Preview the changes: https://turinglang.org/pr-previews/119

Copy link
Contributor

Preview the changes: https://turinglang.org/pr-previews/119
Please avoid using the search feature and navigation bar in PR previews!

@shravanngoswamii
Copy link
Member Author

If anyone is interested, then please feel free to take on this PR!

@shravanngoswamii shravanngoswamii linked an issue Apr 19, 2025 that may be closed by this pull request
simonsteiger and others added 22 commits April 21, 2025 22:54
* very basic redesign

* make buttons interactive
* add dangling code example

* add code example section
* quickfix alignment

* add news and clean up scss
* improve colors

* better link hover color
* paste in svg

* responsive svg header
using the same background colour for the team "cards" as for the non-hoverable cards on the landing page
- added links to discourse and slack to the buttons at the top of the page
- moved link to libraries page to "Learn more" section
Co-authored-by: Penelope Yong <penelopeysm@gmail.com>
@simonsteiger
Copy link
Contributor

I will definitely have time to finish this in July. Which points would you like to see addressed before this PR can be merged?

@penelopeysm
Copy link
Member

Revisiting this. Is there a reason why the old PR was closed?

Also, I'd personally be happy to merge if some of the placeholder content is removed. Honestly, it's not like the existing front page has any resources, so even a fairly clean slate would be a huge improvement over the current one.

@penelopeysm
Copy link
Member

I'm happy to take this on some time next week — I will try to get it into a mergeable state and we can always iterate further after it's merged.

@penelopeysm penelopeysm self-assigned this May 28, 2025
@shravanngoswamii
Copy link
Member Author

Revisiting this. Is there a reason why the old PR was closed?

Apologies for the confusion. I don’t have admin permissions on this repo, and the previous PR had complex merge conflicts. Since it was from Simon’s fork, and I was adding some features to the landing page, I accidentally messed up some git operations. So I took those changes and opened a new PR from a branch within this repo to make it easier to manage.

Honestly, it's not like the existing front page has any resources, so even a fairly clean slate would be a huge improvement over the current one.

Totally agree. However, before merging, I think we should either:

  • Complete the light/dark mode feature and update that in the docs repo for consistency, or
  • Move the color theme changes to a separate PR if we're not ready to finalize them yet.

@shravanngoswamii
Copy link
Member Author

Hi @penelopeysm, I’ve removed @simonsteiger’s styles/theme update from this PR and moved those changes to the current theme format. I also made a few updates to the theme and added some improvements to the news slider animation.

The full SCSS-based theme Simon added was actually a much better approach than the current one, but it needed some updates. For now, let’s focus on completing the landing page. I’ve backed up Simon’s theme, and I’ll open a separate PR for those styles once we’re done.

@shravanngoswamii
Copy link
Member Author

Everything after News section is currently a holding a placeholder texts, can you help me update that, just ping me if any UI layout changes are required

@shravanngoswamii
Copy link
Member Author

#76 - let's add these in the placeholder texts!

@penelopeysm
Copy link
Member
penelopeysm commented Jun 11, 2025

Everything after News section is currently a holding a placeholder texts

I think I am still of the opinion that we don't need to add more content right now. We can restrict this PR to be just a design change. I do recognise maybe we want to add that content in the future (e.g. in a follow-up PR). Thus, what I would do is quite literally comment out everything in index.qmd from the 'Algorithms' section onwards. Feel free to do that if you agree with my take.

Doing that leaves us with just the placeholder text in the "Hello, world" and "Goodbye, world", right?

Let's have a think about what we want to really showcase here. It can be more than two panels too. The target audience is likely to not even be a Julia user. In my opinion, these are the most important things we can use to 'sell' people on Turing:

  1. Basic explanation of Turing.jl syntax and how it matches the mathematical description of a generative model.
  2. Multithreaded sampling "for free" with AbstractMCMC.
  3. Wide range of samplers, including external samplers.
  4. 'you can call any Julia code' (are GPs really the best example? I actually think HMMs are better because it's not at all obvious at first glance how GPs differ from basic distributions -- the point being made is that GPs are defined in a different package outside of Turing, but the syntax is exactly the same and this subtle point is going to be lost on people. With HMMs it's obvious that you're calling external library functions and then 'telling' Turing about it with @addlogprob!.)

Just self-requesting a review to make sure that this doesn't fall off my list.

@penelopeysm penelopeysm self-requested a review June 11, 2025 22:21
@shravanngoswamii
Copy link
Member Author
shravanngoswamii commented Jun 12, 2025

I think I am still of the opinion that we don't need to add more content right now.

Agree, I have commented everything from Algorithms section and added a Citation at the end, just take a look at it, let me know if you have suggestion on improving that citation part + I think we have a new paper on Turing, should we add that in citation or the old one I found on main Turing.jl repo

EDIT: Citation preview -- https://turinglang.org/pr-previews/119/#cite

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.

Redesign the landing page!
3 participants
0