[Seaside] Front-End developer coordination
Jupiter Jones
jupiter.jones at mail.com
Fri May 24 19:59:41 UTC 2019
Hi Bruno,
Like Tim said it “should” be a dream, but in my experience it more often is not :)
Since most dev roles have become sooooo specific, it’s hard to find a CSS developer with an interest in learning another programming language that they can’t perceive as a benefit their career as a “front-end” developer.
In the end I found that creating a static versions of all my main components to hand over to the “front-end” developer got results the fastest.
It allowed them to understand the page structure, as well as the “file” structure without lots of hand-holding.
To keep it maintainable I created a small “dummy” site that exposed a version of each component and then created the static site with wget.
The developer could then use their chosen SASS tools to create CSS that I could load directly into the WAFileMetadataLibrary and it all worked as expected.
Still, there nothing better than a front end developer who wants to learn RenoitSt and improve their whole-life-experience :)
Cheers,
J
> On 25 May 2019, at 5:09 am, BrunoBB <smalltalk at adinet.com.uy> 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
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
More information about the seaside
mailing list