form for building a page and HTML images

Importing Word docs into WP seems to be fraught with problems. I believe there are plugins that purport to do this, but I’m skeptical they do it well in all situations. But if you can find one that works for your specific situation, then you’re in luck!

IMO you’re probably better off going the other direction. Build a document page within WP, which then results in a HTML page. That could then be exported to Word and made into a PDF much more reliably. Of course the problem then is the WP editor is miles different than Word. People used to editing in Word will likely despise the WP editor. No one likes change.

But the big advantage is if the documents exist first as WP pages, the archive page you linked to could be auto-generated based on what document pages exist in the WP database. No one needs to update it, it would be dynamically generated.

I would have to check with the rest of the team on how things are currently done. Right now, I’m on our Communications Committee, which is who manages the website. Newsline is a separate committee, and I’m really not sure what their process is. What they ultimately come out with is a Word document, a PDF file, an HTML document that apparently doesn’t contain images, and an audio version. With the likely exception of the audio, would the plugins you reference be able to keep our archive page up to date? That’s another issue we are having, nobody likes to edit the page where all of these issues are linked from, which is also the page I linked to in this thread.

Once a document becomes a WP post, regardless of how it got there, whether entered in through the WP editor or imported via plugin, the archive page can be auto-generated without anyone needing to regularly update it. In fact, WP does this as its default state. It lists all posts, 10 per page, in reverse chronological order. Of course there can be endless variations on this. “Posts” needn’t be literal blog posts, they could be newsletters, product info, etc. WP posts are better thought of as generic data containers into which you can insert any sort of information.

Okay, I see where you’re going with this. That’s not exactly what I was getting at though. Have you looked at what we currently have on the page I linked to in this thread? If possible, we would like to keep that layout, but we’re also in need of a solution that would make that page easier to update. Also, I’m a bit confused as to how you envision where the links to the Word, PDF, and audio versions go in this scenario.

Your current layout is fine for an automated archive page, except it’d need to be custom built. I doubt you’f find a theme that’s a perfect match. However you could save time by starting with a theme that’s close and customizing it further.

My thinking for an automated archive page would mainly apply to articles either created in WP or imported as some sort of post type. But related files could be managed if WP has appropriate data to work from so the template code can generate the proper links. One possibility would be to upload such files into WP while making their related attachment posts children of the main article. In case you were not aware, all media uploaded into WP have an “attachment” post type generated for it which contains useful data like its URL, MIME type, etc. Attachment posts have a “parent” field which is used to relate the attachment to a specific post.

When the template code is outputting the list of articles, it could query for any child attachments with specific MIME types and also list any that are found. So while the archive is automated, there would need to be some manual effort to relate files to articles. However most users would find this process much more relatable than manually editing a .html file.