Want to get involved? See the handbook and optionally drop into #design to chat. Most active design work happens in the block editor project, consider dropping into Needs design or Needs design feedback.
There’s a WordPress Component Library in Figma. Duplicate to edit, direct access is reserved for the design team.
Just a reminder that the image flow meeting is now on Thursday at 20:00 UTC. That’s:
Thanks everyone who attended the meeting this week. Note that in future the meetings will be at 16:30 UTC, i.e. normal time for everyone now that daylight savings has happened.
Here’s what we discussed:
1. Feedback – there’s a lot of feedback scattered around which we need to get into one place so we can make sure it’s properly addressed. We have a Google Doc here which we’ll consolidate it into.
2. @teamadesign has tried an edited flow with the metadata first. It’s available for testing should anyone want to.
3. Once @wonderboymusic is caught up on where we are, we’ll start ploughing forward with the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
Actions
Now that we’re ready to start making a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, this post will catch you up on some of the important things to read before diving in.
The interactive wireframes will give you a pretty accurate visual overview of where we’re going with the project. Note that the wireframes are based on a large amount of research into how different platforms and applications handle image storage, upload, and editing.
There are also user flow charts which show the planned user flows through the interface. It’s worth comparing these with the current flows through the modal.
The in-browser prototype is a skeleton representation of how we see the basics working. It isn’t perfect, but the basics are there. We’ve decided that at this point it’s best for us to move onto the plugin. However, @mor10 is doing some user testing on the prototype and we’ll use that feedback for refining the plugin.
Prototype Resources
if you’re interested in some more background reading that should give you insight into various decisions, these are some things worth looking at (this is not essential to read before getting started):
The next step is to break the plugin down into discrete, achievable tasks. This should get things moving more quickly. we can use the Image Flow GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ account. As soon as it’s in a usable state we’ll put the plugin in the repo so it’s easy to test and we can get feedback.
The regular meeting is at 17:30 UTC on Thursday.
Thanks everyone who attended the meeting last week (and apologies for my tardiness with the notes!).
Process
We had a serious discussion about the current process. After discussion of the prototype, we decided that in its current state it’s ready for testing the basic flow. There are a few bits of polishing that need to be done:
However, no more major development will be done on the prototype. We don’t think it is a good use of time to work on getting the editing features working. We’re going to start building the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and get the groundwork for that done while morten is testing.
Therefore, next week’s meeting will be dedicated to scoping out the next steps for the plugin and getting that process going.
Actions
(great job on getting everything complete before I even write up the notes 😀 😀 :D)
Thanks to everyone who attended the image editing meeting today. Here’s what we discussed:
Actions
The dev meeting is on Friday at 17:30 UTC for anyone who wants to join.
Thanks everyone for attending the meeting today. Here’s what we discussed:
1. Prototype
2. TinyMCE
We had a brief discussion about what happens to the image outside of the flow. TinyMCE isn’t the most fun to use on a mobile device and it has some jarring behaviours when you’re dealing with the image. @iseulde suggested that we keep track of any issues. These should be reported on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
3. Icons
@teamadesign has created a list of icons, which @empireoflight is going to run by the dashicons team.
Actions
Image Flow meeting is this evening. First thing to note is that we will move our regular Thursday meeting to SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. We’ve reached the limit of how many people we can fit on the Google Hangout. Also, Slack is better for encouraging participation and for logging. We’ll likely continue to do smaller user testing meetings on google hangout.
This evening’s meeting:
See you all at Thursday 17:30 UTC in #feature-imageflow in Slack!
Thanks everyone who attended the image flow meeting. We discussed the following:
Actions agree:
Thanks everyone who attended the Image Flow meeting! It was a very full Google Hangout 🙂 Here’s what we discussed:
Here we are:
Happy New Year everyone! I hope you’re still excited about making those images flow 😀
Today’s our first meeting of 2015 (17:30 UTC), and to celebrate I thought I’d post an agenda.
1. Review of current team resources (we may have some additional team members for 2015)
2. Review of prototype status
3. Plan for moving forward
4. Plan for user testing
I’m still unsure if we’ll meet on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or on Google Hangout. It depends how many people show up (we have a limit of 10 people in Google Hangout). I’ll post in the Slack room (#feature-imageflow) to see how many we have.
