projects/thiswebsite.html

   1 <!DOCTYPE html>
   2 <html>
   3   <head>
   4     <meta charset="UTF-8" />
   5     <title>Athene.Gay</title>
   6     <meta property="og:title" content="Athene.Gay" />
   7     <meta name="twitter:title" content="Athene.Gay" />
   8     <meta
   9       name="description"
  10       content="It's the website you're looking at right now, baby!!"
  11     />
  12     <meta
  13       property="og:description"
  14       content="It's the website you're looking at right now, baby!!"
  15     />
  16     <meta
  17       name="twitter:description"
  18       content="It's the website you're looking at right now, baby!!"
  19     />
  20     <link rel="stylesheet" href="../main.css" />
  21   </head>
  22   <body class="whole-site">
  23     <div>
  24       <iframe class="embed-title" src="../shared/title.html"> </iframe>
  25       <div class="main-container">
  26         <div class="main">
  27           <div class="entry">
  28             <a href="../index.html">Home</a>
  29             <div class="title-block">
  30               <a class="blog-title" target="_blank" href="https://athene.gay">
  31                 <h3>This Website</h3>
  32               </a>
  33               <h3 class="datestamp">2025</h3>
  34             </div>
  35             <div class="content">
  36               <p>It's the website you're looking at right now, baby!!</p>
  37               <p>
  38                 I can't pretend this website is particularly complex. It's pure
  39                 HTML and CSS. I don't even have any javascript in it apart from
  40                 the embedded hit counter at the bottom. Maybe I'll use some in
  41                 future if it's necessary but I'm writing each entry directly in
  42                 the HTML instead of pulling from a database or such, so outside
  43                 of doing some fancy shit I don't see why I'd ever need to. Here,
  44                 here's a live screenshot of the site in VSCode so you can see
  45                 I'm really doing this the 'old-fashioned' way:
  46               </p>
  47               <a href="../img/projects/websitevscode.png">
  48                 <img
  49                   class="blog-img-lrg"
  50                   src="../img/projects/websitevscode.png"
  51                   alt="a screenshot of vscode with the html of this page loaded up in it."
  52                 />
  53               </a>
  54               <p>
  55                 The web is too damn complicated nowadays. I don't think this is
  56                 a particularly controversial statement. Everyone seems to want
  57                 to make everything into a single-page application, host with
  58                 node or some .net backing with a big MVC structure behind it,
  59                 have myriad front-end technologies to make everything
  60                 oh-so-slick. And sure, there's a place for that. I work for a
  61                 company whose main product is an Angular SPA with a big .net
  62                 backend that is hugely multifunctional.
  63               </p>
  64               <p>
  65                 But personal websites do not need that, really. I kind of
  66                 fundamentally disagree with it. A portfolio website can impress
  67                 with your talent for design, for sure, but when you're working
  68                 on something like this, where it's just for you - is any of it
  69                 really necessary?
  70               </p>
  71               <p>
  72                 All that overhead certainly makes it slower. The web is so damn
  73                 <i>slow</i> now. I got gigabit internet recently, which has
  74                 certainly been revelatory for streaming and steam game
  75                 downloads, but actual day-to-day web use is basically
  76                 unimpacted. I can download sites faster, theoretically, but the
  77                 framework is doing so much internally that it makes practically
  78                 no difference.
  79               </p>
  80               <p>
  81                 And for a small site of my own, I simply do not want that. I
  82                 want something that feels fast and responsive. And what's faster
  83                 than a static website?
  84               </p>
  85               <p>
  86                 So this is what that is, in a very classic style. Pure HTML and
  87                 CSS. Iframes for stuff like the links and footer bars. Manual
  88                 linking and organisation. A marquee tag for the header, gotta
  89                 respect the classics.
  90               </p>
  91               <p>
  92                 I even have a links panel, which I hope to fill out with links
  93                 to friends' and acquaintances little homes on the internet.
  94                 Webrings were fuckin' cool and we've lost them, so let's bring
  95                 them back. If you want to be included, shout me on
  96                 <a target="_blank" href="https://bsky.app/profile/athene.gay"
  97                   >bluesky</a
  98                 >.
  99               </p>
 100             </div>
 101           </div>
 102         </div>
 103       </div>
 104       <iframe class="embed-links" src="../shared/links.html"> </iframe>
 105       <iframe class="embed-footer" src="../shared/footer.html"> </iframe>
 106     </div>
 107   </body>
 108 </html>