Moving some discussions to Slack

Last Updated on December 11, 2017 by Neil Murray

Bitbucket Issues meeting on Slack

Lately we've been moving some CF7 Skins Team discussions from Skype to Slack.

All CF7 Skins Team members should have recently received an email inviting you to join our Slack conversations at cf7skins.slack.com.

So far we've only been using Slack to conduct meetings which we were previously doing via Skype.

Bitbucket Issues meeting on Skype

We've found meeting on Slack was a little slower than Skype but does offer some advantages:

  • provides easy to access record of meetings
  • others can access older discussions
  • we can link to previous comments

We should get quicker as we use Slack more.

Better tool for documenting screenshots

Last Updated on December 4, 2017 by Neil Murray

I'm looking for a better tool for documenting screenshots like this:

I'm currently using Awesome Screenshot via Chrome Extension but find it really cumbersome.

I'm Windows based so can't use any fancy Mac only stuff. I've also tried the following which I didn't like for various reasons:

If you have any suggestions, please add them on this post.

You can also add a Comment if you want – you can do that on all our posts.

Human Made developing react-wp-scripts

Last Updated on December 4, 2017 by Neil Murray

I recommend we follow/watch react-wp-scripts

This project solves two issues that prevent seamless usage of webpack in WordPress themes and plugins:

  • WordPress doesn’t necessarily know where to look for the output bundles.
  • WordPress cannot access the development server due to cross-origin restrictions.

It's based on create-react-app – uses a wrapper for create-react-app's react-scripts to allow seamless usage of scripts and styles served from webpack-dev-server in WordPress.

Error / Possible Improvement Log for Translation

Last Updated on December 31, 2017 by Neil Murray

RESOLVED:

[1] Update .pot file to reflect the new translation phrases included in the Indonesian .po file.

[2] The term "Display Log" is not translated in the "Advanced" tab of CF7Skins.

[3] The term "skins" in the meta box is more of a marketing decision, since this is what the CF7 Skins would be displayed as in the search engines and elsewhere. Direct translation to the target language would not be ideal. Code here: admin.php#188 and admin.php#215

The following terms are part of a sentence with the subject missing. This makes translation to other languages harder as conjugation rules vary across languages. For example, in Nepali (or Hindi), translation of a sentence like "CF7 Skins makes your job easier" would have other characters morphed into the subject "CF7Skins" without spaces (like how "'s" morphs into a subject in English). So, just translating the rest of the sentence while putting the subject "CF7Skins" as placeholder wouldn't work. The whole sentence will have to be translated.

[x] getting-started.php
[x] pro-version.php

[4] Term: "makes it easier for regular WordPress users to create forms using built in" in getting-started.php#12.

[5] Term: "covers from how to get started up to how to customize your forms and everything else in between." in getting-started.php#50

[6] Term: "browse over some commonly asked questions." in pro-version.php#151

[7] Term: a great place to find detailed answers."" in pro-version.php#154

[8] Term: "maintained by the CF7 Skins Support Team to help you solve most questions. You can search it either by Categories & Tags or Keywords." in pro-version.php#157

[9] Term: "to help you get started using CF7 Skins quickly & easily." in getting-started.php#56 and pro-version.php#160

[10] Term: "you can search by Categories & Tags or Keywords." in getting-started.php#53

[11] Term: "leave a plugin review on WordPress.org" in getting-started.php#70 and pro-version.php#136

[12] Term: "add your Testimonial to those listed" in getting-started.php#73 and pro-version.php#139

[13] Term: "log in & vote "works" on your current versions" in getting-started.php#76 and pro-version.php#142

[14] Term: "help us to improve CF7 Skins by offering feedback" getting-started.php#79 and pro-version.php#145

[15] Term: "browse over some commonly asked questions." in getting-started.php#87

[16] Term: "covers from how to get started up to how to customize your forms and everything else in between." in getting-started.php#50

[17] Term: "to help you get started quickly with CF7 Skins." in getting-started.php#96

… and several other with similar problems. Basically, sentences that have subject or other noun missing in them have this problem. All of these need to be fixed. Solution might not be generic to all and might need some case-by-case inspection.


CONTINGENT ON OTHER FACTORS:

The problems 1, 4 and 5 arise in CF7Skins Logic, Multi, Pro and Ready:

[1] The post-installation prompts are in English, not in the selected language of WP.

The problems 2 and 3 arise because name of the plugin is just in English and does not provide translations.

[2] Menu titles in the dashboard are in English, not in the selected language of WP.

[3] Page titles (of HTML – shown in the browser) are still in English, not in the selected language.

[4] The terms "Active Licenses" and "License Key" in the CF7Skins license page are not translated.

[5] The prompts to enter licenses are not translated.


UPDATE: Sastra contacted the GTE and PTE and so translation will be done again at 26 December, with Sastra helping them translate the untranslated string.

[ ] The feedback from Indonesian PTE/GTE is that there are several issues with the Indonesian translation. See the conversation below:


You can find the BitBucket issue of this here.


Notes:

  • Make sure someone else can understand each problem easily
  • Add image showing problem – where necessary
  • Add links to code in Bitbucket showing where code is incorrect – if possible
  • Also list problems on the Bitbucket issue
  • On Bitbucket you can also edit your existing comments rather create a new comment.

Staff paid for working with Gutenberg

Last Updated on December 4, 2017 by Neil Murray

CF7 Skins Team members working at least 20 hours per week are now offered to be paid for 10% of their time working with the Gutenberg project.

We often look at the Gutenberg code to help us solve technical issues we are having on interaction between React & WordPress. The Gutenberg team have often already faced similar issues & developed well thought out solutions that we can learn from & follow.

The Gutenberg code is highly sophisticated, well planned & executed and is at the heart of all change within WordPress right now.

Staff working with Gutenberg will have the opportunity to improve their coding skills  & our code as they also form helpful working relationships with some the best WordPress/React Developers in the world.

WordPress/React development work on Gutenberg is absolutely first class .. it's as good as it gets in the WordPress/React world today.

Neil Murray

All CF7 Skins Team Members to add their profile

Last Updated on January 12, 2021 by Neil Murray

I’ve recently noticed that many CF7 Skins Team Members often know very little about others working with the CF7 Skins Team.

As we move towards release of CF7 Skins Visual early next year, I thought it would be good idea if everyone could add something about themselves at Team Members.

Please update your profile picture & tell all of us whatever you feel helps each of us get a better understanding of you.

You can use my profile information for inspiration.

All CF7 Skins Visual code to the WordPress Coding Standards

Last Updated on December 4, 2017 by Neil Murray

I want to move all CF7 Skins Visual code to the WordPress Coding Standards before we go to Beta testing.

This includes:

  • following DocBlock Formatting 
  • semi-colons at the end of all statements
  • if, else, for, while, and try blocks should always use braces, and always go on multiple lines

Refer to Code Documentation Standards