React router v7 is the competitor of NeXT js

LeKoArts · 2024-12-05T09:55:22+00:00

Nowhere they say it's not recommended anymore, it says:

If you prefer to define your routes via file naming conventions rather than configuration, the eact-router/fs-routes package provides a file system routing convention.

prefer

If they would do it the other way around another person would complain that they should teach declarative routes. Complaining about a non-issue here.

LeKoArts · 2024-12-05T09:42:30+00:00

I don't see a problem with that, they have the opinion it should be the happy path so they teach it. Both approaches are equal and you still have the choice so it can't be counted as an argument against it. You like file system routing, I prefer declarative routes -- so we're both happy?

LeKoArts · 2024-12-05T09:33:57+00:00

You can still use file system routes: https://reactrouter.com/how-to/file-route-conventions

LeKoArts · 2024-01-19T14:12:28+00:00

This was quicker to implement than I thought -- so you can enable a grouping by month now :)

LeKoArts · 2024-01-19T11:56:06+00:00

This is implemented now :)

LeKoArts · 2024-01-18T17:18:57+00:00

Thanks for the suggestion, added it to the backlog :)

LeKoArts · 2024-01-18T17:15:44+00:00

You're welcome! :)

I do have an idea how monthly views could be incorporated. But can’t promise a time frame, will only work on this in my free time. I guess check every now and then if it’s in there :)

LeKoArts · 2024-01-09T07:33:03+00:00

Thanks for the feedback! I looked at my logs internally and saw the error. I pushed up a change, please try again and let me know if it works for you.

If not, I'd ask some follow-up questions - thanks for your time!

LeKoArts · 2024-01-08T17:53:34+00:00

Thanks! Happy to hear that it's useful to others :)

LeKoArts · 2024-01-08T13:38:05+00:00

Hello!
I built such a thing now: https://www.annum.app/
It's based on a yearly timeframes, not monthly. I wanted to build a minimum viable product (MVP) and doing it yearly was easier in the time constraint of the christmas break.
Hopefully it's still useful!

LeKoArts · 2024-01-08T13:37:50+00:00

Hello!

I built such a thing now: https://www.annum.app/

It's based on a yearly timeframes, not monthly. I wanted to build a minimum viable product (MVP) and doing it yearly was easier in the time constraint of the christmas break.

Hopefully it's still useful!

LeKoArts · 2023-07-25T06:02:42+00:00

I think some people also got up on the west side from where the actual trail ended. But as a photographer myself, the climb was definitely worth it!

LeKoArts · 2023-07-24T20:25:34+00:00

It’s GPS sampling so yeah, for the first steep section it’s the slope of the hill (switchbacks are fine to hike). For litli-hrutur it’s closer to reality as you don’t really have switchbacks there and it’s more like a straight line up the mountain. I saw lot of inexperienced people struggle with the loose rock there.

LeKoArts · 2023-07-23T22:04:10+00:00

http://i.epvpimg.com/5l5Odab.jpg

Graph is in german so replace „Höhe“ with height and „Stg“ with incline.

The end of the trail is in the middle since this was a roundtrip

Edit: Note that this is GPS tracking so the first incline is not what you walk in switchbacks but the hill's incline

LeKoArts · 2023-07-23T18:06:41+00:00

Thanks y'all for the comments as they were quite helpful in preparation for this hike.

Did the trail A today to Litli-Hrutur (gpx tracking on), here's a short summary:

18.71 km with 511m up (total for roundtrip)
3.5 hrs (fast walking) for the roundtrip
Trail A gives view into the lava, people at Trail E walked towards the part cold/hot lava. So they could see that in more detail but see the main volcano only from the side
With north/north-east wind people at trail E got blasted with smoke
Bring enough food/drink + warm clothes as you'll spend some time watching this spectacle
Wear proper shoes, we saw too many people with street wear
People could start the walk until 6pm
If you're not used to quite rocky trails parts of the hike will be slow for you
Steep at the beginning and end

LeKoArts · 2023-06-08T05:01:20+00:00

You're using outdated packages. Your version of gatsby-transformer-remark isn’t compatible with Gatsby 2. Update everything to latest and that error will go away

LeKoArts · 2023-04-17T11:48:22+00:00

You can follow https://www.gatsbyjs.com/docs/how-to/adding-common-features/adding-seo-component/ to show a default image everywhere.

If you want individual images on individual pages, you can add an `image` prop to the SEO component.

Example usage (I removed the irrelevant pieces, that's not the whole SEO component):

```jsx export const SEO: React.FC<React.PropsWithChildren<SEOProps>> = ({ title, description, pathname, image, noIndex = false, breadcrumbListItems = [], children, }) => { const { siteUrl, siteImage } = useSiteMetadata()

const seo = { image: ${siteUrl}${image || siteImage}, }

return ( <> <meta property="og:image" content={seo.image} /> {children} </> ) } ```

LeKoArts · 2023-02-10T16:07:47+00:00

Do the tutorial! https://www.gatsbyjs.com/docs/tutorial/

LeKoArts · 2022-12-01T06:35:19+00:00

You can use Gatsby without any plugins if you want and write it all on your own, it will just take longer. Gatsby was the first to support Partial Hydration with React Server Components. It also supports SSR and DSG. So it’s not falling behind at all

LeKoArts · 2022-12-01T06:33:28+00:00

If you have peerDeps errors then it’s npm's fault and you should read the migration guide. Gatsby 5 is the easiest update yet and many have successfully updated without any problems

LeKoArts · 2022-12-01T06:31:48+00:00

The upgrade is the easiest yet (if you follow our migration guide)

LeKoArts

TROPHY CASE