Charlie,
Great! I am almost half-way through converting the original ODT
(LibreOffice Writer) text into plain vanilla HTML, so it can go somewhere
yet-to-be-determined on the documentation site. But...I have been editing
it as I go, so now the online and ODT versions differ. I suspect the HTML
is not going to easily convert to PDF, and as soon as this is online,
anyone in the documentation team will be able to edit it. So there is a
file synchronization problem that won't go away.
I would like to remove one or two things from the original PDF (link is
in the handbook thread) maybe do one round of light edits based on initial
feedback, and post it. I agree it's just right as an e-book for
consumption on tablets, etc. (converting it to epub would be great, too,
but I may need help).
PNG should be fine. I will upload the first five chapters in a day or so,
and that will include the title page as a separate file. Some thoughts:
- Conventional "pile o' screenshots" approach
- Something featuring Tux as a hip producer and hotshot musician
- Integrate the Ubuntu logo
- I came across Ubuntu palette, and used that for my callouts
- Maybe some bullet points or "what's inside" info
- A complete departure that uses none of the above is cool, too! It can
only go up from where it is now, which is plain white with a default H1.
The raw HTML is really going to need some styling, too. Is there a
pre-existing style sheet that will automatically cover the basics? Will
probably need help if not.
Pete
On Tue, Jun 5, 2018 at 8:00 AM, <
ubuntu-studio-devel-requ...@lists.ubuntu.com> wrote:
> Send ubuntu-studio-devel mailing list submissions to
> ubuntu-studio-devel@lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> or, via email, send a message with subject or body 'help' to
> ubuntu-studio-devel-requ...@lists.ubuntu.com
>
> You can reach the person managing the list at
> ubuntu-studio-devel-ow...@lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ubuntu-studio-devel digest..."
>
>
> Today's Topics:
>
>1. Cover art - and title needed (Peter Reppert)
>2. Re: Cover art - and title needed (Charlie)
>
>
> --
>
> Message: 1
> Date: Mon, 4 Jun 2018 11:02:12 -0400
> From: Peter Reppert
> To: ubuntu-studio-devel@lists.ubuntu.com
> Subject: [ubuntu-studio-devel] Cover art - and title needed
> Message-ID:
> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> If someone wants to get creative, the Ubuntu Studio Audio Handbook might
> need cover art. Also, I've had three or four working titles:
>
> Home Recording with Ubuntu Studio
> Ubuntu Studio for Musicians - Essential Guide
> Ubuntu Studio Audio Handbook (current working title)
>
> What's best? Any alternative suggestions?
>
> Maybe neither a cover page nor an overall title will be needed, though. I
> am making HTML files for each section, and these may end up dispersed. I
> am keeping the HTML pretty raw - I assume a stylesheet can be applied
> later. So far I made a blockquote style, but don't expect to do much more
> styling. I might try my hand at a cover/thumbnail once it's all converted,
> but would like to see if anyone with true graphic design experience might
> be willing to take it on.
> -- next part --
> An HTML attachment was scrubbed...
> URL: <https://lists.ubuntu.com/archives/ubuntu-studio-devel/
> attachments/20180604/4602604e/attachment-0001.html>
>
> --
>
> Message: 2
> Date: Mon, 4 Jun 2018 13:10:53 -0700
> From: Charlie
> To: Ubuntu Studio Development
> Subject: Re: [ubuntu-studio-devel] Cover art - and title needed
> Message-ID: <567dd2ca-1e49-491e-af67-d27832488...@charlieluna.com>
> Content-Type: text/plain; charset="utf-8"
>
> hey Peter,
>
> I've got experience working on cover art, albeit just my own books, but I
> can definitely try my hand at it and submit it to you or everyone for
> approval.
>
> per your current title suggestions, I like them all but the one you
> consider the working title's great. It's general in nature since some
> people who work with music just do programming like with hydrogen for drums
> and synth and some do with guitars, bass, vocals and all of the live band
> stuff. So it definitely fits the best, IMO.
>
> But let me try to work on some stuff and I'll do my best to get that to
> you/everyone. what format should i save it as? i usually do i
