nextjs-notion-starter-kit
lighthouse-ci
Our great sponsors
nextjs-notion-starter-kit | lighthouse-ci | |
---|---|---|
11 | 18 | |
5,796 | 6,267 | |
- | 1.5% | |
3.5 | 7.2 | |
9 days ago | 16 days ago | |
TypeScript | JavaScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nextjs-notion-starter-kit
-
Using Stable Diffusion techniques to create 2D game environments
I love coming across a great blog like this an realizing it was built using two of my open source repos:
- https://github.com/transitive-bullshit/nextjs-notion-starter...
- https://github.com/NotionX/react-notion-x
-
Need some help to start a project
Here is a repo I used as a starting point before (repo is not mine) https://github.com/transitive-bullshit/nextjs-notion-starter-kit
- What react framework do you guys suggest to create a Blog?
-
Urgent - ITGS WEBSITE IA HELP! I HAVE NO IDEA HOW TO COODE!
The github page: https://github.com/transitive-bullshit/nextjs-notion-starter-kit
-
Looking for site generator
Most of services tried to take money from me for custom domains, sitemap, theme etc. Sorry, I don't have enough money for that. 2. nextjs-notion-starter-kit This was the second for me. ① Cannot handle path well It is OK to map your page to /one but it throws 404 error when path is /one/two or /one/two/three. Since I have to map URL like /category1/subcategory2/sub-subcategory3/sub-sub-subcategory4/page5, this is serious problem. Other than that, it seems quite nice. 3. loconotion ① Does not sort pages in directories I tested this without mapping pages to path, but it seems it doesn't sort pages in directories when processing Notion pages. I found python script that sort those pages, but it doesn't support Windows, the only OS I use for general use. ② Slow generation If my site have few pages, it might be good choice, but my site has ~100 pages and a lot of pages will be added in near future. If it converts every pages whenever I launches it, it would take a lot of time. 4. Fruition I think it is just converting Notion page URL into mapped URL. Kind of nice, but still slow as Notion's shared page is. But I think it is doing some 'magic'. I didn't know that CF Worker can do such job. I'm currently using this.
-
Understanding SEO and Web Vitals for your NextJS site and how to improve them?
If you want more control over your website via React, then we recommend checking out the accompanying Next.js starter kit, which is free and uses react-notion-x under the hood.
-
Ask HN: Share Your Personal Site
https://transitivebullsh.it
It's powered by Notion as a CMS, react-notion-x, Next.js, and Vercel.
I published an open source starter kit so anyone can easily create similar sites: https://github.com/transitive-bullshit/nextjs-notion-starter...
- Tools to create your website from Notion
- We've built a tool to turn Notion pages into websites for free 🐱
-
Embedded interactive WebGL animation in Notion headers (open source & free)
source code
lighthouse-ci
-
help needed with lighthouse ci for angular, github actions, PROTOCOL_TIMEOUT: (Method: Debugger.disable)
- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,
-
Continuous performance audits in Nuxt with Lighthouse CI and Github Actions
This approach would suit most of the cases however to achieve more accurate performance audits you should be conducting Lighthouse tests on a dedicated server to avoid results being affected by the machine capabilities. In other words, if you are running Lighthouse audits on a repository where there are several pull requests/workflows/pushes going on, the result of this audit may not be accurate and this is what we want to avoid. For that you would need a separate machine with Lighthouse Server installed on it. So on a pull request you would trigger this machine to conduct a performance audit and return response to your repository.
-
Measuring Page Speed with Lighthouse
And finally, Lighthouse has a CI version you can run in your continuous integration. We’ll use this method to schedule periodical benchmarks.
-
Ensure your Next.js app's performance is top-notch with Lighthouse CI and GitHub Actions
TLDR; I use the Google Chrome Lighthouse CI with a .lighthouserc json configuration to test next start. The Lighthouse CI GitHub app is used to return a pass or fail status check in a PR.
-
Everything you need to know about Web Performance (in 5 Minutes)
You should also incorporate performance checks into your CI/CD pipeline. Use Lighthouse CI to run a synthetic Lighthouse test on each PR (PS: Learn why you shouldn't believe the Lighthouse score alone) and bundlesize package to raise alerts if your bundle size exceeds a certain threshold. For more nuanced data you should use WebPageTest.
-
Accessibility Automation tool for CI pipeline
You can also run Google’s Lighthouse CI tool against multiple URLs, and then hook that up to their self-hosted dashboard service: https://github.com/GoogleChrome/lighthouse-ci
-
Understanding SEO and Web Vitals for your NextJS site and how to improve them?
You can also set up lighthouse-ci as a github action to evaluate the web vitals on push or in pull requests.
-
You’re probably using Lighthouse wrong: How we got tricked by a single magic number
You can have more consistent results if you set up Lighthouse CI in an external environment to test your page or use tools like SpeedCurve, but if you need to quickly inspect a website, I suggest taking a look at Page Speed Insights.
-
Frontend Testing: No more Unit/Integration/E2E categorizations and priorities
This name is already self-explanatory, and developers just need to run Lighthouse or its CI.
-
I built an open-source tool that scans your entire website with Google Lighthouse (unlighthouse.dev)
They also have a powerful CI tool (https://github.com/GoogleChrome/lighthouse-ci) with custom timelines, may look to implement it at some point
What are some alternatives?
leerob.io - ✨ My portfolio built with Next.js, Tailwind, and Vercel.
pa11y - Pa11y is your automated accessibility testing pal
mkdocs-material - Documentation that simply works
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
shellbear.me - Source code of my personal website and blog ✨
lighthouse - Automated auditing, performance metrics, and best practices for the web.
portfolio - My portfolio website with built-in blogs and courses support
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
trendy-resume - 👋 Junho's new Résumé, themed like a shopping mall website! You can make your own with this template too 🔥 (2020)
WebPageTest.api-nodejs - WebPageTest API wrapper for NodeJS
portfolio-website
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y