If you are a Joomla developer, I am sure you have heard of or used the T3, Gantry, Zen Grid, YJSimpleGrid, or the new Gavern template frameworks built by various sites.
I want to make one for my own company, we have some specific sites we build where pieces are always the same etc. But I am trying to figure out just how to start building one? Have you built one? How would you build one?
Actually you need to create a joomla component for it, the component core objectives should be setting up the template. To eliminate the work redundancy you can create component settings as well. Let me know If you wish to have more info.
Related
I have created a webapp using Wix, which relies heavily on the repeater element to display content from a database inside a repeating element. Repeaters do pretty much exactly what I want, but I realize they are built on a pretty sophisticated API, and there's a lot of stuff making this happen in the background.
Ultimately for this project, a native iOS app is the end goal. However, I have no experience in xcode - but willing to learn. Before I get in too deep, is there any kind of functionality I could find to achieve something like this?
Thanks in advance
You can't convert Wix Repeater element to Xcode. But, you can make deep customization to your Wix elements by using Wix Corvid.
If you not familiar with it, it's is a developing platform integrated into the Wix ecosystem that allows users to build advanced sites. Among other things, it’s able to create and manage databases, build dynamic pages, host user-generated content and more.
I have been learning to develop my own plugins and components for joomla! 2.5.
After a couple of months of developing features for my site, I am starting to realise that some of the components I have created could have probably been just as effective if I'd developed them as a plugin for com_content or com_user.
My question is what's the best way to decided if a full component is needed and when is it ok to use one or multiple plugins to give the same functionality.
My feeling at the moment is that plugins are a much nicer way to go due to them being self contained. Maybe I've answered my own question, and components are needed when interaction between elements is more complicated, where as plugins can be used for very modular functions.
Anyone else have a view?
Components and Plugins are completely different types of extensions.
Components are applications/systems that will appear in the content area such as VirtueMart and where the articles are shown. Consider them as software for you computer.
Plugins are there to manipulate Joomla and/or there extensions it's using. They contains functions that are associated with trigger events. So in a nutshell, they are there to extend the functionality of an existing extension.
So so answer your question, have a think about what you are creating and if will be an aplication or something to extend functionality.
Hope this helps
my boss says to me
"I want a web portal that allows me to install/uninstall new modules. These modules, when installed, can be dragged as widgets onto a portal dashboard and if u navigate to a widget, it will contain its own set of pages. I also want an admin portal where I can set the security level on each module. Lastly modules should be distributable separately from the portal. And yeah, I'm not paying for SharePoint".
I first got excited because I immediately saw in my mind how I would build this. Then I thought, wait, this isn't a new problem, don't CMSs do this? My question is have you guys come across any open source ASP.NET MVC frameworks that I can build upon that already provide this sort of module programming? Or maybe a "light-weight CMS" (a CMS may be overkill for what I want) that I can build on?
I would want to have the CMS capabilities (or at least the basic functionalities like CRUD) for my custom db table. Is there a way to do this. Migration is not an option for me since there are other applications that use this table.
Any help would be appreciated. :)
Two choices spring to mind for quickly build 'basic' components such as you describe here.
JFooBar component - is a component you install into Joomla 1.7 that facilitates building components that you then package up:
https://github.com/Niambie/jfoobar
Alternatively there is an online tool that does a similar job:
http://www.j-cook.pro
I've only played with these tools - but have a couple of projects that need something simple knocking together and will be trying them out on 'real world' projects shortly.
I currently have a simple website that I want to convert to a CMS without losing any of the appearance or existing functionality. Also I would like to re-use my existing code for the site where possible and also make use of our in-house libraries and databases.
Orchard seems like a good bet because it also uses MVC 3 however it seems a bit bloated. There is a small project at atomicCMS which looks interesting. Has anyone used this?
Any hints or tips would be appreciated.
There should be a tag for this post called atomiccms but my account cannot create one.
There was a similar question, which you can find helpful.
Moving an ASP.NET MVC 3-based web application to Orchard is a fairly simple task. You just have to wrap it up in an Orchard module.
I have used both Orchard and N2 CMS. Both work on asp.net mvc.
I like the way Orchard is designed, but it is a rather steep learning curve. Also you will need to develop modules if you want to add your own custom functionallity.
After hearing a .netocks podcast on N2.CMS I decided to try it out for a recent project. It has a different approach/philosophy, you can think of it as a 'plugabble' CMS component. You basically keep your existing web app and can use CMS functionallity where it is required.
However, Orchard does have many more modules and skins available. I would definetly give N2.CMS a closer look, especially if you have an existing application.
In Orchard you must run as an orchard module (Mvc Area) and have no direct access to the root web.config. Depending on what you do in your existing app (wcf, etc...) this might be a limitation. With N2 cms you are not restricted in this manner.