sveltejs / community-legacy Goto Github PK

General Readme differs from readme inside of WhosUsingSvelte

Currently we pull stats from GitHub including stars and last_updated - https://github.com/sveltejs/community/blob/master/scripts/updateGithubStats.js#L23

We just got our first GitLab library resource with PR #150. The existing script doesn't break but it won't keep the GitLab stats in sync.

Should we try to move this stuff over to sveltesociety?

Hi! I am planning to organize a new Svelte Meetup (and also Discovery Live Training). Here are the details:

City: Paris (at first, then other cities around the country)
Country: France
Description: First official Meetup (and also Trainings) to have french developers discover and share about Svelte/Sapper (which I (as CTO of my startup studio - Rocket Studio France) now exclusively use with my teammates - around 6 developers - to build new innovative web platforms). 
Event Name: To be defined, we're still brainstorming with the team !
Organizer contact: Jean-Baptiste Blanc (myself) => [email protected]
Twitter: 
Type: Meetup (or Training Course on Svelte /Sapper)
Url: www.rocketstud.io (sorry, French website and Svelte version is still under development -we focus more on our startups platforms development at the moment)
Other relevant details: 1/ I wonder if this is possible to get our dedicated sveltesociety github repository (like some other cities from the society). 2/ We have dedicated office in Paris so we can host these first events until it gets too popular for our meetup room :-). 3/ I'd love to share with you our plans at Rocket Studio France around Svelte and Sapper for 2020 and next.

https://github.com/sveltejs/svelte/issues/2656

we should split source data files and the scraped files. i've done the basic investigations we will need

• https://www.swyx.io/writing/github-scraping
• https://github.com/sw-yx/gh-action-data-scraping

cheap image hosting for now :)

Move data into JSON and then use an each block inside of svelte component.

I'll do the refactor :)

who is using svelte show more buttons styles are overwritten

TS is coincidentally embarking on the same thing we're doing and they have a bunch of good ideas and inspiration sources

• microsoft/TypeScript-Website#63
• microsoft/TypeScript-Website#88
• https://github.com/typescript-community
• https://github.com/typescript-community/governance/tree/docs

please make spinoff issues for stuff you want to work on if you have an idea you like and link back

for each page, add og:* metadata so this SEOs nicer and shows up nicer in unfurls. fun first project :)

Hey 👋

I browsed the community page a few days ago on my phone and was a bit annoyed that the resources page was not optimized for narrow viewports. Would it be okay to submit a PR to get the page in a better mobile format?

When someone asks "what routers does Svelte have?", you should be able to link to the resources with the "routers" tag/category selected, like /resources/#tags=routers or some other url format. It probably make senses to delay implementing this until we get a more stable design for tags/categories. (see #23)

Searches should be similarly mirrored in the url. Future UI state should likewise be easily added.

The window location should probably update as the user makes changes in the UI.

What url format makes the most sense? Hash, querystring, or a combination of a pushstate and hash/querystring like /resources/tag/routers?search=boo? The best answer may depend on the tags/categories design.

This is a starter boilerplate template

https://svelte-community.netlify.app/code?tag=integrations and https://github.com/sveltejs/integrations both exist and have different lists. It would be nice to consolidate everything in one place

sveltejs/integrations is better organized. There are so many tags on this site that it's hard to read through them all. Perhaps categories and sub-categories would be a better way to go. E.g. "preprocessors" could be a sub-category of "integrations"

This repo could allow sorting by stars (https://github.com/sveltejs/community/issues/202) automatically, which would be really nice. That'd be harder to do on sveltejs/integrations

https://svelte-community.netlify.app/code has a ton on it and can be difficult to navigate. Even when choosing a tag, there can still be a lot in a single category

when i open https://svelte-community.netlify.app/code/
then the sidebar on the right does not scroll
only the content on the left is scrollable

when i scroll all the way down to the bottom
i can see the bottom part of the sidebar

maybe solve this with

.stickySidebar {
    overflow-y: auto;
    height: calc(100vh - 40px);
}

.container {
    /*grid-template-columns: 2fr 1fr;*/
    /* add width for scrollbar */
    grid-template-columns: 2fr 1.1fr;
}

As we start getting more resource submissions, we'll want a clear set of guidelines for tagging resources so they remain useful. Too much or too little looseness can make tags difficult or unhelpful in practice. Curating them well means every resource that should be under a tag is, and the tags are specific, descriptive, and manageable in number. Here on GitHub we have the topics svelte, sveltejs, svelte-v3, svelte3, and many un-topic'd projects, which is just a leaky unhappy experience.

The search function already does fuzzy matching against the name, description, url, and other fields, leading me to believe we can be tighter with our tag usage.

As a concrete example, here's our first submission that prompted me to post this: sveltejs/community@db01c41

  - name: "`Real World Svelte and Google Cloud Masterclass`"
    url: "https://www.youtube.com/playlist?list=PLCrwuqjmVebK08Cwz_XB55cNKFfFYOMGo"
    description: A video series taking you through the Real World Svelte app tied in with a Google Cloud Functions backend
    tags:
      - Sapper
      - Real World
      - Google Cloud

I'm currently thinking I'd tag this resource with sapper, videos, and maybe learning or education, and I'd remove Real World and Google Cloud, which can be searched.

@kevmodrome brought up the idea of having hierarchical categories. The original resources list was organized that way, and it works well but is unable to express cross-cutting information like labeling official resources unless they can belong to many categories. Does it make sense to have both nestable categories and tags as distinct systems? Or should we try to make it one system? Should we rethink cramming code libraries and arbitrary links into the same resource system?

The initial set of tags for the community resources came by copying over the headings from awesome-svelte-resources, so consider them a first pass.

Hi

awesome-svelte from the resources page leads back to the here, should it be removed? replaced?

• Start here:
  https://svelte-community.netlify.app/resources

• click on "awesome-svelte"
  

• it takes you to: https://github.com/CalvinWalzel/awesome-svelte which has a big warning and link that leads you to this github repo.
  

Should it be removed from here since it's no longer needed?
https://github.com/sveltejs/community/blob/master/data/resources.yml#L162

So quite recently (about a week ago) my PR was merged adding our company's site to the who's using component.
Ever since I've been eagerly refreshing the svelte.dev site to see if our logo has been added, but to no prevail.
I've been watching the Svelte commits (as usual) and was hoping a new release would also trigger the site rebuild, but sadly it did not.

From what I could see in all the CI files and whatnot, there does not seem to be something in place that would trigger a site rebuild in case one of the extracted components gets updates.
Is this something that's being planned to be added?

code from typescript

https://github.com/microsoft/TypeScript-website/blob/6ac6bd65097dc5bba29da868703975de9dce51db/packages/community-meta/scripts/generateRichMeetupData.js#L1

http://www.typescriptlang.org/v2/community/

When I load https://svelte-community.netlify.app/code/ it says "Code • Svelte Community" for a second and then changes to "404 • Svelte Community"

There is a problem with the https certificate at

 http://www.sveltestatus.com/

What's a reasonable and scalable policy for including company logos on svelte.dev? I'm not sure what policies are like in comparable projects. The current set of logos now overflow the vertical space on a 1080p layout and there's ~70 requests with ~400k data. When does this become a problem and what are the possible solutions? Continue taking all submissions? Maybe limit the number that are eagerly loaded and put the rest behind a click? (randomly sorted?)

Is there a way I can showcase my project if it has a private repo? It has transaction in it and that's why it can't be public.

Seems the filter functionality has gone haywire the last few days, not sure when or what happened. Couln't spot anything obvious in the few minutes I looked at it.

ReferenceError: options is not defined

Anything like these for Svelte?

• https://github.com/vazco/uniforms

• https://github.com/frontier-forms/frontier-forms

https://github.com/sveltejs/svelte/issues/3908

It would be nice if there was a suggestion box of some description in case searching for events in a specific area yields no results. This would be a good way to see how much interest there would be in organising a meetup in that area. People who upvoted or added the suggestion could possibly be notified if an event ever does get organised in that area (or perhaps within a certain distance of that location).

@lukeed Requested this. If anything needs clarifying Luke is the one to ask!

This is just a question I wasn't sure where to post. Would you accept PR's for the showcase?

@dreitzner what was your prettier config? if there isn't one we could add a config.

Originally posted by @peopledrivemecrazy in https://github.com/sveltejs/community/issues/388#issuecomment-766557107

It might be good to port the editor config from sveltejs/svelte, as they are using some parts from this repo.

It has been brought to our attention here sveltejs/svelte#4001 that the Winston site might be illegally hosting videos.

I think since this is probably not something we want to encourage, and might be a legal grey area, that this particular site should be considered for removal.