opentype

I can’t speak for IPS, but it’s still safe to say that this is extremely unlikely.
The people with coding skills don’t need it. They can just open the respective page, inspect the actual HTML and learn everything they need from it. It’s all public and there for everyone to see. 
The people who don’t have these skills, can’t do much with such a tutorial. They would just have to copy code they don’t understand. If they make the slightest mistake, everything breaks and now someone has to give free support for the tutorial. Who is willing to do that? If the user wants just a tiny variation of the template, they would have no idea how to do it. So again, they would ask for free support. Not to mention that such custom Pages templates correspond to Pages database fields and possibly CSS and JS files. If they don’t exist as expected, again, everything breaks. It just doesn’t work. I’ve created an entire online course around learning Pages, but it does not contain teaching people how to create templates from scratch. That’s just not a suitable topic for a tutorial. Either you know how to do it or you can get stock or custom products which deliver the needed functionality. There really is no middle ground. 

In that spirit: Reddit is a company with 2000 employees, IPS has less than 20. That makes a difference in what they can create. We should not lie to ourselves.

Yes, the IPS Help Guide section describes the general usage of these Pages databases. 
But the necessary customization of the templates needs experience with HTML/CSS and time to learn how the IPS design framework works. No tutorial can easily teach that. 

Yes, the IPS Help Guide section describes the general usage of these Pages databases. 
But the necessary customization of the templates needs experience with HTML/CSS and time to learn how the IPS design framework works. No tutorial can easily teach that. 

There is nothing Invision-Community-specific about such a move. You just:
put the site in offline mode export the files and upload to new server export the MySQL database and import it on the new server test the website with its server IP/domain when everything works again, put installation online and initiate the domain transfer  
Optional, but recommended:
Perform a trial transfer with step 2 to 4 just to make sure everything CAN work on the new server and that the export and import are processed correctly. Watch out for problems with character sets (database) or file permission errors (file system).  Change the DNS settings on the current domain and set a short TTL time. This will speed up the domain transfer. 

In that spirit: Reddit is a company with 2000 employees, IPS has less than 20. That makes a difference in what they can create. We should not lie to ourselves.

I had a user report and can replicate this easily. I appears at least with the combination of Firefox (mobile and desktop) and Cloudflare with guest caching. 
Visit site without stored cookies Cookie bar appears Click Accept or Reject Site shows an error (2S119/1) and URL changes to mysite.com/cookies/?do=cookieConsent I guess it has something to do with the CSFR key being cached and used for multiple users, but I have no idea how to fix this without turning off guest caching altogether. 

We've got an open bug report for this, it will be addressed in a future release.

A Pages block doesn’t take a full HTML page and it should have a better identifier than just “table”. Nathan’s code fixes those things. 
But how is the data fed into the table anyway? If it takes hard-coded data in the block, I wouldn’t want to use JavaScript on the visitor’s site to make those calculations. 

Yeah, you have to have a product ready to be linked to from a file. 

So, it might be a bit more complicated than you hoped for, but it is a native way that does what you want. Instead of selling in Downloads, you push it all to Commerce. 

Yes, but that’s also an advantage as you get a proper shopping cart, custom fields, renewals, pricing options and whatever else is possible in Commerce. 
You can still have the users browse the Downloads section if you want. 

Spotted that there are some x.com/ URLs now appearing for the normal tweet links - as a result, oembed will fail and they'll be links.
'twitter.com' => array( 'https://publish.twitter.com/oembed', static::EMBED_TWEET ), 'mobile.twitter.com' => array( 'https://publish.twitter.com/oembed', static::EMBED_TWEET ), Tested and adding x.com equivalents of the above to oembedServices in \IPS\Text\Parser will sort it out.
'x.com' => array( 'https://publish.x.com/oembed', static::EMBED_TWEET ), 'x.twitter.com' => array( 'https://publish.x.com/oembed', static::EMBED_TWEET ),  

I do that with linked Commerce products. So the user is buying a Commerce product which has the group update and then the Download file links to the Commerce product, so the customer can also download the file. 

Most cloud packages can already use external uploads outside of marketplace. We'll remove the limitation for the others.

I have that option for years through a third-party solution. Get ready to be insulted. 😉 People who leave a community in anger (e.g. after moderator actions) will love the opportunity vent their anger one last time, blaming and insulting you. I can’t remember a single time a text-based option to give reasons to delete an account was actually useful. If anything, I would suggest a checkbox list with admin-defined options. 

Then just start it yourself and we will see if it will work. 

You can add meta tags using the meta tag editor. That works globally, not just for custom pages. 
Regarding <head> content, you can choose to use the suite wrapper or not (see the option in your screenshot). If you do, you use the <head> from the suite without changes, if you turn that off, you can and have to create your own <head>. 

You can add meta tags using the meta tag editor. That works globally, not just for custom pages. 
Regarding <head> content, you can choose to use the suite wrapper or not (see the option in your screenshot). If you do, you use the <head> from the suite without changes, if you turn that off, you can and have to create your own <head>. 

You can add meta tags using the meta tag editor. That works globally, not just for custom pages. 
Regarding <head> content, you can choose to use the suite wrapper or not (see the option in your screenshot). If you do, you use the <head> from the suite without changes, if you turn that off, you can and have to create your own <head>. 

Everything new and recent comes together on the /discover/ page. 
And users have the choice to create a custom version of that page using the “Create New Stream" button:

That’s the native and the best way.
It would be possible to create a “dashboard page” with the Pages app and blocks put on it, but then there will be caching issues and users would not be able to customize it. I wouldn’t recommend it.  

Then just start it yourself and we will see if it will work. 

You can still just create a forum or Pages database called “Support Tickets” and use this mode if you need privacy:

You can still just create a forum or Pages database called “Support Tickets” and use this mode if you need privacy:

You can still just create a forum or Pages database called “Support Tickets” and use this mode if you need privacy:

You can still just create a forum or Pages database called “Support Tickets” and use this mode if you need privacy: