Ahoy!
We have a new version of the Trongate framework - so we might as well have a new website too.
At the time of writing, I’ve just uploaded the (unfinished) forum, and there’s a boat - load of things still to build and fix.
I’ll be using this thread to keep you updated on my progress.
My current to - do list is as follows:
* Upload basic forum - DONE
* Upload new docs for v2
* Sign - in / sign - out mechanism
* Contact us form
* Search forums
* Search docs
* Rebuild desktop app endpoints
With regard to that last point, the desktop app is currently not working for anyone. However, it is absolutely my intention to restore full desktop app functionality for Trongate v1. It may take a few days, but hang tough - I’m confident we’ll have it working again very soon.
Website Status Updates
3 months ago
3 months ago
#1
3 months ago
#2
Hi DC, congratulations on the new site and launch of TGv2. I'm off to work right now, will have a poke around when I get a moment and let you know if I find anything not quite right.
Cheers,
Si
Cheers,
Si
3 months ago
#3
Wow! You got logged in before me! Hello!
Just to give you an update…
It’s going to take me about a week to get this site into a decent state, but here we are.
At the moment, this is a beautiful demonstration of the principle: “just launch it anyway.”
My goals for tomorrow are:
-> Build/check the contact us form.
-> Build search engine for the docs.
-> Build search engine for the discussion forum.
I'm also going to spend time working on the docs. There are currently gaps in the docs and fixing this is a HUGE priority.
The Desktop App API (for v1) should be rebuilt by the end of the week (fingers cross).
First YouTube tutorial goes out between now and Thursday.
Ahoy!
Just to give you an update…
It’s going to take me about a week to get this site into a decent state, but here we are.
At the moment, this is a beautiful demonstration of the principle: “just launch it anyway.”
My goals for tomorrow are:
-> Build/check the contact us form.
-> Build search engine for the docs.
-> Build search engine for the discussion forum.
I'm also going to spend time working on the docs. There are currently gaps in the docs and fixing this is a HUGE priority.
The Desktop App API (for v1) should be rebuilt by the end of the week (fingers cross).
First YouTube tutorial goes out between now and Thursday.
Ahoy!
3 months ago
#4
Just to say, the 'members count' on the home page of this forum is a genuine number. However, it's probably going to go down again before it goes up.
I need to write a script that clears out incomplete sign-ups. So, don't be surprised if you see a dip from the current number which is 1201.
Oh, and I've just realised that we don't have favicons! D'oh!
This is going to be a fun week. :P
Basically, everything is broken but that's how we roll. I'd rather have a less than perfect site up than nothing.
More updates will be posted tomorrow.
Simon, it's good to see you here! You are the king of the forum. We need you and we're so glad you're here.
Once the site is in a decent state, I don't plan on hanging around too much.
I need to write a script that clears out incomplete sign-ups. So, don't be surprised if you see a dip from the current number which is 1201.
Oh, and I've just realised that we don't have favicons! D'oh!
This is going to be a fun week. :P
Basically, everything is broken but that's how we roll. I'd rather have a less than perfect site up than nothing.
More updates will be posted tomorrow.
Simon, it's good to see you here! You are the king of the forum. We need you and we're so glad you're here.
Once the site is in a decent state, I don't plan on hanging around too much.
3 months ago
#5
Thanks DC,
I appreciate the kind words.
The site is noticeably much faster and responsive - great work on getting TGv2 200%+ faster than TGv1 👍
If you need a hand with anything, let me know.
Cheers,
Si
I appreciate the kind words.
The site is noticeably much faster and responsive - great work on getting TGv2 200%+ faster than TGv1 👍
If you need a hand with anything, let me know.
Cheers,
Si
3 months ago
#6
Thanks for that.
I have switched off the Cloudflare thing. If I put it back on then I think we could get this site going much faster.
However, I'm not sure how I feel about Cloudflare these days. I noticed we had a lot of misfired pages with Cloudflare. There may or may not be other issues with Cloudflare. So, I don't know. Maybe this is the way to go. Just honest, shared hosting. I wonder what you think.
I hope we can set up a video call shortly (whenever you have time).
Cheers!
I have switched off the Cloudflare thing. If I put it back on then I think we could get this site going much faster.
However, I'm not sure how I feel about Cloudflare these days. I noticed we had a lot of misfired pages with Cloudflare. There may or may not be other issues with Cloudflare. So, I don't know. Maybe this is the way to go. Just honest, shared hosting. I wonder what you think.
I hope we can set up a video call shortly (whenever you have time).
Cheers!
3 months ago
#7
TUESDAY UPDATE
Just as a reminder, the site has just launched and is very much in a far-from-finished state. So, I am going to post these daily updates - every day - until everything is complete and ready.
WHAT WAS DONE TODAY
It does not sound like much, but I have proof-read the first three chapters of the documentation. I have also added a new 'Essays' section to the homepage.
The 'Essays' part of this website is going to be extremely important. When you build a framework that is radically different from everything else, you do - unfortunately - attract a great deal of pushback. That is fine. People are free to say whatever they like.
However, when comments are made that are demonstrably false and/or designed to mislead, we need a mechanism for responding in a calm and (hopefully!) graceful manner.
For example, the other day someone on YouTube suggested that Trongate might be suitable only for small and medium - sized projects because, after all, it is a small framework.
These are the kinds of erroneous claims that we will have to deal with constantly.
Whether or not that comment was intended to be rude is not important. What is important is that we have a fair opportunity to clear up misconceptions whenever they appear. Let me stress - people absolutely have the right to say whatever they like - and that is a good thing. However, we also have the right to respond.
So, the 'Essays' section is not about attacking other frameworks or other people. It is simply a place where we can set the record straight on matters relating to the framework, PHP, or web development more generally.
WHAT'S COMING UP
I am aware that we don't have a search engine (yet!) and we also have one or two missing pages. However, the priority - for now - has to be making the documentation perfect. If we don't have great documentation then we don't have a framework.
So, I fully intend on pushing forward with more documentation proof-reading tomorrow. I'll send another update tomorrow.
I'm about to record the first Trongate v2 tutorial for YouTube. Feels good to be putting out meaningful content again.
See you tomorrow.
DC
PS - We have a YouTube channel. If anybody wishes to record content for the YouTube channel (tutorials or whatever) then you're welcome. Same goes for essays.
Just as a reminder, the site has just launched and is very much in a far-from-finished state. So, I am going to post these daily updates - every day - until everything is complete and ready.
WHAT WAS DONE TODAY
It does not sound like much, but I have proof-read the first three chapters of the documentation. I have also added a new 'Essays' section to the homepage.
The 'Essays' part of this website is going to be extremely important. When you build a framework that is radically different from everything else, you do - unfortunately - attract a great deal of pushback. That is fine. People are free to say whatever they like.
However, when comments are made that are demonstrably false and/or designed to mislead, we need a mechanism for responding in a calm and (hopefully!) graceful manner.
For example, the other day someone on YouTube suggested that Trongate might be suitable only for small and medium - sized projects because, after all, it is a small framework.
These are the kinds of erroneous claims that we will have to deal with constantly.
Whether or not that comment was intended to be rude is not important. What is important is that we have a fair opportunity to clear up misconceptions whenever they appear. Let me stress - people absolutely have the right to say whatever they like - and that is a good thing. However, we also have the right to respond.
So, the 'Essays' section is not about attacking other frameworks or other people. It is simply a place where we can set the record straight on matters relating to the framework, PHP, or web development more generally.
WHAT'S COMING UP
I am aware that we don't have a search engine (yet!) and we also have one or two missing pages. However, the priority - for now - has to be making the documentation perfect. If we don't have great documentation then we don't have a framework.
So, I fully intend on pushing forward with more documentation proof-reading tomorrow. I'll send another update tomorrow.
I'm about to record the first Trongate v2 tutorial for YouTube. Feels good to be putting out meaningful content again.
See you tomorrow.
DC
PS - We have a YouTube channel. If anybody wishes to record content for the YouTube channel (tutorials or whatever) then you're welcome. Same goes for essays.
3 months ago
#8
Okay, so here we go with another website status update. I'm not sure if anyone is even reading this, so at this point, I'll treat it as a sort of personal diary.
We still don't have search features built, and I'm aware of a few other things about this website that require work.
However, for the moment, the focus has to be on making the documentation perfect.
The good news is that I've now completed up to and including the "Module Fundamentals" chapter - which was a really important chapter.
To my horror, I discovered that I have to rewrite loads of documentation pages. This is because we've now moved to a more AI-friendly syntax, and it turns out that was a very recent decision.
So, I'm having to go through loads of examples and tweak them. For example, table names have to be actively declared when working with the database. Variables that are being read from the URL also have to be actively declared, instead of being 'assumed by the framework'. All of this takes time. It's a very slow process, but I have no choice but to keep going.
By the way, AI is turning out to be pretty useless at writing docs - just so you know.
I'm really bothered by the fact that there's no ability to post links on this forum, nor any ability to make text bold or format things nicely. I'd love to change that soon.
The "Interceptors" page has been completely rewritten, and there is now a downloadable example from GitHub.
Finally, we had a beautiful day or two when Cloudflare was switched off and the website was working fabulously. This morning, I noticed one of those "Cloudflare fail" pages that shows up from time to time. I looked into it, and it seems Cloudflare decided to switch itself back on (I presume this happened yesterday).
Let me be blunt: I don't see any benefits from using Cloudflare at all. I don't think it makes the site faster, and I think it's just a point of potential failure. Maybe some day we can test that.
Eye of the tiger.
We still don't have search features built, and I'm aware of a few other things about this website that require work.
However, for the moment, the focus has to be on making the documentation perfect.
The good news is that I've now completed up to and including the "Module Fundamentals" chapter - which was a really important chapter.
To my horror, I discovered that I have to rewrite loads of documentation pages. This is because we've now moved to a more AI-friendly syntax, and it turns out that was a very recent decision.
So, I'm having to go through loads of examples and tweak them. For example, table names have to be actively declared when working with the database. Variables that are being read from the URL also have to be actively declared, instead of being 'assumed by the framework'. All of this takes time. It's a very slow process, but I have no choice but to keep going.
By the way, AI is turning out to be pretty useless at writing docs - just so you know.
I'm really bothered by the fact that there's no ability to post links on this forum, nor any ability to make text bold or format things nicely. I'd love to change that soon.
The "Interceptors" page has been completely rewritten, and there is now a downloadable example from GitHub.
Finally, we had a beautiful day or two when Cloudflare was switched off and the website was working fabulously. This morning, I noticed one of those "Cloudflare fail" pages that shows up from time to time. I looked into it, and it seems Cloudflare decided to switch itself back on (I presume this happened yesterday).
Let me be blunt: I don't see any benefits from using Cloudflare at all. I don't think it makes the site faster, and I think it's just a point of potential failure. Maybe some day we can test that.
Eye of the tiger.