Impress Guide version 7.0

Chapter 3 Adding and Formatting Text for the Impress Guide 7.0 has been uploaded to the Drafts folder on NextCloud and is ready for review and comment.

This chapter has been rewritten for two reasons.

1. The changes in Version 7.0 required a rewrite of the old version of the chapter.

2. The old version of this chapter was very poorly written and probably by someone who was not experienced in writing software guides. It was confusing and difficult to follow in some instances. Hopefully I have now corrected that problem.

One comment I must make is that whoever wrote Version 4.3 of this chapter did not add their name to the contributors list at the front of the guide. My name appears there as the last contributor and makes it look like I wrote this version of Chapter 3. I definitely did not and the text is definitely not my style or quality.

If anybody writes a chapter or does a review and comment, then PLEASE add your name to th contributors list.

Regards
Peter Schofield
psauthor@gmail.com

Hi Peter, and Team,

I have downloaded Impress Chapter 3 for first review. Expected return date
is Saturday the 15th. Just a quick note: I've been getting a "502 Bad
Gateway" error on the Status Spreadsheet, but I will try again later to
update that page.

Cheers,
Sam.

  Samantha Hamilton
  darling docs

  <https://darlingdocs.wordpress.com/> <https://github.com/samanthahamilton>
<https://www.linkedin.com/in/shamilton-64b4b71b0/>

Hi Peter, and Team,

I have completed a first pass review of Impress Chapter 3 and uploaded it
to the Feedback folder (changes noted on the Status Spreadsheet). Peter,
you mentioned in an email to Felipe that "the template for version 7.0 is
not 100% set in stone." As such, I did not investigate too deeply the
finite formatting details. I do have a few quick questions, though, and
perhaps they are template-related questions:

   - Why is Sidebar capitalized, but main menu bar and toolbar are not?
   - Was there a decision made about the Note header on page 2 to be
   re-styled as a Warning header?

Overall, I thought the writing was very clear and concise---I was able to
follow all the directions easily.
Cheers,
Sam.

  Samantha Hamilton
  darling docs

  <https://darlingdocs.wordpress.com/> <https://github.com/samanthahamilton>
<https://www.linkedin.com/in/shamilton-64b4b71b0/>

Hello Samantha

1st question — not sure why Sidebar is capitalised. Easily changed when I create 2nd draft.

2nd question — it is a note. Warning header, in my opinion, should not be used at all. There is no danger to life or serious risk of injury, which is what a warning is all about. Definition of a warning comes from ISO rules. Also, in my opinion, caution should not be used. There is no real danger of causing a malfunction of equipment. In software guides there is only a need for notes and tips.

Had a quick look at your suggestions and you have made some good points.

Moving figures would create large white spaces in the document. In my opinion, too much white space in a document is something to be avoided. It looks very unprofessional. I am of the old school where user guides used to be printed.

Regards
Peter Schofield
psauthor@gmail.com

Thank you, Peter,

Your feedback and answers make perfect sense. I feel I have learned a lot
from reviewing this chapter!

Cheers,
Sam.

  Samantha Hamilton
  darling docs

  <https://darlingdocs.wordpress.com/> <https://github.com/samanthahamilton>
<https://www.linkedin.com/in/shamilton-64b4b71b0/>

Hello Samantha

1st question — not sure why Sidebar is capitalised. Easily changed when I create 2nd draft.

2nd question — it is a note. Warning header, in my opinion, should not be used at all. There is no danger to life or serious risk of injury, which is what a warning is all about. Definition of a warning comes from ISO rules. Also, in my opinion, caution should not be used. There is no real danger of causing a malfunction of equipment. In software guides there is only a need for notes and tips.

While this may be true for Impress, I think that there are cases in Base in which using a caution makes sense. Data can be lost permanently if the user does not pay attention to what they are doing. Many of these thing are mitigated by Base offering to save something.//When creating a new form, saving it often is very important. This is especially true in areas where power is not always reliable as where thunderstorms are relatively common during the hotter part of the year.

Dan

Hello Dan

You have a good point and will take it on board. No danger of causing loss of data in Impress and you cannot caution users not to make a bad presentation :-))))

Peter Schofield
psauthor@gmail.com