From e7f51114064b52b42b8344cbd45b3a9170dbd5e1 Mon Sep 17 00:00:00 2001 From: ndamulelo Date: Tue, 16 Jan 2024 18:28:05 +0200 Subject: [PATCH] Add hero image to blog front matter and update sync scripts --- package.json | 4 +- src/consts.ts | 4 +- ...e-Had-b217907f61984aec959d1cbb208f9442.mdx | 157 +++++++++++++ ...-City-586f6047a8d64cef8fd62b9e993b36fa.mdx | 1 + src/content/blog/first-post.md | 16 -- src/content/blog/markdown-style-guide.md | 214 ------------------ src/content/blog/second-post.md | 16 -- src/content/blog/third-post.md | 16 -- src/content/blog/using-mdx.mdx | 31 --- src/pages/blog/index.astro | 5 +- src/pages/index.astro | 35 +-- src/utils/downloadBlogs.ts | 1 + src/utils/notion_proxy.ts | 5 +- 13 files changed, 180 insertions(+), 325 deletions(-) create mode 100644 src/content/blog/Impressive-AWS-features-I-wish-Azure-Had-b217907f61984aec959d1cbb208f9442.mdx delete mode 100644 src/content/blog/first-post.md delete mode 100644 src/content/blog/markdown-style-guide.md delete mode 100644 src/content/blog/second-post.md delete mode 100644 src/content/blog/third-post.md delete mode 100644 src/content/blog/using-mdx.mdx diff --git a/package.json b/package.json index d90af24..f5f81cd 100644 --- a/package.json +++ b/package.json @@ -34,8 +34,8 @@ "build": "astro check && astro build", "preview": "astro preview", "astro": "astro", - "sync": "tsx --no-cache src/api/downloadBlogs.ts", - "syncDev": "tsx --no-cache --env-file .env src/api/downloadBlogs.ts" + "sync": "tsx --no-cache src/utils/downloadBlogs.ts", + "syncDev": "tsx --no-cache --env-file .env src/utils/downloadBlogs.ts" }, "dependencies": { "@astrojs/check": "^0.4.1", diff --git a/src/consts.ts b/src/consts.ts index b2cda32..aec4143 100644 --- a/src/consts.ts +++ b/src/consts.ts @@ -3,5 +3,5 @@ export const SITE_TITLE = 'Astro with Notion' export const SITE_DESCRIPTION = 'A rudimentary implementation of a CMS using Notion as the backend and Astro Content Collection API'; -export const UNSPLASH_RANDOM_IMAGE_URL = 'https://source.unsplash.com/random/150x150'; -export const UNSPLASH_RANDOM_IMAGE_URL_LG = 'https://source.unsplash.com/random/1600x900'; \ No newline at end of file +export const UNSPLASH_RANDOM_IMAGE_URL = 'https://source.unsplash.com/random/720x360?space#<%+new Date().getTime()%>'; +export const UNSPLASH_RANDOM_IMAGE_URL_LG = 'https://source.unsplash.com/random/1600x900?space#<%+new Date().getTime()%>'; \ No newline at end of file diff --git a/src/content/blog/Impressive-AWS-features-I-wish-Azure-Had-b217907f61984aec959d1cbb208f9442.mdx b/src/content/blog/Impressive-AWS-features-I-wish-Azure-Had-b217907f61984aec959d1cbb208f9442.mdx new file mode 100644 index 0000000..426517e --- /dev/null +++ b/src/content/blog/Impressive-AWS-features-I-wish-Azure-Had-b217907f61984aec959d1cbb208f9442.mdx @@ -0,0 +1,157 @@ +--- +title: "Impressive AWS features (I wish Azure Had)" +pubDate: "2024-01-05T20:46:00.000Z" +slug: "Impressive-AWS-features-I-wish-Azure-Had-b217907f61984aec959d1cbb208f9442" +description: "Recently, while preparing for my AWS MLS-CO1 exam, I discovered some features that impressed me. As someone with an extensive Azure background, I was pleasantly surprised to find that there may be mor" +tags: aws,machine learning,azure,cloud,cloud certification +heroImage: "https://source.unsplash.com/random/720x360?space#<%+new Date().getTime()%>" +--- + + + +Recently, while preparing for my AWS MLS-CO1 exam, I discovered some features that impressed me. As someone with an extensive Azure background, I was pleasantly surprised to find that there may be more compelling reasons to make me lose my loyalty to Azure. + +In this blog, I’ll walk you through these AWS features that made me sit up and take notice. From intelligent policy generation based on activity logs to advanced AI and machine learning integrations, these are elements that, in my opinion, could give Azure a run for its money. Let's take a closer look and see what lessons Azure might learn from AWS’s playbook. + +# Generate IAM Policies Based on CloudTrail Logs + +When it comes to managing cloud resources, security is paramount. This is where AWS's ability to generate Identity and Access Management (IAM) policies based on CloudTrail logs stands out. It's a feature that goes beyond the traditional methods of policy management, offering a dynamic and intelligent approach. + + + +AWS’s Approach: A Closer Look +AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account. By integrating CloudTrail logs with IAM policy generation, AWS provides a more automated and data-driven approach to policy management. Essentially, it analyzes user activities and API usage to recommend appropriate IAM policies, making the process not just simpler but more secure. This feature can be particularly useful for organizations looking to streamline their security protocols without compromising on efficiency. + +Reference for Further Reading: + +- AWS CloudTrail Overview: AWS CloudTrail Documentation + +- IAM Policy Generation using CloudTrail: AWS IAM Policy Generation Tool + +Azure’s Current Capabilities +Comparatively, Azure offers robust policy and role-based access control mechanisms. Azure Policy helps enforce organizational standards and assess compliance at scale. However, the policy generation process is largely manual and doesn't dynamically adapt based on activity logs as AWS’s solution does. Azure Activity Log provides insights into subscription-level events but doesn’t directly integrate with policy generation in the same way. + +Potential Benefits for Azure +Adopting a similar feature in Azure could significantly enhance the cloud experience for Azure users. Automating policy generation based on user activities and API usage, like AWS, could lead to more tailored and secure access controls. This would not only bolster security but also reduce the administrative burden and potential human errors in policy configurations. + +Reference for Azure Users: + +- Azure Policy Documentation: Azure Policy + +- Understanding Azure Activity Log: Azure Activity Log + +# Intelligent Blob Access Tiers + +Did you know that AWS has a fascinating feature called Intelligent Blob Tiers? It's a highly advanced system that optimizes your data storage efficiency like never before! You won't have to worry about manually moving data around as this feature automatically shifts your data to the most cost-effective access tier based on how frequently it's being accessed. + +AWS’s Intelligent Tiering +AWS S3 Intelligent-Tiering is a storage class that delivers automatic cost savings by moving data to the most economical tier, based on usage patterns. It's designed for data with unknown or changing access patterns, making it ideal for long-term storage without the need to classify data based on its usage. The feature eliminates the need for manual intervention, ensuring that data is stored in the most cost-effective manner possible. + +Reference for Further Reading: + +- AWS S3 Intelligent-Tiering: AWS S3 Documentation + +Azure Blob Storage: Current Capabilities +In contrast, Azure Blob Storage offers several storage tiers (Hot, Cool, and Archive), but the transition between these tiers is mostly manual or based on fixed policies. While Azure Blob Storage is highly effective and reliable, the lack of an automated tiering system like AWS’s can lead to less optimized cost and efficiency, especially for data with unpredictable access patterns. + +Potential Benefits for Azure +Implementing an intelligent tiering system similar to AWS could greatly enhance Azure Blob Storage. It would provide Azure users with automatic cost optimization and efficiency, particularly for data that doesn’t have a predictable access pattern. This feature would allow Azure users to save on costs without the complexity of manually shifting data across different storage tiers. + +Reference for Azure Users: + +- Azure Blob Storage Tiers: Azure Blob Storage Documentation + +With AWS's intelligent tiering system setting a new benchmark in storage efficiency, it's an area where Azure could potentially innovate to provide similar or even better solutions to its users. + + + +# ML-Driven Cost Anomaly Detection + +A critical aspect of cloud service management is cost control and optimization. AWS has taken a significant leap in this area with its ML-driven Cost Anomaly Detection feature, a tool that combines the power of machine learning with detailed cloud usage insights to identify unusual spending patterns. + +AWS’s Innovative Cost Management +AWS Cost Anomaly Detection harnesses machine learning to automatically monitor and analyze AWS spending. This feature flags unusual patterns and potential issues, providing detailed alerts and root cause analysis. It's a proactive approach to cost management, allowing organizations to quickly identify and address unexpected charges, thereby avoiding budget overruns and optimizing cloud spending. + +Reference for Further Reading: + +- AWS Cost Anomaly Detection: AWS Cost Management + +Azure's Current Cost Management Tools +Azure also provides comprehensive cost management tools, including Azure Cost Management and Billing. These tools offer budgeting, cost analysis, and alerts. However, they primarily rely on threshold-based alerts and lack the advanced machine learning capabilities found in AWS's solution. This means Azure users may not be getting the same level of predictive insights and automated anomaly detection that AWS offers. + +Potential Benefits for Azure +Incorporating ML-driven cost anomaly detection into Azure could significantly enhance its cost management capabilities. By leveraging machine learning, Azure could provide more nuanced and predictive insights into spending patterns, empowering users to manage their cloud expenses more efficiently. This would be especially beneficial for large-scale enterprises where cloud spending is substantial and complex. + +Reference for Azure Users: + +- Azure Cost Management and Billing: Azure Cost Management Documentation + +Adopting a machine learning-driven approach, similar to AWS, could give Azure a competitive edge in helping users better understand and manage their cloud expenditures in real-time. + + + +# A Better, More Extensible Annotation Solution + +One of the areas where AWS excels is in providing data labelling solutions. It offers a range of options, from manual to semi-automated and fully automated solutions, to accelerate data annotation for supervised training. Additionally, there is a seamless integration with external labelling workforces if your private labelling team is not sufficient. + + + +AWS’s Advanced Labeling Solutions +AWS offers robust labeling features, especially notable in services like AWS SageMaker. SageMaker Ground Truth helps users build highly accurate training datasets for machine learning quickly. It supports a wide range of labeling tasks, including image, text, and 3D point cloud labeling. This service is not just about labeling; it's about doing so efficiently and at scale, with features like automated data labeling powered by machine learning and easy integration with other AWS services. + +Reference for Further Reading: + +- AWS SageMaker Ground Truth: AWS SageMaker Ground Truth Documentation + +- AWS A2I + +- AWS Mechanical Turk + +Azure’s Labeling Capabilities +While Azure offers several tools for data classification and management, its capabilities, particularly in terms of labeling solutions for machine learning, are not as extensive as AWS's. Azure Machine Learning does provide data labeling services, but these are generally more basic and less integrated with machine learning processes compared to AWS's offering. + +Potential Benefits for Azure +By enhancing its data labeling solutions, Azure could significantly improve the efficiency and accuracy of machine learning projects. A more comprehensive labeling solution would streamline the process of preparing large datasets, potentially offering features like AWS's automated data labeling and extensive integration capabilities. This would not only save time but also improve the overall quality of machine learning models developed on Azure. + +Reference for Azure Users: + +- Azure Machine Learning Data Labeling: Azure Machine Learning Documentation + +Improving data labeling solutions can be a game-changer for Azure, especially for users heavily engaged in machine learning and AI projects. A more sophisticated approach, akin to AWS's, could enhance user experience and outcomes in data-driven projects. + +# Augmented AI Features + +Augmented AI is a burgeoning field in cloud computing, blending traditional AI capabilities with human intelligence to enhance machine learning models. These features allow developers to easily verify Machine Learning predictions by building quality control workflows to allow humans to assist the models where the prediction confidence is low. + +AWS’s Approach to Augmented AI +AWS offers a suite of Augmented AI services, particularly within Amazon SageMaker. These services allow developers to build, train, and deploy machine learning models more effectively by incorporating human judgment into the workflow. For instance, Amazon SageMaker A2I (Augmented AI) integrates human reviews into machine learning pipelines, ensuring that AI predictions meet the quality standards and are continually improved based on human feedback. + +Reference for Further Reading: + +- Amazon SageMaker A2I: Amazon SageMaker Augmented AI Documentation + + + +Azure’s Current AI Offerings +Azure provides a range of AI and machine learning services, including Azure Machine Learning and various cognitive services. However, the platform’s integration of augmented AI isn’t as pronounced as AWS's. While Azure does offer tools for building and training machine learning models, the emphasis on blending these capabilities with human judgment is less evident. + +Potential Benefits for Azure +Incorporating more augmented AI features into Azure's offerings could greatly enhance the platform’s capabilities in AI and machine learning. By integrating human insight into AI workflows, Azure could help businesses achieve more accurate and reliable AI outcomes, especially in scenarios where human judgment is crucial. It could also aid in continuously refining AI models based on real-world feedback and applications. + +Reference for Azure Users: + +- Azure Machine Learning: Azure Machine Learning Documentation + +By embracing an approach similar to AWS's Augmented AI, Azure could significantly bolster its AI offerings, aligning more closely with the evolving needs of businesses and developers in the AI space. + + + +
+ +# Closing thoughts + +As someone deeply involved in Azure's ecosystem, recognizing the strengths of a rival platform like AWS has been both humbling and enlightening. It highlights the importance of cross-platform learning and the continuous pursuit of improvement in technology. With its recent partnership with OpenAI, Azure’s future in Machine Learning and Data Management looks bright, and with potential adoption or adaptation of these AWS features, it could shine even brighter. + + + +How do you think Azure could integrate or improve upon these ideas? Let me know in the comments below. \ No newline at end of file diff --git a/src/content/blog/Understanding-AWS-IAM-using-a-football-analogy-Manchester-City-586f6047a8d64cef8fd62b9e993b36fa.mdx b/src/content/blog/Understanding-AWS-IAM-using-a-football-analogy-Manchester-City-586f6047a8d64cef8fd62b9e993b36fa.mdx index 155d9b8..3126917 100644 --- a/src/content/blog/Understanding-AWS-IAM-using-a-football-analogy-Manchester-City-586f6047a8d64cef8fd62b9e993b36fa.mdx +++ b/src/content/blog/Understanding-AWS-IAM-using-a-football-analogy-Manchester-City-586f6047a8d64cef8fd62b9e993b36fa.mdx @@ -4,6 +4,7 @@ pubDate: "2023-11-13T07:17:00.000Z" slug: "Understanding-AWS-IAM-using-a-football-analogy-Manchester-City-586f6047a8d64cef8fd62b9e993b36fa" description: "When it comes to understanding AWS Identity and Access Management (IAM), it can be as complex as a tactical football match. To simplify this, let's use Manchester City, one of the premier football c" tags: cloud,aws,system design,cyber security,identity and access management +heroImage: "https://source.unsplash.com/random/720x360?space#<%+new Date().getTime()%>" --- diff --git a/src/content/blog/first-post.md b/src/content/blog/first-post.md deleted file mode 100644 index 3066715..0000000 --- a/src/content/blog/first-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'First post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 08 2022' -heroImage: '/blog-placeholder-3.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/src/content/blog/markdown-style-guide.md b/src/content/blog/markdown-style-guide.md deleted file mode 100644 index 877ec2f..0000000 --- a/src/content/blog/markdown-style-guide.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -title: 'Markdown Style Guide' -description: 'Here is a sample of some basic Markdown syntax that can be used when writing Markdown content in Astro.' -pubDate: 'Jul 01 2022' -heroImage: '/blog-placeholder-1.jpg' ---- - -Here is a sample of some basic Markdown syntax that can be used when writing Markdown content in Astro. - -## Headings - -The following HTML `

`—`

` elements represent six levels of section headings. `

` is the highest section level while `

` is the lowest. - -# H1 - -## H2 - -### H3 - -#### H4 - -##### H5 - -###### H6 - -## Paragraph - -Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat. - -Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat. - -## Images - -#### Syntax - -```markdown -![Alt text](./full/or/relative/path/of/image) -``` - -#### Output - -![blog placeholder](/blog-placeholder-about.jpg) - -## Blockquotes - -The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a `footer` or `cite` element, and optionally with in-line changes such as annotations and abbreviations. - -### Blockquote without attribution - -#### Syntax - -```markdown -> Tiam, ad mint andaepu dandae nostion secatur sequo quae. -> **Note** that you can use _Markdown syntax_ within a blockquote. -``` - -#### Output - -> Tiam, ad mint andaepu dandae nostion secatur sequo quae. -> **Note** that you can use _Markdown syntax_ within a blockquote. - -### Blockquote with attribution - -#### Syntax - -```markdown -> Don't communicate by sharing memory, share memory by communicating.
-> — Rob Pike[^1] -``` - -#### Output - -> Don't communicate by sharing memory, share memory by communicating.
-> — Rob Pike[^1] - -[^1]: The above quote is excerpted from Rob Pike's [talk](https://www.youtube.com/watch?v=PAAkCSZUG1c) during Gopherfest, November 18, 2015. - -## Tables - -#### Syntax - -```markdown -| Italics | Bold | Code | -| --------- | -------- | ------ | -| _italics_ | **bold** | `code` | -``` - -#### Output - -| Italics | Bold | Code | -| --------- | -------- | ------ | -| _italics_ | **bold** | `code` | - -## Code Blocks - -#### Syntax - -we can use 3 backticks ``` in new line and write snippet and close with 3 backticks on new line and to highlight language specific syntac, write one word of language name after first 3 backticks, for eg. html, javascript, css, markdown, typescript, txt, bash - -````markdown -```html - - - - - Example HTML5 Document - - -

Test

- - -``` -```` - -Output - -```html - - - - - Example HTML5 Document - - -

Test

- - -``` - -## List Types - -### Ordered List - -#### Syntax - -```markdown -1. First item -2. Second item -3. Third item -``` - -#### Output - -1. First item -2. Second item -3. Third item - -### Unordered List - -#### Syntax - -```markdown -- List item -- Another item -- And another item -``` - -#### Output - -- List item -- Another item -- And another item - -### Nested list - -#### Syntax - -```markdown -- Fruit - - Apple - - Orange - - Banana -- Dairy - - Milk - - Cheese -``` - -#### Output - -- Fruit - - Apple - - Orange - - Banana -- Dairy - - Milk - - Cheese - -## Other Elements — abbr, sub, sup, kbd, mark - -#### Syntax - -```markdown -GIF is a bitmap image format. - -H2O - -Xn + Yn = Zn - -Press CTRL+ALT+Delete to end the session. - -Most salamanders are nocturnal, and hunt for insects, worms, and other small creatures. -``` - -#### Output - -GIF is a bitmap image format. - -H2O - -Xn + Yn = Zn - -Press CTRL+ALT+Delete to end the session. - -Most salamanders are nocturnal, and hunt for insects, worms, and other small creatures. diff --git a/src/content/blog/second-post.md b/src/content/blog/second-post.md deleted file mode 100644 index 19a9105..0000000 --- a/src/content/blog/second-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Second post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 22 2022' -heroImage: '/blog-placeholder-4.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/src/content/blog/third-post.md b/src/content/blog/third-post.md deleted file mode 100644 index 463cd25..0000000 --- a/src/content/blog/third-post.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Third post' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 15 2022' -heroImage: '/blog-placeholder-2.jpg' ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae ultricies leo integer malesuada nunc vel risus commodo viverra. Adipiscing enim eu turpis egestas pretium. Euismod elementum nisi quis eleifend quam adipiscing. In hac habitasse platea dictumst vestibulum. Sagittis purus sit amet volutpat. Netus et malesuada fames ac turpis egestas. Eget magna fermentum iaculis eu non diam phasellus vestibulum lorem. Varius sit amet mattis vulputate enim. Habitasse platea dictumst quisque sagittis. Integer quis auctor elit sed vulputate mi. Dictumst quisque sagittis purus sit amet. - -Morbi tristique senectus et netus. Id semper risus in hendrerit gravida rutrum quisque non tellus. Habitasse platea dictumst quisque sagittis purus sit amet. Tellus molestie nunc non blandit massa. Cursus vitae congue mauris rhoncus. Accumsan tortor posuere ac ut. Fringilla urna porttitor rhoncus dolor. Elit ullamcorper dignissim cras tincidunt lobortis. In cursus turpis massa tincidunt dui ut ornare lectus. Integer feugiat scelerisque varius morbi enim nunc. Bibendum neque egestas congue quisque egestas diam. Cras ornare arcu dui vivamus arcu felis bibendum. Dignissim suspendisse in est ante in nibh mauris. Sed tempus urna et pharetra pharetra massa massa ultricies mi. - -Mollis nunc sed id semper risus in. Convallis a cras semper auctor neque. Diam sit amet nisl suscipit. Lacus viverra vitae congue eu consequat ac felis donec. Egestas integer eget aliquet nibh praesent tristique magna sit amet. Eget magna fermentum iaculis eu non diam. In vitae turpis massa sed elementum. Tristique et egestas quis ipsum suspendisse ultrices. Eget lorem dolor sed viverra ipsum. Vel turpis nunc eget lorem dolor sed viverra. Posuere ac ut consequat semper viverra nam. Laoreet suspendisse interdum consectetur libero id faucibus. Diam phasellus vestibulum lorem sed risus ultricies tristique. Rhoncus dolor purus non enim praesent elementum facilisis. Ultrices tincidunt arcu non sodales neque. Tempus egestas sed sed risus pretium quam vulputate. Viverra suspendisse potenti nullam ac tortor vitae purus faucibus ornare. Fringilla urna porttitor rhoncus dolor purus non. Amet dictum sit amet justo donec enim. - -Mattis ullamcorper velit sed ullamcorper morbi tincidunt. Tortor posuere ac ut consequat semper viverra. Tellus mauris a diam maecenas sed enim ut sem viverra. Venenatis urna cursus eget nunc scelerisque viverra mauris in. Arcu ac tortor dignissim convallis aenean et tortor at. Curabitur gravida arcu ac tortor dignissim convallis aenean et tortor. Egestas tellus rutrum tellus pellentesque eu. Fusce ut placerat orci nulla pellentesque dignissim enim sit amet. Ut enim blandit volutpat maecenas volutpat blandit aliquam etiam. Id donec ultrices tincidunt arcu. Id cursus metus aliquam eleifend mi. - -Tempus quam pellentesque nec nam aliquam sem. Risus at ultrices mi tempus imperdiet. Id porta nibh venenatis cras sed felis eget velit. Ipsum a arcu cursus vitae. Facilisis magna etiam tempor orci eu lobortis elementum. Tincidunt dui ut ornare lectus sit. Quisque non tellus orci ac. Blandit libero volutpat sed cras. Nec tincidunt praesent semper feugiat nibh sed pulvinar proin gravida. Egestas integer eget aliquet nibh praesent tristique magna. diff --git a/src/content/blog/using-mdx.mdx b/src/content/blog/using-mdx.mdx deleted file mode 100644 index d976693..0000000 --- a/src/content/blog/using-mdx.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: 'Using MDX' -description: 'Lorem ipsum dolor sit amet' -pubDate: 'Jul 02 2022' -heroImage: '/blog-placeholder-5.jpg' ---- - -This theme comes with the [@astrojs/mdx](https://docs.astro.build/en/guides/integrations-guide/mdx/) integration installed and configured in your `astro.config.mjs` config file. If you prefer not to use MDX, you can disable support by removing the integration from your config file. - -## Why MDX? - -MDX is a special flavor of Markdown that supports embedded JavaScript & JSX syntax. This unlocks the ability to [mix JavaScript and UI Components into your Markdown content](https://docs.astro.build/en/guides/markdown-content/#mdx-features) for things like interactive charts or alerts. - -If you have existing content authored in MDX, this integration will hopefully make migrating to Astro a breeze. - -## Example - -Here is how you import and use a UI component inside of MDX. -When you open this page in the browser, you should see the clickable button below. - -import HeaderLink from '../../components/HeaderLink.astro'; - - - Embedded component in MDX - - -## More Links - -- [MDX Syntax Documentation](https://mdxjs.com/docs/what-is-mdx) -- [Astro Usage Documentation](https://docs.astro.build/en/guides/markdown-content/#markdown-and-mdx-pages) -- **Note:** [Client Directives](https://docs.astro.build/en/reference/directives-reference/#client-directives) are still required to create interactive components. Otherwise, all components in your MDX will render as static HTML (no JavaScript) by default. diff --git a/src/pages/blog/index.astro b/src/pages/blog/index.astro index 59f20a5..d8fa45c 100644 --- a/src/pages/blog/index.astro +++ b/src/pages/blog/index.astro @@ -34,6 +34,7 @@ const posts = (await getCollection("blog")).sort((a, b) => a.data.pubDate.valueO } ul li:first-child { width: 100%; + margin-bottom: 1rem; text-align: center; } @@ -46,6 +47,7 @@ const posts = (await getCollection("blog")).sort((a, b) => a.data.pubDate.valueO ul li img { margin-bottom: 0.5rem; border-radius: 12px; + } ul li a { display: block; @@ -92,7 +94,7 @@ const posts = (await getCollection("blog")).sort((a, b) => a.data.pubDate.valueO posts.map((post) => (
  • - +

    {post.data.title}

    @@ -106,5 +108,4 @@ const posts = (await getCollection("blog")).sort((a, b) => a.data.pubDate.valueO