+[[!meta title="The SIPB Website"]]
+
## Design
* The design is equivalent to the old design, just with the design trends of the current time (alternatively, built in the 21st century, but without sufficient design clue)
* Too grey
* Blocks of color are gratuitous and jarring
* Gradients are gratuitous
+* A design that could be reused for other websites with minor color tweaking would be nice (like the Debathena stylesheet)
+* Rectangles and straight lines make it look angular and stark
+* The design is too generic; needs more SIPB personality, so that another website couldn't just be swapped in
+* Consider rebranding possibilities (e.g. making fuzzball more "internal" like octocat on github, developing new logos, etc.) (publicity opportunities)
## Todo
* git push (scripts-git, or gitosis on an XVM)
* commit zephyrs for git (wiki.git and ikiwiki.git)
* breadcrumbs style
-* style for code blocks (see [[projects/sipb-afs-sync]])
* make style usable for other SIPB sites?
* make title == alt on images
* sipb-door widgets
* other widgets
* migrate sipb.mit.edu/doc
* usability tests
+
+## How Things Work
+
+(this is by fawkes's understanding, it may be wrong)
+
+###When a request comes in:
+ a connection comes in for sipb.mit.edu which via a hack in MIT DNS gets directed instead to PENGUIN-LUST.MIT.EDU. If its on ports 80, (443?), or 444 it gets passed off to scripts (where its handled by b-m or b-k, whichever).
+
+vhost configuration on scripts looks in ~~sipb-ww/web_scripts and checks the .htaccess file:
+
+if request is for /rtfm.html, pass through
+if request is for /iap pass of to stuff/iap (lives in /afs/athena.mit.edu/activity/s/sipb-iap/www/ of all place)
+if request if for /cgit, or /wiki pass through
+else pass request for foo to wiki/foo, served from there
+
+
+###For developments sake:
+
+####How Do I make edits?
+If you want to just edit contents, use the web interface (edit links at bottom of page) or "git clone git+ssh://sipb-www@scripts.mit.edu/mit/sipb-www/wiki.git", make your edits in the mdwn, etc.
+
+When you commit, ikiwiki should get automatically republished as HTML
+
+
+####Detailed Locker Layout
+
+.
+|-- Scripts: was being used for scripts.git, currently unused
+|-- arch
+| \-- amd64_fedora9_scripts: binaries related to publishing ikiwiki
+|-- bin, lib, sbin: links into arch
+|-- ikiwiki
+|-- man: a link into arch, ikiwiki manpages. add sipb-www to get them into MANPATH
+|-- share -> arch/amd64_fedora9_scripts/share
+| |-- ikiwiki: where some basic things are pulled from during build
+| |-- locale: i18n things we aren't using
+| `-- man: where the manpages really live
+|-- ikiwiki: thing of it as like a mix of etc and build
+| |-- cgitrc : configuration for cgit
+| |-- ikiwiki.setup: configuration for ikiwiki
+| `-- src: where the git repo (wiki.git) is staged for building
+|-- src
+| |-- cgit: where cgit was built from (not actively changed)
+| |-- ikiwiki.git: the git repository representing the SIPB variation on ikiwiki.
+| `-- old.ikiwiki: irrelevant
+|-- web_scripts
+| |-- RCS: .htaccess mus be versioned
+| |-- cgit: what you look at when you click on "History"
+| |-- doc: the old Trac Wiki
+| |-- iap -> /mit/sipb-iap/www
+| |-- radiant: old and irrelevant
+| |-- rtfm: contains an index.html identical to rtfm.html below
+| |-- rtfm.html: served for rtfm.mit.edu:80
+| `-- wiki: the published HTML that you are being served right now
+|-- web_scripts_tmp: old directory around to keep trac up-to-date. Should vanish sooner or later
+`-- wiki.git: this is where all the content lives as markdown. Clone this if you hate web interfaces
+
+