The goal
Before the content is there, the website is nothing. As the content importer, you are preparing the site for client QA. Please pay close attention to capitalization, spacing, and spelling while editing content. Don’t worry about copy edits for now, but just make notes so that the client is aware.
Requirements
Before diving in, take some time to familiarize yourself with the website’s layout and intended tone. You can do this by:
- Reviewing the Style Guide: Our style guide lays the foundation for a consistent and cohesive online voice. Refer to the guide often to ensure proper tone, formatting, and grammar. You can find the style guide here: [insert link or location].
- Exploring Clickable Mockups: Design team will provide clickable mockups showcasing how content should be laid out. Carefully review these mockups to understand the intended presentation of each content piece.
- Website Tutorial: Dev team will provide a tutorial of the blocks and how to add content to the website. They will highlight anything unique to the site.
From the client you should have…
- Written content
- Links
- Photos or approved stock images.
How to Import Content
Image Perfect
Images play a vital role in engaging users. However, proper sizing is crucial. Learn the appropriate image dimensions for different areas of the website. For resizing, utilize Figma, Photoshop, or another tool you are comfortable with
Video
Never directly upload a full video! Instead, request a YouTube or Vimeo link from the client. This ensures efficient loading and smooth user experience.
Buttons
Remember, buttons aren’t just labels. Always link them to the appropriate destination, guiding users seamlessly through the website.
Heading Hierarchy
Headings (H1 – H6) structure your content for readability and impact. Learn when to use each heading level to create a logical flow and guide users effectively.
Written Content
Most of the time, content will be coming from either the client’s current website or a Google folder structure that contains all the content and sitemap. Your goal is to build out pages within WordPress (using all the blocks created) that contain all the client’s requested content.
Each page in the sitemap should have a Page within the website. Keep in mind the hierarchy: If a page is “under” another page, make sure you are setting the appropriate Parent Page within WordPress.
As you are going through the sitemap and building pages, make notes of things as you go:
- If a page feels empty with the content that has been provided (go ahead and fill out the page with some dummy content – lipsum.com is a good bet), build out some structures you feel would make sense for that page with dummy content. Make a note of that page to make sure the client knows to go back and give us more content
- If a block isn’t acting like it should, don’t try and force it. Do what you feel is correct, make a note for the developer, and move on. A good example of this is if you are working with a custom block and you upload an image to a field called Background Image. When you view the website, that image doesn’t show up. Rather than trying to use other blocks to “recreate” the look you’re going for, just upload the image into the appropriate field, make a note of it, and move on.
- If you had to alter the content that a client gave us to make it “fit” appropriately, make a note of that page and what you did. We always want to make sure we notate any change so we can make both our team and the client aware of it.
- If we’re missing any images/documents/links/etc, make a note of the URL of the page it is on and what we are missing. You should have a running list of all missing content pieces so we can deliver it to the client in a single document.
Completion requirements
- The website is clickable and any missing links are documented.
- All images and content have been imported, and anything missing/wrong/changed has been documented.
- Loom video to show completion and the link should be in your documentation.
- Project manager has been sent your documentation and has been notified that the site is ready for internal QA.