Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

docs: overhaul homepage#11345

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
JoshuaKGoldberg wants to merge1 commit intotypescript-eslint:main
base:main
Choose a base branch
Loading
fromJoshuaKGoldberg:homepage-overhaul

Conversation

JoshuaKGoldberg
Copy link
Member

PR Checklist

Overview

Overhauls the homepage to address the points in the issue. I tried make each section more clear & direct for what it was trying to convey.

The main change points are, top-to-bottom:

  1. Shrunk the big blurple banner to put more information side-by-side
  2. Changed the project slogan from:
    • Previous:"The tooling that enables ESLint and Prettier to support TypeScript."
    • Updated:"Powerful static analysis for JavaScript and TypeScript."
  3. Switched the initial explainer section to start with the three main value props of the project: language support, standard (TS) rules, and typed linting. It also decreases the vertical size of the ESLint & TypeScript explanations by removing their logos and trimming down the text.
  4. Replaced the now-redundant"Why does typescript-eslint exist?" with a section for recent blog posts.
  5. Added brief explanatory text toFinancial Contributors, and made the links a little more clear.
BeforeAfter
imageimage
imageimage
imageimage

@typescript-eslint
Copy link
Contributor

Thanks for the PR,@JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

@netlifyNetlify
Copy link

netlifybot commentedJun 25, 2025•
edited
Loading

✅ Deploy Preview fortypescript-eslint ready!

NameLink
🔨 Latest commite7c3b86
🔍 Latest deploy loghttps://app.netlify.com/projects/typescript-eslint/deploys/685c390a92e79500082b6598
😎 Deploy Previewhttps://deploy-preview-11345--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse		1 paths audited
Performance: 96 (🟢 up 1 from production)
Accessibility: 97 (🔴 down 3 from production)
Best Practices: 100 (no change from production)
SEO: 90 (🔴 down 10 from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify project configuration.

@nx-cloudNx Cloud
Copy link

nx-cloudbot commentedJun 25, 2025•
edited
Loading

View yourCI Pipeline Execution ↗ for commite7c3b86.

CommandStatusDurationResult
nx run-many -t lint❌ Failed11sView ↗
nx test eslint-plugin --coverage=false✅ Succeeded5m 2sView ↗
nx run integration-tests:test✅ Succeeded44sView ↗
nx test typescript-estree --coverage=false✅ Succeeded19sView ↗
nx test eslint-plugin-internal --coverage=false✅ Succeeded7sView ↗
nx run types:build✅ Succeeded<1sView ↗
nx run generate-configs✅ Succeeded13sView ↗
nx run-many --target=build --parallel --exclude...✅ Succeeded44sView ↗
Additional runs (26)✅ Succeeded...View ↗

☁️Nx Cloud last updated this comment at2025-06-25 18:12:34 UTC

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

This was much more work than I'd hoped it would be. There's no exported way to get blog posts from@docusaurus/plugin-content-docs that I could find.https://www.cheehow.dev/blog/2024/04/01/show-recent-posts-in-docusaurus has a suggested strategy & links to more info. I did that at first but kept hitting tricky edge cases with the plugin. So in the end I just went with this more direct approach: manually re-reading and re-parsing the files. 🤷

}),
);

awaitfs.mkdir(storageDirectory,{recursive:true});
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

(unnecessary, it's checked in)

Suggested change
await fs.mkdir(storageDirectory, { recursive: true });

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Docs: Homepage overhaul
1 participant
@JoshuaKGoldberg
[8]ページ先頭
©2009-2025 Movatter.jp