[GRASS-dev] hi

[Vaclav Petras]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20220730/995ee234/attachment.htm>