JointsWP 6: Updates & Call for Contributors #366
Comments
|
That's exciting @JeremyEnglert I had a couple fixes for the JWP5 code base I've been meaning to PR, would it be worth crushing them so we can cleanup the issue queue and leave JWP5 users with a final tidied version? |
|
Hello Jeremy,
I want to contribute to JointsWP 6 project, tell me what to do ;)
greetz,
Steven Persoons
…On 11 Oct 2018, 22:39 +0200, Jeremy Englert ***@***.***>, wrote:
The development of JointsWP 6 has started - and it's by far the biggest change to the framework since it launched. I'm starting this thread as a way to keep everyone looped in and see if anyone wants to help contribute to the project. For some of these, I'll also create separate "issues" where they can be discussed in depth.
Project Goal
JointsWP is more than a "starter theme" - it's a badass starter theme with a modern development workflow that allows developers to create custom WordPress themes more efficiently with fewer headaches.
Automated Theme Setup with Node
After running npm install or yarn install, the console will ask you a few questions to help automate the setup of the theme. This will do things such as automatically update the namespace of functions and the textdomain of translated strings.
Issue Link: Coming Soon
CSS Framework Options - Foundation, Bootstrap, No Framework
Flexbox and CSS Grid have made CSS frameworks less vital than before, however, they are still very important for many developer's workflows and are also great tools for prototyping. JointsWP 6 will allow you to use Foundation, Bootstrap or no framework at all. Check out the issue link below for more details on how this will work.
Issue Link: Coming Soon
WCAG AA 2.0 Compliance
The theme needs to be fully WCAG AA compliant. This means we need to use the right Aria labels and follow the recommended WCAG guidelines. Ideally, we leave some notes throughout the theme that will help users keep their builds compliant even after they start to customize it. Also, maybe we use something like pa11y (https://github.com/pa11y/pa11y) to add automated testing as part of the Gulp workflow.
Issue Link: Coming Soon
Gulp: Automated Translation Files
Gulp: Regression Testing with Backdrop JS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Glad to hear a new version is coming, this is definitely the go to starter theme. One question @JeremyEnglert what is your take on Gutenberg for this new version ? |
I think the idea of Gutenberg is great! We'll finally have a consistent way to generate custom content across sites - instead of using 30 different "page builders", we'll have a native way of doing the same thing. However, I don't like that it is being rushed into core despite not being fully accessible - which breaks a fundamental promise to the WP community. With that said. I hope future versions of JointsWP can include custom Gutenberg blocks for the frameworks it supports. For example, it would be awesome to have all of the Foundation components be available as Gutenberg blocks. |
I think that's a great idea. I'll start working through the Issue and PR queue and see what we can clean up before we completely shift focus to the new version. |
|
I'll help where I can. Proper integration into gutenberg would be fantastic news, it's really easy for site admins to use. I love the concept of it, but as you've said, they're maybe rushing it a bit as I'm still finding clashes in places with other plugins. |
|
I would love to be able to help, Our company has been paying a lot more attention to WCAG so I will share what knowledge we come across. Also documenting the theme folder name must be lowercase for multisite installs in order for customizer to work correctly will save someone some headaches. We are using JointsWP to serve multisite sites to our Franchising clients, currently we have 600 active sites, and are in the process of revamping and existing network of 400 sites converting them from bootstrap to Joints, so my experience in Multisite can be helpful. Thanks for the opportunity to assist, I am excited. ML |
|
Hey @JeremyEnglert I was just speaking with @mlangone and we were hoping you could setup a Slack for collaboration (and potentially support in future). Or we could connect on the Foundation slack. Thank you |
|
I would caveat the request with invitations to the slack channel, as a development channel, not a support channel for previous JointsWP releases.
… On Oct 29, 2018, at 12:40 PM, Garrett Hyder ***@***.***> wrote:
Hey @JeremyEnglert <https://github.com/JeremyEnglert> I was just speaking with @mlangone <https://github.com/mlangone> and we were hoping you could setup a Slack for collaboration (and potentially support in future). Or we could connect on the Foundation slack. Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#366 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD11Nwjf_KFBJHwSL1VEYtRiru0xcGTwks5up1m2gaJpZM4XYU65>.
|
Hi. I'm a newcomer to Foundation, but an old hat in WP. Can I throw a wild idea out here? Would it make sense to skip reinventing the wheel (theme base) and go straight to added value (Foundation integration)? Instead of putting in months of "yet another badass theme framework" churn work (a lot of it required just to get to "table stakes" vs others), perhaps the committee could gather around the campfire and work to pick a solid modern base from the ecosystem (there's a ton, why add more?) - and build the smoothest ever Foundation integration / layer / whatnot on top of that. Stretch goal: become the official source of Foundation integrations to > 1 widely known theme frameworks (Mythic, Roots, Genesis, WP Rig, ..., ...) I am about to embark on Foundation-integration project for https://github.com/justintadlock/mythic/ for our in-house projects, and was researching the ecosystem for prior work. Your thoughts? |
|
@mlangone @garrett-eclipse - I'll get a slack channel setup for development discussion. I'll shoot out invites as soon as it's ready. Great idea! @lkraav - the current version of JointsWP does a great job of integrating with Foundation (in fact, it's often recommended and used by the people at ZURB). If the goal was to create an awesome WP theme that integrates with Foundation, we already have that. But I have some concerns with sticking to Foundation. Progress on the Foundation project has come to almost a complete stop. There's a couple of users who are super active in trying to support the framework - but without more help, it's hard to see where the framework is going. Also, with Flexbox and CSS Grid becoming more and more popular, the need for a framework is starting to diminish.
Roots already supports Foundation and Bootstrap. Genesis has integrations with Foundation. And JointsWP is more well known than WP Rig and Mythic (which are both pretty new). The goal is to have JointsWP be more than "a starter theme that uses Foundation". The Gulp (soon to be Webpack) workflow is really damn good. I see JointsWP becoming a "go to" theme regardless of what framework you want to use. The workflow included in JointsWP will be what attracts developers. No more messy Webpack configs or changing between themes because you need to use a different framework. JointsWP will be able to handle it all in a sane fashion. The flexibility of Roots is probably the closest thing to what we're trying to mimic (but Roots takes its own course in regards to the WP hierarchy - which adds a bit of a learning curve). If you're interested in joining the developer slack channel that was mentioned above, let me know and i'll get you added! |
|
Jeremy,
I have been working on integrating material design with JointsWP, my new
designers are leaning on material design for everything now. Im glad to
hear we are moving towards webpack this will fit in nicely with my current
project, future proofing it. Let me know if your interested in going down
this (Material Design) rabbit hole :)
ML
…On Fri, Nov 16, 2018 at 2:37 PM Jeremy Englert ***@***.***> wrote:
@mlangone <https://github.com/mlangone> @garrett-eclipse
<https://github.com/garrett-eclipse> - I'll get a slack channel setup for
development discussion. I'll shoot out invites as soon as it's ready. Great
idea!
@lkraav <https://github.com/lkraav> - the current version of JointsWP
does a great job of integrating with Foundation (in fact, it's often
recommended and used by the people at ZURB). If the goal was to create an
awesome WP theme that integrates with Foundation, we already have that.
But I have some concerns with sticking to Foundation. Progress on the
Foundation project has come to almost a complete stop. There's a couple of
users who are super active in trying to support the framework - but without
more help, it's hard to see where the framework is going.
Also, with Flexbox and CSS Grid becoming more and more popular, the need
for a framework is starting to diminish.
Stretch goal: become the official source of Foundation integrations to > 1
widely known theme frameworks (Mythic, Roots, Genesis, WP Rig, ..., ...)
Roots already supports Foundation and Bootstrap. Genesis has integrations
with Foundation. And JointsWP is more well known than WP Rig and Mythic
(which are both pretty new).
The goal is to have JointsWP be more than "a starter theme that uses
Foundation". The Gulp (soon to be Webpack) workflow is really damn good. I
see JointsWP becoming a "go to" theme regardless of what framework you want
to use. The workflow included in JointsWP will be what attracts developers.
No more messy Webpack configs or changing between themes because you need
to use a different framework. JointsWP will be able to handle it all in a
sane fashion.
The flexibility of Roots is probably the closest thing to what we're
trying to mimic (but Roots takes its own course in regards to the WP
hierarchy - which adds a bit of a learning curve).
If you're interested in joining the developer slack channel that was
mentioned above, let me know and i'll get you added!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#366 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD11N5nXJUhL34PJkmUY8xpVIYoo61z_ks5uvzAWgaJpZM4XYU65>
.
|
|
@JeremyEnglert mL |
Hi @JeremyEnglert. I quoted a few parts that appeared most relevant to the "efficiency" thread started earlier. For context, I'm coming from a background of "no infinite budget to hire infinite engineers", so I value efficient work and cooperation. While I don't doubt this team's to-be re-engineering effort might result in a solid "workflow that attracts developers", I'd like to point out that a bunch of themes and/or frameworks are already there. Very modern, very advanced, months if not years of high fidelity work completed. Here, I see a tremendous risk of spending months if not a few years, and at best, reaching feature parity with someone else (this after reviewing existing JointsWP code). Depending on how much time and energy this team has next to families, day jobs, etc. At the same time, most open source projects are starving for energy and work, including above-mentioned systems that today might have already arrived at some higher fidelity by modern standards. There's always new ways to compose additional value (sometimes much more) on top of an existing framework, instead of competing at the base framework fidelity level. Have yet to see a good tool that has less than 100 issues open.. Probably depends on what the ultimate overarching goal is here - for personal engineering learning, of course, nothing beats rolling your own. True value for the world.. might lie somewhere else. Depends on if can make the "sum is greater than parts" vector work with someone. PS I happened across JointsWP relatively randomly, so don't really have a dog in the race at this point, but this thinking has rolled around in my head for a while, so I thought I'd write it out with someone and get some real world feedback - why, why not, etc. FLOSS research project so to speak. |
I think the way JointsWP does things (especially in the V6 dev branch) is what attracts so many developers. For the most part, we do things exactly the way the codex suggests - so the learning curve is minimal. JointsWP isn't new. Hundreds - if not thousands - of hours have been put into making it better over the years from dozens of developers. I don't think we need to use someone else's base when we have our own. We can always improve what we have, but starting from a different base doesn't appeal to me. At that point, why not just use that theme? Slapping Foundation on top of any of those themes is simple enough. (And being a "Foundation-only" theme doesn't seem like a good long term strategy anymore). Sidenote: JointsWP started as a fork of Bones with Foundation baked in. So I totally get where you're coming from. |
|
Thanks for thinking with me. That's all I have for now. |
|
Hi @JeremyEnglert! I'm super excited about a JWP6 version. I have been using JWP for many many client sites over a few years period now. Would be happy to help wherever I can. Any news on that slack channel? |
|
Is this still open? Would like to contribute :) |
|
@Baggio89 - whats your email? Would love to get you added to the Slack channel. |
The development of JointsWP 6 has started - and it's by far the biggest change to the framework since it launched. I'm starting this thread as a way to keep everyone looped in and see if anyone wants to help contribute to the project. For some of these, I'll also create separate "issues" where they can be discussed in depth.
If you can comment on what you'd be interested in helping on, that'd be great!
6.0 Branch Link: https://github.com/JeremyEnglert/JointsWP/tree/6.0-dev
Project Goal
JointsWP is more than a "starter theme" - it's a badass starter theme with a modern development workflow that allows developers to create custom WordPress themes more efficiently with fewer headaches.
Automated Theme Setup with Node
After running
npm installoryarn install, the console will ask you a few questions to help automate the setup of the theme. This will do things such as automatically update the namespace of functions and the textdomain of translated strings.This is all handled by Node, so anyone with solid Node/JS skills would be helpful!
Issue Link: Coming Soon
CSS Framework Options - Foundation, Bootstrap, No Framework
Flexbox and CSS Grid have made CSS frameworks less vital than before, however, they are still very important for many developer's workflows and are also great tools for prototyping. JointsWP 6 will allow you to use Foundation, Bootstrap or no framework at all. Check out the issue link below for more details on how this will work.
Anyone who is familiar with Foundation or Bootstrap can be extremely helpful here.
Issue Links
JointsWP 6: Supporting Multiple Frameworks - #367
JointsWP 6: Base Theme Style Discussion - #368
WCAG AA 2.0 Compliance
The theme needs to be fully WCAG AA compliant. This means we need to use the right Aria labels and follow the recommended WCAG guidelines. Ideally, we leave some notes throughout the theme that will help users keep their builds compliant even after they start to customize it. Also, maybe we use something like pa11y (https://github.com/pa11y/pa11y) to add automated testing as part of the workflow.
Anyone familiar with WCAG compliance and testing can be extremely useful here.
Issue Link: Coming Soon
Drop Gulp in favor of Webpack
Better Documentation
The text was updated successfully, but these errors were encountered: