Sprint #1 - Daily Scrum #01

Product: CMS API
Sprint Summary

Daily Objectives

• Create a low-spec wireframe of the project

Notes

haha hey! Ok time to bust out this wireframe! I can probably reference strapi IO for this kinda stuff. But ok so let’s define our Users and what they’ll be doing in the admin interface:

• Project Owner
• Client

Let’s define our objects too and maybe some of their relationships:

• Admin Users
  • Creating Content Types/Collections
  • Has all the permissions of a Client User
  • Manage Clients
  • Manage Projects
  • Manage Roles
• Client Users
  • Can be part of multiple projects
  • Can only add/create entries for existing Content Types/Collections
  • Can potentially make a Content Type
• Projects
  • Belongs to a client(s)
• Content Type/Collections
  • ‘Content Types’ don’t need super specific formats since ‘Post’ entries in generally use different amounts of paragraph items and media mixed around, so make sure that’s a setting
• Content Entries
  • Entry of Content Type or part of a Collection
• Content Items
  • Header, paragraph, media, etc.

While I’m doing this lets try out wordpress:

• Media and file uploads all in one area
• Wordpress only allows for one content type which are ‘Posts’
• ‘Posts’ belong to Categories, which can also contain Subcategories
• ‘Posts’ can also contain multiple tags
• Now how do websites utilize wordpress as just a headless CMS?
  • Just realized wordpress is literally this project haha
  • “WordPress is a free and open-source content management system based on PHP & MySQL”
  • I will try and download wordpress once I get home and poke around it
  • Differences between WP and my project is more flexibility for developers and simplicity for users? Like I’m actually separating the services for the developers and the services for the users. Also will support different databases. I don’t know too much about the entire plugin ecosystem though.

fetch('http://localhost:8888/wp-cms/wp-json/wp/v2/posts')
.then(r => r.json())
.then(posts => {
	posts.map(post => {
		const postDiv = document.createELement('div');
		postDiv.innerHTML = post.title.rendered;
		postsContainer.appendChild(postDiv);
	}
}

Ok now what lol Define functions for each user:

We can separate ‘PAGES’ and ‘COLLECTIONS’ where pages are editable content on one off types of pages and collections are content types designed to exist in multiples. For example, pages can be the content on an about page, or images featured on the home page. Collections can be groups of blog posts, or series of portfolio images. Collections can still also be along the lines of ‘home-page-carousel’

If logged in as an admin, a set of admin pages (for users, content types, etc.) will appear in the sidebar under an ‘ADMIN’ section. In the project dropdown, an admin console option will appear if logged in as a superuser.

What appears in the ‘ADMIN CONSOLE’ project section? Creating a New Project, creating and adding new Users, editing Roles and permission for individual Users.

Objectives Completed

• Gained a more comprehensive description of what content will appear on what pages and a general overview of the navigation

• Made rough descriptions of user types and objects

• Poked around through wordpress to gain a better understanding of other existing popular CMS alternatives

Thoughts/Questions to Come Back To

• add a WYSIWYG editor to the backlog
• think about how to do SEO(search engine optimization) stuff
• not that the admin will make use of it, but just so we can support anything that the client projects might need for it
• allow client sites to preload a list of static resources?
• Is there a way to track network traffic? Despite that being a function for the actual client site rather than the CMS.

Plans for Tomorrow

• Finish making low-spec wireframe
• Find software for web-based wireframing and begin making a med-high wireframe draft