Re:Implementing single-file web components
by the_other on Monday March 23, 2020 @02:03PM
(#22666798)
_This_ front end developer _loves_ writing HTML and CSS, regardless of my previous several years of JS, React, Angular, Backbone etc.
Re:Implementing single-file web components
by woodrowbarlow on Monday March 23, 2020 @01:43PM
(#22666560)
would you mind sharing the source or stack for your microsite? your setup sounds like something i'd enjoy using.
Re:Implementing single-file web components
by chrisfinazzo on Monday March 23, 2020 @02:36PM
(#22667154)
Code is here - https://github.com/chrisfinazzo/reverse-job-posting
Started on GH Pages, but moved to Netlify which gives me a bit more fine grained control.
Pardon the dust;
First, I'm not a graphic designer and second this is actually an older deploy that I've "locked" so I can continue tinkering with the master branch behind the scenes. Will be a single page with just anchors to navigate when done.
Everything old is new again. Homepages, kids, ask your parents about them :)
A web that was built on documents fragments because the JS and server-side developers think writing raw HTML and CSS is gross.
Email developers would like a word with them.
This isn't going away, and at some point, adding more abstractions is actually harmful.
As I have little else to do at this point - Tl;dr When you work for a public library, but are closed the public, nothing happens - I'm rewriting a small microsite I made for job hunting purposes.
Other than a Service Worker cache, it's markup and styles all the way down, stitched together with Make.
For my blog, I've stuck with Liquid, because Jekyll - which I actually like (ducks) - will be interesting to see if this gets revived and actually lands one day.