The TailwindCSS config (tailwind.config.ts) extends the default theme with some custom colors (see theme.extend.colors) which are not adequately named and not used as extensively as you might expect. The project should make better use of these colors so changes apply more widely and cohesively.
Additionally, there are other config settings I would like to explore to see if they really ought to be in the config or if they can be reproduced easily in component files.
Furthermore, I would like to remove the tailwind-bootstrap-grid plugin and use TailwindCSS grid/flex layout classes instead.
We currently filter out any content items that are marked as draft: true. We can conditionally show these in dev mode:
// Example: Filter out content entries with `draft: true` only when building for productionimport{getCollection}from'astro:content';constblogEntries=awaitgetCollection('blog',({ data })=>{returnimport.meta.env.PROD ? data.draft!==true : true;});
Because the Search page is one large React component, it doesn't use any of our custom Astro components, and so document structure and styles must be duplicated.
A lot of structure/style changes have been made to other areas of the project, and they now need to be replicated to the Search component.