P050601a: Develop InfoNote Boostrap

Status	Date	Description





	2005-08-21	Errata: i000006 0.20 First steps say nothing about putting a title for the note in the title block. [Look to see what the rest say for putting the title in too.]
	2005-08-21	Errata: i000006 0.20 self-anchor is split into two URLs at the "i" - watch that in customizing and also fix it (the i is not to _top).
	2005-08-21	Errata: i000006a 0.20 has two 2's in the first steps
	2005-08-21	Errata: i000006b and i000006c 0.20 , First step is redundant and needs to be cleaner
	2005-08-21	Errata: i000006b 0.20 has a blank line at the top of the page body
	2005-08-20	Errata: i000006a 0.20 First Steps (1) should refer to the <head> title only (the one manipulated by editing the FrontPage File \| Properties). The other cases are covered in following items.
	2005-08-20	Errata: i000006 0.20 absolute URL for "Develop InfoNote Bootstrap Template 0.20 Material" is completely wrong in the initial Revision History entry. It should be ...
	2005-08-20	Errata: i000006 0.20 The not on customizing the bottom-of-page job-jar link needs to be first in step 5, so that it is not overlooked.
	2005-08-18	Errata: P050601d.txt 0.18 in Section 5, "Creative COmmons" should be "Creative Commons"
	2005-08-18	Errata: P050601d.txt 0.18 has double occurence of "the" in the first lines of the Web page editor entry of section 2, Tools Required. Delete the one beginning the second line.
	2005-08-18	Errata: P050601d.txt 0.18 refers to P050601c.zip in the first entry in section 2, Tools Required. It should refer to P050601d.zip.
	2005-08-17	I can put bugs on the materials pages, just like on man pages. This is a good place for them, even if they link to bug reports for more-extensive detail.
	2005-08-17	Errata: On i050601d.txt 0.18, the statement on attributions needs to be followed by a statement that these versions do change, and it may be important to say at what date the cited page and material was accessed.
	2005-08-17	Errata: On i050601d.txt 0.18, there is a duplicate "at the" on the end of section 5 (from one line to the next)
	2005-08-17	At some point, this project and the archive manifests need to be tied to the bootspiral checklist (by whatever name it ends up with after the patterns are paraded out and reconciled).
	2005-08-15	Errata: Make it known that there is a bug in the Template 0.00 archive and that we're not going to fix it. This is about taking snapshots in compagno and how the will have relative links resolved to URLs that don't work for anyone else. (It's like the links that end up being to someone's hard drive.)
	2005-08-15	Notebook #46.93: Comment somewhere on the importance of having version suffixes on the archived `.mht` files, so they can be unpacked and compared from different archives. This is tied into identifications, accession numbers, and other goodies.
	2005-08-15	Notebook #46.94: Placeholders are similar to slots for wiki words that haven't been defined yet, but have been mentioned already. They leave a spot for editing and addition, and also let someone else know that there's something that belongs that is coming soon. [dh:2005-08-17 I did that in a comment on the page, but this may be worth mentioning in the pattern involved.]
	2005-08-14	Errata: The bug that I introduced making some browser-captured pages for archiving reminds me about how much I am doing this by the seat of my pants, and I don't have a clear course to navigate. This is a place where documentation is needed even by the implementer of the accountability pattern reflected in how this project's materials are maintained and preserved.
	2005-07-28	At some point we need a description of the template usage process, and the reliance on Microsoft FrontPage that some of the practices are related to.
	2005-06-30	Some of the changes below may apply to P000006 0.10 as well (catch when customizing on ODMA, reflect on P050501 here).
	2005-07-03	There may need to be something about skills needed here in P050601e if not in P000006c.txt.
	2005-06-23	It looks like duplicating all of this stuff bottom-up has to end. It is way too much manual effort, and their are problems maintaining consistency with earlier versions, feeding improvements back to older versions, etc. This is a challenge for software too. We can help some of this by abstracting the common procedure and patterns out, which is very much to the point of TROSTing. We also need to look at how automated templates would help for forward improvements. What about backward refactoring (back-factoring) though?
	2005-06-22	We need more material about attribution and the different uses of them. We need some worked examples too, such as an attribution of the ideas around batch files used with Microsoft Visual C++ Toolkit 2003 and the Platform SDK too.
	2005-06-20	What is the pattern for this? Where do I describe it? [dh:2005-06-22 It looks like migration is a pattern, refactoring is a pattern, splitting and archiving is a pattern, and these are in some integrity/provenance higher-level scheme. There's also a pattern with regard to branching and merging and preserving the history of a development.]
done	2005-08-18	*Post the updated P050601e. material to the hosted site. This is the candidate stable version, although non-template files can be added for improved packaging and documentation.**
done 0.21	2005-08-18	Update P000001 to reflect movement to 0.21 sustaining state.
done	2005-08-18	Check in P050601e.zip and update P050601e.htm to refer to the manifest and the archive versions that are now available.
done 0.23	2005-08-18	Add P050601e.txt into the archive.
done 0.23	2005-08-18	Finalize P050601e.txt to make the manifest that will be archived.
done	2005-08-18	Add .mht snapshots of P050601, P050601e, P050601a3, and this P050601a into P050601e.zip.
done 0.21	2005-08-18	Set the project to a sustaining state on an as-needed continuation activity, on P050601.
done 0.20	2005-08-18	Split all completed items in this Diary and Job Jar into a new P050601a3.htm file.
done	2005-08-13	Split out material into a new P050601a2 so that we can prune this page of as many completed items as possible. Preserve the pages in P050601d.zip.
done	2005-06-22	Split the completed items in this diary out into a backup page so that it is easier to work on what's next. It is not necessary to drag those completed items into 0.10 work when they are already accounted for in the 0.01 snapshot.