The light from the #stars travels for years (and years) until it reaches your eyes. This #interactive#map of the night sky shows you for each star what happened on Earth when the light started traveling from the star to you. That way, any star has a story to tell you. You can zoom in, move around and hover all the stars to reveal the historical events they are connected to.
Working on my PHP side project, feeling an intense pull to migrate it to SvelteKit. But I know this is the biggest trap every coder with a side project can relate to - working on architectural changes instead of features. On the other hand, I love #SvelteKit and can make this thing way better with Svelte & SvelteKit than I ever will be able to with PHP. #Svelte + #PHP might be the way, except I lose the server-side rendering. Send help pls. :blob_dizzy_face:
I’ve spent the last few months crafting my own home on the Web, and I wanted to make sure it presented me as a human, not defined solely by my work as a #DesignEngineer / #WebDev.
This has also been a great opportunity to finally use #Svelte & #SvelteKit in a project. I love how easy it was to learn and how intuitive it is, as someone who started with vanilla HTML and CSS
Migrating from CodeIgniter #PHP to #SvelteKit is so easy and pleasant.
By building the site 15 years ago, and modernizing it today, I skipped over the awkward middle stage of making an API & fetching data to render it in the browser.
SvelteKit's form actions let you build a fast site that even works without #JavaScript, which means I'm going from server-side rendering with links & forms, to server-side rendering with links & forms. Except now I have the power of #Svelte to make it way nicer!
This D3.js data visualization I’m working on started as a page on my (Next.js) blog, but I think it’ll be better long-term to have it in its own repo.
After some planning for what I’ll need, I think The Pudding’s Svelte Starter Repo is the way to go. Coming from a group whose primary focus is D3.js data Viz, this looks far better than anything I could come up with.
Anyone have any recommended resources for learning Svelte?
I think it's time to update my portfolio site after 5 years of neglect.. going to use #svelte / #sveltekit as a bit of a learning exercise. Any recommendations for a simple clean customisable "portfolio" starter template/repo? I'd also like to add an experiments/sketches section too. Thx!
The biggest thing that slows me down when learning new tech is running into basic issues when setting things up. Like with #SvelteKit. The basic index page shows up in the browser, but when I create any other new page, nada. Did I miss setting something up? So frustrating. I've searched for some answers, but have found nothing and this type of problem is hard to describe.
So I'm a little deeper into #svelte and #sveltekit now.
I love svelte and there are a lot of really awesome things in #sveltekit as well but I just cant get myself to like the file based router.
Having every page file be named +page.svelte by definition means that I need to see the full file path to know what I am working on, which means that I cant use Zenmode to develop in sveltekit. 😥
What would the users of both platforms do if Medium and Substack suddenly closed, or they did something super-shady with all of the user data and content that they both have? I wonder this most times I see either domain linked here now.
Not everyone is a web developer, I get that, but self-hosting doesn’t have to involve too much fucking around with code. Worth it to own your content for life, surely?
Want to use view transitions in your #SvelteKit app?
v1.24 unlocks view transitions with a new lifecycle method. We’ve already added them to the #Svelte site - watch the blog titles slide into place! (note: it will fade instead of slide if reduced-motion is requested)
I asked a frontend friend what framework he would recommend if he was starting a new project today. He said #svelte, so I spent the afternoon walking through their online tutorial and playing around with #sveltekit.
I've got to say, as someone with fairly rudimentary JS skills, it was a great experience. It feels a lot closer to HTML/CSS and a lot simpler than a lot of the other JS frameworks.
I am Tjerk (pronounced as Chair + k). I teach web development and UI/UX design. Have a small indie development studio and love to use #svelte and #sveltekit.
Looking for more webdesign inspiration and pictures of home grown vegetables and cats.
I have been evaluating #SvelteKit for one of my personal business projects, and cannot really decide if adding it is going to be a blessing, or a total headache in the long run. I want it mainly as the front end counterpart to a #golang-based backend.
I love #Svelte for its simplicity, and it has saved my back in quite a few situations. However, looking at SvelteKit, integrating it into a real production scenario is anything but simple.
It never occurred to me that fonts not being loaded right away could cause content formatting issues. Had it not been for Rodney's (@rodney) post, I likely never would have never addressed this issue in my own apps!
Starting on a rewrite of an internal tool for a client, but trying to decide on which stack to use. The previous developer is versed in Vue/express and is able to help me out if I went that route. However, I've gotten a taste of sveltekit and love it because I can combine the frontend and API pretty seamlessly. Its problems are twofold though:
The previous dev would be significantly less help
Sveltekit is very new, meaning it is constantly changing and has a smaller, though more invested ecosystem (libraries, community, etc.)
I'm leaning towards Vue/Express right now, but I'm still not sure..
New blog post: #SvelteKit 2.4 added a new read method that simplifies reading assets on the server. I did a quick writeup on how it simplifies retrieving raw font data in one of my old #Svelte social image demos.