For those wondering what's going on...
I've been rewriting the whole thing from scratch. I'll probably have a browseable demo (no admin access) posted this weekend.
Here's a short rundown of how things are going to work now:
URLs to each article, profile, etc., look like directories/files, like how page.cgi works. For example, articles can be accessed as "blog.cgi/site_directory/article/12345.html" or "blog.cgi?g=site_directory/article/12345.html". This means it'll be easier for you to run a simple rewrite rule to get these dynamic pages to appear static.
A single user can be own one or more blog sites. He may invite a friend to become an editor. That person would recieve an email with an activation key to join that blog. The person would need to register a Links account and/or login if neccessary to complete the activation.
The owner can then individualize the permssions for each editor. They may be marked as "admin", where they have same control as the owner of the site. Or, you can specify which functions: general settings, templates, etc. they have control over.
Same goes for posting. You can assign a category to each editor, whether or not they need to be approved prior to posting, and so on.
You'll also be able to "sticky" a post to the top of the main page and/or its category. Or save the post as a draft.
I'm sure I'm going to alienate a few people with this next one:
I've become pretty fond of using GLinks 3.0 template system. It allows for complex data structures in tags, as well as nested loops.
It's because of this I'm going to be making 3.0 a requirement. (I suppose you could copy GT::Template into 2.x)
I believe it makes sense to enforce naming structure for related data (ie, <%Post.Title%> rather than <%Title%>). This also helps avoid a global tag from being temporarily overwritten during a loop.
As I said, nested loops are very helpful when bulding tabular data. For example, a calendar.
<tr><td colspan="7"><%Calendar.Title%></td></tr>
<%loop Calendar.Weeks%>
<tr>
<%loop Week.Days%>
<td width="20">
<%if Day.HasPosts%><a href="blog.cgi/<%Site.DirName%>/archive/<%Calendar.Year%>/<%Calendar.Month%>#<%Day.Date%>"><%endif%>
<%Day.Date%>
<%if Day.HasPosts%></a><%endif%>
</td>
<%endloop%>
</tr>
<%endloop%>
</table>
The nested looping also makes it possible to include a date header between each days posts.
An idea I'm toying around with is building static pages. Since this is potentially hazardous, I'd like opinion on whether or not to include this option. Maybe this would be on/off globably in the plugin options, or individualized on a site by site basis.
Philip
------------------
Limecat is not pleased.
I've been rewriting the whole thing from scratch. I'll probably have a browseable demo (no admin access) posted this weekend.
Here's a short rundown of how things are going to work now:
URLs to each article, profile, etc., look like directories/files, like how page.cgi works. For example, articles can be accessed as "blog.cgi/site_directory/article/12345.html" or "blog.cgi?g=site_directory/article/12345.html". This means it'll be easier for you to run a simple rewrite rule to get these dynamic pages to appear static.
A single user can be own one or more blog sites. He may invite a friend to become an editor. That person would recieve an email with an activation key to join that blog. The person would need to register a Links account and/or login if neccessary to complete the activation.
The owner can then individualize the permssions for each editor. They may be marked as "admin", where they have same control as the owner of the site. Or, you can specify which functions: general settings, templates, etc. they have control over.
Same goes for posting. You can assign a category to each editor, whether or not they need to be approved prior to posting, and so on.
You'll also be able to "sticky" a post to the top of the main page and/or its category. Or save the post as a draft.
I'm sure I'm going to alienate a few people with this next one:
I've become pretty fond of using GLinks 3.0 template system. It allows for complex data structures in tags, as well as nested loops.
It's because of this I'm going to be making 3.0 a requirement. (I suppose you could copy GT::Template into 2.x)
I believe it makes sense to enforce naming structure for related data (ie, <%Post.Title%> rather than <%Title%>). This also helps avoid a global tag from being temporarily overwritten during a loop.
As I said, nested loops are very helpful when bulding tabular data. For example, a calendar.
Code:
<table border="1"> <tr><td colspan="7"><%Calendar.Title%></td></tr>
<%loop Calendar.Weeks%>
<tr>
<%loop Week.Days%>
<td width="20">
<%if Day.HasPosts%><a href="blog.cgi/<%Site.DirName%>/archive/<%Calendar.Year%>/<%Calendar.Month%>#<%Day.Date%>"><%endif%>
<%Day.Date%>
<%if Day.HasPosts%></a><%endif%>
</td>
<%endloop%>
</tr>
<%endloop%>
</table>
The nested looping also makes it possible to include a date header between each days posts.
An idea I'm toying around with is building static pages. Since this is potentially hazardous, I'd like opinion on whether or not to include this option. Maybe this would be on/off globably in the plugin options, or individualized on a site by site basis.
Philip
------------------
Limecat is not pleased.