OK, back to topic. Therefore top posting.
I was a bit curious. So, I did a little test.
The "instructions.html" file does not contain any references about CSS.
So, I included the "styles.css" and "exceptions.css" files and looked at
the local file --> It changed the layout.
Now I committed the file to the test area into staging and compared old
[1] and new [2]. Now the headings can be identified as headings again.
If this is looking nice is a different topic. ;-)
[1] http://ooo-site.staging.apache.org/download/common/instructions.html
[2] http://ooo-site.staging.apache.org/download/test/instructions.html
Marcus
Am 03/14/2014 09:46 PM, schrieb Marcus (OOo):
Am 03/14/2014 08:20 AM, schrieb Oliver-Rainer Wittmann:
Hi,
On 13.03.2014 21:52, Marcus (OOo) wrote:
Am 03/13/2014 09:36 AM, schrieb Oliver-Rainer Wittmann:
Hi,
On 12.03.2014 21:15, Marcus (OOo) wrote:
Am 03/12/2014 12:30 PM, schrieb Oliver-Rainer Wittmann:
Hi,
Rainer recently noticed that our installation guides needs
improvement -
see issues 124343 and 124400.
I am volunteering to take corresponding actions. But I need support
and
feedback - I am neither a web designer nor a technical writer
I can support you with the webdesign. Maybe it's gets a bit hard
(when I
read Kay's mail ;-) ) but I would try.
Issue 124343:
This is about the visibility of the headings.
My suggestion here is to make the font used for the headings (all
levels) bold. Thus, I would like to propose to change our
corresponding
CSS [1].
Please provide feedback regarding my suggestion.
This is a central CSS file. Changes here would affect nearly all
webpages. This needs to be treated very carefully.
Does it makes sense to make more or less all headings on our website
bold?
No, I'm pretty sure here and there it wouldn't be the intended style.
Are there alternatives to improve the visibility of heading?
Should we make all heading italic or larger?
Again no. ;-)
Such a feedback does not help as you only say no, no, no, ... without
any alternative suggestion :-)
I'm sorry when you expected some code or else. But without looking
closer into the CSS styling I wouldn't do anything.
No, I do not expect any code.
Just feedback as you have given, but also alternative suggestions, when
my proposed changes are not your favorites.
I would start with improving the text content. Then we should think
about the formatting.
BTW:
This was my suggestion. Maybe you have overlooked it. ;-)
No, but I mad a mistake - see below.
What do you think?
Hm. We have issue 124343 for the formatting and issue 124400 for the
content.
Changing the words of a heading will not improve its visibility.
Thus, I
think that these issues can be treated separately.
https://issues.apache.org/ooo/show_bug.cgi?id=124400
Website: Installation guides: Headings do not look like headings
https://issues.apache.org/ooo/show_bug.cgi?id=124343
Website: Bugzilla documentation: Headings do not look like headings
For me it's the same - just 2 different websites. I've adjusted the
issue summaries.
Damn, now I know what went wrong.
I referenced the wrong issues - I am sorry.
It is 124400 for the formatting on the installation guide website
and 124408 [1] for the content on the installation guide website.
That is why I was puzzled by your suggestion to 'start improving content
and then look on formatting'.
ah, got it. :-)
Thus, content and formatting of our installation guide is what I want to
work on
[1] https://issues.apache.org/ooo/show_bug.cgi?id=124408 - Improve AOO
Installation Guide
With the content I think I cannot help. I've just Linux and my
installation is just:
cd <path_to_RPMS>
sudo rpm -ivh *
I don't care about icons, system integration as I don't use it anyway.
But I can work on the styling if it's OK.
My suggestion remains:
1. Improve the content.
2. Then we know the document structure.
3. Then we can improve the styling.
If there a good reasons, we can start to improve the styling earlier of
course.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org