Needing advice for launching theme builder integrated with CMS on Git Hub

Hi, I’m asking advice as I’m new to Git Hub and have been working a long long time (years) on a project, self teaching as a hobby then working full time on it independently but its ready to be shown as a working model and I  don’t know what to do about choosing a license. What if I choose a GPL license then find out it wasn’t the best choice for what more savvy team member(s) would like to go with it? I’ve read enough to only realize there are subtle differences between the various free and open source licenses out there. Not sure even how to list it on Git Hub ie under template builder, theme builder or CMS. Template has few options and CMS has oh so many! Theme builder some where in between. Open to advice/suggestions on this and best approach to move forward.

So the system is designed with developers in mind to provide necessary tools for theme building and content management, RWD response and still be editable by non techies. It is built on php, mysql, js with flatfiles generated in editmode to replace most mysql queries for normal webpage mode.

One can create new, or clone or duplicate both simple or complex nested and/or non-nested column structures (styled divs) to organize page layout just as needed. So at any point in a web page you can choose to create a new content post type which may be a new column (div) to organize content such as when starting off a new page from scratch. Or choose to clone or copy or move a previously created column (including any columns nested within along with posts and associated styles and configurations) or do the same for a simple content post to positions within the same page or any position on another page. And for cloned content (mirrored content typically from another page) which may be a whole page now serving as a mirrored template on another page you can unclone any portion of it whether a column with its associated content or a single content post and substitute in newly created content/columns or clone, move, or copy content types including columns of content from elsewhere.

Like this any portion of a page can be used for other projects, ie for building other pages and the site can use any number of different templates if needed. The idea also is once made pages (primary columns containing columns of organized posts) are importable to other websites built on the system which in turn can use them in part or as a complete template wherein page specific content is substituted. The system also has a mechanism where templates can be easily switched out and page specific data retained.

By default cloned posts will be styled and configured according to the parent post and any changes to the parent are reflected immediately in any clone of it on any page. But you can choose to locally style or configure any cloned posts types as required making page specific changes. Similarly, you can locally change the actual data of a cloned post and keep the styling and configurations of the parent which is very handy for posts such as multiple galleries.

Developers will find advanced options for general and RWD styling and the ability to customize functions if required. The system is built to maximize customization options providing mobile response tools, detailed styling options, configuration options, and tools to enable exporting and importing of previously configurations.

There is a site showing a summary video giving quick view of basic features. Below that are more detailed (less edited and more real time) videos of the same if anyone interested.

Well, if you really, REALLY want to be sure you choose the license that fits you best you probably want to ask some real legal advice from a laywer.

I am, and I think that’s the case for many people on the forum, not confident enough to provide information to you on that matter.

1 Like

Appreciate the reply Mark.  Advice from lawyer is good idea.  Be nice if there were some kind of guide to why developers choose a particular license! 

If I knew what fit me best that would help   but  I’m happy if theres is  interest with any license as it takes teamwork to get  project like this up to speed and maintain it! 

1 Like

Hi @sdrshn,

As @mpboom mentioned, you really can’t get any better advice than that from your own lawyer, buy GitHub has put together a guide on the legal side of Open Source that you might find helpful:

1 Like

yes that should do it ty

1 Like