Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have a website build in own php framework, complete with an elaborate product catalogue and cms system. Now I would like to add a blog and I wanted others' opinions on whether to keep using the framework and develop it as fully integrated with existing website and cms or if I should use wordpress. I am leaning towards the first option but was wondering if I'm not missing something important about wordpress that should sway me.
I have never used wordpress before so will have to learn it first to customise it fully to my requirements (will be creating custom template). I know it's a great blogging tool for people not that into code, but I'm wondering that if you do know coding, if it's still the best option.
Opinions, pros and cons will be highly appreciated.
There are several reasons why you would want to develop your own PHP blog, but also several reasons why you should use an existing framework like Wordpress.
Developing your own:
Better understanding of how things work, making it easier to customize it.
The blog is fully yours, no license applies.
Using Wordpress:
A lot easier to create blog post
You can easily install themes etc. to customize your blog.
All in all, I would recommend Wordpress, but thats just my opinion.
Go with whatever suits your needs :)
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Yes, while i'm working on node.js, i still love perl, :)
The old web product is based on old perl CGI, i'm looking to the simplest way to fix XSS/Sql injection/etc. web security holes, within a week including testing, :(
So for
Catalyst
Dancer
Mason
Maypole
Mojolicious
which one should i use in the ARM platform ?
Thank you !
You have fallen foul of the primarily opinion-based off-topic categorisation, and your question will probably be closed very soon. However I think it's worth offering a few guidelines here
First of all you should absorb what is written in CGI::Alternatives as it is a reasonable summary of the subject
Next you should separate the HTML generation functionality of your existing CGI code from the interface itself, and consider replacements for each of them separately. If you were to use HTML::Tiny together with CGI::Simple then your code would have to change very little and you would have achieved better partitioning of functionality
Ideally you will move on to one of the many templating systems such as Template Toolkit, together with one of the frameworks, which is the topic of your question. In the end you will need to do a lot of research and many trials to discover how well each framework fits your requirement, in terms of both the feature list and the convenience and clarity of the API
All I can do here is say that I am very fond of the Mojolicious suite and suggest that it may be a good starting point. The API focuses on command chaining in a way similar to Ruby, and there is a Mojolicious::Plugin::CGI accessory which will allow you to execute CGI scripts unchanged during your migration
Note however that all of the frameworks that you mention, as well as several others, will have their proponents. That is why you must make the selection yourself, as such recommendations will be influenced primarily by familiarity, and without your own knowledge of the requirements of your project
Unfortunately I cannot speak to the security issues of the various options, but I hope that has helped a little
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have been evaluating DNN over a few months. It has it´s pros and cons. I find it hard to evaluate systems by reading articles and don´t have time to check them all on my own.
What are your general feeling about this?
As my background is with .net, which system would you choose?
Also, does anybody know if these pages at stack overflow is based on a CMS and if so which?
Since everyone would rather spend more time criticizing your post than answering it, I'll give it a shot.
You have a few options with building a portal. Either go with an established, open source portal (like DNN), look into some paid solutions or build your own.
Open Source - I've worked with DNN and MojoPortal. DNN is a little slower and has a few more requirements to develop skins and modules, but it has A LOT more features and some of the free/paid modules are really cool. Overall, DNN wins here, but if you don't need a large portal and you want to keep development really simple, MojoPortal might be better. MojoPortal has a few nice features that makes it easier to configure.
Open Source (Other) - There are tons of them out there. Orchard is one I'm thinking of because I'm interested in MVC. But, it's still young in terms of features and support.
Umbraco - I can't really speak to this because I have not used it, but it does have some popularity.
Build it - This is an option and allows the most flexibility, but it takes a lot of time and so many features that are built into these portals could be left out. Role based access, page management, page/module permissions, downloadable modules, profile/profile properties, file management, skinning, acct management, menu management, event logs, etc
I left out non .NET solutions like ones based on PHP, Grails, etc because you are a .NET developer. There is plenty out there, but sticking to .NET will help speed your development up.... unless you are just wanting to learn something new.
Hope this helps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
A friend has asked me to make a website for him, for a games arcade he runs. It's an extremely simple website so no big deal.
The thing is I'm not quite sure how to approach it, I haven't worked on sites in a while. It would probably be easiest for me to create the site entirely myself, a few pages, css and probably a bit of javascript. But then I thought what if he wants to change things himself in the future, so I should maybe use a cms like wordpress or drupal. The last cms I used was nopcommerce about 2 years ago so I'm not really up to speed with them and themes etc.
Back in uni we were making websites with xml, which sounds ideal as I could create pages that would remain unchanged then use xml for arcade machines and news updates which he could edit himself. But that was a few years ago, is that how things are done nowadays?
Apologies for sounding so stupid but I'd like to get into web design again and I just want the opinion of someone with a bit of experience as to how they would go forward with this so I can do things properly.
Thanks!
I found WordPress ok for smaller sites.
Things evolve quickly around the web and you would probably benefit from the large collection of available templates.
Use Wordpress. It's really easy to setup and you can find a lot of free plugins and themes to create a web site with professional aesthetic and basic functionality. Having your information in a database and the modularity of the product makes easy to scale to a bigger site later if it is needed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Can anyone recommend a simple, lightweight CMS gem or plugin for Rails 3 that can easily be embedded into an existing app?
I think you might find this useful: https://github.com/comfy/comfortable-mexican-sofa
It's specifically built to be a CMS plugin for your existing Rails 3 app.
Sorry for the shameless plug :)
I found Refinery CMS to be easily emebddable into my app (with some modifications).
https://github.com/browsermedia/browsercms
BrowserCMS: Humane Content Management for Rails
BrowserCMS is a general purpose, open source Web Content Management System (CMS), written in Ruby on Rails. It is designed to support three distinct groups of people:
Non-technical web editors who want a humane system to manage their site, without needing to understand what HTML or even Rails is.
Designers who want to create large and elegantly designed websites with no artificial constraints by the CMS.
Developers who want to drop a CMS into their Rails projects, or create CMS driven websites for their clients.
Rich CMS is another: https://github.com/archan937/rich_cms
There's also CopyCopter for Rails from Thoughtbot: https://copycopter.com but it's more for managing copy than managing full page content
Best CMS till date
MCMS
gem install mcms
rails g mcms install
please check it
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm thinking about starting to develop a plugin for AutoCAD, but I have absolutely no knowledge of the field. How does the plugin system work? What are the licensing terms? What programming platforms are available?
I'd really appreciate if somebody could give me a primer, or, even better, link to some resources for the total beginner I am.
Thanks!
Prior to AutoCAD 2014, there were three basic plugin types for AutoCAD:
AutoLisp
.Net
ObjectARX
AutoCAD 2014 also provides:
4. Javascript API. You can find a link to the documentation at the AutoCAD DevBlog.
AutoLisp can be used with DIESEL scripts/macros to accomplish and automate basically anything that a user can due through the UI, and a maybe a little bit more, but .Net and ObjectARX are much more powerful, allowing you to create your own entities and more advanced behavior.
ObjectARX is a C++ interface, and the .NET classes are actually wrappers to the ObjectARX interface. The .Net interface abstracts things fairly well, but you still have to be concerned with the threading and possibly some other things as you develop more complex applications.
As previously mentioned, Through the Interface is a great blog for .NET stuff.
For ObjectARX, there is a good introduction at ObjectARX & Dummies, but for the deeper material the Developers Forums are a good resource.
If you are developing anything for people other than yourself, you should also seriously consider getting a registered developer symbol to prevent conflicts among different plugins. You can do that at the Symbols Registration page on the AutoDesk website.
Depending on your resources, you may also want to join the AutoDesk Developers Network (ADN), which provides access to software technical support, and early and beta access to upcoming AutoDesk products and APIs.
What type of application are you thinking of writing? I've written a couple WPF user controls that communicate with AutoCad. To do so, I used the AutoCad .NET Developers Guide found here:
http://docs.autodesk.com/ACD/2010/ENU/AutoCAD%20.NET%20Developer's%20Guide/index.html
This is a great blog to with some good video tutorials on it too.
This is a GREAT video if you just want to get started!