[GRASS-dev] hi

[Veronica Andreo]

Hola Daniel,

None of those at time, but you could open a new discussion in github
(though that is in the main grass repo...)

Vero

El lun., 1 ago. 2022 19:51, Daniel Torres <nobeeakon at gmail.com> escribió:

> thanks Veronica, then I'll  try with the ones suggested in Hugo website
>
> (is there another communication method you guys use, like Slack, discord
> or something like kind of more direct or  quick questions and stuff? )
>
> On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo <veroandreo at gmail.com>
> wrote:
>
>> Hello Daniel,
>>
>> IIRC, I suggested using something similar to what wowchemy (former hugo
>> academic) has, but the path chosen was different. Paulo, also made a
>> suggestion, but I didn't have the time to try, honestly. I think it's all
>> in the PRs and probably this issue too:
>> https://github.com/OSGeo/grass-website/issues/19
>>
>> Vero
>>
>> El lun, 1 ago 2022 a las 15:55, Daniel Torres (<nobeeakon at gmail.com>)
>> escribió:
>>
>>> Thanks guys,
>>> I'm ok with starting on the website.
>>>
>>> About the search, in Hugo website they suggest a couple of methods
>>> https://gohugo.io/tools/search/ , have those been tried?
>>>
>>> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo <veroandreo at gmail.com>
>>> wrote:
>>>
>>>> Hi Daniel,
>>>>
>>>> Welcome! Besides what Vashek pointed out, if you feel comfortable
>>>> starting with something for the website, we are missing a search engine
>>>> there. There were a couple of attempts in the past but none of them worked
>>>> fully as expected. Have a look at the PRs here:
>>>> https://github.com/OSGeo/grass-website/pulls
>>>>
>>>> Best,
>>>> Vero
>>>>
>>>> El sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus at gmail.com>)
>>>> escribió:
>>>>
>>>>> Hi Daniel,
>>>>>
>>>>> Welcome. That sounds great. For Python, check this presentation I'm
>>>>> preparing for FOSS4G where are I describe how to do good PRs which fix
>>>>> coding standards and the load of tools which can be applied:
>>>>>
>>>>> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45
>>>>>
>>>>> JavaScript at this point means starting with your own idea which may
>>>>> or may not be what you are looking for. Website is certainly one option.
>>>>>
>>>>> I would really like to see changes in the documentation (aka HTML
>>>>> manual pages):
>>>>>
>>>>> https://grass.osgeo.org/grass83/manuals/
>>>>>
>>>>> ...but that's certainly "bring your own idea." It likely involves some
>>>>> HTML and CSS design, but perhaps there is something more functional that
>>>>> can be done. An alternative to this is migrating to Sphinx first, but
>>>>> that's just a thought from the past.
>>>>>
>>>>> Now when I think about it, the full JavaScript checks in Super-Liner
>>>>> are not enabled, so that's perhaps a small JavaScript task to tackle before
>>>>> starting a bigger project (that's up to you!).
>>>>>
>>>>> Let me know if there is any other info which would be helpful.
>>>>>
>>>>> Best,
>>>>> Vaclav
>>>>>
>>>>>
>>>>> On Sat, 30 Jul 2022 at 14:18, Daniel Torres <nobeeakon at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi guys, I'm Daniel , I work as Front end dev. I would like to
>>>>>> contribute to the project, as I find it really nice. I have experience with
>>>>>> JS and front end stuff, but also with Python.
>>>>>>
>>>>>> Happy to contribute, but don't really know where to start. (Maybe
>>>>>> something on the website side?)
>>>>>>
>>>>>> Cheers,
>>>>>>   Daniel
>>>>>> _______________________________________________
>>>>>> grass-dev mailing list
>>>>>> grass-dev at lists.osgeo.org
>>>>>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>>>>>
>>>>> _______________________________________________
>>>>> grass-dev mailing list
>>>>> grass-dev at lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20220801/50be73b6/attachment.htm>