Custom Websites

5 Reasons to Consider a Custom Website:

  1.   You want your website to stand out from the crowd
  2.   You need fast and efficient code for search engine rankings
  3.   You want to simplify maintenance and security
  4.   You need  quick and easy editing options
  5.   You don't have time for manuals and tutorials

Visit HERE for a demonstration of the LilaWorks custom website/blogging framework. 


If you need a basic 'brochure' website to display your services, products, background or contact information,  you should consider a custom website.  

You are probably thinking that 'custom' implies difficult and expensive, but for many applications,  this is not true.   In fact, a website puposely created for your needs can be much smaller, faster and easier to maintain than a website build on a multi-purpose CMS framework.  

Website/blog combination

This option combines a basic website with the LilaWorks blogging engine.  LilaWorks uses a flat-file database that is easy to access and maintain, and also gives you control of your content.   Your blog pages and other content are stored in accessible text files that are easy to save, backup and transport.  

Add a Portfolio

You can include a portfolio collection and choose the way you would like your images displayed.   Each image will also have a unique page where you can add a description.

You can contact me here:

(513) 418-1480

Build a Flat-File CMS - Part 1


VIew LilaWorks flat-file Content Management System Demonstration

If you are curious as to why I decided to do this, when there are so many CMS frameworks already available, you can read about it here.

Warning:  This is not very complicated.   The only code used is basic HTML, CSS and PHP.  The only package I used was a free version of CKEditor.

Who is this Product For?

Most of the popular frameworks that I am familiar with, such as WordPress, Squarespace and Wix, provide exhaustive design capabilities.   Lots of extra code is required so that the person customizing and configuring the website can avoid ever encountering code.  

This makes sense when the designer and user are the same person.   However, in my experience, a designer/developer (like me) is usually asked to get a new website ready before the customer can use it.  

Since the customer always has unique requirements, the first thing I must do is choose a 'theme' that will work now and in the future.   Some frameworks make it difficult to change a theme once it is in place.   Others provide a mind-boggling myriad of themes.  In desperation it's tempting to pick a giant 'do-it-all' theme, the equivalent of taking an ocean liner across a pond.

Since there is so much code involved it's difficult and time consuming to figure out where and what can be changed.    I feel like one of those little birds cleaning a shark's teeth - I have to be very careful of the huge monster I am interacting with. 

To paraphrase Andrei Sorin ("Software and Mind"), lots of extra code is required for the purpose of avoiding coding. 

LilaWorks was created for people like myself who have the responsibility of customizing and maintaining websites.   At present, the design tasks can  be accomplished with a little knowledge of HTML, CSS and simple PHP.   The non-coding user is limited to a very few options - adding and editing posts and pages, managing comments, uploading images and using categories.  

The LilaWorks basic functions are performed in small modules with really obvious names like 'show-latest-posts'.   They are small and comprehensible so It's easy to mix and match and rearrange them on pages.

If the user would like their blog post snippets for the category 'cat recipes' on the bottom of the sidebar, but then they decide that should be a menu item, all you need to do is add an 'includes' to the module that builds that particular page and a line of code in the header module for the menu item.

The great thing about PHP is that it's written in plain English.   How nice to see a statement like 'If (file_exists ($thisfile))" - I know exactly what this means.   Go PHP!!

Ok, let's get started!


In order to manage a collection of posts, a blogging engine should:

  • provide an administrative area for authorized users and a login screen
  • provide a way for the user to create and edit posts,  assign categories, featured images and choose a post status
  • provide a variety of ways for post archives to be displayed
  • provide a way to upload images
  • allow readers to comment on posts
  • allow  owner to flag comments as 'approved' or 'unnapproved' for display
  • provide choice of page layouts, including a contact page and sidebar content
  • allow owner to manage content blocks on pages other than posts
  • provide post version backups

There should also be a control panel displaying the website content and user options such as adding posts or images.  


My strategy was to use four types of files:

1) Data files such as posts, content blocks and images

2) Design files that create the theme or skin: style, header and footer

3) Layout files that organize the data on the page: ex: blog-single, blog-series

4) Program files – php programs that manipulate the Data files and insert them into the Layout files, modified by the Design files.

lilaworks files

...stay tuned for Part 2 - Data Files ...

Category: tutorials