I am trying out VirtoCommerce for a work project. I am impressed with all the technologies being used. However the community seems rather small.
In VirtoCommerce, what file should I choose to add a theme?
Thanks for any help.
You can take any of the existing themes as a starting point to creating your own. You can also download skeleton theme, that contains all the basic controls.
Related
I recently started using SASS and right now I need Font Awesome for one of my project but I want to use it offline. I know that I could simply use CDN (as I did) but I just don't know how to use it offline so it's pretty annoying :D
Well, basically you just download the resources, add the .js/css-links to your .html and use the icons ;-)
It's all described on their website - but the choice of options (CSS or SVG) might make it look more difficult than it is...
Where place my custom files in magento if i want develop extension in design/frontend/base/default or design/frontend/default/default. I think be logic place it to design/frontend/default/default, but i am find opinion about that good practice place it to design/frontend/base/default
Thanks!
It depends on what Magento versions will you support.
If you plan to make your extension work on Magento 1.3 and lower than you should put your design files in default/default.
If your extension is for versions 1.4+ then place them in base/default.
You can see other tips and tricks that might help you when building an extension in here
I'm playing with Joomla 2.5.9 (The latest 2.X download). Do you know how you can add additional menu's to the "Article Manager: Edit Article" page? (This is in the Administration)
Their API gives me some hint on several things but I am don't know what this right "Slide Down Option Area" is called in the Administration.
In the right area there are things such as:
Publishing options
Article Options
Configure Edit Screen
Images and Links
etc..
I want to know where to start to add my own, or where they are already built in the system so I can base mine off it -- Is this a plugin, module, or something else? :)
As i say don't change any of the core file in Joomla. If you want to add any functionality into the article manager you can make your own plugin to add functionality in it. For doing this see this link :
Creating a content plugin
I hope this is what you looking for.Good luck.
There are some extensions that allow you to do that.
I recommend (although somewhat buggy and a code mess) this one:
FieldsAttach
It does exactly what you want.
Or, you could make your own as Toretto suggests, there are some tutorials on creating a plugin for extra items in the article form, but the already-made-extension route seems to make more sence.
I've been using FieldsAttach for this sort of thing, for a few years, the code is often a little messy, that is true, but the the concepts are clean and eloquent. Brian Teeman explains it well from an integrator point of view in his talk at https://www.youtube.com/watch?v=f2WLKWbRj5U but in some ways it is even more compelling from a developer's perspective.
However, after watching Marco Ding's Joomla Day UK 2016 talk on https://www.youtube.com/watch?v=KDh1IPuZAVA I think DPFields may be a better choice. The architecture is perhaps more rugged and neater, but also because it may well end up being a core extension in Joomla in the near future. More info on DPFields is at http://extensions.joomla.org/extension/dpfields , https://joomla.digital-peak.com/products/dpfields and https://joomla.digital-peak.com/documentation/162-dpfields .
A good number of the tutorials I've found on Magento theme development recommend starting off with using blank as a guideline for making your own custom theme. A lot of these articles are pretty old, as of the current version (1.7), is this still the case?
P.S. - If there are any good/relevant theme development articles out there, aside from Magento's official design guide, please feel free to link them.
In my opinion you should never 'carve out' your own theme from a base theme. You aren't learning theme development in its entirety. You will potentially run into unforeseen consequences. You will likely have excess code and templates by the time you are done.
I wrote a Magento 1.6.1 tutorial on creating a theme that should hold up for 1.7:
http://zaclee.net/magento/make-magento-1-6-theme-from-scratch
If you run into any problems with 1.7 let me know and I'll be glad to take a gander.
I would agree with the above answer in the sense that converting an existing theme (ie a commercial theme you've purchased) to fit a design you've been given or done yourself can be more consuming. You end up doing more deleting than adding, and inevitably end up with a tonne of code that isn't being used (because taking it out might cause problems, the deadline is approaching....sod it, it's only a few Kb, you just leave it in).
However I disagree with the statement that the Magento blank theme will result in excess code and templates. For a start you only pull in the templates you need and the theme is about as bare bones as it gets. I always use the blank theme as a basis. It may well be the case that I am not then learning theme development in it's entirety but the work has to go out, bills have to be paid - and I'm not about to sit and build everything from scratch every time.
To further this discussion, for some time I have really been bugged by the default CSS that Magento ships with. It is a pain to work on, and when you start developing in an environment where multiple people are working on the CSS, you inevitably run into CSS Kudzu.
It's been on my plate for awhile to completely rewrite the default CSS to something more maintainable and trimmed down, but like rabmcnab mentioned, there are deadlines, bills to pay, etc.
What I should do except writing owner Site.css? It is possible to give writing Site.css to designer without any worry about merger functionallity and design?
I wrote an intro blog post on theming Orchard.
On my latest project the designer in our team read it so he could turn his designs into an Orchard Template.
The key thing we found was that the designer needed to have his own local version of Orchard running that he could make changes to and see the affects. We had him running it through Visual Studio, but Web Matrix or IIS running locally with him using his own editor of choice would have been just as good.
A combination of the Developer module and visual studio helped him work out what was what.
My article is not pitched at designers though, so I did pair him with a developer at first to get him started. This worked really well and the designer now feels confident and can make new templates from scratch by himself.
It depends on what you are trying to do. In some cases, CSS is enough. In some cases, not, and you also need to change layout and a number of other templates. CSS should be no problem for your designer. For templates, they just have to understand what the #{}, #() and # are doing and learn not to touch these parts and work around them. Good web designers should be used to that sort of thing.