2023-02-17 Friday

I re-wrote the styles for the New Post form and the File Uploader. I tried to remove most of the inline styles but found that it was best to leave some of them intact to work with the JS/JQ scripting.

I tried to style only the base form elements, at least those currently in use, so that they are applied to all other forms (comments, admin, pages) on the site and only applied specific styles to the form/uploader where absolutely necessary.

I didn't bother cleaning up the IDs and Classes used for the form/uploader; I am not certain if there's much point of this at the moment. As a larger project, once all of the functionality is tackled— Pages and Admin are next, I may spend a significant amount of time cleaning up existing CSS structure as well as what I initially crafted.

Next Up

I think things are at a good place for the core posting/daily functionality. There's nothing that doesn't work. There's some weird styling issues, and a couple of things regarding UI elements showing when they shouldn't, but nothing that I'm too concerned with at the moment. I think it would be good to move on to the next big task.

Pages.

At the moment, Pages still appear as part of the original/core CSS/template and do not match the rest of the public facing portions of the sites. I need to add in the shared header, footer, and sidebar while accounting for what elements are common between pages and post and what are unique.

If that's all I needed to do then I'm fairly impressed with myself.

Given that the pages aren't the main function of the platform, and recognizing that I am not building this all from scratch, I had to tell myself it's ok if everything isn't 100% perfect or working the ideal way I'd like to see it working.

What does this mean?

The pages are templated (those which you add/remove).

All it took was adjusting my expectation of what a common header.php file looks like for (franked)log

It's not perfect, but it works.

Now to tackle the static pages /feeds and /colophon