[QGIS-Developer] QGIS Server visibility and documentation

[Andreas Neumann]

I'm also not convinced about the need for a new logo. 

Like Raymond suggested I think we should use the existing logo and add
some text to it. 

But the website, docs, examples, etc. should be improved as envisaged by
the QEPs/Grant proposals. 

Greetings, 

Andreas 

On 2020-07-07 13:56, Raymond Nijssen wrote:

> Indeed, marketing it as "one of the QGIS products' could be a good plan.
> 
> Now, our website says:
> QGIS - The Leading Open Source Desktop GIS
> 
> Also, the download buttons at the landing page point to QGIS Desktop only.
> 
> Not sure about the need for a new logo though. New logos can take forever! :) What about writing "desktop" and "server" next to or below the existing logo?
> (similar to this:
> https://qgis.org/en/_static/images/trademark.png?t=23feb2018
> )
> 
> Regards,
> Raymond
> 
> On 07-07-2020 00:29, Jorge Gustavo Rocha wrote: Hi all,
> 
> A dedicated logo and a dedicated landing page would be great (we could
> use server.qgis.org for example). Part of QGIS Server "identity" problem
> is because people think it as some QGIS additional feature. Not as
> something that can be deployed in a headless server, independently of
> QGIS. In fact, QGIS and QGIS Server share the same code base, but from a
> functional point of view, they are different applications, for different
> purposes. As developers, we put all the code in the same repo, but as
> marketeers, we should sell two different products :-)
> 
> People looking for "map servers" should go there. Developers/sysops
> should be able to deploy new QGIS Server instances from there.
> 
> Thank you Alexandre for volunteer. Julien, as far as I understood, will
> lead this QEP implementation. Thank you both.
> 
> Regards,
> 
> Jorge
> 
> On 06/07/20 21:55, Alexandre Neto wrote: Hi all,
> 
> I agree the QGIS server deserves its own "document" in QGIS docs.
> 
> I Wouldn't mind assisting with that. Always a good opportunity to learn
> more about it.
> 
> Best regards,
> 
> Alexandre
> 
> A segunda, 6/07/2020, 15:36, Julien Cabieces
> <julien.cabieces at oslandia.com <mailto:julien.cabieces at oslandia.com>>
> escreveu:
> 
> Hi,
> 
>> Hi,
>>
>> During our recent meeting about QGIS Server it was pointed out that
>> QGIS Server does not have all the visibility that it deserves.
>>
>> One of the possible actions is to move the server documentation to its
>> own independent chapter.
>>
> 
> +1
> 
>> The server documentation is now mainly mainly buried deep under
>>
> https://docs.qgis.org/3.10/en/docs/user_manual/working_with_ogc/server/index.html
>>
>> A few other resources are in:
>> the training manual:
>>
> https://docs.qgis.org/3.10/en/docs/training_manual/qgis_server/index.html
>> and
>>
> https://docs.qgis.org/3.10/en/docs/pyqgis_developer_cookbook/server.html
>>
>> I was wondering this activity a could be performed as a part of the
>> paid/funded activity
>> https://github.com/qgis/QGIS-Enhancement-Proposals/issues/184
> 
> Yes, I believe it should. We'll do it while we realize the QEP.
> 
>>
>> Kind regards
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org <mailto:QGIS-Developer at lists.osgeo.org>
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> J. Gustavo
 _______________________________________________
QGIS-Developer mailing list
QGIS-Developer at lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20200707/29dc1fc9/attachment.html>