You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "NiklasMerz (via GitHub)" <gi...@apache.org> on 2023/05/26 11:41:21 UTC

[GitHub] [cordova-docs] NiklasMerz commented on a diff in pull request #1315: doc: refactor next step

NiklasMerz commented on code in PR #1315:
URL: https://github.com/apache/cordova-docs/pull/1315#discussion_r1206655566


##########
www/docs/en/dev/guide/next/index.md:
##########
@@ -155,40 +162,61 @@ When building your user interface, it is important to think about all platforms
 
 * [iOS](https://developer.apple.com/design/human-interface-guidelines/ios/overview/themes/)
 * [Android](https://developer.android.com/design/)
-* [Windows Phone](https://developer.microsoft.com/en-us/windows/apps/design)
 
-# Special Considerations
+## Special Considerations
 
 Although Cordova makes cross-platform development easier, it's just not possible to provide 100% isolation from the underlying native platform, so do be aware of restrictions.
 
-## Platform Quirks
+### Platform Quirks
 
 While reading the documentation, look for sections which outline different behaviors or requirements on multiple platforms. If present, these would be in a section titled "Android Quirks", "iOS Quirks", etc. Read through these quirks and be aware of them as you work with Cordova.
 
-## Loading Remote Content
+### Loading Remote Content
 
 Invoking Cordova JavaScript functions from a remotely-loaded HTML page (an HTML page not stored locally on the device) is an unsupported configuration. This is because Cordova was not designed for this, and the Apache Cordova community does no testing of this configuration. While it can work in some circumstances, it is not recommended nor supported. There are challenges with the same origin policy, keeping the JavaScript and native portions of Cordova synchronized at the same version (since they are coupled via private APIs which may change), the trustworthiness of remote content calling native local functions, and potential app store rejection.
 
 The display of remotely-loaded HTML content in a webview should be done using Cordova's InAppBrowser. The InAppBrowser is designed so that JavaScript running there does not have access to the Cordova JavaScript APIs for the reasons listed above. Please refer to the [Security Guide](../appdev/security/index.html).
 
-# Keeping Up
+## Keeping Up
 
 Here are a few ways to keep up to date with Cordova.
 
 * Subscribe to the [Cordova blog](https://cordova.apache.org/blog/).
 * Subscribe to the [developer list](https://cordova.apache.org/contact/). Note - this is not a support group, but a place where development of Cordova is discussed.
 
-# Getting Help
+## Getting Help
 
 The following links are the best places to get help for Cordova:
 
-* Slack: [http://slack.cordova.io/](http://slack.cordova.io/) The official Cordova Slack channel is a great way to get help from the community, and the place you are most likely to get answers to your questions
-* StackOverflow: [https://stackoverflow.com/questions/tagged/cordova](https://stackoverflow.com/questions/tagged/cordova)
-By using the Cordova tag, you can view and browse all Cordova questions. Note that StackOverflow automatically converts the "Phonegap" tag to "Cordova", so this way you will be able to access historical questions as well
-* PhoneGap Google Group: [https://groups.google.com/forum/#!forum/phonegap](https://groups.google.com/forum/#!forum/phonegap)
-This Google Group was the old support forum when Cordova was still called PhoneGap. While there are still a lot of Cordova users that frequently visit this group, the Cordova community has expressed an interest in focusing less on this group and instead using StackOverflow for support
-* Meetup: [http://phonegap.meetup.com](https://phonegap.meetup.com) -
-Consider finding a local Cordova/PhoneGap meetup group
+* [GitHub Discussions - Apache Cordova][GitHubDiscussionCommunity]
+
+    The official Apache Cordova GitHub Discussions channel is a recent addition to our support resources, aimed at centralizing community discussions and questions within our GitHub repositories.
+
+    This channel is highly recommended as it brings together all things Cordova and provides the advantage of retaining a complete history of discussions. By utilizing GitHub Discussions, we can ensure better continuity and accessibility for future reference.
+
+* [Slack - Apache Cordova][SlackCommunity]
+
+    The official Apache Cordova Slack workspace is an excellent resource for seeking help from the community and obtaining quick answers to your questions.
+
+    However, it's important to note that our Slack workspace does not retain message history. This limits the accessibility of information in the long term. To ensure better retension of your question, it is advisable to create a thread in GitHub Discussions and share the link and a summary of your question in the Slack. 

Review Comment:
   ```suggestion
       However, it's important to note that our Slack workspace does not retain message history. This limits the accessibility of information in the long term. To ensure better retention of your question, it is advisable to create a thread in GitHub Discussions and share the link and a summary of your question in the Slack. 
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org