Wordpress or static PHP site

by 17 replies
19
Should I build a WordPress driven site or have it as a static site that is PHP driven?

It is in process now. Basically, it is a WP Responsive theme style sheet with separate footer,header, navbar, and body php files.

Originally, it was thought there would be no blogging but now there will be some articles. So, would you leave it as a static php file and add content as needed which would then not have the benefit of tags, automatic adding to xml sitemap, dates, authorship, pinging, etc.

If there were a way as a static php site to do the above (include the date/url format like wp, content tags,adding to sitemap automatically, author, etc.) I think I would leave it as is. It will be for a loan site, if it makes a difference.

It appears I answered my own question.
#website design #php #site #static #wordpress
  • If you wanted those features that wordpress offers then by all means use wordpress.

    You can do all that with regular PHP obviously (since that's how wordpress does it) but you would need to fiddle with databases and such to get the comments and tags correctly. It's not all that hard to mimic those features, but it will take some time to plan it all out and implement it.

    If you don't need those features then you can safe your self the time in converting your code over to wordpress.

    My advice is this: if those features matter, then definitely go with wordpress, it will be easier to take your code and power it with wordpress then trying to replicate the features it offers.

    If you don't care too much about those types of things then just go with the static php driven site, no use wasting time for features you don't need.
  • My answer It's better to use wordpress for those featured you mention..
  • Wordpres is my first choice. You can also control wordpress n better way rather than PHP site....
    • [1] reply
  • As the plans have changed, I would recommend using platform such as wordpress. Adding content can be a bit tedious with static websites. CMS's are out there to handle the job. If you have a ready-made static PHP site, then converting it to Wordpress friendly template can be done for even less than 100$. Of course all depends to the person, quality of work and complexity of your markup + design (in general).
  • Definitely go with WordPress. It is much easier not only for the simple tasks, but you can add many other features as well. The free plugins available on the WordPress platform is plenty.
  • I recomend you WP. It is better than custom build site at first. Of course if you have a lot of visitors you can make a php site.

    http://obrazovani.info
    • [1] reply
    • In my opinion you should definitely go for WordPress than using/develop a custom php driven CMS.

      Why? because of the following reasons based on your current condition:

      * Wordpress is free, secure and stable CMS, but you have a pay a handsome amount to a developer to develop your custom php script.
      * There is no easier CMS available in the WordPress, its user friendly, SEO friendly and well structured.
      * Its a stable script and very less chances to get hacked when proper steps are taken and security plugins are installed.
      * Minimum cost or one time cost is required to pay to developer in order to convert your template files to WordPress.
      * You can extend your website features anytime with thousands of free plugins available, where a custom php will be too expensive to develop and integrate those features with your website.
      * Finally You will get very smart and handsome SEO plugins which will make your website SEO friendly.
      * Additional media query based CSS will add responsive feature to your website template (not required if the template already has responsive CSS)
  • Definitely you can do the same with custom code. we are already doing the same websites with our own class concept and more over seo also managing dynamically with meta tags and all .. My suggestion is if you want a blog type website you may use wordpress only as it is more helpfull to SEO plugin like Yoast and all . And if it using for your business websites you may use the custom std with a nice admin management and all.
  • Wordpress is great for the features you require, just WP to start, if your traffic is high, you can use php driven site
  • Wordpress is just once and good choice for you because it's very good platform of this kind of work.
  • And the winner is WordPress.

    You can actually tweak and add some codings on the wordpress if you want to tweak any themes or so. WordPress is flexible and easy to use.

    Highly Recommended.
  • you can add php to WordPress using certain plugins. You can have a php-html form running in the sidebar if you want. WordPress is a good base to start, so its not either or (WP or php) since you can have both.
  • OK, maybe to get a meaningful answer you should first figure out how to ask a meaningful question.

    If your "static" PHP site is connected to a database and you store the content (plus, comments, tags etc.) there, i.e. in the database... then there is NOTHING STATIC there!
    It is as dynamic as WP or any other ready-made CMS (content management system). So in that case the real dilemma is between an available open source CMS (WP, Joomla, Drupal, sNews...) and your own hand-coded custom CMS!

    A "static" page/solution is plain HTML files.
  • Ha Ha Ha.....Every Body is biased with WordPress Just Like Me.....Just Use WordPress Always considering its frequent updates.

    In future, You may need a specific feature which today you might not be able to visualize and for that WordPress is best.
  • I would go with WordPress because its a tested platform, making it cross-browser compliant.
  • Banned
    That doesn't even make sense.

    It's like asking, should I drive a car or should I drive an automobile?

Next Topics on Trending Feed

  • 19

    Should I build a WordPress driven site or have it as a static site that is PHP driven? It is in process now. Basically, it is a WP Responsive theme style sheet with separate footer,header, navbar, and body php files.