Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap 2015 #5

Open
MrSaints opened this issue Feb 15, 2015 · 4 comments
Open

Roadmap 2015 #5

MrSaints opened this issue Feb 15, 2015 · 4 comments

Comments

@MrSaints
Copy link
Owner

If you need assistance with the plugin but you do not have a Github or a Twitter account, you can drop a question at my Ask.fm.

We, as a community, have made several changes to this project since its inception in 2013. It was originally inspired by Simple Text Rotator and driven by the need for an up-to-date / modern plugin for text transitions.

In 2014, I had focused my attention on fine-tuning it (albeit unnecessary at times due to the negligible impact), and on increasing its flexibility (mostly encouraged by users' requests) by introducing new, meaningful methods (internal and external).

Looking ahead in 2015 (and possibly 2016), I intend on doing the following:

  • Porting the plugin over to React.js and Polymer (something I had already begun working on, but not to a standard that I deem acceptable / stable)
  • Possibly introducing ES6 to the plugin (I will need to look further into this and see if it is even worthwhile or advisable to do so)
  • Developing a more advance version of this plugin and Morphist (i.e. animating individual letters - I have also already begun working on this)
  • Updating the documentation and the website (make it easier for people to deploy this and understand the difference between this and Morphist)
  • Collating a list of sites that are currently using it (you can leave your URL in the comments in preparation for this)
  • Release a Wordpress plugin

At the same time, I would like to stick to its original philosophy:

  • Simplicity (all aspects, i.e. understanding how it works, modifying it and using it)
  • Performance (optimum solutions to achieve the desired effects)
  • It should do one thing, and do it well (which is why Morphist is on a separate repository)
  • Lightweight (similar to the previous ones; no unnecessary bloat)
  • Compatible (across most browsers)
  • Open (by the community, for the community)

Balancing these different considerations is not going to be an easy job and certain conditions will be given a greater priority than others.

As always, suggestions and questions will always be entertained.

Have a good year everyone.

P.S. Be sure to give Morphist some love as well!

EDIT: Let's start collecting cool typography effects...

@nateinaction
Copy link

nateinaction commented Aug 19, 2016

I see that one of your goals was to release a plugin for WordPress. I wanted to let you know that I launched a plugin in April called WP Morphext. https://github.com/nateinaction/wp-morphext and on the WordPress plugin directory https://wordpress.org/plugins/wp-morphext/. Cheers! :-)

@MrSaints
Copy link
Owner Author

@nateinaction, thank you so much for that. I'm planning on cleaning up the README, and the homepage soon. I'll be sure to include a link to your plugin.

@oyeanuj
Copy link

oyeanuj commented Nov 5, 2016

@MrSaints I notice that you have 'React port' as one of the goals. Is a React library still your plan? And would it be without JQuery?

Thank you for sharing the library with OSS community!

@MrSaints
Copy link
Owner Author

MrSaints commented Nov 6, 2016

@oyeanuj Yea, definitely. I just need to find some time to pick this up again. And yes, it will function without jQuery (the current prototype already does this). Thank you 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants