Collin J. Doering
512e89f565
* Changes
** Hakyll "site.hs"
*** Added the ability to have per-page templates (for all "pages/*")
*** "pages/*" can now be sectioned off into blocks
A section is a logical division of a page. It removes the requirement
for pages that have multiple sections to have some html in the
markdown for the page or to move some of the markdown content to the
template. Both of which are un-maintainable.
There are two types of sections, both with slightly different syntax's.
A _global section_ is a section who's content will be included in all
sections (regardless of ordering). This is handy for including links
and footnotes that might be needed in more then one section or
non-section . It is not accessible from the Context obtained from
genSectionContext. To indicate where a global section begins and ends
use "$section$" and "$endsection$" respectively (without
quotes). Formally:
$section$ <body> $endsection$
A _named section_ is a section of a document that can be accessed by a
given name from the context obtained from the function
genSectionContext. To specify a named section use the following syntax:
$section("<name>")$ <body> $endsection$
where <name> is the name of the section (any character except \")
and <body> is the section body
Anything that is not a section is referred to as a non-section. These
are still important as they will include all
content of the global sections of the document as well as the
non-section itself. To be a little more formal a non-section is
everything between "$end-section$" and ("$section$ or
$section("<name>")$").
**** Example: mypage.markdown
page title
==========
$section("column-one")$
This is text that can be formatted in the individual page template
located at "templates/pages/mypage.haml". Here is a link from a
global section. See [Home][].
$endsection$
This is some text in between two sections or a section and the top or
bottom of the page. It can be accessed by $body<n>$ where <n> its
position from the top of all non-sections starting from 0. Here i can
also use
$section$
[Home]: http://blog.rekahsoft.ca
$endsection$
***** To see more visit
- "pages/<name>" where the sectioned page markdown is written
- "templates/pages/<name>.haml" where the individual page
template is stored/loaded from
- "templates/page.haml" the generic page wrapper
** Miscellaneous
*** Reorganized the file structure
- created folder "image-src" for image-sources
- created folder "lib" for libraries that will be needed on the server
- moved jQuery and Skeleton to lib and made appropriate
- created folder "fonts" for FreeMono and FreeSans font files which are
now used via css @font-face
- create folder "css" and setup "site.hs" to minimize all css files
and publish them to idRoute
- created folder "sass" which contains a variety of s[ac]ss files along
with a file named "default.s[ax]ss" which will be processed by sass
to include any other s[ac]ss files that are needed and output
"default.css" to the site root
*** cleaned up .gitmodules
** Javascript
- fixed processing of urls
- temporarily disabled nojs version of site as its under heavy development
Note: still need to merge changes made to default version into the
nojs one; specifically having "templates/pages/*.haml" be applied to
there respective page before "templates/page.haml" is applied to the
result
** Styling
- switched to using sass (with a side bourbon) instead of css
leaving css folder and processing for convenience
- slimmed the site of the nav-loading image
- updated favicon (rounded corders, preparing to support more sizes)
- updated the logo-banner
- added new images for tab page
** Templates
- converted all "templates/**" to haml and made the apropriate
adjustments in site.hs
- added "templates/pages/*" which contains individual templates per
page in "pages/*"
** Known Issues
**** Sections cannot contain $section$ or $section("<name>")$ or $sectionend$ in them (this is an issue with escaping in the parser)
**** pagination has been attempted but no solution yet
**** haven't been able to generate two sets of tag-pages (one for the default version and the other for the nojs version
**** opening a internal link in a new tab in any browser will load the snippet that would normally loaded by by ajax
Signed-off-by: Collin J. Doering <rekahsoft@gmail.com>
2.9 KiB
| title | author | date | description | updated | tags |
|---|---|---|---|---|---|
| Deploy Command Working | Collin J. Doering | 2013-10-30 | An Article about programming in general | 2013-11-26 | general, programming |
I'm happy to announce another peice of bogus news! The deploy command is now functional! Yeah! Anwyays a Loren Ipsum is below. Sensors indicate no shuttle or other ships in this sector. According to coordinates, we have travelled 7,000 light years and are located near the system J-25. Tractor beam released, sir. Force field maintaining our hull integrity. Damage report? Sections 27, 28 and 29 on decks four, five and six destroyed. Without our shields, at this range it is probable a photon detonation could destroy the Enterprise.
These are the voyages of the Starship Enterprise. Its continuing mission, to explore strange new worlds, to seek out new life and new civilizations, to boldly go where no one has gone before. We need to neutralize the homing signal. Each unit has total environmental control, gravity, temperature, atmosphere, light, in a protective field. Sensors show energy readings in your area. We had a forced chamber explosion in the resonator coil. Field strength has increased by 3,000 percent.
Communication is not possible. The shuttle has no power. Using the gravitational pull of a star to slingshot back in time? We are going to Starbase Montgomery for Engineering consultations prompted by minor read-out anomalies. Probes have recorded unusual levels of geological activity in all five planetary systems. Assemble a team. Look at records of the Drema quadrant. Would these scans detect artificial transmissions as well as natural signals?
Exceeding reaction chamber thermal limit. We have begun power-supply calibration. Force fields have been established on all turbo lifts and crawlways. Computer, run a level-two diagnostic on warp-drive systems. Antimatter containment positive. Warp drive within normal parameters. I read an ion trail characteristic of a freighter escape pod. The bomb had a molecular-decay detonator. Detecting some unusual fluctuations in subspace frequencies.
Deflector power at maximum. Energy discharge in six seconds. Warp reactor core primary coolant failure. Fluctuate phaser resonance frequencies. Resistance is futile. Recommend we adjust shield harmonics to the upper EM band when proceeding. These appear to be some kind of power-wave-guide conduits which allow them to work collectively as they perform ship functions. Increase deflector modulation to upper frequency band.
Run a manual sweep of anomalous airborne or electromagnetic readings. Radiation levels in our atmosphere have increased by 3,000 percent. Electromagnetic and subspace wave fronts approaching synchronization. What is the strength of the ship's deflector shields at maximum output? The wormhole's size and short period would make this a local phenomenon. Do you have sufficient data to compile a holographic simulation?
Resistance is futile.