Why Start a Blog?

The short answer is: you don't need one. But I wanted a place to share my knowledge and document what I'm learning in this beautiful, ever-evolving world of technology. Thanks to this constant renewal, there's always an opportunity to learn something new, and I believe sharing that journey can benefit both myself and the developer community.

The Motivation Behind Security Log

As a developer, I found myself constantly learning new concepts, debugging interesting problems, and discovering solutions. However, like many developers, I wasn't documenting these experiences effectively.

Documentation isn't just about helping others—it's about helping your future self.

• Knowledge retention: Writing about concepts forces you to understand them deeply
• Community contribution: Sharing solutions helps other developers facing similar challenges

Technical Stack: Building with Simplicity in Mind

When it comes to building this blog, I deliberately chose simplicity over complexity. Here's my reasoning and the technical decisions behind it.

Frontend: Next.js with Minimalist Design

I started with a Vercel template for the frontend honestly, it's more than sufficient for what I'm building here. The philosophy behind the design is:

Design Principles

• Minimalist aesthetic: No flashy animations or complex layouts
• Content-first approach: The focus should be on the writing, not the interface
• Performance optimization: Fast loading times and responsive design

Technical Implementation

// Example: Simple, semantic HTML structure  
<article>  
  <header>  
    <h1>{post.title}</h1>  
    <time dateTime={post.publishedAt}>  
      {formatDate(post.publishedAt)}  
    </time>  
  </header>  
  <div>{post.content}</div>  
</article>  

Backend: Exploring Appwrite as a Service

For the backend, I'm experimenting with Appwrite because it seemed like an interesting tool to explore. More importantly, I needed a free backend hosting solution, and Appwrite delivers exactly that.

Implementation Example

// Simple post creation with Appwrite  
const createPost = async (title, content, tags) => {  
  try {  
    const response = await databases.createDocument(  
      DATABASE_ID,  
      POSTS_COLLECTION_ID,  
      ID.unique(),  
      {  
        title,  
        content,  
        tags,  
        publishedAt: new Date().toISOString(),  
        status: 'published'  
      }  
    );  
    return response;  
  } catch (error) {  
    console.error('Error creating post:', error);  
    throw error;  
  }  
};  

Deployment Strategy: GitHub Pages + Appwrite

The combination I chose proves to be quite optimal: GitHub Pages for hosting the frontend connected to Appwrite for the backend gives you a blueprint for hosting whatever you want with minimal effort.

Future Roadmap

As Security Log evolves, here are some planned improvements:

Technical Enhancements

• Search functionality: Full-text search across all posts
• Dark mode: System preference-aware theme switching

Content Strategy

• Books reviews: All technical books I need to read and make a review here.
• Project breakdowns: Detailed analysis of personal projects.
• Code reviews: Public reviews of interesting open-source projects.

Conclusion: Building in Public

Starting this blog represents more than just a technical project—it's a commitment to building in public and contributing to the developer community. By sharing both successes and failures, we create a more transparent and collaborative environment.

Tags

blogging web-development appwrite github-pages developer-experience technical-writing