I am thinking of running a website that sells Joomla template (similar like TemplateMonster). When I look at TemplateMonster, what come up into my mind is they have multiple instances of Joomla and they populate the content of every single of them depending on the template.
Is this the only way to achieve this? What if I have 100 templates, do I have to copy paste 100 Joomla?
These are the examples of two different contents:
http://www.templatemonster.com/demo/44048.html
http://www.templatemonster.com/demo/44129.html
Best Regards,
I think simplest way would be adding ?template=beez3 to the uri.
More complicated to use extension like Virtual Domains.
Current menu item (and so template) is set based on rules like current URI. Extension is little tricky to setup but could be exactly what you are looking for.
Related
I have a question regarding the creation of a multilingual website. In short I would like to send online a website and present it translated in 4 languages.
The most important thing is that the website is SEO friendly.
I have read several articles about this topic and some of them were published here.
In the end I decided to create sub-folders like this:
www.example.com/es for Spanish
www.example.com/de for German
and so on …
The main language will be English www.example.com.
Because it is the very first time I am dealing with this issue and I'd like to ask how to proceed.
At first sight, a similar approach makes me realize that each sub-folder www.example.com/es etc. will contain all the codes of the main site. This means that every time when I change something I have to copy/paste the change in each and every folder? Is there a more effective and dynamic way how to do that?
Rewrite URLs
E.g: mysite.com/en FOR mysite.com?lang=en
E.g 2: mysite.com/fr FOR mysite.com?lang=fr
Create a language array with combinaison of key => value in an inclusion file (e.g: inc.lang.php) such as
'en_apple' => Apple
'fr_apple' => Pomme
Replace terms to translate by your included array.
That's my way, it works for SEO (tested with Google tools) and it's light, because you have one directory to maintain for all your languages and it's invisible for users.
This is dynamic has you want, and you don't have to maintain 3 or 4 different folders each time you work on your website.
Hope it helps.
At first sight, a similar approach makes me realize that each
sub-folder www.example.com/es etc. will contain all the codes of the
main site. This means that every time when I change something I have
to copy/paste the change in each and every folder? Is there a more
effective and dynamic way how to do that?
No, you don't need to copy all the code of the main site. You only need to create the HTML content for each language and store it correspondingly in each directory. Then you need to learn about hreflang. It is not very hard, it is only about adding a couple of links in your header.
I'm maintaining a PHP code base that is shared between wiki websites. What I mean is that there is a single directory /web/wiki with PHP scripts that serve several websites, like wiki-devs.domain.com, wiki-public.domain.com, etc. It was written this way because all wikis look the same, and fixing a bug (or adding a feature) in one of them automatically means that all of them get the same fix/feature. The PHP code uses $_SERVER['HTTP_HOST'] to change logo of the wiki and to select the right database, etc, but all the other code remains the same for all wikis.
I'm rewriting this web project to use Smarty templates, but I can't quite understand how to make Smarty avoid serving a template (let's say sidebar.template.html) that was compiled for wiki-devs.domain.com to wiki-public.domain.com, as it doesn't know that there are multiple domains accessing the same code.
I hope you understand what I mean. Just to re-iterate: when "wiki-devs" accesses the site, Smarty generates template for "wiki-devs", but then if "wiki-public" accesses the site a second later, the same template will get served to them.
You should use the one directory for Smarty template and different compile directory for each site. This way you will avoid the problems with compilation.
For example you can use something like that:
$sitename=$_SERVER['HTTP_HOST'];
$smarty->template_dir='themes/themename/';
$smarty->compile_dir='files/compile/'.$sitename.'/';
I am a beginner with Magento trying to build a simple custom theme and while I have done a fair bit of research I am really in need of some simple clarifications because I think that the learning curve is rather steep but worth it once some basic concepts are understood. My design goals are very basic: All products listed on the homepage with different image sizes, floating left.
What I've done is downloaded the 'Modern' theme as a base to work with and renamed it:
app/design/frontend/default/mytheme
skin/frontend/default/mytheme
I've done some basic tweaking to the phtml files in
app/design/frontend/default/mytheme/template/
However, I have a number of questions:
Where exactly is the template for the homepage? Is it only customizable using the CMS>Pages control in the backend under Design>Page Layout? This confuses me because I am used to developing in wordpress and creating a custom php file for the index/homepage. I really think this separation of html/xml is really the hard thing for me to grasp.
If i can only customize the homepage using the backend, I see the block: <block type="catalog/product_new" name="home.catalog.product.new" alias="product_new" template="catalog/product/new.phtml" after="cms_page">. Navigating to mytheme directory, I don't see anything referring to this. Where are these things located? Am I supposed to copy any file missing from mytheme from the base?
Is it only possible to have 1 column, 2 column, 3 column etc. layouts?
An endless thanks to anyone who can steer me in the right direction. I really think it is just a matter of understanding very important fundamentals of how Magento themes are structured. At the moment I am already finding it so frustrating having my finder window open 7 folders deep and having to move around constantly. How I miss the simplicity of Wordpress' single folder themes.
Thank you!!
I suggest you to read all things in http://www.magentocommerce.com/knowledge-base before you go further
homepage content can be anything you want and you can reference it to be anything with layout file descriptors
MVC concept tells that it is taken from catalog/product_new block and from whatever is set to it's template. In current case catalog/product/new.phtml is used and you can edit this
you can have a completely custom setup and not restricted to anything that default contains. However it is wise to use defaults as almost all extensions depend on defaults more or less.
A very big part of magento design is layouts.
whether you choose to use a local.xml or change files from layouts folder you must have an ideea on how they work.
Here is a link for start
Intro to Layouts
There are many others resources outhere ofcourse.
after using own custom cms for over 6 years, I decided to go for Drupal from now on. I will use Drupal for all my works. I'm pretty new at Drupal, started just 2 days ago :D
just a simple question;
I have a simple xhtml-css site (5 pages), and client is asking cms for gallery page (xhtml for now). so is it possible to make only 1 page with drupal and rest pages are using current xhtml somehow? How would I create the base with Drupal for such custom (out of Drupal) pages' links? or do I have to transfer all other html pages into Drupal as Page (drupal page)?
ps, as a new drupal user, i didnt see anything complicated as everybody complains, it is pretty well structured-clear... love it so far :) ps, i say 2 days but I had only few hours so far :)
Thanks a lot!!
The Drupal URL rewriting rules only apply to files and directories that do not exist on the file system, so as long as you avoid naming conflicts, you can put 'static' pages more or less anywhere you like, and Drupal will not interfere with them being served.
That said, it would probably be a good idea to consolidate them within a 'static' folder, either on the top level of the document root, or (more appropriate) within the 'sites' or the 'files' folder of the new Drupal install (which implies adjusting your current paths).
However, I agree with Kevin (+1) that for only 5 pages, it is probably less work in the long run to 'migrate' them to Drupal right from the start, as you will save work and trouble down the road as soon as you further enhance the site.
If its only 5 pages, why not put it all into Drupal? Less overhead that way. Otherwise you will have to edit .htaccess, manually update files instead of making simple changes in Drupal, and edit multiple files should the theme change in any way.
If you need a Gallery solution, I would suggest checking out the Gallery Assist module.
If all 5 pages use the same or similar layouts, navigation, etc then it makes the most sense to put them all in Drupal.
Setting up, configuring, and theming Drupal will be a lot more effort than one page is worth.
But if all your content does not share a similar layout and have very different looks then you may consider leaving them static.
There are many ways to vary the the layout, navigaiton, and such within Drupal, but this may be a challenge for a Drupal beginner and even require a substantial effort from Drupal pros.
If you leave content external to Drupal that includes identical layout elements, it leads to redundant work.
I've been trying out loads of different way to make the most effecient "template" for a site. The site consists of 'Sections', 'Menus' and 'SubMenus'. So to the question; what would be the most efficient and "slick" way of making a "template" for it? I've tried including headers and footers (Making all "head" items in the "header.php" and closing everything in the "footer.php"). I've tried using Case/Switches and includes - But all this gets very inefficient when you have a lot of redirects and pages. So I've been pondering over other sites go about in doing this..
What would you suggest that I start looking into?
Why not use a CMS system like Drupal or Joomla. Then you can take an existing template and build off of it. Drupal uses PHP Templating engine. http://drupal.org/node/11810