creating wiki page for audio_tipitaka





placement of new page

1. create a page or subpage in the tree hierarchy by navigating in audio_tipitaka site to where you want to put the wiki page. Near the top of your screen on the googlesite menu bar choose the "+ create page" option. When creating a page, most of the time you want to choose the second option of putting it under the current page, rather than the first option of "top level".

leave some white space

2. It's a good idea when inserting objects on table of contents, tables, leave yourself some white space (put some surrounding carriage returns where you want to place the object). Googlesite for example seemed to be slightly buggy about insert table row below current row if your table is at the bottom of the page with no white space after it.

insert table of contents object

3. On pull down menu bar (near top of screen) choose the "insert" -> "table of contents" and you'll get a table of contents object, which will build entries based on lines that you format using "format"->"heading H2". The tree can branch 3 levels deep, by formatting sub headings (h3) and sub-sub-headings.

maintaining mobile touch screen device friendliness

4. It would be nice to keep our website for small mobile internet surfing devices like iphone, ipod, android phones, blackberries. A quick and easy way to support it is to use table columns. This way a mobile touch screen device can zoom in and snap into alignment with screen with a quick "tap-tap" command (making tiny text into readable size).  You'll notice all the pages on this site use tables. Tables are different from "layout columns". Layout columns, another formatting option offered by googlesites, at least the way google implements them, won't wrap text and work the way the table columns do.

insert blank 2 column table

4b. insert a blank table with "table"->"insert table", and then choose a size that is two or more columns wide. In general unless there's a really good reason to use more than 2 columns, 2 is better, because too many columns makes the "tap-tap" zoom in snap to a small cell which is too much zoom.

We're really only using the left side of the 2 columns whenever feasible. The right column is left intentionally blank so mobile users don't build up a nagging fear that they're not reading/surveying all of the page. For the mobile user, they can develop a comfort treating the left column as the only real screen most of the time, and glide over to the left menu sidebar to navigate when necessary.

what can mess up mobile devices

5. a note on another thing that can sabotage mobile device screen formatting even if you've followed all the steps so far: If you put in an address with "http://" etc, but without fully setting it up as a "link" (top menu bar), some smart phones like the palm pre will automatically convert that into a hyperlink on the phone's end, and in doing so screws up the nice table formatting we just went through the trouble to set up.

hyperlinks should have some elbow room

When it's feasible, it's best to space out hyperlinks so that they're not bunched up together (vertically and/or horizontally) and hard for a mobile touch screen device user to accurately select a link.

insert blank lines between hyperlinks

the simple approach, but sometimes space is at a premium and we can't afford blank lines, so...

stagger which words are hyperlink clickable

for example this is a (fake hyperlink #1)
(fake hyperlink #2) triggers a different page to load.

Getting rid of ugly table borders?

Select the "html" edit option in the toolbar (last option on right).
Search for this string in the table code:
border-width: 1px;" border="1"
replace it with
border-width: 0px;" border="0"

The audtip.org and subdomain sites (wikis, wip) have some custom templates such as the one named "inviso-table" which you can choose instead of the default "webpage" when creating a new page. Using the template will automatically include a table with invisible borders.


 


Comments