Build a Blog Using Django, GraphQL, and Vue – Real Python

Install Django

Now you’re ready to start building the Django application. To separate the dependencies for this project from your other projects, create a virtual environment in which you’ll install your project’s requirements.

In your terminal, make sure that you’re inside the back_end/ folder you just created. Then, select your operating system below and use your platform-specific command to set up a virtual environment:

With the above commands, you create and activate a virtual environment named venv by using Python’s built-in venv module. The parenthetical (venv) in front of the prompt indicates that you’ve successfully activated the virtual environment.

Now that you have a virtual environment in which to install requirements, create a requirements.txt file in the back_end/ directory and define the first requirement you’ll need:

Once you’ve created the requirements.txt file, use it to install Django:

Now, you’re ready to start creating your Django project.

Create the Django Project

Now that Django is installed, use the django-admin command to initialize your Django project:

Don’t forget to add the dot (.) at the end of the command above.
The dot prevents Django from creating a nested project directory for your backend project.

At this point, your project directory structure should now look like this:

dvg/
└── back_end/
    ├── manage.py
    ├── requirements.txt
    └── backend/
        ├── __init__.py
        ├── asgi.py
        ├── settings.py
        ├── urls.py
        └── wsgi.py

In your dvg/ project root, there is a back_end/ folder that contains your Django project. Inside back_end/ there is a backend/ folder, a manage.py file, and the requirements.txt file. Not shown in the directory tree above is the venv/ folder for your virtual environment.

Run Django Migrations

Before you add anything specific to your application, it’s time to run Django’s initial migrations. If you haven’t dealt with migrations before, then check out Django Migrations: A Primer. Run the migrations with the migrate management command:

You should see a long list of migrations, each with an OK after it:

Running the Django migrations will also create an SQLite file named db.sqlite3. This is the database of your project. As the name suggests, it’ll store the data for your project. All the blog posts you’ll create during the tutorial will be saved in this file.

Create a Superuser

Now that you have the database, you can create a superuser. You’ll need this user so you can eventually log in to the Django admin interface. Use the createsuperuser management command to create one:

Running the createsuperuser management command prompts you to choose a username, provide an email address, and set a password. Use your own data for these fields and make sure to remember them. You’ll need these credentials to log in to the Django admin interface in a moment.

Step 1 Summary

Now that you’ve installed Django, created the Django project, run the Django migrations, and created a superuser, you have a fully functioning Django application. You should now be able to start the Django development server and view it in your browser. Start the server using the runserver management command, which will listen to port 8000 by default:

Next, visit http://localhost:8000 in your browser. You should see the Django splash page, indicating that the installation worked successfully:

You should also be able to visit http://localhost:8000/admin, where you’ll see a login form:

Use the username and password you made for your superuser to log in to the Django admin. If everything’s working, then you’ll be taken to the Django admin interface. This page will be pretty bare for the moment, but you’ll make it much more interesting in the next step.

Create the Django Blog Application

Keep in mind that a single Django project can contain many Django applications. You should separate your blog-specific behavior into its own Django application so that it remains distinct from any future applications you build into your project. Create the application using the startapp management command:

This will create a blog/ directory with several files, similar to the ones you already have in backend/:

dvg/
└── back_end/
    ├── manage.py
    ├── requirements.txt
    ├── db.sqlite3
    ├── backend/
    │    └── ...
    └── blog/
        ├── __init__.py
        ├── admin.py
        ├── apps.py
        ├── migrations/
        │   └── __init__.py
        ├── models.py
        ├── tests.py
        └── views.py

You’ll make changes and additions to some of these files later in this tutorial. First, you need to make some adjustments in the backend/ project app.

Enable the Django Blog Application

Creating a Django application doesn’t make it available in your project by default. To make sure the project knows about your new blog application, you’ll need to add it to the list of installed applications. Update the INSTALLED_APPS variable in backend/settings.py:

Adding "blog" to the INSTALLED_APPS list is sufficient to let Django know about the app. When you explicitly point to the configuration class of your app, then INSTALLED_APPS will help Django discover information about your application, such as the data models and URL patterns it may contain.

Create the Django Blog Data Models

Now that Django can discover your blog application, you can create the data models. You’ll create three models to start:

1. Profile stores additional information about blog users.
2. Tag represents a category in which blog posts can be grouped.
3. Post stores the content and metadata of each blog post.

You’ll add each of these models to blog/models.py. Each of your models will inherit from Django’s models.Model class.

Create the Model Admin Configuration

Now that your models are in place, you’ll need to tell Django how they should be displayed in the admin interface. In blog/admin.py, start by importing Django’s admin module and your models:

Then, create and register the admin classes for Profile and Tag, which only need the model specified:

Just like the model, the admin class for Post is more involved. Posts contain a lot of information, so it helps to be more judicious about what information you display to avoid crowding the interface:

To make browsing and editing posts more fluid, you customize a post’s details with these special variables:

• list_display: Only show the specific information about each post.
• list_filter: Allow filtering the post list by posts that are published or unpublished, and by publish date.
• list_editable: Allow editing of all the displayed fields, with the exception of the ID.
• search_fields: Allow searching for posts using the title, subtitle, slug, and body.
• prepopulated_fields: Prepopulate the slug field using the title and subtitle fields.
• date_hierarchy: Use the publish date of all posts to create a browsable date hierarchy.
• save_on_top: Show a button at the top of the list to save changes.

You can read more about all the options the Django admin has to offer in Customize the Django Admin With Python.

Create the Model Migrations

Django has all the information it needs to administer and persist your blog content, but you’ll need to update the database to support these changes. Earlier in this tutorial, you ran Django’s migrations for its built-in models. Now, you’ll create and run migrations for your models.

First, create the migrations using the makemigrations management command:

This creates a migration whose name is 0001_initial.py by default. Run this migration using the migrate management command:

You now have all of your data models in place, and you’ve configured the Django admin so that you can add and edit those models.

Start Blogging

Start the Django development server again if you stopped it before to run the migrations. Then, visit the admin interface at http://localhost:8000/admin, and explore what’s changed.

You should see links to the list of tags, profiles, and posts, as well as links to add or edit each of them. Try to add your own posts now and edit a few to see how the admin interface responds:

Before you continue with the next steps, you should have around three blog posts saved in your blog. Make sure that you also have a few tags attached to them.

Step 2 Summary

At this point, you’ve completed enough of the back end that you could decide to go headlong in the Django direction. You could use Django’s URL routing and templating engine to build pages that would show all the post content you create in the admin to readers.

Instead, you’ll wrap the back end you’ve created in a GraphQL API so you can eventually consume it from the browser and provide a richer client-side experience.

Install Graphene-Django

To get started with Graphene-Django, first add it to your project’s requirements file:

Then install it using the updated requirements file:

Add "graphene_django" to the INSTALLED_APPS variable in your project’s settings.py module so Django will find it:

After installing third party Django apps like Graphene-Django with pip, you need to add it to your project by listing it in your INSTALLED_APPS. Now that Django knows about "graphene_django", you’ve got some configuration to do.

Configure Graphene-Django

To get Graphene-Django working in your project, you’ll need to configure a few pieces:

1. Update settings.py so the project knows where to look for GraphQL information.
2. Add a URL pattern to serve the GraphQL API and GraphiQL, GraphQL’s explorable interface.
3. Create the GraphQL schema so Graphene-Django knows how to translate your models into GraphQL.

Step 3 Summary

You’ve fleshed out your blog’s data model, and now you’ve also wrapped your data model with Graphene-Django to serve that data as a GraphQL API.

Run the Django development server and visit http://localhost:8000/graphql:

You should see the GraphiQL interface with some commented text that explains how to use the tool.

Expand the Docs section in the top left of the screen and click query: Query. You should see each of the queries and types that you configured in your schema:

If you haven’t created any test blog content yet, do so now. Try the following query, which should return a list of all the posts you’ve created:

The response should return a list of posts. The structure of each post should match the shape of the query, like in the following example:

The response you get should match the posts that you created so far.
If you’ve saved some posts and see them in the response, then you’re ready to continue on.

First, add django-cors-headers to your requirements file:

Then install it using the updated requirements file:

Add "corsheaders" to the INSTALLED_APPS list in your project’s settings.py module:

Stay in settings.py and add "corsheaders.middleware.CorsMiddleware" to the beginning of the MIDDLEWARE list:

The django-cors-headers documentation suggests putting the middleware as early in the MIDDLEWARE list as possible. If you don’t want to put the CORS middleware at the very top of the list, then you need to at least make sure to put it before Django’s CommonMiddleware.

CORS exists for a good reason. You don’t want to expose your application so it can be used from anywhere on the Internet. To define how much you want to open up the GraphQL API, you must use one of these three settings:

1. CORS_ALLOWED_ORIGINS: A list of domains from which your Django application will allow requests.
2. CORS_ALLOWED_ORIGIN_REGEXES: A list of regular expressions that match domains from which to allow requests.
3. CORS_ALLOW_ALL_ORIGINS: A Boolean value that defines whether Django should be all open or all closed by default.

For this project, CORS_ALLOWED_ORIGINS is sufficient.
Add the following settings to settings.py:

This setting will allow requests only from your front end, which you’ll create later and which will run on port 5173 locally.

Step 4 Summary

Congratulations, you’ve completed the back end of your blog! You have a working data model, a working admin interface, a working GraphQL API that you can explore using GraphiQL, and the ability to query the API from the front end you’ll build next. This is a great place to pause if you haven’t taken a break in a while.

Install Node.js

Before you can work with Vue you must install Node.js. Node.js is a JavaScript runtime environment that enables you to run JavaScript outside of your browser.

Just like Python and pip, Node.js provides a package manager. The Node Package Manager is named npm and you’ll use it in a moment to install Vue and some additional plugins.

To verify that Node.js and npm are available on your operating system, open a new terminal window and check their versions with the commands below:

Once you’ve verified that Node.js and npm are present, keep your terminal window open and navigate to your project directory:

The dvg/ directory is the starting point to initialize your Vue project.

Create the Vue Project

Much like Django’s startproject command, the create-vue tool helps you to build your project structure. Even more so, it asks you a bunch of questions to fine-tune your setup. If you want to follow along closely with this tutorial, then you should answer the questions like this:

The most important selections are naming your project “front_end” and adding Vue Router to the project.

To start the scaffolding process, run this command in your project directory:

After you’ve initated the process, you need to install the create-vue tool. Then, you need to answer several questions about the tooling of your Vue project. Again, make sure to name your project “front_end” and to add Vue Router to the project

The scaffolding process creates a front_end/ directory alongside your existing back_end/ directory, installs a number of JavaScript dependencies, and creates some skeleton files for the application:

front_end/
│
├── public/
│   └── ...
│
├── src/
│   │
│   ├── assets/
│   │   └── ...
│   │
│   ├── components/
│   │   └── ...
│   │
│   ├── router/
│   │   └── index.js
│   │
│   ├── views/
│   │   ├── AboutView.vue
│   │   └── HomeView.vue
│   │
│   ├── App.vue
│   └── main.js
│
├── README.md
├── index.html
├── jsconfig.json
├── package.json
└── vite.config.js

In addition to the files and folders shown above, you can also find a .vscode/ folder with recommended Visual Studio Code extensions and a .gitignore file that contains some default files you may want to ignore when working with Git.

Step 5 Summary

The front_end/ folder will be the root folder for the front end part of your project. You’ll run all upcoming commands from within this directory or its subfolders.

Move into the front_end/ folder and install all dependencies for your Vue project:

Make sure to add the --include dev flag to the npm install command to also install development dependencies like Vite.
With your project structure in place and all dependencies installed, you can run the Vite development server:

By default, your Vite server runs on port 5173. If this port is already in use, then Vite looks for another port. In that case, you’ll get a message in the terminal output.

You now have your Django application running at http://localhost:8000 and your Vue application running at http://localhost:5173. Now visit http://localhost:5173 in your browser:

You should see the Vue splash page, which indicates that you’ve installed everything successfully. If you see the splash page, you’re ready to start creating some of your own views and components.

Remove Existing Views

The create-vue tool is helpful to create your project structure. It creates files that can give you a good starting point on how to create your own Vue project files. So you don’t confuse your new files with the existing ones, it’s a good idea to clean up the project first.

There are two default views in the src/views/ directory that you need to remove:

1. HomeView.vue
2. AboutView.vue

Once you’ve deleted both files, you can stay in the same directory. The src/views/ directory is where you’ll create your views next.

Add Your Views

Your blog will have four views. Start with AuthorView.vue. This file is a Vue Single-File Component (SFC). SFCs contain HTML, JavaScript, and CSS blocks that bundle view, logic, and styling:

You can order the blocks anyway you like. But commonly you start with the <script> block. Here, you import any components that your SFC uses. In this case, the PostList component that you’ll create later.

The HTML must be placed inside a <template> block. For the components that you want to render you use custom HTML tags.

The CSS inside <style> is scoped. That means any styling you define in a SFC will only affect elements in the same file. Even child components don’t inherit this styling by default.

Next, create the AllPostsView.vue file with the code below:

Just like in AuthorView.vue you import PostList and render it in your HTML block. For now, AllPostsView looks similar to AuthorView, but you’ll adjust it later. To differentiate between views, you can change the headline and the headline’s color.

The third view is very similar again. Create PostsByTagView.vue inside the views/ folder and add the code below:

The last view you create is named PostView.vue. As the name suggests, this view will contain a single post of your blog:

In this view, you import an AuthorLink component. Just like the components that you imported in the former views, this component doesn’t exist yet. Before you create this, it’s time for another small cleanup.

Remove Existing Components

If you navigate to the components/ folder inside your src/ folder, then you can see that there are some files and an icons/ folder present already. Go on and delete the icons/ folder with its contents, and these three files:

1. WelcomeItem.vue
2. TheWelcome.vue
3. HelloWorld.vue

With a clean components/ folder, you can go on and create the components you referenced in your views.

Create Your Components

In this section, you’ll create the two components that you need for your blog. Again, you’ll keep them basic for now and won’t add any special content to them just yet.

Start with the component that’ll display an author’s link later. To do so, create a file named AuthorLink.vue in the components/ folder:

For now, that’s all the code you need to verify that the component renders correctly. You’ll add more content to it later.

Next, create PostList.vue in the same folder:

In PostList, you also render AuthorLink. You can import components as building blocks wherever you need them.

Set Up Routes

If you’d visit http://localhost:5173 right now, you’d still get an error. At the moment, the Vite server still looks for the default views that Vue created during the scaffolding process.

To fix the wrong routes and set up routes to your new views, open the existing index.js file in src/router/. Replace the content with the code below:

Now that your routes point to existing views, all the errors in your Vite server output should be gone. To conveniently jump between the different pages, add the route links to the App.vue file.

The App.vue file is the base component that your Vue app looks for. You can find it prominently placed directly in the src/ folder.

Open App.vue and replace the existing content with the content below:

You can reference Vue routes either by their path or their name. Later, you’ll remove the links here again because you’ll link to the routes from within your content. But for now, adding routes to the navigation is helpful to see if everything works.

Step 6 Summary

In this step, you cleaned up parts of your Vue project folders and created your own views and components. With all routes in place, you can open http://localhost:5173 in your browser and check out how your components render:

Perfect! Now that you’ve verified that you can access your views in the browser and that your components render correctly, you can move on and add more useful content to your components.

Link to the Author

The AuthorLink component should accept an author prop whose structure corresponds to the data about authors in your GraphQL API. Props are custom attributes that you can use in your component. The component should show the author’s first and last name if provided, or the author’s username otherwise.

Replace the existing content in the AuthorLink.vue file with the content below:

This component won’t work with GraphQL directly but with a passed in author object that other components provide. To be able to work with the author object, you define it as a prop in line 5 with defineProps().

The defineProps() function returns an object that you can store in a variable. That’s helpful when you want to access properties from within the <script> block like you do in lines 6 and 7, for example.

In lines 18 to 22, you create a link to the author’s page. To let Vue do the linking, you work with the RouterLink component. The displayed name in line 21 is the value of a computed property.

Computed properties help you implement complex data into your <template> block. The displayName variable you define in line 8 will be either the first and last name or the username of an author.

Prep the Blog Posts List

You can define the props of a component with a list of strings. However, you can also finegrain the information of the provided props using object syntax. For the PostList component, you’ll use object syntax to declare more complex props.

The PostList component accepts a posts prop, whose structure corresponds to the data about posts in your GraphQL API. The component also accepts a Boolean showAuthor prop. In the end, the component should display the following features:

• The title of the post
• A link to the post’s page
• A link to the author of the post using AuthorLink if showAuthor is true

Open PostList.vue in the src/components/ directory and update the file with the highlighted content below:

Giving more context to your props like you do in line 5 can help you and other developers to understand the intention of the provided props better.

In this component, you’ll receive a list of posts. You loop through them in line 20. When you use the v-for built-in Vue directive on an element, the element and its contents are rendered for every step of the loop.

In each step of the loop, you show the title as a link using RouterLink in lines 21 to 23. If the showAuthor prop is set to true, then you also display the AuthorLink component in line 24.

Render All Blog Posts

Now that you’ve got PostList sorted, you can move on to update AllPostsView. This component should display a list of all the posts on the blog.

Open AllPosts.vue component in the src/views/ directory and update it with the content below:

In line 4, you prepare the GraphQL API call, which you’ll implement later. You deconstruct the returned object into result, loading, and error using JavaScript’s destructuring assignment.

While you’re fetching the data from the API, loading will be true. Once you receive the data, it’ll be the value of result. If something goes wrong, then error will contain a message property with more information.

For now, you only define an error message in line 5. That means you won’t show a Loading indicator or the PostList component because both loading and result are undefined at the moment. Still, your <template> block is perfectly prepared to work with the data you’ll get in result.allPosts when you implement the GraphQL API call later.

Show Posts for a Given Tag

Next, update the PostsByTagView.vue file in the src/views/ directory to match the code below:

The pattern in lines 7 to 9 is the same as in AllPostsView. For now, you’ll work with a placeholder error message and implement the GraphQL API call later.

Additionally, you grab the current tag name of the dynamically matched route in line 6. The tag variable definition will become handy later on when you filter the posts for this specific tag.

To make your life easier, you define the custom variable for your template in line 15. By using a bound attribute to set the tagPosts variable, you’ll save yourself a bit of typing later on. That way, you can use tagPosts in your template instead of result.postsByTag, which the API will return.

Show Information About an Author

The AuthorView component acts as an author’s profile page. It should display the following information:

• A heading with the author’s username
• A subheading with the author’s full name, if provided
• A link to the author’s website, if provided
• The author’s biography, if provided
• The list of posts by the author, with showAuthor set to false

Update the AuthorView.vue file in src/views/ with the content below:

Later, when you get the data from the GraphQL API, you’ll render the information you outline in lines 13 to 30:

• Line 13 shows the author’s username as a headline.
• Line 15 displays the author’s full name if their first name and last name are set.
• Line 17 checks if there is a biography present. If so, then you render the biography in line 18 and add an optional link to the website in line 21.
• Lines 25 to 29 render the PostList component if the author has posted.
• Line 30 shows a fallback message if there are no blog posts.

With AuthorView updated, there are two components left. First, you’ll tackle PostView and, after that, the App.vue component.

Display a Single Blog Post

Just like the Post data model in your Django app, the PostView component is a bit more complex because it has the responsibility of displaying all the post’s information. The component should display the following information about the post:

• Title and subtitle, as a heading
• Author, as a link using AuthorLink
• Publication date
• Meta description
• Content body
• List of associated tags, as links

Update the PostView.vue file in the src/view/ directory with the highlighted content below:

When the post data is present, it’ll be saved in the result variable you define in line 6 and display the content inside the <template> block in lines 14 to 31.

In line 19, you pass the .publishDate of a post into displayableDate(), which you define in line 5. The publish date is saved as a datetime object in your database and won’t look good without some treatment. With the help of dateFormatter in line 4, you return a well-readable formatted date in the template.

In lines 23 to 27, you render the tags a blog post contains as dynamic links. Each link will point to the tag-specifc URL. So far, your routes don’t recognize additional params like the one you provide in line 24. So that’s a good reminder to tackle the App component and the routes next.

Adjust the Routes for the App

In the previous step, you added some links to your blog’s navigation to see if the views and components render. While updating the components in this step, you may have noticed that most of your links require additional parameters.

The only view that doesn’t require parameters is your AllPostsView. This is the only link you want to keep in your navigation. Open App.vue and remove the other links:

In line 11, you remove the RouterLink components for author, post, and tag. In the future, you may add an About page or other menu items into <nav>. For now, keep the menu basic by just showing Posts.

In your index.js file you’re still referencing routes without any parameters. Update router/index.js with the route parameters you added in your components:

In lines 16, 21, and 26, you adjust the path values to accept the route params you used when rendering the RouterLink components. Make sure not to forget the colon (:) in front of the param substring.

Step 7 Summary

If you haven’t used Vue much before, this step might have been a lot to digest. You’ve reached an important milestone, though. You have a working Vue application, complete with dynamic routes and templates that are ready to work with the content the GraphQL API will provide soon.

You can confirm your application is working by starting the Vite server and visiting http://localhost:5173:

You should see the Posts link and the Recent Posts heading. If you do, then you’re ready to take on the final step, where you’ll use Apollo to query your GraphQL API to bring the front end and back end together.

Install Vue Apollo

To conveniently work with Apollo in your Vue project, you need the Vue Apollo client and the apollo-composable package. Additionally, you’ll install GraphQL.js and graphql-tag to help you write the GraphQL API queries.

Open a terminal window in the front_end/ folder and install the packages with this command:

With all packages installed, you need to make a few adjustments before you can work with the GraphQL queries in your components.

Configure Vue Apollo

Vue Apollo is mostly configured out of the box, but you’ll need to tell it the right endpoint to query. Also, you want the Apollo Client to do some caching. Open main.js in the src/ folder and add your Apollo Client configuration to the file:

With these lines of code, you’re telling the Apollo Client where to find the GraphQL API. Also, you set the cache to InMemoryCache(). This allows you to retrieve data without redundant network requests if the data hasn’t changed.

Next, you need to initiate your Vue app with the Apollo Client using the Apollo Composable package. Stay in main.js and update the highlighted lines:

The provide() function you import in line 3 allows a component to provide data or methods to all its descendant components. This is particularly useful for deeply nested components or when you want to share common functionality across many components. The perfect example of this mechanism is the DefaultApolloClient you import in line 11. Passing DefaultApolloClient to provide() in line 26 makes the Apollo client available in all your components.

In line 3, you also import h(). Vue uses the h() render function to create Virtual DOM elements. The Virtual DOM is a lightweight copy of the Document Object Model (DOM). In line 29, you tell Vue to use the h() function to create a Virtual DOM representation of the App component and mount it as the root of your application.

Step 8 Summary

In this step, you installed additional plugins such as Vue Apollo and you configured the Apollo Client to be able to work with your back end.

When you check out your front end in the browser at http://localhost:5173, there are no changes on the surface. But that also means there are no errors and you configured the Apollo Client successfully.

Your Vue application is now ready to work with the GraphQL API. It’s time to get the back end into the picture again!

AllPostsView Query

The query for AllPostsView should only return the set of information that you render in your template. That means you only need your post’s title, the slug, and information about the author:

In line 3, you’re importing useQuery(), which lets you execute a query and reactively track its result. The gql that you import in line 4 helps you to parse your GraphQL query string into a query document that useQuery() can understand and work with.

You define the GraphQL query in lines 7 to 19 within the gql template literal. The content is the same string that you’d use on the GraphiQL platform. Here, you request only the specific set of data that you need in your template.

When you call useQuery() with your GraphQL query, it returns an object containing three properties:

1. result, which will be populated with the result of your query once it has successfully completed
2. loading, which is true while the query is in progress
3. error, which will contain details if there is an issue with the API request

These three properties enable you to control when you display specific information to the user. You already prepared your template to work with the properties, so you can keep the content in <template> as it is and move on to the next component.

PostView Query

The query for an individual post must accept the slug of the desired post. It should return all the necessary pieces of information to display the post information and content. Consequently, the code to make the query work is a bit more complex.

Update your PostView component with the highlighted code below:

This query pulls in most of the data about the post and its associated author and tags. This time, you’ll need to do a bit of extra work.

In lines 9 and 10, you define route and grab the slug from your route’s parameters. Then, you use the slug for your query in line 14.

AuthorView Query

In the query for PostView, you fetched the single post’s data and some nested data about the author. In the AuthorView query, you’ll need to fetch the author data and the list of all the posts by the author.

The author query accepts the username of the desired author and should return all the necessary pieces of information to display the author and their list of posts. It should look like the following:

This query uses postSet, which might look familiar if you’ve done some Django data modeling before. The name “post set” comes from the reverse relationship Django creates for a ForeignKey field. In this case, the post has a foreign key relationship to its author, which has a reverse relationship with the post called post_set. Graphene-Django has automatically exposed this as postSet in the GraphQL API.

PostsByTagView Query

The query for PostsByTagView is pretty similar to query in AllPostsView. The important difference is that the query in PostsByTagView requires the desired tag and returns the list of matching posts.

Open PostsByTagView.vue and adjust the file with the highlighted code below:

You might notice that some pieces of each query look quite similar to one another. Although it won’t be covered in this tutorial, you can use GraphQL fragments to reduce duplication in your query code.

Step 9 Summary

Now that each component is fetching the data it needs to display, you’ve arrived at a functioning blog. Run the Django development server and the Vue development server. Visit http://localhost:5173 and browse through your blog:

Congratulations! You started by creating a Django blog back end to administer, persist, and serve the data for a blog. Then you created a Vue front end to consume and display that data. You made the two communicate with GraphQL using Graphene and Apollo. Well done!