You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience.
The event contains a piece of information that may be of interest in the future. A day is typically a flow of events and each event is in its own event document. That way the events may be referenced easily by a link.
While the event document my feel like a form at first glance, it is not. All properties (besides name and short description) and sections are - as always with the projectdoc Toolbox - strictly optional. But some of them are very handy to quickly organize events and add references to related information.
Properties
The document type event provides the following properties:
Continuation of
Provide a link to an event this event continues with. Sometimes topics are investigated over a number of days. With pointing to the last event of investigation the flow of events on a very specific topic is easier to lookup later.
Rating
A rating on how much fun this event provided.
Sections
Description
All things to remember about this event goes in here.
Subordinate Events
In case you need to divide the information of this event in several events. The only reason to do so is to have each subordinate event referable by its own URL.
Attachments
In case you add documents of any other type than event as child to this page, they will be automatically shown in this section. Again, this is only useful if you need to make references to these pieces of information.
Previous Work
This section lists the events that have previously dealt with the same piece of work. This is a listing of the "Continuation of" information.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
Resources
Related document types.
Name | Short Description |
---|
Annual Vision | Describe your vision for one year. You plan will help you stay focussed to accomplish your goals. |
Annual Vision Type | Categories for annual visions. |
Asset | Explain an asset of your work. Add this document to a day in your diary. |
Asset Type | |
Cheat | A brief solution to a problem. |
Cheat Type | |
Day | Store relevant information discovered today in your developer diary. |
Day Type | |
Diary | The homepage of a developer's daily diary pages. Consider to add your diary to your personal space! |
Diary Type | |
Event | Associated an event with a day. A event is a collection of associated information for your later reference. Information may further be organized by subject, tags, categories, and audience. |
Event Type | |
Month | Plan and run a retrospective for your month of work. |
Month Type | |
Todo | Add a todo note to your developer diary. |
Todo Type | |
Vision | Describe your vision for your career. |
Vision Type | |
Week | Plan and run a retrospective for your week of work. |
Week Type | |
Year | Create a year in your Diary. |
Year Type | |