Thursday, 17 January 2019

Toph Tucker and Jasmine Lee on Why Restaurant Websites Are Good and We’re All Going to Miss Them

quote [ No, there’s absolutely no nostalgia for the web from the position of restaurant workers. I think nostalgia in this context is a privilege. For restaurants, social media is a blessing and a curse. While it reaches a much larger audience, restaurants also become dependent on it to convey their mood or spirit. ]

Webdesigners lamenting over the loss of handmade websites.
[SFW] [do it yourSElf] [+1 Underrated]
[by Paracetamol@11:53pmGMT]

Comments

ComposerNate said[5] @ 11:00am GMT on 18th Jan [Score:1 Underrated]
captainstubing said @ 12:49pm GMT on 18th Jan
Your testimonials are seriously impressive. Congratulations on those.
ComposerNate said[1] @ 2:46pm GMT on 18th Jan
Thanks! Client comments (hopefully?) also double as new content whenever Google respiders a page, showing no page is sitting stagnant as most html only gets otherwise updated every ~30 months.
Bruceski said @ 7:41pm GMT on 18th Jan
The other day someone found out I learned HTML in high school and asked if I can build web pages. My response was "I don't know, can you do frames in Chrome?" If someone wants a Geocities page I can probably remember my old tricks but it's not a skill I've kept up with and there's a HUGE gap between what web design meant in 2000 vs now.
ComposerNate said[2] @ 8:12pm GMT on 18th Jan
My web pages now are all directly evolved from my first band page in 1997 using html 2.0, starting with the Mozilla Composer WYSIWYG program (link), fittingly enough. For each new site, I just copied the most recently built page from my site prior, change the words and images, and gradually shift the tables and swap backgrounds, etc.
Paracetamol said[2] @ 5:52am GMT on 19th Jan [Score:1 Informative]
There are pretty straightforward tactics to make these pages more manageable– this is done by going the static site generator route. Basically, for each language (PHP, Perl, Python, JS, even the pure shell) you have the option to interpret text files as templates.

So once you have a workflow that pipes all of your HTML pages to a second, distribution place, but processing them as templates, you can begin shortening your code.

You start by replacing all repeating blocks like header/footer code with includes, then you can start to use loops for repeating code. Soon you want to use an optional data source next to each template file, which will probably be a JSON/YAML file or a raw object in the language you're using. With every change to one of the pages, you need to trigger a distribution command now, but the result can still be updated via FTP sync, just like before.
ComposerNate said @ 11:06am GMT on 19th Jan
Thanks for this opening introduction! Reading and watching tutorials on this is exhausting, but indeed something I may pursue further, glad to know it exists.
R1Xhard said @ 9:24am GMT on 18th Jan
I thought this might of been a Ussmak post {↧} I'm a little lippie, but 4 pints in :P

Post a comment
[note: if you are replying to a specific comment, then click the reply link on that comment instead]

You must be logged in to comment on posts.



Posts of Import
Karma
SE v2 Closed BETA
First Post
Subscriptions and Things

Karma Rankings
ScoobySnacks
HoZay
Paracetamol
lilmookieesquire
Ankylosaur