I wrote an early blog post on the topic Styleguide Driven Development
I just read that again and must have missed the point that this style guide uses real views just with fake data.
This is incredible! Not just a bunch of HTML mockups that some UI team put together for the developers to copy.
Thanks @SummerNightCity ! haha.
Update help doc: it’s now 20 times in 24 hours. More than enough. https://help.market.envato.com/hc/en-us/articles/202821300
I hope that helped, let me know if I should try again!
One of the first thoughts I had was is it at all possible to automatically pull parts of the style guide into the app, so you only have to make UI changes to the style guide?
I think the WeBuild article mentioned something about that?
I think Envato themselves should be the ones providing the tools to do this
Oh yes definitely. If we can come to them with a proposal (something we know works well for lots of authors currently) maybe they can take that and make it “official”
I’ll check out wp updates once back on a computer, cheers!
just an idea !
I think all WP themes and plugins on the market should have a standard way of telling the user an update is available. This includes standalone plugins along with plugins that have been bundled with themes under an extended license.
This should be required when submitting an item.
This will help with any future theme security issues and help buyers keep their bundled plugins up to date.
I’m not necessarily talking about automatic updates, as that’s quite difficult to implement (and an entirely different beast under wp network mode). Just a notice saying “there’s a new version of XYZ available, click here for update instructions”.
If anyone else thinks this is a good idea maybe we can compile a list of current ways authors show update notices (along with automatic updates- but keeping that part optional – focus on the notification).
If we can then build a couple of “standard” ways to do this then that’ll help all authors.
Let me know any thoughts!