Re: Front-End developer coordination
Tim Mackinnon <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <[email protected]> |
Isn’t that the whole point of Seaside and the way it creates well marked html with the ability to consistently put Id’s and structure in everything? It should be a dream for a CSS front end dev? Even more - teach them a bit of Smalltalk and they can create all the hooks they need for pure css? Tim Sent from my iPhone > On 24 May 2019, at 20:09, BrunoBB <[email protected]> wrote: > > Hi, > > We are doing a project with Seaside and there is a Front-end developer > mostly for CSS creation. > > How do you approach this problem (coordination between Seaside developer and > frontend developer) ? > > I mean in Seaside the HTML code is generated but it has to do some > references to the CSS created by the frontend developer. > > One approach can be: > 1) Add css class names (the css does no exist yet) in Seaside code (html div > class: 'to-be-developed-by-frontend-dev'). > 2) The frontend create the CSS file for classes in 1). > > Very simple but i wonder how do you solved this problem ? > > regards, > bruno > > > > > > -- > Sent from: http://forum.world.st/Seaside-General-f86180.html > _______________________________________________ > seaside mailing list > [email protected] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside