eyebeam.orgHome - Eyebeam

\/____/ \/___/ \/____/\/__/\/_/\/_/\/_/\/_/ /\___/ \/__/ ///// VIEW SOURCE BLOG: 01-hello-world ///// Hello world, Thanks for viewing source, I appreciate that you care how this works. @dphiffer here, writing my first "secret" View Source blog post. You can ~only~ read this if you *view source*, it does not otherwise exist in the realm of visible hypertext. (I mean, sure, I bet you could find this text file on GitHub, rendered as a web page, but IMO it's more fun to read this next to the ` ` tags.) The idea for this blog is to help you understand how this site is built, what it is made out of. I learned how to build websites by using 'the source' command on Netscape. Having the source code be visible, but also *legible* is important. HTML source code doesn't include the range of stuff that constitutes a modern web page; back-end code, minified assets, AJAX requests. I'm hoping that these blog posts can help you discover and understand those otherwise hidden away aspects of how each page on here is built. I want you to understand how it all works and maybe you'll even decide to pitch in and contribute your own fixes! The Eyebeam website is here for you to learn from, and perhaps contribute to. If you know how to, you can suggest changes on GitHub as pull requests. Maybe I'll explain how that process works at some point. You can also submit bug reports for things that don't work for you, that is also a super helpful way to contribute. All of that happens on this GitHub repo: https://github.com/eyebeam/eyebeam.org Here is where the bug reports live: https://github.com/eyebeam/eyebeam.org/issues My belief is that running code is only part of the story. After you write and test and deploy the code, things can still go wrong. All Code Has Bugs something I have learned over the years, even for the simplest and most insignificant computer programs. Seemingly tiny changes can cascade to break things unexpectedly. In the long span of its life, software needs to be maintained to continue being useful. This View Source Blog will attempt to make the code that runs eyebeam.org more legible and productive for future maintainers. (And also for Future Me, for when I forget how everything works.) Okay that is all, back to post-launch fixes for me. The next blog post can be found by viewing source over here: https://www.eyebeam.org/archive/ (20180308/dphiffer) -- Click to Show the Menu -- Impact Programs Artists Search Support Support Eyebeam! -- Eyebeam’s mission is to ensure artists become central in the invention and design of our shared future. Become a Member Eyebeam is unveiling a new initiative that aims to bring our community closer to the core of what we do. Our new membership offers inside access to the radical ideas happening behind-the-scenes, a platform for genuine exchange, and a chance to join the conversation with the artists we support. Rapid Response for a Better Digital Future Eyebeam’s Rapid Response for A Better Digital Future supports artists who are reclaiming virtual space from surveillance capitalism. Eyebeam Center for The Future of Journalism ECFJ in BuzzFeed News Alison Killing and Megha Rajagopalan use satellite images, architectural analysis, and digital reconstruction to expose the cruel reality of the modern-day internment camps of Xinjiang. Read More Learn About Eyebeam's Values Read More Values Openness All the work here is driven by an open-source ethos. Invention Build on old ideas to generate new possibilities. Justice Technology by artists is a step towards equality and democracy. -- Stay Updated Enter your e-mail to stay up to date on all of our programs Please wait... Thanks for subscribing! That didn’t work for some reason. About FAQ Values Archive About Us Staff + Interns Advisory + Board Info Press Support Financials Accessibility Data Protection Policy Join Residency Digital Day Camp Jobs & Internships Eyebeam Center for the Future of Journalism 199 Cook St Brooklyn, NY 11206 View on Map +1 347.378.9163 [email protected] @eyebeamnyc eyebeam.org Featured Sponsors --...