[Helpers] Library files

Thu Feb 16 22:46:20 PST 2006

   I made the library form months ago, and there were errors, which were 
compounded when Hillary used the form to make new pages, with inadequate 
directions from me, on how they were supposed to be handled.  I'm fixing 
them all today, and I will grab Sandra D's archived files and convert them 
too...

   unless you want to do it, Sandra? You were asking about it in August but 
I was not ready for that step yet.  You are more familiar with the files 
you saved, and what lesson they are for. Holy cow there are a lot of them! 
Looks like you got up to lesson #9...

   but I really need you to continue as you were doing, editing poplink 
files and archiving wayback pages.

   Not sure I have clearly communicated how the library  will work, so I 
thought it best to write a fresh email with clear instructions, that can be 
archived for future reference. I'm also attaching the instructions as a 
plain text file so people viewing with an html browser can read it without 
the html samples disappearing.

Revived links from the wayback machine are going into
www.kundalini-gateway.org/library

   I decided to put them there instead of on FS.c because the gateway being 
nonprofit educational, probably gets more elbow room with "fair use" 
copyright guidelines... hopefully reducing the necessity for tracking down 
authors and getting permission.

  FST poplink file links that are revived will appear as
    http://www.kundalini-gateway.org/library/lib_FILENAME.html

  The original form I created for the library pages had some errors that 
are now fixed.. like the SSI not working.

   I've attached the new form to this email so you can have a copy with the 
SSI links intact... which is not possible if you save it with a browser.

  I decided to go with SSI originally, so that gathering the content and 
updating the poplinks could be done separately from making library pages 
out of it. Splitting the big task into pieces that could be done by 
different people.

   Anyone could save the wayback files, and update the poplink with the 
filename
  www.kundalini-gateway.org/library/lib_CONTENTFILENAME.html as a single 
job- Sandra D!

   and she/they or another could edit the saved files into includes and 
submit the include content, as a simple html file with basic formatting of 
paragraphs and line breaks, but no tables, head or footer, (Easiest to copy 
& paste the relevant bit into a new file, rather than delete the excess. 
Also spam proof email addresses) and the same person or someone else 
-people with FTP upload access could enclose the SSI into the lib_form to 
make new library pages.

  Thus, my intention was that the poplinks going to the library could be 
updated according to what the archived page was saved as, or a placeholder 
url with the filename, even though the library form was not finished, and 
the pages they link to are not yet created.

   I've gone through the linkylink notes for lesson matgod&introK, made 
notes where the new library files are located, and created the files for 
the missing pages that were worth keeping.
   Updated linkylinks file is in helpers/sdavis and the library files are 
uploaded to the K-gateway.

   Each library page will have two files:
  The include file of basic content:
   www.kundalini-gateway.org/library/CONTENTFILENAME.html

The page to link to, with the form visitors will see:
www.kundalini-gateway.org/library/lib_CONTENTFILENAME.html
plus, some pages will have a subfolder of files of images if there are any.

    So, if you find a file at the wayback machine, view-source and save, 
with an appropriate and short filename. Make the poplink link to match it.

   The next step in the assembly line, is to open the html file and delete 
the headers, footers, everything but the basic content and essential 
formatting of line breaks, etc. Leave in <img-src=links to important 
images, and make sure the images are saved in a subfolder and they 
work.  Remove tables, and spam proof addresses.

At the top, for reference, paste in a *comment*  
identifying the filename, the dead link url and the wayback machine url 
where it was found, and an email address for the author, if there is one. 
Make a note of which poplink file it is for. Re-save.

   In this way -using coment tags- we can gather the basic content files to 
use as includes, and save the reference info in the code so it will be 
available to helpers but invisible to visitors. Most of that info I see is 
saved into reference pages accompanying the file. Excellent! Using comments 
instead, will mean fewer files to keep track of.

   The next step is to enclose the include content into the 
lib_form.html  by updating the form: the SSI link to the include, and 
pasting the title and the reference info from the comment tag or reference 
file, into the appropriate place in the form,  to make the pages appear 
consistent. That process is explained in more detail, below.

  Save the updated lib_form as the include name, but keeping the prefixed 
lib_ to indicate it belongs in the library folder.  lib_filename.html.

  Someone, adds a link to it in the library/index.html file. I think it is 
good to have an index file, but I don't think it is important to keep it 
perfectly up to date.

  How to use the lib_form.html to make new library pages,  in more detail:

  To use to make a new file, adjust the lib_form.html  in these three places:

Step 1:
line 3: <title>Kundalini Gateway: Library of lost links. TITLE </title>
+Paste in the original page title where it says TITLE.

Step 2:
line 17: <font size="-2">The original location of this page circa --- was 
<b><br>
PASTE IN DEAD LINK URL

+ paste in the year of the wayback file archive, in place of ---
+ Paste in the old dead link url, in lowercase.( It is a text url, for 
reference,  not a link. No point in creating a dead link! )

Step 3:
line 22: <!--#include virtual="/library/PASTE IN INCLUDE FILENAME.html" -->

+paste in the filename of the include content, in lowercase.
Example:
<!--#include virtual="/library/chakras.html"-->

optional step 4!
line 26:  Archived page found at <a href="http://web.archive.org/" 
target="link_window">http://web.archive.org</a>

+optionally, update these urls to the actual wayback machine link where the 
page was found. No big if it is not done. I have a feeling the time machine 
probably reorganizes itself on a regular basis and I'm not looking forward 
to having to always update the links to it!

   Finally: Save the form under a new name, lib_filename.html

   Someone, probably Hillary will add a link to it, to the 
library/index.html page.

  Update the poplink file with the new url, if it needs doing.  Links that 
are revived will appear as
    http://www.kundalini-gateway.org/library/lib_FILENAME.html

  Got questions?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fire-serpent.org/pipermail/helpers_fire-serpent.org/attachments/20060216/fb7ffbb3/attachment.html>
-------------- next part --------------

Revived links from the wayback machine are going into
www.kundalini-gateway.org/library 

  I decided to put them there instead of on FS.c because the gateway being nonprofit educational, probably gets more elbow room with "fair use" copyright guidelines... hopefully reducing the necessity for tracking down authors and getting permission. 

 FST poplink file links that are revived will appear as 
   http://www.kundalini-gateway.org/library/lib_FILENAME.html 

 The original form I created for the library pages had some errors that are now fixed.. like the SSI not working. 

  I've attached the new form to this email so you can have a copy with the SSI links intact... which is not possible if you save it with a browser.  

 I decided to go with SSI originally, so that gathering the content and updating the poplinks could be done separately from making library pages out of it. Splitting the big task into pieces that could be done by different people.  

  Anyone could save the wayback files, and update the poplink with the filename 
 www.kundalini-gateway.org/library/lib_CONTENTFILENAME.html as a single job- Sandra D! 

  and she/they or another could edit the saved files into includes and submit the include content, as a simple html file with basic formatting of paragraphs and line breaks, but no tables, head or footer, (Easiest to copy & paste the relevant bit into a new file, rather than delete the excess. Also spam proof email addresses) and the same person or someone else -people with FTP upload access could enclose the SSI into the lib_form to make new library pages. 

 Thus, my intention was that the poplinks going to the library could be updated according to what the archived page was saved as, or a placeholder url with the filename, even though the library form was not finished, and the pages they link to are not yet created.  

  I've gone through the linkylink notes for lesson 1 & 2, made notes where the new library files are located, and created the files for the missing pages that were worth keeping. Updated linkylinks file is in helpers/sdavis and the library files are uploaded. 

  Each library page will have two files:
 The include file of basic content:
  www.kundalini-gateway.org/library/CONTENTFILENAME.html  

The page to link to, with the form visitors will see: 
www.kundalini-gateway.org/library/lib_CONTENTFILENAME.html  
plus, some pages will have a subfolder of files of images if there are any. 

   So, if you find a file at the wayback machine, view-source and save, with an appropriate and short filename. Make the poplink link to match it.

  The next step in the assembly line, is to open the html file and delete the headers, footers, everything but the basic content and essential formatting of line breaks, etc. Leave in <img-src=links to important images, and make sure the images are saved in a subfolder and they work.  Remove tables, and spam proof addresses. 

At the top, for reference, paste in a *comment*  identifying the filename, the dead link url and the wayback machine url where it was found, and an email address for the author, if there is one. Make a note of which poplink file it is for. Re-save.

  In this way -using coment tags- we can gather the basic content files to use as includes, and save the reference info in the code so it will be available to helpers but invisible to visitors. Most of that info I see is saved into reference pages accompanying the file. Excellent! Using comments instead, will mean fewer files to keep track of. 

  The next step is to enclose the include content into the lib_form.html  by updating the form: the SSI link to the include, and pasting the title and the reference info from the comment tag or reference file, into the appropriate place in the form,  to make the pages appear consistent. That process is explained in more detail, below. 

 Save the updated lib_form as the include name, but keeping the prefixed lib_ to indicate it belongs in the library folder.  lib_filename.html.

 Someone, adds a link to it in the library/index.html file. I think it is good to have an index file, but I don't think it is important to keep it perfectly up to date. 

 How to use the lib_form.html to make new library pages,  in more detail: 

 To use to make a new file, adjust the lib_form.html  in these three places:

Step 1: 
line 3: <title>Kundalini Gateway: Library of lost links. TITLE </title> 
+Paste in the original page title where it says TITLE.

Step 2: 
line 17: <font size="-2">The original location of this page circa --- was <b><br> 
PASTE IN DEAD LINK URL 

+ paste in the year of the wayback file archive, in place of ---
+ Paste in the old dead link url, in lowercase.( It is a text url, for reference,  not a link. No point in creating a dead link! )

Step 3:
line 22: <!--#include virtual="/library/PASTE IN INCLUDE FILENAME.html" -->

+paste in the filename of the include content, in lowercase.
Example:
<!--#include virtual="/library/chakras.html"-->

optional step 4! 
line 26:  Archived page found at <a href="http://web.archive.org/" target="link_window">http://web.archive.org</a>

+optionally, update these urls to the actual wayback machine link where the page was found. No big if it is not done. I have a feeling the time machine probably reorganizes itself on a regular basis and I'm not looking forward to having to always update the links to it! 

  Finally: Save the form under a new name, lib_filename.html 

  Someone, probably Hillary will add a link to it, to the library/index.html page.  

 Update the poplink file with the new url, if it needs doing.  Links that are revived will appear as 
   http://www.kundalini-gateway.org/library/lib_FILENAME.html  