New design features: include token, URL token, and design editor syntax highlighting

Today, we’re excited to bring a few new design features to the LightCMS system. Custom design flexibility is what LightCMS does best, and these features are specifically designed to make designing sites for LightCMS even easier. These features are already live on the system and ready for you to use.

New tokens

First off, we’re adding a couple of new tokens to our simple yet robust token set. For those who may not know, tokens are the little bits of code you can add to your HTML files in order to integrate LightCMS’s dynamic functionality into your own designs. You can check out all of our available tokens our the token reference guide.

One thing you may notice is that our token system, when compared to other systems, is refreshingly simple. We offer a streamlined set of tokens designed to give you maximum flexibility without making things complex. This gives you the functionality you need while ensuring that you can easily learn to work with LightCMS.

The two new tokens we’re adding today fall right in line with this approach. Here’s a little more information about them.

The include token

You can now integrate include files into your LightCMS templates. This can save you a ton of time if you have certain content, like headers or footers, that stay consistent across all pages. Previously, making a change to a header or footer meant changing it on every template, which in some cases might be a lot of extra work. Now, with the include token, you can set up your boilerplate content in separate include files and call those files into your templates through the include token. Then, when you need to make a change to the boilerplate content, you only have to change it in one place.

Include files can contain other tokens as well, including editable regions. They just can’t contain another include token. For all of the specifics on implementing the include token, see the include token page in the token reference guide.

The URL token

This token simply generates the URL of the current page. This can be handy if you want to dynamically generate a “link to this page” badge that will work easily on your blog posts or pages. Or, if you want to implement certain widgets that require a reference to the current page’s URL. An example is Feedburner’s Feed Flare functionality, which you can now easily implement on your blog template using the URL token.

For full specs on the URL token, check out the URL token page in the token reference guide.

Design editor syntax highlighting

The final feature we’re launching today involves LightCMS’s built-in design editor, which is a fast an easy place to tweak your design code. To access the design editor, go to My Website –> Design, click on “My Designs” then choose a design and select “edit.” This will load the design editor where you can access and edit all of the html, css, js, and inc files associated with your design.

We’ve now implement syntax highlighting to make this editor easier to read. As you can see in the image below, HTML, CSS, and JS content is color coded with familiar conventions. Content specific to the LightCMS system (such as token code) is highlighted in yellow to set it apart from the rest of your markup.

Tweak-Editor-Highlights 

Enjoy

As mentioned above, these changes are now live and ready for you to use. Feel free to take them for a spin. Thanks for using LightCMS!

11 comments (Add your own)

1. Mark wrote:
Awesome new feature guys. Would there happen to be a way to turn off word wrap for the code editor?

Wed, March 24, 2010 @ 3:40 PM

2. Tim Wall wrote:
Hi Mark,

Thanks for the kind words! At this point there's no way to turn that off, but we are planning more improvements to the design editor in the coming months and we will definitely consider that idea.

Thanks,
Tim

Wed, March 24, 2010 @ 3:45 PM

3. Andrew Schepers wrote:
Great new features! The include token is going to be a huge time-saver.

Wed, March 24, 2010 @ 4:04 PM

4. FromScratch wrote:
The include token is perfect! NICEE!!

Wed, March 24, 2010 @ 4:29 PM

5. Nickolas wrote:
I love the new additions, this is something that I asked about in the past... regarding the footers. Great to see that your team has addressed this.

The only problem is that I don't know HOW to implement a footer.inc file. I noticed on the help page this information that explains how to call it up using the token:


Use this token to include the contents of a file called "footer.inc" which is in the design's root.



Or, include a file that's in a subdirectory off the design's root:




So, is there a way to coach me through that, I'm dying to save time on the footers.

Wed, April 14, 2010 @ 8:29 PM

6. Nickolas wrote:
Sorry about that, the code I pasted from the TOKEN page disappeared.

Wed, April 14, 2010 @ 8:30 PM

7. Tim Wall wrote:
Nickolas,

In short, you just need to take the content you want to include out of your design templates and put it into a separate file with a name like "myfile.inc". Then, use the include token in your templates to pull in the content from that outside file. So, for your footers, you put all of the footer content in the include file (HTML and everything) and then you simply put the include token in your templates and reference the file.

I hope this helps. If you need more help, you can post a message on our forum (http://forum.speaklight.com) or our web concierge team can walk you through this. Just send them an email at answers@speaklight.com.

Thanks,
Tim

Thu, April 15, 2010 @ 8:42 AM

8. Nickolas wrote:
Worked like a charm Tim. Thanks. That's going to come in handy.

Got one question. Is there any way (from the CMS) that the include file can be edited. I know FTP is a way... but from my client's perspective, can the change this file in a simpler way than FTP??

Thanks!

Thu, April 29, 2010 @ 5:52 PM

9. Tim Wall wrote:
Nickolas,

The .inc files are editable in the built-in design editor, but that area is, by design, off limits to your clients. So, at this point, the only way to allow a client to edit a .inc file is by FTP.

Thanks,
Tim

Fri, April 30, 2010 @ 8:26 AM

10. Alex wrote:
The include file is nice, but it appears that any editable regions in the included file are specific to each page of ones site. Surely it would make sense for changes in these to be reflected in all pages in which they are included? Or to at least have that option. Without that, most of the benefit is removed for me.

Thanks.

Fri, September 30, 2011 @ 6:26 AM

11. Lava Infotech wrote:
CMS Hyderabad .
This is really interesting, You’re a very skilled blogger. I have joined your feed and stay up for in the hunt for extra of your fantastic post. Also, I have shared your website in my social networks.

Tue, September 18, 2012 @ 4:32 AM

Add a New Comment

Enter the code you see below:
code
 

Comment Guidelines: No HTML is allowed. Off-topic or inappropriate comments will be edited or deleted. Thanks.

Tags

Archive

Try it yourself. It's free.

Takes less than 60 secondsNo commitmentNo payment information required

Sign Up for Free