typesettercms - teardown

rcjordan · February 22, 2016, 05:59:00 PM

It uploaded a pix from the phone's camera roll to the site. Only 75% as painful. OK, maybe 85.

Drastic · February 23, 2016, 02:33:49 PM

I like what I hear so far. Should I start with this or try another option for comparing notes?

rcjordan · February 23, 2016, 02:47:09 PM

You should start, I think. I'm almost certain that you are going to want this one in your client toolbox. The caveat is that I think it will hit a wall at 50-100 pages. But that's a minor concern, I've made hybrid sites plenty of times.

rcjordan · February 23, 2016, 04:44:20 PM

AFAIK^now, there is no way to import html files into this cms and have them work as public pages out of the box. That said, this cms sets the path to its asset directory. Under that, it has 4 subdirs for these predefined asset types: image, file, flash, media. The cms allows nested dirs. SO, a dev moving (or fast-building) a site could lay out his asset dirs in sync with where the TScms twin site is going to expect to find them using the same relative paths. FTP the images, snippets, etc into the asset dirs, then use the admin console to create the cms-recognized page as a shell. THEN past the page code into that shell. That clear?

<added>
image path in my test site
http://gmcmotorhomesforsale.com/data/_uploaded/image/groundeffects0front.jpg

<added2>
I should verify that nested image dirs will work with their pages.

Drastic · February 23, 2016, 07:18:41 PM

Yeah that would complicate things for my use. I plan to leave existing html alone and drop this (or something) into a dir for a matching blog.

rcjordan · February 23, 2016, 07:49:53 PM

>leave existing html alone and drop this (or something) into a dir for a matching blog

Should work, but won't be dog simple. I've done it before. You're going to have to change a config path or three so they share the same layout files; js, css, php includes.

A quicker/dirtier fix is to just make TMcss blog in a complimentary design and code it into your main menu both sides. TS just treats anywhere you drop it as home, so sub dir for blogging only would work. The problem, though, will be linking to existing images on the master site. I'd move them down into TM and do a F&R on the master site's paths, then they'd share.

Drastic · February 24, 2016, 01:25:14 PM

Well, what I'm hoping is to drop in php includes for <blog side nav>, <the post> (plus loop), etc.

I asked a dev I've been talking with on upwork, for how much to just make it happen, if he could work with this cms and he said sure, it's just "gpeasy" with a new brand. FWIW

rcjordan · February 24, 2016, 02:17:27 PM

>drop in php includes for <blog side nav>, <the post> (plus loop), etc.

That's what I *think* will work, but I'm not versed enough in gpeasy>TS to know for sure. Debbie says that bootstrap should flow across the domain, blog included, without extreme amounts of work.

Drastic · February 24, 2016, 02:46:04 PM

That's my thinking/debbie too. I'm planning to hire someone to just-do-it and be able to replicate.

rcjordan · February 24, 2016, 03:00:11 PM

I'm going with this one for a quickie AMZ aff site. I'm in deep enough already that I can see that it'll work with some hacks and work-arounds. Even the default theme looks PFG on mobile.

You don't have to hold my beer, though. I'm slammed with stuff to do that I've been putting off. It may be a while. I hope to have some notes to compare in Hanoi.