🚀 Create Guten Block 2.0 Goals/Call for Contributors!

[ahmadawais]

🚀 Today, I am super excited to release the first public version of create-guten-block.

📖 I wrote a 3,000 words blog post about it → https://awais.dev/cgb-post

Yes, that's not all done, yet. I have managed to change the codebase and release many updates by now, before actually announcing a stable release. The next step is to get this toolkit tested and mature the entire app to release version 2.0.0 for that not only do I need your support, I ask that you hop on board and contribute — that's the only way forward.

Goals listed below — without any order of priority:

• [x] Add single-block and multi-block examples to this repository — Examples directory added here →
• [ ] 💯 Get folks on React, webpack, & Babel teams to review the configurations for best possible results
• [ ] ⚡ Go beyond React — with Preact, Inferno, Marko, Angular, Vue, etc. JavaScript frameworks
• [ ] 📖 More examples need to be documented. Especially a Multi-block example which is easy
• [ ] 🔰 Babel 7, webpack 4, upgrades to follow in the next major version of create-guten-block
• [ ] 🚧 ESLint integration needs a refresher — ESLint + Prettier setup is already WIP
• [ ] ⛓️ Refactor code into small modules and maybe make small npm packages
• [ ] 📑 Improve inline documentation throughout the codebase
• [ ] 💎 Build more cgb-dev-utils — separation of concerns
• [ ] 📤 Possible integrations: Service Workers from Google
• [ ] 📣 Possible integrations: Progressive Web Apps
• [ ] 👻 .env file limited set of customizations
• [ ] 🤓 Allow custom forks of cgb-scripts
• [ ] 📦 Create New Block Command → #18
• [ ] 🛠️ Improve the entire Webpack defaults
• [ ] 🗃️ Webpack file handling done right
• [ ] 📹 Webpack image optimization
• [ ] 👹 Webpack Uglify ES6 plugin
• [ ] ⚙️ Webpack + BrowserSync
• [ ] 💠 Automated test suit
• [ ] 🔔 Create examples
• [ ] 🤔 Other stuff? #Suggest
• [ ] 🙌 PR's welcomed

Peace! ✌️

[tfrommen]

Hey there,

I will give it a shot later this weekend. And: I'm happy to contribute where I can! 🙌

[JulienMelissas]

This is super exciting! Would love to help tackle some Webpack optimizations or .env stuff if you lay that out with what you're thinking a bit more. Feel free to @ me dude!

[ahmadawais]

📣 This is super awesome @tfrommen and @JulienMelissas — I'd like to proceed in a similar fashion to how we are working at WPGulp 2.0 — basically anything you'd like to start working on, copy its title from here and make an issue and let's start tracking it's progress in there.

So happy to have you onboard trying to make this project better. 💎

[MaedahBatool]

🙌 Super excited to be a part of this project and I am looking forward to leading its documentation and building user guides around it. 🎯

— And @MrSaqibAmeen will be assisting me.

[asharirfan]

🙌 I would love to contribute to this project.

👀 I will start by reading the code ✅ Improving the inline documentation of the codebase 🚀 And work my way up from there

[dmhendricks]

Would it be interesting to (optionally) run prepack on the build result?

[abdullah1908]

🙌 Yes, I am also interested! Explore the Gutenberg in free time.

[ahmadawais]

@asharirfan @abdullah1908 sure thing dig in!

@dmhendricks what would be the benefit in doing that?

[JulienMelissas]

@dmhendricks, I know this should probably be in a separate issue... BUT,

While I am far from an expert on Prepack it says this on their site:

Prepack is still in an early development stage and not ready for production use just yet. Please try it out, give feedback, and help fix bugs.

I'm not sure if I'd recommend adding it to this library considering people are looking to build production-ready blocks. The benefits could be nice, but it can create some unwanted side-effects that be difficult to debug (at least for people who are not aware of it's existence in the build process) currently.