December 2019 Summaries

This detailed tutorial guides users through the process of creating a blog using Strapi as the backend, Angular for the frontend, and Apollo for querying the Strapi API with GraphQL. It includes step-by-step instructions for setting up a Strapi project, configuring Angular with UIkit for styling, and using Apollo to facilitate GraphQL queries. The tutorial covers creating and managing content types in Strapi, setting up Angular components to display articles and categories, and routing within the Angular application. It emphasizes modular development, encouraging users to adapt the project according to their needs and contribute to the Strapi community. The tutorial also acknowledges its reliance on Strapi v3 and offers guidance for users to contribute feedback or updates to the community.

The provided text is a comprehensive tutorial on creating a plugin for Strapi, a popular headless content management system (CMS), authored by a Strapi community member, Pouya Miralayi. It begins with instructions on setting up a new Strapi project using command line tools and continues with detailed steps to develop an import plugin, which allows users to upload data in CSV or RSS formats into Strapi's content types. The guide also covers the integration of React components and styled-components for building the plugin's user interface, including an upload form and an "Analyze" button to process the uploaded files. The tutorial explains how to set up options for different import sources, such as file uploads and external URLs, and details the process of sending requests to Strapi's backend for data analysis. Additionally, it discusses the use of Strapi's content type builder to manage where the imported data will be stored and provides insights into leveraging "Strapi Helper Plugin" UI components for enhanced user interaction. The tutorial is part of a series aimed at empowering users to create custom plugins for Strapi, emphasizing the community-driven nature of the platform.

Strapi, an open-source composable Content Management System (CMS) based on Node.js, facilitates the rapid development of RESTful and GraphQL APIs and offers a managed platform called Strapi Cloud to enhance content delivery without infrastructure concerns. This tutorial details building a blog website using Strapi for the backend and Next.js for the frontend, covering steps such as setting up the project, creating and seeding a Strapi app, configuring API tokens, and implementing internationalization. It emphasizes using Strapi's flexible API to fetch and display data in a blog format, including pagination and category-specific views, while also integrating middleware for enhanced data handling. The guide highlights Strapi's commitment to open-source innovation and offers Strapi Cloud as an option for developers who prefer focusing on development over infrastructure management, while also maintaining self-hosting options to cater to different project needs.

The tutorial covers creating a new plugin for Strapi, a headless CMS, to manage import history. It involves setting up a new route, creating a container component, and defining a custom table using Buffet.js. The table displays a list of imported content with options to delete or undo the imports. The tutorial also demonstrates how to fetch data from Strapi using the `request` function and handle errors. Additionally, it shows how to use Redux to manage state changes in the plugin and integrate testing into the development process.

The tutorial guides users through creating a custom plugin for Strapi, focusing on building a system to analyze, import, and manage content data from various sources such as CSV files and RSS feeds. It begins with setting up Strapi and creating utility functions to validate and parse data from URLs and different content types, like XML and CSV, using parsers such as rss-parser and csv-parser. The guide elaborates on mapping data fields to Strapi's content types, allowing users to relate imported data fields with target content type fields. It also covers implementing an endpoint to analyze and import data, handling media files associated with the content, and providing an interface for users to manage field mappings. The tutorial culminates with the development of a History page to track user-initiated imports, allowing for actions like undoing imports and deleting import configurations. Additionally, it emphasizes the importance of creating controllers for better consistency and managing content types efficiently.

The tutorial outlines the process of creating custom plugins in Strapi, specifically focusing on implementing new data import methods beyond the existing file upload option. It introduces two new components, ExternalUrlForm and RawInputForm, designed to facilitate data import via external URLs and raw text input, respectively. Each component is equipped with functions to handle state updates and data analysis requests. The tutorial guides users through setting up these components, integrating them into the main application, and modifying the HomePage index.js file to accommodate the new import options. This allows users to choose between uploading files, inputting URLs, or pasting raw data for analysis. The tutorial is part of a larger series on plugin creation and acknowledges that some content might be outdated due to newer Strapi versions, inviting users to report discrepancies.

The author of this article shares their vision for Strapi, an open-source headless CMS, after introducing several changes to its interface and core architecture. The project was initially focused on providing a framework for developers to build APIs quickly, but the authors soon realized that they needed to redefine their target audience and create a more user-friendly experience for both front-end developers and content editors. The author explains how these design choices were made with high confidence, despite being complex, and how they aim to improve consistency in the interface and provide better support for non-technical users. The article also touches on the challenges of developing a developer tool and the importance of separating technical aspects from visual interfaces.