kalamuna
Evaluate and Demo similar styleguide solutions
Edit this issue to add in details to each approach.
Pattern Builder
Look at Pattern Builder and see its implementation. Their Starter that they just launched as well.
KSS + Twig.js
Have a look at implementing sharing the prototyping and templating with the KSS styleguide.... Using Drupal 8.
Drupal Lab
Look at Drupal Lab to see its approach.
@RobLoach @madeofpeople @soniktrooth Can we motivate a first step of moving Kalastatic from Swig to Twig.js (via KSS-node 3.0.0-beta)? This would provide a big win on Dent and GBZ3 by allowing us to re-use component templates.
That only takes care of the style guide but not the prototyping.
On May 30, 2016 10:06:39 PM EDT, Derek DeRaps [email protected] wrote:
@RobLoach @madeofpeople @soniktrooth Can we motivate a first step of moving Kalastatic from Swig to Twig.js (via KSS-node 3.0.0-beta)? This would provide a big win on Dent and GBZ3 by allowing us to re-use component templates.
You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Correcto. I thought you were on board with nixing the prototype on Dent and GBZ3. My plan was styleguide + implementation, no prototype.
On May 31, 2016, at 5:51 AM, Thiago de Mello Bueno <[email protected] mailto:[email protected]> wrote:
That only takes care of the style guide but not the prototyping.
On May 30, 2016 10:06:39 PM EDT, Derek DeRaps <[email protected] mailto:[email protected]> wrote:
@RobLoach @madeofpeople @soniktrooth Can we motivate a first step of moving Kalastatic from Swig to Twig.js (via KSS-node 3.0.0-beta)? This would provide a big win on Dent and GBZ3 by allowing us to re-use component templates.
You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282 https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282
Sent from my Android device with K-9 Mail. Please excuse my brevity. — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222643065, or mute the thread https://github.com/notifications/unsubscribe/ABNKeNH-m9iTFb4zXJ4AjWZFsAYsNq-Aks5qHASfgaJpZM4Im2tj.
I just dnt see nixing the prototype from kalastatic as something that we should be discussing in the kalastatic repo.
Can we avoid this complexity on current projects, sure.
Now changing the codebase in a way that effectively “unsupports” static sites and prototypes (eg. breaks current functionality) is something I think would take more care/discussion and planning.
On May 31, 2016, at 9:34 AM, Derek DeRaps [email protected] wrote:
Correcto. I thought you were on board with nixing the prototype on Dent and GBZ3. My plan was styleguide + implementation, no prototype.
On May 31, 2016, at 5:51 AM, Thiago de Mello Bueno <[email protected] mailto:[email protected]> wrote:
That only takes care of the style guide but not the prototyping.
On May 30, 2016 10:06:39 PM EDT, Derek DeRaps <[email protected] mailto:[email protected]> wrote:
@RobLoach @madeofpeople @soniktrooth Can we motivate a first step of moving Kalastatic from Swig to Twig.js (via KSS-node 3.0.0-beta)? This would provide a big win on Dent and GBZ3 by allowing us to re-use component templates.
You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282 https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282
Sent from my Android device with K-9 Mail. Please excuse my brevity. — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222643065, or mute the thread https://github.com/notifications/unsubscribe/ABNKeNH-m9iTFb4zXJ4AjWZFsAYsNq-Aks5qHASfgaJpZM4Im2tj.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222689662, or mute the thread https://github.com/notifications/unsubscribe/AAE1dXCE5fzEbf9SCs-T_Ckt9bZYDmkhks5qHDjzgaJpZM4Im2tj.
At the same time, it does get us up and running “in the present” so I fully support it. ;)
On May 31, 2016, at 10:04 AM, Thiago de Mello Bueno [email protected] wrote:
I just dnt see nixing the prototype from kalastatic as something that we should be discussing in the kalastatic repo.
Can we avoid this complexity on current projects, sure.
Now changing the codebase in a way that effectively “unsupports” static sites and prototypes (eg. breaks current functionality) is something I think would take more care/discussion and planning.
On May 31, 2016, at 9:34 AM, Derek DeRaps <[email protected] mailto:[email protected]> wrote:
Correcto. I thought you were on board with nixing the prototype on Dent and GBZ3. My plan was styleguide + implementation, no prototype.
On May 31, 2016, at 5:51 AM, Thiago de Mello Bueno <[email protected] mailto:[email protected] <mailto:[email protected] mailto:[email protected]>> wrote:
That only takes care of the style guide but not the prototyping.
On May 30, 2016 10:06:39 PM EDT, Derek DeRaps <[email protected] mailto:[email protected] <mailto:[email protected] mailto:[email protected]>> wrote:
@RobLoach @madeofpeople @soniktrooth Can we motivate a first step of moving Kalastatic from Swig to Twig.js (via KSS-node 3.0.0-beta)? This would provide a big win on Dent and GBZ3 by allowing us to re-use component templates.
You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282 https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282 <https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282 https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222577282>
Sent from my Android device with K-9 Mail. Please excuse my brevity. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222643065 https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222643065>, or mute the thread <https://github.com/notifications/unsubscribe/ABNKeNH-m9iTFb4zXJ4AjWZFsAYsNq-Aks5qHASfgaJpZM4Im2tj https://github.com/notifications/unsubscribe/ABNKeNH-m9iTFb4zXJ4AjWZFsAYsNq-Aks5qHASfgaJpZM4Im2tj>.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222689662, or mute the thread https://github.com/notifications/unsubscribe/AAE1dXCE5fzEbf9SCs-T_Ckt9bZYDmkhks5qHDjzgaJpZM4Im2tj.
the prototype and the style guide aren't sharing templates atm anyway so if there is a 'twig for the style guide' solution then that could be cool. Is that what you're proposing @derekderaps ?
Do eeeeeeeet!
On May 31, 2016, at 4:49 PM, Derek DeRaps [email protected] wrote:
@Josh, yup! Prioritizing the twig switch for the sake of agency work. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kalamuna/kalastatic/issues/306#issuecomment-222816043, or mute the thread https://github.com/notifications/unsubscribe/AAE1dadd1f4eNgVun6pMED11R8i-N_xCks5qHJ73gaJpZM4Im2tj.
#92 is the switch over to Twig, which is a good one to read through. Outlined some of the steps required for the Twig/KSS concept there.
D8 https://www.drupal.org/project/lightning
Panels + Content Editing fixes, a few other things.