Basic, basic tutorials or documentation... anywhere?

The issue here is not about being able to modify the css or knowing to install quickstart or modifying PHP code, the question is about basic context.
- What are the basic principles behind Gavern (nowhere to be found)?
- Where are the layers in the source files (missing)?
- What is Style1 and Style 2 and how do they relate to Light and Dark (are they the same)?
- Why are the module positions defined in Quickstart completely different from the documented ones on the site? (very strange)
- How does one make a simple logo change on each template variation for interior pages (incredibly simple for [...] and [...] templates, but who knows if it's even possible on Gavick templates without any guidance whatsoever)?

These aren't technical questions, they are design questions. I can't seem to find any documentation at all anywhere here, and only random bits and pieces on Gavick Magazine. I simply can't believe after this many years, there is not a single tutorial or document to explain Gavick template designs or operation? Is this true?

Hi

We are preparing documentation support for Gavern framework.
Please be a little more patience.

Cheers

Hi

We are preparing documentation support for Gavern framework.
Please be a little more patience.

Cheers

I've been seeing documentation requests (and promises) for months, and no documentation. So the "patience" argument is a bit worn out.

The Gavick team creates wonderful templates and you all seem to be nice guys, but we understand that talented developers hate writing documentation worse than death itself. Believe me, I'm sympathetic.

So I have a suggestion that may solve both our needs for guidance and your distaste for writing. Instead of trying to create a massive set of documentation describing everything, simply start with small, incremental explanations of basics. You could use a Wiki, or even consolidate and pin comments to the top of the discussion boards (this alone would be terribly helpful)... anything would be better than nothing! Thus, you could use your customers to help write the documentation and use these informal mechanisms as input for the "official" documentation.

I believe that the questions I and other customers have could literally be answered in about 1-2 pages of help - it's simply the context we're lacking, not a hoard of details. It would take you no more than 1-2 hours to write enough to answer these (even if you do it in Polish I guess we English-speakers could use Google translate and still get a good-enough idea). We can find our way around the CSS and the PHP code if we simply know where to find stuff and get answers to the most basic of questions.

Hope this helps. TIA. Cheers!

+1

When I have buyed this suscription I wait to found instructions or a manual