This is running well and doing the job. WF implementation will be handled in T891.

This is supported on the backend now, and enabled on the #fight_back_news blog. a user-facing interface for this will be addressed in T889.

On Apr 23 2021 at 9:20 PM, Colby Russell wrote:

Taking this; related to existing work to eliminate references to "static pages" in user-facing docs, etc., in favor of "pinned pages". I should have something to show for this (in terms of changes) next week.

Deployed

Deploying on Write.as soon; WriteFreely PR is here: #531.

This is pretty easy to tackle.

Just deployed on Write.as, and seems to be running smoothly. The real test will be tonight through tomorrow morning, when we see our normal influx of traffic.

This is more important on Write.as now, especially with replica MySQL databases that have become increasingly laggy.

@heyakyra Yep, we can do that. Was thinking that might be a future task and we would hard-code the term for now, but we can probably make it customizable out of the gate.

Can the /posts be customizable too, so it would be /{custom subpath}/{slug} this way we could call ours articles, and other publishers might call them chapters, stories, etc

Re. T879: we'll need to track that a certain blog post is a reply to another.

As suggested on the forum, we should also add an API endpoint for this.

Internal support for this is finished on Write.as Web, and will be deployed soon.

Perhaps we can unite this implementation with T497: Support pinning hashtags.

Perhaps we can unite this implementation with T599: Pin external URLs to navigation.

High-level implementation ideas so far: https://micro.baer.works/working-on-support-for-categories-phabricator-write-as-t809-today

Still to do:

We won't include a way for users to set an author in the plain text editor for now. Everything else is complete.