draft blog post about sveltekit

[Rich-Harris]

We never did quite figure out whether it's going to be SvelteKit or Svelte Kit or svelte-kit or svelte/kit or something else entirely — if anyone has strong opinions, this is the place to share them.

Also, if there's any obvious stuff I missed from this post, let me know

[benmccann]

lgtm. and I'm glad you went with the SvelteKit variant 😄

[vedam]

hey all,
concerning naming I just want to throw in my two cents from the design-view of things.
I try to figure out on how we treat/see KIT in context of svelte.
Is ist a product, a subbrand, a tool? Because this will influence the way we want to deal with it visually later.
I've made a quick rough'n'dirty to visualize what I mean.
And from what we have so far with our branding, I'm not really happy with CamelCase-Kit. ;-)

[antony]

Hey @vedam! I think we briefly discussed svelte/kit on the recent maintainers call. I really like uppercase lowercase on one line, but also the 2nd and 3rd. In terms of how it sits, it's more akin to a product I guess. But I'll let others correct me.

On Tue, 3 Nov 2020 at 14:27, Achim Vedam ***@***.***> wrote: hey all, concerning naming I just want to throw in my two cents from the design-view of things. I try to figure out on how we treat/see KIT in context of svelte. Is ist a product, a subbrand, a tool? Because this will influence the way we want to deal with it visually later. I've made a quick rough'n'dirty to visualize what I mean. And from what we have so far with our branding, I'm not really happy with CamelCase-Kit. ;-) [image: brand-perspective] <https://user-images.githubusercontent.com/64245/97996989-c171a200-1de8-11eb-8d32-3df00e98ebcd.jpg> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5638 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVORPPVFSQLW66WJDBOWDSOAHOVANCNFSM4TIJ7CPA> .

--

…

________________________________ ꜽ . antony jones . http://www.enzy.org

[vedam]

Are we using it standalone somewhere (i.e. an own landing-page), or will it always been seen in conjunction with SVELTE?

[benmccann]

It will be hosted on kit.svelte.dev

While the Svelte logo is written in all caps on svelte.dev, people still write Svelte when writing it (instead of all caps). I think the most consistent thing to do here would be to do the same and make the logo something like the fourth one where it's all caps, but still write SvelteKit in the text.

[arxpoetica]

@vedam awesome work. We should probably separate out the branding stuff into its own ticket somewhere. Just so we don't muddy the waters here. Yes?

[vedam]

My fav is the second. SVELTE remains SVELTE and KIT is the engine behind.
kind of ... powered by

[vedam]

Ahh, ok sorry... just because Rich mentioned it on top...

[gterras]

Two minors points :

• the first sentence mentionning kit is Snowpack is at the vanguard of this movement, and it's what powers SvelteKit. it may need a dedicated introduction sentence.
• In the Typescript part it would be nice to add if full TS support will still need svelte-check or if any other kind of enhancement is planned.

[arxpoetica]

@vedam oh, I guess you're right. Still might be good to have it's own ticket just so we can track any branding stuff when this gets merged.

[Rich-Harris]

@gterras excellent points — I've addressed both of those in the updated copy

[Rich-Harris]

Thanks for the feedback everyone, have merged this and will tweet out tomorrow at some point.

@vedam thanks for these ideas. I think I'm more into the all caps variants. I also wondered about something along these lines?