phorge-phorge/externals/skins/oblivious/header.php

<!DOCTYPE html>
<html>
  <head>
    <title><?php echo _e($title); ?></title>

    <?php echo $skin->getCSSResources(); ?>

  </head>
  <body>
    <div class="oblivious-info">
      <h1>
        <a href="<?php echo _e($home_uri); ?>"><?php
          echo _e($blog->getName());
        ?></a>
      </h1>
      <p><?php echo _e($blog->getDescription()); ?></p>
    </div>
    <div class="oblivious-content">
Allow simple template-based skin definitions Summary: Lower the barrier to entry for installing and creating skins, so we can kill Wordpress. You can now install skins by dropping them into a directory, and build either "advanced" (full phutil library) skins or "basic" (simple PHP templates) skins. Next up is getting static resources working in an easy way for skins. I put these in `externals/` for now so they don't get hit by lint. Test Plan: Viewed the Pokeblog with the Oblivious skin. Reviewers: btrahan Reviewed By: btrahan CC: aran Maniphest Tasks: T1373 Differential Revision: https://secure.phabricator.com/D3717 2012-10-17 08:36:48 -07:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<title><?php echo _e($title); ?></title>`
Allow blog resources to be served without Celerity Summary: Allow skins to serve arbitrary resources without needing to be mapped, so we can have a vibrant community of amateur skinners. For "basic" skins, just put all the "css/" on the page always. Includes an image to prove that works. @vrana, pretty sure this has no impact outside of Phame but it does change Celerity so it might be to blame if there's any weirdness with static resources. Test Plan: {F21341} {F21340} Reviewers: btrahan Reviewed By: btrahan CC: aran Maniphest Tasks: T1373 Differential Revision: https://secure.phabricator.com/D3719 2012-10-17 08:37:05 -07:00
			`<?php echo $skin->getCSSResources(); ?>`

Allow simple template-based skin definitions Summary: Lower the barrier to entry for installing and creating skins, so we can kill Wordpress. You can now install skins by dropping them into a directory, and build either "advanced" (full phutil library) skins or "basic" (simple PHP templates) skins. Next up is getting static resources working in an easy way for skins. I put these in `externals/` for now so they don't get hit by lint. Test Plan: Viewed the Pokeblog with the Oblivious skin. Reviewers: btrahan Reviewed By: btrahan CC: aran Maniphest Tasks: T1373 Differential Revision: https://secure.phabricator.com/D3717 2012-10-17 08:36:48 -07:00			`</head>`
			`<body>`
			`<div class="oblivious-info">`
			`<h1>`
one more phame tweak for better social sharing -- make sure $uri is the full uri Summary: basically when we're on a page we have a URIPath so set that and pass it over. I wasn't super duper happy with this but it seems to be the best way to pass this data. Test Plan: verified the og:url was correct on my dev instance of phacility blog for both the main blog and individual post view Reviewers: epriestley Reviewed By: epriestley CC: chad, aran, Korvin Differential Revision: https://secure.phabricator.com/D4269 2012-12-21 13:46:23 -08:00			`<a href="<?php echo _e($home_uri); ?>"><?php`
Allow simple template-based skin definitions Summary: Lower the barrier to entry for installing and creating skins, so we can kill Wordpress. You can now install skins by dropping them into a directory, and build either "advanced" (full phutil library) skins or "basic" (simple PHP templates) skins. Next up is getting static resources working in an easy way for skins. I put these in `externals/` for now so they don't get hit by lint. Test Plan: Viewed the Pokeblog with the Oblivious skin. Reviewers: btrahan Reviewed By: btrahan CC: aran Maniphest Tasks: T1373 Differential Revision: https://secure.phabricator.com/D3717 2012-10-17 08:36:48 -07:00			`echo _e($blog->getName());`
			`?></a>`
			`</h1>`
			`<p><?php echo _e($blog->getDescription()); ?></p>`
			`</div>`
			`<div class="oblivious-content">`