1002889 - Port bugzilla.org static content over to WordPress

Status: RESOLVED WONTFIX

(Bugzilla :: bugzilla.org, defect)

Description

[Mark Côté [:mcote]]

Once we have the Word Press site up, we need to port all static content from bugzilla.org over, that is, everything except the installation list ("Who Uses Bugzilla?") and the paid support list.

Comment 1

[techmessiah]

A few things I need -

1. What do I do with Releases and Security Advisories? There are a lot of them, and I need to know how important they are. Can I copy over the most recent ones and upload the older ones as html files into WP (or same place as Documentation. See #2)? I can indeed port them all over into WP posts, I just want to make sure I'm not spending time on old, rarely viewed content that could be handled differently.

2. Documentation: These folders need to be hosted somewhere for me to link to them. They have specific css/images/supporting files and cannot just be uploaded into WP. 

3. The menu on the default Moz theme is awful. See exhibit A: http://wpms.mozilla-community.org/bugzilla/ I need access to other themes and/or this theme needs to be fixed. I can also use Twenty Fourteen, but it doesn't really fit.

4. What do you want me to do about the https setting in WP? Do I check it for all pages?

Thanks!

Comment 2

[Logan Rosen [:Logan]]

Reassigning the needinfo to Tanner, as he is stepping in for me for a few months while I'm busy.

Comment 3

[Mark Côté [:mcote]]

Going to needinfo :justdave on the first point.  Also CCing other Bugzilla officials.

To clarify the second point, we're wondering if there's some space somewhere for static files to be served and linked to from WP, since they won't fit into WP neatly.

Comment 4

[Simon Green]

Can't the docs be linked to readthedocs?

Comment 5

[David Lawrence [:dkl]]

(In reply to Simon Green from comment #4)
> Can't the docs be linked to readthedocs?

That is only for 5.0+. We need to be able to host the static HTML for the 4.4 and earlier docs we currently have.

(In reply to techmessiah from comment #1)
> 1. What do I do with Releases and Security Advisories? There are a lot of
> them, and I need to know how important they are. Can I copy over the most
> recent ones and upload the older ones as html files into WP (or same place
> as Documentation. See #2)? I can indeed port them all over into WP posts, I
> just want to make sure I'm not spending time on old, rarely viewed content
> that could be handled differently.

We need them all to be available for reference somehow. They don't necessarily
need to be actual posts (just maybe the last year or so can be) but need to be
easily accessible.

> 2. Documentation: These folders need to be hosted somewhere for me to link
> to them. They have specific css/images/supporting files and cannot just be
> uploaded into WP. 

Above comment.

dkl

Comment 6

[:glob ✱]

a primary use-case for all the old release notes is they are required reading when upgrading old versions of bugzilla -- the process is basically "read every relnote between your version and the one you're upgrading to".

Comment 7

[tad]

For any static content, we can upload it to our CDN partner, MaxCDN. Are you okay with adding a "This content is hosted at MaxCDN" link to the bottom of stuff (I can handle it), just a small link. They provide us with free usage, so it's nice to add a link as much as we can.

Comment 8

[Tanner Filip [:tanner]]

(In reply to techmessiah from comment #1)
> 2. Documentation: These folders need to be hosted somewhere for me to link
> to them. They have specific css/images/supporting files and cannot just be
> uploaded into WP. 

I'm trying to work out the best way to do this. My current thought is to just have a bucket on S3 and serve from there, but I'm not sure if that's the best way. Another thing we could do is host on MaxCDN, we have a sponsored unlimited account there, so that may be better than paying to use S3.

> 
> 3. The menu on the default Moz theme is awful. See exhibit A:
> http://wpms.mozilla-community.org/bugzilla/ I need access to other themes
> and/or this theme needs to be fixed. I can also use Twenty Fourteen, but it
> doesn't really fit.

Not quite sure what to do about this one... The source is at https://github.com/mozilla/One-Mozilla-blog/, so we can always hack on that if needed. 

> 
> 4. What do you want me to do about the https setting in WP? Do I check it
> for all pages?

Unless bugzilla.org has its own SSL certificate, no. You'll always login from wpms.mozilla-community.org.

Comment 9

[Mark Côté [:mcote]]

Curious if you have any further thoughts on S3 vs MaxCDN.

Also, could we use our own theme?  Probably easier than trying to fix the weirdness in the current one.

Comment 10

[tad]

Not to speak for Tanner, but MaxCDN is likely the best option here.

You can use your own theme, but we will need to test the theme in a dev environment beforehand, and if using MaxCDN, we will want to add a footer link, no different to anything else in the site stating that the site is "Accelerated by MaxCDN". Mozilla Branding are okay with this, just up to you.

Comment 11

[Tanner Filip [:tanner]]

What :tad said.

Comment 12

[techmessiah]

I think I found a theme that might work. Can we get "Decode"
By ScottSmith installed? It's super simple.

MaxCDN sure - Will I have ftp access?

Comment 13

[David Weir (satdav)]

I am willing to help with moving the code over to wordpress 

for the docs maybe even move them to the wiki

Comment 14

[Mark Côté [:mcote]]

We have a contributor working on this; she's just waiting for some answers to questions in comment 12.

Comment 15

[matthew zeier [:mrz]]

Let's pause for a bit. I'm not convinced MaxCDN is the right solution. Currently discussing the appropriate Wordpress Multisite architecture as it pertains to Amazon. Integration into Amazon primitives such as S3 & Cloudfront might be a better approach (and as such you can have access to the S3 bucket if needed).

Comment 16

[Tanner Filip [:tanner]]

I've received almost no status updates on WPMS in several weeks, so I'm not sure what the status of this is. Tad would know better than I would.

Comment 17

[tad]

WPMS works.

Using Cloudfront instead of MaxCDN.

I'd suggest we can start doing this.

Let's open a community it bug, I'll do that. You can use this bug for moving your content, we'll implement our bit in another bug :)

Comment 18

[matthew zeier [:mrz]]

(In reply to Tanner Filip [:tanner] from comment #16)
> I've received almost no status updates on WPMS in several weeks, so I'm not


@tanner - are you able to join the Monday meeting? That's where we've been talking about WPMS and providing updates. Meeting notes are also online.

Comment 19

[Gervase Markham [:gerv]]

Justdave added a relevant comment to bug 891260.

Gerv

Comment 20

[Gervase Markham [:gerv]]

It looks like Community IT are no longer setting up WPMS (bug 971411 comment 6).

So what do we do now?

Gerv

Comment 21

[Mark Côté [:mcote]]

We have our own WordPress; I was just thinking yesterday that apparently we didn't announce it anywhere: https://bugzilla.mofostaging.net/

Still very much in progress.

Comment 22

[tad]

WPMS isn't happening, but a wordpress solution will be available

We're looking into a managed hosting solution that can power every type of site, should hopefully have final details on what we're doing in early May

Comment 23

[matthew zeier [:mrz]]

(In reply to Gervase Markham [:gerv] from comment #20)
> It looks like Community IT are no longer setting up WPMS (bug 971411 comment
> 6).
> 
> So what do we do now?


Just to clarify, Wordpress Multisite isn't the current direction.

We are, however, looking at a Wordpress-as-a-Service. https://wiki.mozilla.org/IT/Community/WG/WordpressMS has some information on one idea (the other being a hosted service like Rackspace Cloud Sites).

Comment 24

[Dave Miller [:justdave]]

The last few comments seem to have overlapped with each other and don't quite all line up.

Comment 21 has accurate current status. The underlying modules needed to accomplish our custom pages are all in place, we just need the content migrated at this point.  There was a short effort to start migrating content but it stalled and hasn't been touched in several months.  This doesn't cover the docs...  we could probably host the older versions of the docs on landfill and provide redirects if we had to.

Comment 25

[Gervase Markham [:gerv]]

(In reply to Dave Miller [:justdave] ([e-mail]) from comment #24)
> The last few comments seem to have overlapped with each other and don't
> quite all line up.
> 
> Comment 21 has accurate current status. The underlying modules needed to
> accomplish our custom pages are all in place, we just need the content
> migrated at this point.  

justdave: can you elaborate more on what that means? How do we migrate content? Does it mean creating new pages by hand on the staging Wordpress instance and copying the content in? How will data make it from the staging Wordpress to the production one? Is there any more automated way of creating a lot of pages on a Wordpress? 

> There was a short effort to start migrating content
> but it stalled and hasn't been touched in several months.

Who was doing that?

> This doesn't
> cover the docs...  we could probably host the older versions of the docs on
> landfill and provide redirects if we had to.

That sounds like a reasonable solution if it is hard to just upload a directory of HTML files and say "serve this".
Gerv

Comment 26

[Gervase Markham [:gerv]]

justdave: can you provide updated status here? https://bugzilla.mofostaging.net/ seems to have disappeared. It would be good to move to something more maintainable, even if it's only Github Pages.

Gerv

Comment 27

[Dylan Hardison [:dylan] (he/him)]

Since the current site is static, we could just serve it as a github page. Updating it would look like:

checkout repo
build content locally
commit built content to gh-pages branch.

Comment 28

[Gervase Markham [:gerv]]

We could do that, but it would be nice to ditch the existing website build system in favour of something more standard, flexible and extensible.

Gerv

Comment 29

[Gervase Markham [:gerv]]

We're going for Github Pages instead - see http://bugzilla.github.io/ .

Gerv