 |
guide.gph - gopher-lawn - The gopher lawn gopher directory project. |
 |
git clone git://bitreich.org/gopher-lawn/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhf… |
 |
Log |
|
Files |
|
Refs |
|
Tags |
|
--- |
|
guide.gph (1015B) |
|
--- |
|
1 |
|
2 ~~[[ T H E G O P H E R L A W N ]]~~ |
|
3 |
|
4 Meta description of the gopher lawn. |
|
5 |
|
6 _____[[ G_O_A_L_S ]] |
|
7 Goals of THE GOPHER LAWN project. |
|
8 |
|
9 * Categorize the interesting part of the gopherspace. |
|
10 * Categorize useful links to telnet, ssh, usenet, bbs services. |
|
11 |
|
12 _____[[ S_T_Y_L_E ]] |
|
13 Writing the index file for a gopherhole is very easy. Just see the |
|
14 files in the »db« directory in the repository: |
|
15 [h|git://bitreich.org/gopher-lawn|URL:git://bitreich.org/gopher-lawn|ser… |
|
16 |
|
17 _____[[ N_A_M_I_N_G ]] |
|
18 Category naming. |
|
19 |
|
20 * The frontpage categories have to be self-describing. Unobvious naming … |
|
21 lead to too much text, making the directory unusable. |
|
22 * If some naming is too complex, make the internal search more practical. |
|
23 * First reuse existing categories. |
|
24 |
|
25 _____[[ L_I_N_K_I_N_G ]] |
|
26 Linking guide. |
|
27 |
|
28 * Pick a short name for the link. |
|
29 * Add a description of what to find at that link and how it is related t… |
|
30 category. |
|
31 * Try to avoid more than two lines of description. |
|
32 |
|
33 |
|
34 [1|<< back|/lawn|server|port] |
|
35 |
