Matt Robinson

@KTS915 - We have a conflict in this PR after merging some of the other JS related PRs. I think the correct code with this PR should be: ``` $scripts->add(...

[links.txt](https://github.com/ClassicPress/ClassicPress/files/3708994/links.txt) Using the `find ./src/wp-admin/ -iname "*.php" | xargs grep "classicpress.net"` command these are the existing links back to a ClassicPress domain in the wp-admin folder. Some are already using...

Security screen was removed in ClassicPress `2.0.0` and the links.classicpress.net domain is not longer in use. Closing but can be reopened if a need is identified.

This seems to be code specific to ClassicPress and is intended to display a message that future security updates will be automatically applied. I have tested through the code as...

If anyone is still interested in contributing a translation we are now all set up at CrowdIn, this is the link to our Project Page: https://classicpress.crowdin.com If you need a...

Closing this issue now; translations are processed in the ClassicPress CrowdIn project.

I haven't tested this is a browser as yet but there are a lot of JavaScript issues that need tidying up in the amended files as per JSHint. Things like...

A lot of changes in the last 24 hours have many tests now passing. The last failure to address is a validity check after the build process. In the Gruntfile.js...

> What does WP do? I know Gutenberg, for example, uses the spread operator. WordPress and also Gutenberg are using build steps with things like wepback and babel, particularly with...

> Just came across this [changeset](https://core.trac.wordpress.org/changeset/56247), where WP dropped js-validate task from Gruntfile to "simplif[y] the build and avoid[] false-positive warnings where the outdated tool flags modern JS syntax incorrectly."...