Comments (13)
Starters are a key part of where I see Gatsby going.
Great starters are key because:
- They vastly speed up the initial time-to-value.
- Give non-programmers a way to play.
- Long-term they help disseminate best-practices.
from gatsby.
@fson suggested on Slack that instead of maintaining a central yaml file, just standardize around a "gatsby-starter" tag in package.json. 👍 from me for that.
from gatsby.
package.json
That would only work if the starter is published to npm but the starter is hosted on github?
from gatsby.
No the indexer could read the package.json from github just fine.
from gatsby.
But then you still need to provide a central place for telling about the github repo with that package.json
from gatsby.
Right, starters will be manually added here via PRs.
from gatsby.
It's actually possible to scan the whole npm registry looking for specific tags inside the packages.
I have a toy project (not a Node.js developer... yet?) that does that. It would need a server for running the "live" version of it, otherwise it would need to be triggered on demand.
It's a bit of work but it would discover any starter published on npm.
Not sure about Github's API.
from gatsby.
There might (hopefully) be a day where there's too many Gatsby starters to easily manually curate but I'd guess we're a long ways off from that :) So for now, creating a registry maintained here seems like a reasonable approach. So until then, adding Github repos to the registry which then get scanned for metadata (most likely added to the package.json) and added to the Gatsby website seems like the right approach.
from gatsby.
@gesposito https://www.npmjs.com/browse/keyword/http :) it pretty simple, but gatsby starters is git repos and not npm modules
from gatsby.
Oh, I did forget about #20. If/when that lands, then the "base" sites would almost certainly be installed via NPM. E.g. you'd install the gatsby-blog-base
package which would provide the base _template
+ index
files and you'd just need to add markdown files for posts. But those (whatever they're called) would always be treated differently than starters. Starters are meant to "start" off a site. They're malleable etc. "Base" sites are more like Wordpress themes where they set the structure, etc. of your site so you just need to add content.
from gatsby.
Some CLI inspiration https://github.com/drjekyllthemes/drjekyll
from gatsby.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
from gatsby.
closing this issue as active discussion has moved to #3003
from gatsby.
Related Issues (20)
- Skip media from download, get URL in query only
- Outdated reference to Gatsby Cloud in documentation HOT 1
- While shadowing a css file from a gatsby theme the changes are reflected in netlify preview but not on deployment HOT 4
- Null-Byte (\0) in HTML output files
- Missing onError handler for invocation 'building-schema', error was 'Error: Cannot create as TypeComposer the following value: Date.' HOT 1
- onClientEntry not called when using `gatsby develop`
- Redirects and Headers stopped working on Netlify (and work again in gatsby 5.12.12 / adapter 1.0.4) HOT 9
- Showcase page has some sites which are not using Gatsby js anymore, and still they are in Featured sites section HOT 4
- Show case crashed when search HOT 1
- gatsby-source-wordpress (v^7.13.1) incompatible with latest version of WPGraphQL HOT 1
- The repository archived babel-plugin-lodash is using the deprecated isModuleDeclaration.
- Compatibility issues between gatsby-plugin-mdx v5 and remark-gfm v4
- GatsbyImage process the image on build & build is slow HOT 5
- Media Image is null. HOT 1
- double rendering on mobile
- Error on gatsby build command : WebpackError: TypeError: Endpoint URL must start with `http:` or `https:`. HOT 1
- UNHANDLED REJECTION There is no worker with "1" id. when building on aws amplify
- Adding loading strategy to Gatsby GTM plugin (or any other script loader)
- After gatsby build and gserve: not able to access/use newly added files from the server.
- gatsby-plugin-page-creator: slugify.preserveCharacters does not have any effect
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gatsby.