Setting up a CMS
 

For the past two and a half days (including today) I've been looking into Bolt CMS as a way to have users enter and store data into a database and display the information in a user-friendly manner. Back on the release of the Batch Search Engine August 31st this year, I mentioned that was supposed to be a demo and that I wanted to eventually move it over to a CMS.

With a Content Management System (CMS), users can log in to an account (created by the administrator) and add their own song submissions, both song information and the zip or rar. This is eventually planned to be done after I can get a working version of a revamped Crossover Spectrum Site up and running. Since I'm only able to run the site locally right now, I'll be posting screenshots of my progress.

Re: Setting up a CMS
 

Days 1-3

Main Accomplishments:
- Got Bolt CMS up and running on a local server in addition to a repository.
- Defined content types for songs, scoreboards, songpacks, and scores.
- Made twig template pages to display scoreboards in a proper manner.
- Defined relationship from score --> song --> scoreboard (and songpack).

Permissions will come at a later time. Right now I'm focusing on the data points to display on a page. Since the images I'm posting below are huge, I'll put them in spoilers -- my new laptop makes everything look small when the actual image itself is big.

Song Editing Page


Scoreboard Page

Re: Setting up a CMS
 

Bolt seems pretty neat. I have a general dislike of twig templates, but that just might be due to the fact that the things I've had to use them for have been miserable projects.

I don't know if it would be any help, but I do have PHP code available that can parse out metadata from .SM files, and I'm sure it could be adapted to help speed up your file entering process. PM me if you'd like to take a look at it.

Re: Setting up a CMS
 

Thanks, I'll definitely consider that. In this particular case, Bolt seems to fit in nicely with twig -- I can't say for the projects you're mentioning though, it always depends on the specific application.

I also realized how unnecessary a scoreboard content type was. The song itself can have the scoreboard already, just in a non-intrusive way (such as a collapsible panel).

Re: Setting up a CMS
 

Days 4-8

Main Accomplishments:
- Implemented all content-related pages: Stats, Packs, Songs, Scores.
- Tremendous site cleanup.
- Included blog-style posts with paging.

The last step I see now is permissions, which will take some time to sort out. However, in terms of the relations between content and the pages that will be on the site, I am close to completion. I have a video which goes through the site as it is right now locally, and I forgot to include the stats page which I took a screenshot for below.

Pack Stats Page

Re: Setting up a CMS
 

The site has been released! It's http://www.crossoverspectrum.com/ and I can change this framework to fit the needs of the Batch Search Engine.