The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
Starting a food blog has always been my dream but having an around the world recipe blog? That is really something interesting!
This week, we are featuring CookingSurfing. They are a team of professional and dedicated programmers who started this site to spread their love for cooking with food lovers around the world.
I received an email from Marco Ferruggia, developer and co-founder of CookingSurfing. He is one of our satisfied users who would love to tell others how EasyBlog helped him and his site.
This is what he’s got to say:
We are professional developers and we have known Joomla since its first version. It was because our experience that we know how to evaluate a good product like EasyBlog for our customers. There were many features and options that allowed our customers to customize their blogs according to their needs hence the decision we made for EasyBlog.
My users are very satisfied with the autoposting feature on their social network. As a result, they got returning visitors to their site! The SEF in the URL is nicely done and with a few tweaks you can easily adapt to it.
Many features for admin are easy to use at the frontend for blog authors. EasyBlog is well integrated with comments system. A good media gallery integrated with the community, and much more other features were just great.
The only disadvantage is that there is not a search module so we had to create and adapt to the site.
In choosing a good product for my clients, I always offer the maximum value available. I'd rather spend money and be sure to get what I want. Free does not always guarantee the best solution. I have also experienced that the support offered by Stackideas is excellent and timely.
What do you think about this week’s site? Go to our Demo Page and check out EasyBlog. We would like to thank Marco for this week’s site, and all who took their time to read this blog.
Stay with us for more Case Studies!
Read more https://stackideas.com/blog/cookingsurfing-share-recipes-with-easyblog
Read more https://feeds.joomla.org/~r/JoomlaExtensionsUpdated/~3/8FZR7Fra_lI/18100
Finally, my worlds have collided! In case you didn’t know, I regularly write a Vim blog. It’s surprisingly easy to find things to say about this 22 year old text editor, and it’s been my main tool for writing code and articles for a long time. Vim.js (GitHub: coolwanglu / vim.js) by Lu Wang is an Emscripten port of Vim, allowing you to use Vim in a browser.
It runs pretty well on my computer – it seems fast, and the commands I typically use work. It’s not like these Vim layers for IDEs and other editors that miss certain motions, registers, and so on: it’s basically Vim. Split windows and tabs work, but the help files aren’t available (or I can’t find them). The way it works in the browser is to use a <span>
for each terminal character, which means for the 43x115 example window there are 4945 spans!
From a JavaScript point of view, I found the Sync to Async Transformation document interesting. The author is trying to figure out how to deal with JavaScript’s asynchronous nature, given that Vim expects to have a non-busy synchronous sleep()
function:
Most works are automatically done by
web/transform.js
, read the comments inside for more detail. But there are a few left, mainly function pointers, which cannot be automatically identified. Whenever vim.js crashes and you see callback function is not specified! in the browser console, congratulations, you have found one more async function at large.
I wonder if there are any Node developers or ES6 experts that can help with this? If you’re interested in the project, there’s a TODO which has some Emscripten issues and client-side work that needs doing.
Read more https://feedproxy.google.com/~r/dailyjs/~3/8sqP-19ZUC4/vimjs
With the holidays approaching, we have some busy elves working overtime in Joomla! land! If you haven't noticed, Joomla! 3.2 is packed with new features. Unfortunately, one of the features has a problem that was not discovered during pre-release testing. During late-stage development in September and October, there were alpha, beta and release candidate testing cycles where many community members kicked the tires to uncover as many possible issues. But one was missed, and unfortunately it was a big one causing some users deploying new sites to get locked out of their site with no easy solutions to restore access.
Read more https://community.joomla.org/blogs/leadership/1790-update-on-321-and-security-enhancements.html
After UIkit 2.0, we are excited to announce the release of Warp 7.2. First of all, we would like to thank you all for your feedback! We took a lot of your suggestions into consideration, which helped us to come up with what we consider a major step forward in the development of our framework. In this update we improved and simplified the customization workflow. This makes working with Warp much more intuitive and user-friendly. The newest UIkit version 2.0 is of course included and you will also find an updated theme documentation to assist you with your projects.
Essentially the override cascade is more similar to the one you are used to from Warp 6. You can work directly in your styles to customize layouts, CSS and JavaScript. The /custom
folder has been removed. You now use the styles/STYLE-NAME
folder to do customizations and overrides.
We also released a new version of UIkit, the front-end framework on which Warp is based. We simplified the UIKit themes and variables so it is now easier to work with. UIkit now offers new add-ons which you can easily include in your projects. Read more about the UIkit 2.0 release.
All Warp 7 based themes are updated for the Warp 7.2 release.
If you have already added or changed files in the /custom
folder, you can easily move these to your styles. But before updating, please make sure to have a backup of your customizations.
After the update you can move your customizations to your /styles/STYLE-NAME
folder. But keep in mind: your style will only be shown in the Customizer, if there is a style.less
file in the styles folder. Here are three possibilites on how to use the style folder for customizations.
Folder/File | Description |
---|---|
styles/STYLE-NAME/css/theme.css styles/STYLE-NAME/style.less |
This is the default file structure. When you save changes in the Customizer, the style.less file will be compiled into CSS the theme.css file and override any customizations you may have done in that file. |
styles/STYLE-NAME/css/theme.css styles/STYLE-NAME/css/custom.css styles/STYLE-NAME/style.less |
You can use the Customizer and also add your own CSS by creating a custom.css file. That way your CSS won't be overridden when you save changes in the Customizer. |
styles/STYLE-NAME/css/theme.css |
If you are not planning to use the Customizer at all, just duplicate an existing style or create your own one. You can then delete the style.less file of your new style and write customizations directly in the the theme.css file. Your style will NOT show up in the customizer and NOT overwritten when compiling LESS. |
Learn more about it in the Customization tutorial.
The approach to adding your own LESS is a bit different. You won't do this in the /styles
folder. Detailed instructions on this can be found in our revised LESS Customization tutorial.
Font Awesome, the open source icon font used by both Warp and UIkit, has recently been updated to Font Awesome 4.0. This update is now included in our new UIkit versions. This means that icon class names have been revised to provide a more consistent naming convention and there are even more icons available. For more information, take a look at the UIkit documentation on the Icon component.
Read more https://www.yootheme.com/component/blog/2013/12/12/warp-72-released
Page 850 of 1312