• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.


Search the Community

Showing results for tags 'frameworks'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • vpsBoard
    • Announcements & Contests
    • Industry News
  • Virtual Private Servers
    • General Talk
    • Operating a VPS Business
    • Tutorials and Guides
    • Questions and Answers
  • The Lounge
    • The Pub (Off topic discussion)
    • Coding, Scripting & Programming
    • SBC, ARM, Home Automation
  • Marketplace & Reviews
    • Reviews
    • VPS Offers
    • Other Offers
    • Service Requests

Found 1 result

  1. For me planning a homepage does include three steps: plattform framework management I would like to discuss what current options are available for these topics. Basically if I am still on the right path. Back to the topic: Management Do I need a GUI for creating content? Dynamic or static content? Framework Site creators or CMS Plattform vps server webhosting About 10 years ago I started with the plattform (budget) and afterwards thought about the frameworks. Nowadays my first question is if it has to be dynamic, second one if it can be avoided to be dynamic. Long story short: I am done with about any CMS. Content management systems brake on about anything from upgrades, themes and plugins. Don't even think you can customize anything without slapping yourself a few months later. Yooomla, Badpress, Ghosty, Drupi or Redexe are broken by design. I stopped using them and I stopped hosting them. My tutorials, my blog, my documentation are all written in md. Markdown helps a lot if you want to generate something out of it. No style, only content. I started with Jekyll, moved to Octopress (due to the addons - it is more like a Jekyll++), tried Pelican and Middleman, moved to Hyde and now moved everything to Hugo. There is still a little bit of Ruby flying aroung, because searching and paging (if you do not want to generate 1000nd of html pages) is still the last resort of dynamic content generation. But even wlanboy.com is 99% static content with two dynamic views. After about 15 years of php, phyton and ruby frameworks I feel quite well with: markdown to preserve content static site generators to get css/js injected html ruby & phyton for some searching/paging My next plan is to get rid of ruby & phyton on the frontend side. 100% generated webpage with some js code which is doing the searching, paging, tagging stuff through a rest-service: - [js] - [js rest-client] - [rest-service] - [database]. Simple html only hosting for all webpages and frontends and some javascript clue that is handling the dynamic stuff. The rest-service is hiding the database. So no SQL-injection and an easy move if I want to switch databases. There will be something like a 100% dynamic management frontend to create content, but that does not have to be installed on the webservers. Good luck to hack a static html page on a get-only webserver without any write or execution rights. I like to have my homepages on my dropbox. Generating new content on my laptop and it is automatically published - a small ruby script ftp-ing the html/css/js stuff. write markdown file with your texteditor of choice start static site generator of your choice syncing generated folder (html files) to your server/hosting account done Perfect separation of content (markdown), theme (css/jss/layout) and output (generated html).