swyx [9:07 PM]
idea 1: gatsbb : phbb clone of gatsby (to move support off github?) and to show off the incremental building speed. including gatsby chat?
sub-idea - gatsbb with hooks into github to support monorepo open source orgs - this is something github themselves know they suck at (edited)
idea 2: gatsbysandbox - a way to upload and share only the gatsby-relevant parts of an app for better communication around debugging (edited)
idea 3: gatsby cloud services - easily transferable bundled hosting and cms solution for freelancers doing client sites
idea 4: one click transfer from wordpress
idea 5: gatsby analytics - apart from guess.js, providing analytics as a plugin
swyx [9:58 PM]
idea 6: (havent figured this out) pave path to buffer content into regular email list
idea 7: youtuber email capture
idea 8: twitter/tweetstorm source + page generation
idea 9: inspo sites (designsystemsrepo.com, reallygoodux.com, etc) templates
—
we need to figure out the top 3 user archetypes we want to focus on - how to aim at influencers here?
—
idea 10: podcast pages - libsyn, overcast.fm
idea 11: eggheadio course
idea 12: add to freecodecamp syllabus
idea 13: howitworks.io
swyx [10:24 PM]
idea 14: screencast onboarding - people to try recording themselves trying out gatsby, in exchange for one hour of help on any problem of their choice from a gatsby team member
idea 15: gatsby talks central - aggregate all the talks given on gatsby everywhere
swyx [7:09 PM]
idea 16: fast.com for gatsby
idea 17: jamstack jobs board
idea 18: microsite starters
idea 19: (low level dx) fb style invariant warnings with links
swyx [8:32 PM]
idea 20: versioned docs? react is doing it
shannonsoper [12:14 PM]
joined #swyx-ideas.
shannonsoper [12:52 PM]
This is awesome! Some of these things (more ambitious things) could turn into RFCs!!
swyx [12:53 PM]
thanks!!haha i’ll have to elaborate on some of them, i was just doing some brain storming and needed a place to store ideas
kylemathews [1:59 PM]
joined #swyx-ideas.
swyx [4:33 PM]
idea 21: darwin information typing: https://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture
Wikipedia
Darwin Information Typing Architecture
The Darwin Information Typing Architecture or Document Information Typing Architecture (DITA) is an XML data model for authoring and publishing. It is an open standard that is defined and maintained by the OASIS DITA Technical Committee.
The name derives from the following components:
Darwin: it uses the principles of specialization and inheritance, which is in some ways analogous to the naturalist Charles Darwin’s concept of evolutionary adaptation,
Information typing, which means each topic has a defined primary objective (procedure, glossary entry, troubleshooting information) and structure,
Architecture: DITA is an extensible set of structures.
swyx [5:49 PM]
idea 22: gatsbysaurus :: https://docusaurus.io/
docusaurus.io
Docusaurus · Easy to Maintain Open Source Documentation Websites
Easy to Maintain Open Source Documentation Websites
idea 23: gatsby on github pages guide - how to kill jekyll?
swyx [10:54 AM]
idea 24: gatsbybook (for internal use, later outsourcing)
swyx [5:49 PM]
idea 25: vscode liveshare debug https://overcast.fm/+B1TFXIgWM
overcast.fm
JSJ 316: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build — All JavaScript Podcasts by Devchat.tv
Panel: Charles Max Wood Special Guests: Rachel MacFarlane and Matt Bierner In this episode, the JavaScript Jabber panelists discuss Visual Studio Code with Rachel MacFarlane and Matt Bierner, who are both developers on Visual Studio Code. They talk about what the workflow at Visual Studio Code looks like, what people can look forward to coming out soon, and how people can follow along the VS Code improvements on GitHub and Twitter. They also touch on their favorite extensions, like the Docker extension and the Azure extension and their favorite VS Code features. In particular, we dive pretty deep on: Rachel and Matt intro Month to month workflow of Visual Studio Code VS Code JavaScript, Type… Show more
swyx [1:07 AM]
idea 26: swag as a service
swyx [1:47 AM]
idea 27: mdn + gatsby
swyx [1:47 AM]
uploaded this image: idea 28: chrome lighthouse docs + gatsby
swyx [12:28 PM]
idea 29: (internal) we need a project manager.
swyx [1:25 PM]
idea 30: How Gatsby Works guide (for me)
swyx [2:40 PM]
idea 31: plugin configurator https://webpack.jakoblind.no/
qtn 1: how do we decide on fundamental api changes - this determines a lot of downstream things
qtn 2: how do we have a sense of urgency
swyx [3:46 PM]
qtn 3: gatsby on spectrum? vs gatsby on github?
swyx [3:56 PM]
qtn 4: where did meteor fail?
swyx [7:34 PM]
idea 31?: create-jamstack-app is ejectable gatsby setup with: mdx + netlifycms, swappable themes, plug and play components. 3 marketplaces.
swyx [7:59 PM]
in typescript
swyx [8:08 PM]
idea 32: new graphiql
swyx [9:14 PM]
idea 33: tutorials/guides/starters to link to plugin page
idea 34: gatsby vs code extension - to hint at lifecycle apis (edited)
qtn 5: what would you -remove-?
idea 35: separate plugin support?
swyx [9:31 PM]
qtn 6: (minor) move www out to own repo?
shannonsoper [12:05 PM]
replied to a thread:
Sounds similar to what I just saw in https://www.cockroachlabs.com/docs/stable/start-a-local-cluster.html
cockroachlabs.com
Start a Local Cluster (Insecure) | CockroachDB
Run an insecure multi-node CockroachDB cluster locally with each node listening on a different port.
swyx [1:24 PM]
qtn 7: what’s our true north?
qtn 8: what is the riskiest assumption in .com?
qtn 9: gatsby and netlify are veeeeerry closely tied in people’s minds. do we lean into it? if so, how can we do more frequent/formal collaboration?
swyx [7:52 PM]
idea 36: devrel strategy in japan - japan has a huuuge perf culture https://www.youtube.com/watch?v=Afy7H04X9Us
YouTubeConfreaks
RailsConf 2018: How We Made Our App So Fast it Went Viral in Japan by Ben Halpern
swyx [8:12 PM]
qtn 10: do we want to support the reactiflux gatsby channel? can we tie it into the slack? ditto spectrum. my bias is kill reactiflux. (edited)
swyx [9:11 PM]
idea 37: gatsby tiered plugin author/docs recognition - blazing/smoldering - enforce docs standards, reward with prominent recognition
swyx [9:43 PM]
qtn 11: what am i responsible for in first month?
swyx [9:53 PM]
qtn 12: jlengstorf inspired - is OSS strategy about expanding and improving newbie dx (eg create-jamstack-app) or solely improving what we already have?
swyx [1:53 PM]
qtn 13: how to manage external plugin dependencies with gatsby breaking changes - we may want to change the plugin api’s
(related) idea 38: gatsby plugin validator for compatibility check?
swyx [2:58 PM]
idea 39: (small) CLI parameter to opt out of deleting cache because gatsby things “one or more of my plugins have changed”
swyx [3:04 PM]
idea 40: gatsby to typescript.
swyx [3:49 PM]
qtn 14: (within reason) are we: move fast and break things? bias to action, ask for permission later? (edited)
swyx [4:19 PM]
qtn 15: say Tanner Linsley got 4m to go to market with react-static. Do we have a problem marketing to enterprise?
swyx [6:57 PM]
idea 41: graphql endpoint for tools to query gatsby ecosystem https://gatsbyjs.slack.com/archives/CB4V648ET/p1528671339000070?thread_ts=1528591685.000061&cid=CB4V648ET
kylemathews
And actually, making this a publicly accessible graphql server would be pretty hot. Then all the js desktop tools coming out could very easily query the same API for their integration
From a thread in #p-starter-showcaseJun 10th
swyx [7:33 PM]
might as well make a plugin to pull it in too, full circle
swyx [9:20 AM]
idea 42: “gatsbypress idea”: templates to be a magic folder, break up gatsby-node.js’ createPages into individual templates. this is far too common a pattern not to be part of the platform
swyx [10:32 AM]
it should not be possible for templates to “bump” into each other
figure out a way to “force” better filtering of sources for templates
in particular try to prevent lazy filtering like this: if (!_.includes(slug, /blog/)) {
swyx [11:25 AM]
idea 43: gatsby-link state management!!!
swyx [10:13 PM]
idea 44: blogpost: top 7 misconceptions people have about gatsby
swyx [2:37 PM]
idea 45: blogpost - gatsby-plugin-netlify-cache https://github.com/gatsbyjs/gatsby/pull/5956
GitHub
Add gatsby-plugin-netlify-cache to cache image thumbnails by KyleAMathews · Pull Request #5956 · gatsbyjs/gatsby
swyx [4:29 PM]
i put a bunch of starter related ideas here https://github.com/ichabod-cranes/mansion/issues/656
swyx [8:23 AM]
idea 46: headless cms comparison microsite
we win when they win
always drive down the cost of your product complement
swyx [2:08 PM]
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
Joel on Software
Strategy Letter V
When I was in college I took two intro economics courses: macroeconomics and microeconomics. Macro was full of theories like “low unemployment causes inflation” that never quite stood u…
Jun 11th, 2002
swyx [4:19 PM]
idea 47 : dynamic serving with babel: https://developers.google.com/search/mobile-sites/mobile-seo/dynamic-serving discussion in https://softwareengineeringdaily.com/2018/06/21/babel-with-henry-zhu/
Google Developers
Dynamic serving | Search | Google Developers
https://developers.google.com/_static/f3998f9c12/images/share/devsite-google-blue.png
Software Engineering Daily
Babel with Henry Zhu - Software Engineering Daily
Different browsers consume JavaScript in different ways. When a new version of JavaScript comes out, developers are eager to use the new functionality of that language version. But if you are writing frontend JavaScript code, that code needs to be interpretable by every browser that might consume it–whether the consumer is on an iPhone running
Jun 21st
idea 48: a/b testing for enterprise gatsby? need to learn alot more about optimizely
swyx [5:30 PM]
idea 49: firm permalinking guarantee. how to accomplish? what is the value of this?
gatsby permalink ___ command to do special things. actually doesnt seem that hard.
build errors where permalinks are overridden
biz value is debatable tho
swyx [9:30 PM]
idea 50: gatsby macros like babel macros
swyx [3:59 PM]
idea 51: gatsby debug mode
swyx [5:37 PM]
query graphql at each point of the gatsby build phases
swyx [8:37 PM]
hook into/display(/rewind?) redux store
swyx [10:01 PM]
idea 52: design our console output. - can we do better than a bunch of small success numbers
swyx [9:08 PM]
https://github.com/gatsbyjs/gatsby/issues/6137
GitHub
[Discussion] Gatsby Devtools · Issue #6137 · gatsbyjs/gatsby
Summary There is a redux devtools section in the docs and some old issues. But i believe the docs are outdated and also those are for working within the Gatsby repo itself, not with a Gatsby site, …
swyx [6:37 PM]
project management
swyx [6:38 PM]
uploaded this image: Image from iOS
swyx [6:38 PM]
uploaded this image: Image from iOS
swyx [1:31 PM]
idea 53: gatsby educators program - special fast track/support/swag for people who teach webdev eg scott tolinski/wesbos
swyx [2:17 PM]
idea 54: GATSBY SPRINT EVENTS
(and swag)
swyx [2:30 PM]
lol that was answered
swyx
qtn 15: say Tanner Linsley got 4m to go to market with react-static. Do we have a problem marketing to enterprise?
Posted in #swyx-ideasJun 10th
—
qtn 16: still a lot of uncertainty from my contacts about when they can use gatsby. how to communicate “static” vs whatever the heck it is that gatsby actually is?
—
swyx [2:46 PM]
idea 55: special feature for CMSes in plugins section