search

xfiveco / dev-tools

Discussion, ideas, comments on our development tools & workflows.
0 stars 0 forks source link

General Discussion #2

Open luboskmetko opened 9 years ago

luboskmetko commented 9 years ago

A general thread for quick discussions, brainstorming ideas, etc.

danekszy commented 9 years ago

So the whole point of this repo is to give voice to developers and see what we're struggling with, what would help us and throw our ideas around. Since idea for this repo was established out of our discontent with generator, I propose we put it at the center, and think what could be done better and what would help us work more efficiently...

To kick off the discussion here are some of my ideas (inc. crazy ones :smile:):

Let me know what you think and don't hesitate to discuss or to propose your own. If some ideas will get traction we'll move the discussion to separate issue. Let the brainstorm begin! :smile:

adamsfather commented 9 years ago

Very good ideas Dan! :+1:

in addition to scss reusable mixins I believe there's potential of collecting reusable html snippets and javascript interactions which are frequently used from project to project. We don't need to recreate Bootstrap or ZURB foundation, however having own standardized and fine tuned library of responsive FE elements, would save work time and avoid repetitive coding tasks, I believe. (maybe I'm totally wrong here ;P)

danekszy commented 9 years ago

@adamsfather Sure, like: http://pea.rs/navigation/horizontal-tabs http://refills.bourbon.io/components/ http://responsiveemailpatterns.com/ We could get the essentials and make them easy to import (eg. uncomment the file import etc.) But we have to remember that the key here is to speed us up, and not bloat with unused stuff... :wink:

adamsfather commented 9 years ago

@danekszy you know I had an idea some time ago when generating project in generator, to have such possibility to choose which elements it will generate based on selection which corresponds with designs e.g. image slider, accordion, header nav, mobile menu, parallax-like div, page scroll, news box, service box, content box with image, etc...

As developer you can easily recognise what elements you'll use in your code by reviewing the design. Example, an image with heading, paragraph and button will always have the same markup on any project, I see no point of creating different markup each time project is setup.

You wanted crazy ideas, here they are! - LOL

luboskmetko commented 9 years ago

Nice ideas, guys!

Objects in ITCSS (I propose to switch to it in #1) are such reusable design patterns, check https://github.com/inuitcss?utf8=%E2%9C%93&query=objects

The advantage of objects is that they are, let's say, visually agnostic but can be quickly combined with components to create desired UI

Generic Object https://github.com/itcss/itcss-netmag/blob/master/css/_objects.media.scss

Project specific Component https://github.com/itcss/itcss-netmag/blob/master/css/_components.testimonials.scss

HTML snippet: https://github.com/itcss/itcss-netmag/blob/master/index.html#L76

danekszy commented 9 years ago

Yeah, these 2 can be complementary. Reusability is a broad term and therefore we may apply it at various levels of abstractions. Be it patterns, components or just simple mixins or helpers. :)

luboskmetko commented 9 years ago

Right :) Just some thoughts on your ideas yet:

Azzam commented 9 years ago

Hi guys well i like that ideas so far i got some of points

also if we create default snippets and components etc we can build our own template for example using something like Polymer or x-tag or custom elements that will reduce a lot of time too