troglodyne-internet-widgets / tcms Goto Github PK

https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types

Preload should be handy

The posts, blogs, projects and other user data should be in a separate repo from tCMS to enable ez-updating of the core code, and rollback. Just check it out yo.

As to the content and user theme overrides, it too should be a git repo -- this has better ownership/modification data and revision graphs.

This would make backing up of content, rollbacks, etc trivial and preserve edit/ownership quite nicely -- and add emails for authors to boot.

Deal with dead links and sneaky retcons of the content

heard @troglodyne talking about this one

Would be good to have on the CLI and available through the config UI.
Basicallly, I'd want any custom themes made in issue #2, everything in /microblog and /blog along with whatever modifications were made to the titlebars/sidebars in /special. Really just as simple as tarring and gzipping the directories for you and providing you a link (if in the UI).

saw this morning

Just don't load them if the file not exist

Wanna be able to jump between revisions of posts

for love

Remove dropdown selector from the posts form, only display posts of the relevant type, section out user edit into it's own page

gotta think a bit about this one

Particularly interesting for things like photo albums

I'd leave the content from whatever time threshhold the user sets alone, but once it becomes old news, I'd like it to turn it into a static page. This would enhance SEO, page/server load stats, and enable tCMS sites to be easily exported to networks like Malestrom and SAFE.

I'm thinking the way to get this done is having the functionality in both a CLI script that installs a cron to do this and in the sys/admin UI under general configuration options.

This will probably be a good thing to do whilst loading the configs in general up on that page and making a coherent control panel UI.

hup starman

show everything to admin ACL, otherwise just add the acl name to the tags array passed.

During the refactors to take care of other issues on this, it's become obvious that I break crap all the time. I should add tests.

mo' branding and themable

bad

I should have the data for that live in ~/.tcms as a json blob or something, as that would also help with fuzzing in future

Kinda surprised there isn't a default fuzzing framework using a JSON data model etc...nor anything on cpan

better ux, fall back to paginator in

and by who, using what campaign, etc.

Right now all we have is UUID per request, which should be slapped in a cookie instead

make it so

To ease migration to newer versions, or to new servers, having the theming users do above and beyond what already is there in an override CSS file with additional imagery in a theme directory would be useful. Having a button to export this on the config page would be useful. In the future, adding support for multiple themes would also be good, but getting that bit first is more important.

Having a minor hint to the user what the filetype is would be handy, normal file managers do this.

That said, we already break things up by filetype in the main menu. This might be enough.

make it so

Make this an OPTIONAL feature per post.

Comments need to be posts themselves!

Restrict to paid users.

Need to make issues per the ones i have laying around before hitting the data model

get dat email marketings

put behind auth obviously